Re: [w3c/payment-request] PaymentAddress 'region' inconsistencies (#663)

@TSMatthews

For Chrome, "regionCode" should be present most of the time. We have the
data for most countries and I'm trying to get the data for the rest. The
reason we cannot guarantee it however is that the ISO standard moves pretty
slowly. So as things change in a certain country, it might take a while for
the changes to get into the ISO. In that case, we don't want to block the
user so we would send the merchant only the "region". This should be pretty
rare though.

Hope this helps!

Le ven. 26 janv. 2018 08 h 17, TSMatthews <notifications@github.com> a
écrit :

> @marcoscaceres <https://github.com/marcoscaceres> Thank you.
>
> 'regionCode' does seem like it will help the inconsistency issues as it
> must be valid ISO3166-2.
>
> Just so I am clear.. the forms could still have 'region' or 'regionCode'
> right? And it's really up to the browser vendors to implement it?
>
> We would not have 'regionCode' being an expected field returned from every
> address form? 'regionCode' solves inconsistency of value issues, but if
> it's not a mandatory field, it won't fix our issue that we always need this
> value (original post -> need region as consistent data and always present,
> so that we can verify against shipping rules / options specific to certain
> regions).
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/w3c/payment-request/issues/663#issuecomment-360781989>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AaKMaxf-ajCA5IrwqEC5HOAaPnqrGrNgks5tOdBrgaJpZM4RDnkl>
> .
>


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/payment-request/issues/663#issuecomment-360835355