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

Many thanks for the FAQ item lightening FTF discussion. I’m sincerely sorry not being able to participate to the Singapore discussion and I’m really sorry again to re-open the discussion that was done during last FTF meeting.

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?

With a standard network manifest format, a merchant will be able to extend browser default list with local networks he wants to support. Last question to solve is how to detect non built-in networks? Why not to use an event listener similarly to what was done for `shippingaddresschange`?

It could be an event like `cardbinchange` giving a way for the merchant to implement its local brand detection. In case the browser build-in detection resolve the brand differently of the merchant implementation, why not to let the merchant ask consumer to select the brand he want to use?

What would be the complexity to implement such model in basic-card?

Just to try having a broader understanding according functional problematic, please take a look on page 2 of that [presentation](http://www.payforum.fr/pdf/Pierre-Juhen.pdf) representing card payments in Europe (light blue=international schemes, dark blue=local schemes):
 
![schemas](https://user-images.githubusercontent.com/1512261/39805946-aa65f01c-5378-11e8-9732-1ed3f0ad148b.png)

My personal feeling is that if browser implementation doesn’t support local schemes, there is no chance for those implementation to be generalized on market with strong local brand such as France. Alternative will probably be to use specific merchant/brand payment handlers but if we go in that direction, what is the interest to invest on browser “basic-card” native implementation?

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