Re: [w3c/browser-payment-api] Supporting push payment methods (#224)

A few comments:

1) I think it is important that the payment app be allowed to provide the identifier because the payment app is the one implementing a bunch of abstractions that rely on this identifier being unique. Allowing the merchant to supply the identifier forces all payment apps to architect their backend around tuples of the form (merchant, identifier) which is not going to be easily adoptable by any existing apps. It makes sense for merchants to take on this burden because in many situations the merchant will be incentivized to implement addition integrations with a particular payment app (when sufficient traction has amassed) and in doing so need to differentiate ids.

2) You are right that a requestId could fail to make its way to the merchant from the payment app, but it is of little consequence because it only provides a way to query about payment status. Failure to receive the requestId implies that payment did not occur.

---
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/224#issuecomment-231246707