Re: [w3c/browser-payment-api] Merged PaymentRequest params and tweaked to address some issues (#133)

>            <pre class="example highlight">
> -            ["visa", "bitcoin", "bobpay.com"]
> +            {
> +              "amount" : [{

@zkoch We have had strong support for including this.

I understand that it makes the UX more complex but that's an implementer challenge that I assumed would be embraced as a way to differentiate.

Off the top of my head I can imagine a browser having a small selector that allows the user to select their payment currency and when they do the rest of the UI adjusts to display the pricing in that currency. The selector would only be visible if the request actually contains more than one currency.

On the other hand, I don't see us having any conformance language that forces the implementer to display all currencies to the user in the app selection UI. If the browser picks one currency and displays that currency and price that is still valid as the user's option to select another currency will then be made in the app.

---
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/browser-payment-api/pull/133/files/cf56b89b9fd4927e652f57db1b2d2c0d8a7d5aa5#r60030655