You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a merchant only ships to certain regions, it would be useful to pre-filter the shipping addresses the user can select from. The case of no eligible address would be quite frequent - the user could see instead an explanation provided by the merchant, along with an affordance for adding an eligible address.
Example use cases:
Merchant doesn't ship to non-continental US, and the user has two addresses, one in Hawaii and one in California. In this case, only the California address would be shown.
The text was updated successfully, but these errors were encountered:
Smarter filtering would be nice. However, it would mean passing all addresses to the merchant, and that doesn't seem great from a privacy perspective...
Conversely, the merchant would need to pass in all the states for each country that they support. That could be more doable, but we would need a standardized list of all the states/provinces/regions in the world.
the merchant would need to pass in all the states for each country that they support
ISO3166 standardizes the country code. Provinces and regions are more of a can of worms, agreed, but perhaps filtering by country would cover 80% of the use cases.
This issue was raised in Payment Request, but closed once we removed addresses from that API. We anticipate adding addresses back to the specification and so are re-opening this issue proactively.
If a merchant only ships to certain regions, it would be useful to pre-filter the shipping addresses the user can select from. The case of no eligible address would be quite frequent - the user could see instead an explanation provided by the merchant, along with an affordance for adding an eligible address.
Example use cases:
The text was updated successfully, but these errors were encountered: