Re: [w3c/browser-payment-api] Currency Types and Rendering (#185)

> We need input from the browsers how they would display amounts if there were different amounts per payment method/

I would like to give a payment app the ability to provide detailed information about the ways in which the user can pay, a.k.a. instruments. When I say "instrument", I only mean a way to pay with a payment app.

An instrument can be as broad as "App 3" and as narrow as "Bitcoin account X in App3". An instrument includes such information as an id, a label, an icon, the way to invoke the payment app, and a non-empty list of payment methods.

For example, "App 3" instrument can specify `["bitcoin", "visa/debit"]` methods. Given this information, a user agent can present a list or range of prices to the user in the selector UI. (Ranges for same currency, lists for different currencies.)

Payment |                                          Price |
-------------|-----------------------------------------:|
App 1      |                    _USD_ $1.00-1.10 |
App 3      | _BTC_ 0.00001, _USD_ $1.00 |

Alternatively, "App 3" app can provide two instruments: "Bitcoin wallet X in App 3" with `["bitcoin"]` method and "Debit card Y in App 3" with `["visa/debit]` method. Then price can be displayed one-per-row, without ranges or lists.

Payment |                                          Price |
-------------|-----------------------------------------:|
Debit card A in App 1  |                    _USD_ $1.00 |
Credit card B in App 1 |                    _USD_ $1.10 |
Bitcoin wallet X in App 3 |  _BTC_ 0.00001 |
Debit card Y in App 3     |  _USD_ $1.00 |



---
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/issues/185#issuecomment-223047965