Re: [w3c/webpayments-payment-handler] Do we need "Payment Manager" and "Payment Handler"? (#127)

So if a Payment Handler is a synonym for EventHandler  onpaymentequest, should the spec be called just "Payment Handler", since it is so much more. Also, what was the original rationale for changing away from Payment App, especially since the specification still refer to Payment Apps (e.g. PaymentAppRequest).

Even though I see the point @adrianhopebailie makes above, the existence of the separate terms of Payment App, Payment Handler and Payment Manager is confusing. Perhaps clearing up the Payment App terminology may be a good 1st step to removing that confusion.

My feeling (without the context and history) is;

1. Spec should be called Web Payment App
2. Payment Handler is a synonym for "EventHandler onpaymentrequest" and we should perhaps call that out fairly early in the spec. However I am unconvinced that we need the term Payment Handler very often in the spec, instead using the term Payment App
3. PaymentAppResponse & PaymentAppRequest make sense given point 1
4. Payment Manager would remain

-- 
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-handler/issues/127#issuecomment-294713131