> In France use case, we aren't looking to distinguish fees for buyer. Problematic is to identify how to route the transaction according the fact that the brand information is associated to a buyer explicit choice.
Right - got it: The API doesn't currently tell you which network on the card was selected by the user. Do you have a link to where this law is described (hopefully in English, if it's EU🤞)? This would mean a significant change to browser's UIs and how our card type detection code works - so need to verify this with our legal folks to understand what the law actually stipulates and who needs to comply with it.
> As a consequence, in my opinion, BasicCardRequest should contain something like "preferedNetworks" to manage merchant networks presentation order.
The payment request spec says:
> When ordering payment handlers and payment instruments, the user agent is expected to honor user preferences over other preferences.
The instruments part is supposed to handle "network" display, if I recall correctly. However, in case there is no preference, wouldn't the ordering in the list suffice:
```JS
// Merchant's preferred order is...
supportedNetworks: ["visa", "mastercard", "cb"],
```
> Concerning BasicCardResponse, it should probably contain something like "selectedNetwork".
Yep, makes sense.
--
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-method-basic-card/issues/49#issuecomment-372325154
Received on Monday, 12 March 2018 14:18:52 UTC