Re: [w3c/browser-payment-api] PaymentDetails should include a transaction ID (#287)

I don't like the idea of this in the payment method data.  That data is opaque to the payment app, which means the payment app cannot then help its user out with correlating things later.

I don't hate the idea of a request ID rather than a transaction ID.  Just some top level unique identifier from the merchant that stays around through the flow.

-- 
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/287#issuecomment-249223156