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

Currently the payment details method does not include a transaction ID.  In order to facilitate future work (e.g., receipts) and to help Payment Apps track user's transactions, I think it would be good to have merchants get used to including this information in their payment requests.

As to sending it to the Payment App, I will raise a separate issue for that, but in this model the transactionID (a DOMString) would be included in the Payment App Request Data object along with the origin and other information.  In this way a Payment App could correlate origin / transaction IDs and assist with future related transactions such as returns or order status queries.

If there is support for this, I am happy to supply a PR.

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