Re: [browser-payment-api] Should the API handle pre-auth, recurring payments, and similar scenarios (#19)

@burdges, my view is that this comes down to what people are agreeing to when they hit "Authorise", at the moment, this is simply a proceed button, I believe it should be the point at which a contract is struck, aka a payment obligation in ISO20022. This 'agreement' should be signed such that in the event of dispute later it is clear what was agreed to and by whom.

To do this, the agreement needs passing into the API so it can be displayed to the user and so this can be part of the data that is signed.

I have referenced the need for signatures in issue #31 and also https://github.com/w3c/webpayments/issues/60

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/browser-payment-api/issues/19#issuecomment-195291783