- From: Dave Longley <notifications@github.com>
- Date: Wed, 14 Dec 2016 12:22:21 -0800
- To: w3c/browser-payment-api <browser-payment-api@noreply.github.com>
Received on Wednesday, 14 December 2016 20:22:54 UTC
> To fix this, probably what is necessary is to insert a step into https://w3c.github.io/browser-payment-api/#user-accepts-the-payment-request-algorithm which passes data to some algorithm defined in each payment method specification... Or passes it to some algorithm defined in the Payment App spec. My understanding is that that's where the data is actually going -- to a selected Payment App. Only in the case of a Payment App that is "built-in" to the user agent will it do something different (but this difference could be abstracted away). -- 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/338#issuecomment-267145421
Received on Wednesday, 14 December 2016 20:22:54 UTC