- From: Jeff Burdges <notifications@github.com>
- Date: Thu, 31 Mar 2016 04:49:48 -0700
- To: w3c/browser-payment-api <browser-payment-api@noreply.github.com>
Received on Thursday, 31 March 2016 11:50:44 UTC
I think web based payment apps might necessary be rather similar to the way they work today: After the pay button is hit, the user gets forwarded to the payment app selector, which forwards them to the web based payment app. After the user approves the transaction, the web based payment app forwards them back to the payees fulfillment page. We must watch anything fancier closely for same origin violations. In this space, the spec's real value is probably standardizing the data formats to enable payees to support more payment apps more easily, not enabling some additional interaction. --- 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/39#issuecomment-203895547
Received on Thursday, 31 March 2016 11:50:44 UTC