Re: [w3c/webpayments-payment-apps-api] Is the concept of payment app registration necessary? (#8)

Manu, my underlying problem with payment app registration is that payment apps already exist today, they exist on the web, as native apps, etc and the majority have an existing registration process, but we're now saying that we want to add another layer of registration on top of that for each browser the customer is using.

I understand the wish to give customers choices and create an even playing field for new payment methods but in the end the merchant is going to have to support the underlying payment method that an app wants to support (your example would be storing basic credit cards, even then there's specific card brands). So unless one payment method becomes adopted by 100% of customers (no matter the app they use) there's still a requirement on the merchant to support the different methods, leading to the same uneven playing field you are trying to avoid. It's creating a somewhat even playing field for wallets that support storing the most popular (arguable) basic credit card, but the future of payments I see isn't to monopolize a single payment method, it's to make it easy for new methods to be adopted by merchants, a merchant will support the best ones for their subset of customers and enabling ease of competition will even the playing field.

---
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-payment-apps-api/issues/8#issuecomment-233994502