Re: [w3c/payment-request] Modifiers and [[serializedModifierData]] not actually used anywhere. (#753)

We talked about this topic in the working group meeting earlier today. What I heard is that it's really not possible to definitively determine the card type in real time. For instance, for Mastercard the card might be identified as Maestro first, debit second, credit third. The business logic dictates that an application run through those options in that order, where credit is the fallthrough if the others don't work out. However, this decision process might not occur in real time (e.g., it could happen overnight during clearing).

Given this information, we need to figure out if it is realistic to support card type matching and type-based modifiers. I tend to think it isn't - certainly not in a way that enables the browser or payment handler to show helpful UI hints before hitting "Pay" at the end of the workflow.

-- 
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/payment-request/issues/753#issuecomment-415606768