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

I think the question here is, should the wording be defined by the website (merchant) or the payment app?

One could argue that the payment app, having the knowledge of the terms and the payment method that is being used is well equipped to prompt the user appropriately in authorizing the transaction.

However, I can't imagine this being done very well across multiple languages, or including the level of detail as @triblondon has above if it is generated by some logic in the app.

My suggestion is that we include some mechanism in the payment request for the merchant to pass this to the payment app. This may be a simple standard field which contains some text that all payment apps can display to the user.

Payment apps/methods can depend on this being provided and use it if they wish. Example, a payment method may require that this is digitally signed/timestamped and returned in the response.

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