Re: [w3c/browser-payment-api] How do the payer and payee agree on the payment obligation as part of the flow? (#113)

This issue is not about Ts&Cs.

There is a need to prompt the user when they are at the moment of authorizing the payment with a message that states clearly what they are authorizing and what they are getting in return.

In ISO20022 parlance this is the "obligation" that backs the payment. In many jurisdictions the way this is presented and agreed by the user is defined in law and we need to ensure we accommodate those local requirements.

We can punt this by making it the job of the payment app to figure out what to prompt the user but that prompt is likely to be lacking context without some input from the payee. i.e. "Authorize a recurring $5 payment to XYZ" isn't as good as "Authorize a recurring $5 payment to XYZ for weekly delivery of ABC".

It sounds like the consensus is to punt this pending further feedback so I will drop the priority down to low and mark it as a PostponedFeature.

---
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/113#issuecomment-211804233