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

I hope to leave the subclassing semantics to the payment method specifications. In case of Basic Card Payment Method spec that we're writing in the working group, I hope to use "/" for subclasses.

> I'm not sure your approach works in this case:
>
> * User has Visa Debit
> * Merchant accepts Visa Credit
>
>If the user's payment app normalizes to "Visa" it might look like a match, but it's not.

Exact matching in browser should take care of that.
````
                                browser<---["visa","visa/debit"]---user's payment app
merchant----["visa/credit"]---->browser
                            (no exact match)
````
I admit that I have not thought through this proposal thoroughly. I am open to suggestions and other proposals as well.

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