Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138)

adrianhopebailie commented on this pull request.



>          </li>
         <li>Once activated, the payment handler performs whatever steps are
-        necessary to authenticate the user, process the payment, and return
-        payment information to the <a>payee</a>. If interaction with the user
-        is necessary, the <a>payment handler</a> can open a window for that
+        necessary to handle the payment request, and return an appropriate
+        payment response to the <a>payee</a>. If interaction with the user is
+        necessary, the <a>payment handler</a> can open a window for that
         purpose.
         </li>

The original text is incorrect. We should not bring discussion of authentication of the user into this text at all. 

IMO this is what causes the confusion and results in long mail trails from people who want to understand how we are handling authentication. The answer is simple, we are not. That is the job of payment apps.

I will add a non-normative note that explains what "handle a payment request" means and provide examples using basic card and credit transfer to explain 

-- 
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/pull/138#discussion_r111896846