API naming and confusion

[rsolomakhin]

Hi everyone,

As the PaymentRequest ecosystem has grown, there has been some confusion about what constitutes a "Payment Handler".

Some people take "Payment Handler" to mean any payment app that can handle a PaymentRequest, be it based on service worker (https://w3c.github.io/payment-handler/), Android intents (https://web.dev/articles/android-payment-apps-developers-guide), built into an OS or a user agent.

Other people take "Payment Handler" to mean specifically the "Payment Handler API" as defined in https://w3c.github.io/payment-handler/.

To resolve this confusion, we propose:

1. Rename https://w3c.github.io/payment-handler/ to "Web Payment Handler API".
2. "Payment Handler" is any payment app that works with the PaymentRequest API.

---

Please provide your feedback in responses to this issue in the following format:

1. Yes/No - <Rename https://w3c.github.io/payment-handler/ to "Web Payment Handler API"?>
2. Yes/No - <Should "Payment Handler" mean any payment app that works with the PaymentRequest API?>

[stephenmcgruer]

"Payment Handler" is any payment app that works with the PaymentRequest API.

Note: within the Payment Request spec, this is already how a Payment Handler is defined!

https://w3c.github.io/payment-request/#dfn-payment-handler

"The details of how to fulfill a payment request for a given payment method is an implementation detail of a payment handler, which is an application or service that handles requests for payment."

[stephenmcgruer]

And for posterity:

1. Yes - <Rename https://w3c.github.io/payment-handler/ to "Web Payment Handler API"?>
2. Yes - <Should "Payment Handler" mean any payment app that works with the PaymentRequest API?>

[ianbjacobs]

1. Yes - <Rename https://w3c.github.io/payment-handler/ to "Web Payment Handler API"?>
2. Yes - <Should "Payment Handler" mean any payment app that works with the PaymentRequest API?>

[rsolomakhin]

@marcoscaceres - can we get your take?