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

> I assert that this is being done at the point where the mediator (user agent) shows the list of apps/instruments.

I'm a strong -1 to this. We can't assume that payment apps will always able to make payments using multiple instruments OR that user's will configure them with multiple payment instruments OR that users won't configure their mediator with a default app (and only have one installed).

It's only in the case that the user has multiple apps that support multiple payments instruments that there is even a need for a two step process.

The whole architecture is based on the user selecting an app and then within that app selecting the payment method (implicitly through selection of a payment instrument or not, we don't prescribe this) if required to do so.

Good payment apps will make this a seamless process using sensible defaults.


---
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-208335241