[w3c/payment-handler] API naming and confusion (Issue #417)

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"?>
1. Yes/No - <Should "Payment Handler" mean any payment app that works with the PaymentRequest API?>


-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/payment-handler/issues/417
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/payment-handler/issues/417@github.com>