info
Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
[WebPayments] problem with country code in JWT price array
20 views
Skip to first unread message
Kumar McMillan
Sep 5, 2012, 1:06:51 PM9/5/12
to dev- >> dev-webapps@lists.mozilla.org, DAVID LOZANO LLANOS
Hello David (and anyone else following the WebPayments API).
When implementing a list of prices in all currencies for the JWT payment format -- https://wiki.mozilla.org/WebAPI/WebPayment#In-app_payment -- the Marketplace team ran into snag with the country code. Why is country code needed? Is this needed by BlueVia? Can we remove this and just specify a currency code and price? It is unclear to us how or why we would declare a country code. For example, EUR (Euro) would map to many many countries, not a single one.
Making this change would also require changing request.defaultPrice to point to a currency code instead of a country code.
Kumar
When implementing a list of prices in all currencies for the JWT payment format -- https://wiki.mozilla.org/WebAPI/WebPayment#In-app_payment -- the Marketplace team ran into snag with the country code. Why is country code needed? Is this needed by BlueVia? Can we remove this and just specify a currency code and price? It is unclear to us how or why we would declare a country code. For example, EUR (Euro) would map to many many countries, not a single one.
Making this change would also require changing request.defaultPrice to point to a currency code instead of a country code.
Kumar
Kumar McMillan
Sep 6, 2012, 11:16:17 AM9/6/12
to DAVID LOZANO LLANOS, dev- >> dev-webapps@lists.mozilla.org, Jimenez Ernesto (UK)
On Sep 6, 2012, at 4:26 AM, DAVID LOZANO LLANOS wrote:
> HI Kumar
>
> The only reason I can see to include the country is to cover cases where
> the desired prices vary between different countries sharing the same
> currency (e.g. Germany - Spain), due to "market/economic" reasons. If we
> agree this is just a corner-case, we could simplify and just include
> currency. At BlueVia side we "discover" the country based on user's
> identity/MSISDN.
>
> +1 for the simplification.
Yeah, I was thinking it would be up to BlueVia (or whatever processor) to decide what currency to use in a given region. I think it is more reasonable to ask the processor to make that decision.
OK, we will implement it with just currencies, no country codes, and I will update the wiki.
thanks, Kumar
>
> Regards,
>
> David
>
> El 05/09/12 19:06, "Kumar McMillan" <kmcm...@mozilla.com> escribió:
>
> Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
> This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
DAVID LOZANO LLANOS
Sep 6, 2012, 5:26:38 AM9/6/12
to Kumar McMillan, dev- >> dev-webapps@lists.mozilla.org, Jimenez Ernesto (UK)
HI Kumar
The only reason I can see to include the country is to cover cases where
the desired prices vary between different countries sharing the same
currency (e.g. Germany - Spain), due to "market/economic" reasons. If we
agree this is just a corner-case, we could simplify and just include
currency. At BlueVia side we "discover" the country based on user's
identity/MSISDN.
+1 for the simplification.
The only reason I can see to include the country is to cover cases where
the desired prices vary between different countries sharing the same
currency (e.g. Germany - Spain), due to "market/economic" reasons. If we
agree this is just a corner-case, we could simplify and just include
currency. At BlueVia side we "discover" the country based on user's
identity/MSISDN.
+1 for the simplification.
0 new messages