- From: mattsaxon <notifications@github.com>
- Date: Fri, 29 Apr 2016 09:53:04 -0700
- To: w3c/browser-payment-api <browser-payment-api@noreply.github.com>
- Cc:
Received on Friday, 29 April 2016 16:53:39 UTC
@hober as this PR has not been accepted and I'm not sure if your concerns have been addressed, I wonder if you'd consider submitting a sequence diagram to show this issue. You can see the ApplePay flow represented here http://www.plantuml.com/plantuml/proxy?fmt=svg&src=https://raw.githubusercontent.com/w3c/webpayments-flows/gh-pages/PaymentFlows/ApplePay/ApplePay-Native-Current.pml It would be good to represent this correctly if it it not, and to show how the flow will work under the API as has been done in the Basic Card Payment spec. If you're willing I can assist. The basic flow for the new API is here https://raw.githubusercontent.com/w3c/webpayments-flows/gh-pages/TargetFlows/PaymentRequestAPI.pml --- 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/pull/153#issuecomment-215805680
Received on Friday, 29 April 2016 16:53:39 UTC