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

> As a merchant, I want to know with certainty that if I'm supporting basic cards, for example, that the experience is first class

I'm skeptical of this line of thinking. As a general rule, every merchant wants their customer experience to be first class. I assert that in addition to that, giving the customer the choice to pay in the way that they want to is preferable (from a customer experience standpoint) than via a limited set of "experiences" provided by the merchant.

To put it another way - the customer will choose to register and use the payment apps that /they/ find most compelling. I don't support an ecosystem where a merchant forces usability choices onto the customer because doing that will lead to an uneven playing field.

> Have we ever considered removing the payment app registration concept from the spec and just letting payment apps handle the first-time experience in their own way?

Our company would like to provide software that helps our customers safeguard their cards, store verifiable claims, and help them manage their financial lives. In order for us to do this, we need a mechanism that enables customers to choose which payment applications they use.

It sounds like you're requesting that we remove this functionality? Or are you arguing for the removal of something more subtle?

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