Re: [w3c/payment-method-basic-card] Brand selection (#49)

@glelouarn thanks for this info, the data around use of local networks is very compelling and I think we'd see similar numbers in countries outside Europe (such as Japan) where local networks are much more widely supported than the large international networks.

You asked:
> Today, networks are considered as a static deterministic list implemented by browser agents. It works great and seems simple to appreciate at a technical and functional point of view.

> However, why not to open that static list of browser default supported networks list giving capabilities for merchant to define new ones. How is defined a network? A name, an identifier and a logo? Why not to define a manifest format for that?

This has been a point of contention in the group for some time however given that the networks represented in the group are predominantly international networks it has maybe not had the level of focus you'd like.

The list of possible networks is hard-coded by the browsers and comes from here https://www.w3.org/Payments/card-network-ids. I understand this to be for security reasons. i.e. Browsers want to do strong data validation of built-in payment methods and that requires enumerations to be well-defined (i.e. this can't just be a set if random strings).

Things have moved along a bit since so perhaps @marcoscaceres, @aestes or @zkoch can comment on the viability of making the list of networks more flexible.

That said, I would recommend following the change request procedure defined in the card-network-ids document to add any regional networks you think need to be in the list.

As a general comment it does seem that the design of the basic-card payment method (and in some respects the PR API) continues to be very biased toward the US market which is unfortunate.

What many of the discussions in Singapore highlighted for me is that implementing a payment handler for basic-card (whether built into the browser or as a stand-alone handler) will require some level of BIN matching capabilities, which is something of a dark art considering there is no authoritative source on BINs, issuers and networks that I am aware.

We continue to skirt this issue but I think we are simply pushing this complexity onto merchants (like we have done to date with gift cards, coupons, billing address collection etc).

It would be helpful to understand how merchants are expected to do this under current legislation so we can understand the impact it would make on the API if it were implemented.

i.e. If a merchant gets a PAN back from the PR API how are they expected to determine that it is a multi-network card? Is there a public database they can use to look this up?

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