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

@rvm4 thanks for kicking this off!

In my experience the best way to guarantee that the sender (in this case the merchant) will have the same transaction reference as the receiver (in this case the payment app) in the case where no response is received and we don't know how far processing got is to send the transaction identifier in the original request.

I'd propose that we have a field in payment request that allows a unique identifier (UUID makes the most sense I think) and that this is returned in the "payment processing" event.

If you wait for the TX id to come from the app you risk comms going down before the app can provide this to the browser.

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