Re: [w3c/browser-payment-api] Specification to include Flow Diagram (#32)

@mattsaxon The selection of the payment app is facilitated by the browser when using the browser API. I don't believe that the browsers have any intention of mixing up payment instruments and payment apps and offering a selection UI that surfaces the payment instrument in any way.

Our architecture intentionally abstracts the whole idea of a payment instrument behind the payment app because not all payments actually use a payment instrument at all. It allows the payment app to stand for one, many or no payment instruments and the details are up to the payment app publisher.

If the issuer of a payment instrument decides that they want their payment instrument to be surfaced in the app selection UI then they need to publish a payment app that is tightly coupled to only that payment instrument.

---
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/32#issuecomment-211293657

Received on Monday, 18 April 2016 09:28:44 UTC