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

My motivation for the split is that I consider "payment options" as data that is only consumed by the user agent which could easily include this in it's own "chrome" but I agree that perhaps these need to be done together and passed to the payment app.

That way we allow payment apps to ignore these if the payment method allows that. I'm conscious that our API only enables features that are required (either technically or legally) but doesn't impose anything. The payment apps which will need to explicitly support a payment method should be the ones that ensure they do all the right things to be compliant with that method.

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