- From: mattsaxon <notifications@github.com>
- Date: Fri, 24 Mar 2017 06:07:14 -0700
- To: w3c/browser-payment-api <browser-payment-api@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 24 March 2017 13:08:12 UTC
Currently the documented algorithm has the following issues; 1. Unclear separation of concerns makes payment handler functionality ambiguous 2. as a result, brittle specification between payment handler spec and payment request spec (changes to algorithm in payment request makes algorithm in payment handlers incorrect) - for example see that in payment handlers, it current states that it replaces steps 6 & 7, whereas this is incorrect and it should be steps 7 & 8 (probably as a result of a removed step in PaymentRequest algorithm). With the recently matured Payment Handlers specification having specified amendments to this algorithm, I recommend that the algorithm is updated in the PaymentRequest specification to clearly define a separation of concerns between the mediators and the payment handlers. -- 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/browser-payment-api/issues/476
Received on Friday, 24 March 2017 13:08:12 UTC