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

@tommythorsen,

Ah, I haven't fully reviewed Adrian's Payment App proposal yet. Reading over it, I have a slightly different view of how I would expect this to work with Payment Apps installed in browsers. Non-interactive HTTP-based payment apps would almost certainly receive payment request messages via POST -- but I'm not yet convinced we want those apps that also provide a Web-based UI to work that way. It may be more natural for them to interface with the user agent using JavaScript and Promises. Maintaining state may also be easier this way. We're kind of right in the middle of trying to figure out the best way to design this part of the API :).

> If I implement it this way, I don't strictly need any changes to the spec, but it would be nice if the cancel/error scenario was mentioned in the spec anyway, for clarity.

Sure. It's worth trying it out that way -- experiments here are definitely welcome. And, yes, we'll want to indicate an example of how "cancel" (or refusal to consent) can be done.

---
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-214906902