Re: [w3c/webpayments-method-identifiers] Should we define nesting/grouping semantics for payment method identifier matching? (#1)

A simple approach (from the browser perspective).

1. Browser matches the identifiers exactly.
2. A payment app that contains visa debit card details can tell the browser that it handles both "visa" and "visa/debit".

As a result, if the merchant requests "visa", then they always get "visa" identifier back, even if it's actually "visa/debit".

Thus we're pushing this question out to the payment app's responsibilities. 

---
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/webpayments-method-identifiers/issues/1#issuecomment-227629894