Re: [w3c/webpayments] How can a Web Based Payment App cancel the payment flow? (#128)

@ianbjacobs 

I'll just answer your questions with a short comment here, as this payment app is not nearly as impressive as you might think. The answer to the first two points is that it's all hard-coded into the browser at the moment. I'm planning to start experimenting with app registration soon, but I haven't gotten there quite yet.

The browser communicates with the payment app pretty much exactly as specified in the [Payment Apps spec proposal, section 6](https://w3c.github.io/webpayments/proposals/paymentapps/payment-apps.html#processing-payment-requests), that is to say, I convert the whole payment request to JSON and POST it to the web app. The result is delivered back in the form of JSON passed through a javascript api, as in the spec proposal.

The payment app itself can be seen here: https://people.opera.com/tommyt/pay.php. Just view the page source to see how simple it is. There is some server-side PHP that handles the POST data, but this code will insert test data if nothing was POST'ed. If you want to look at the whole flow of the payment app, you can create a test account at https://sandbox.secure.checkout.visa.com.


---
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/issues/128#issuecomment-215368530