Re: [w3c/browser-payment-api] Card Sub-Brands (#95)

(After discussion with Matt Saxon,) I wanted to summarize a few points:

* A mediator job is to compute the intersection between merchant-known payment method identifiers and user-known payment identifiers. The mediator learns about supported payment method identifiers from the user through the payment registration app registration process.

 * How the payment app determines which payment methods it supports, is a separate business decision. However, this thread suggests an additional point needs to be made: when the user types in (for example) card information, the payment app will want to determine the corresponding payment method identifier (for example, for a card sub-brand). How the payment app maps user-supplied credentials to supported payment method identifiers is outside the scope of our work, in my view.

 * I don't think the WG will specify how payment apps are updated (e.g., to support new payment methods). But the group does need to address the question of how the mediator learns about these updates (or, for example, that the user has registered some credentials with the payment app subsequent to registration).

Ian

---
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/95#issuecomment-203008554