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

@adamroach and @adrianhopebailie I agree with both of you here.  

My understanding of this is a bit broader though.  While this is an identifier the payee and the payment app can use to correlate information, in the real word it has other uses.  

Today if I go into a convenience store and purchase something, my receipt has two critical pieces of information on it that have nothing to do with the payment method.   These are the origin (merchant name + store identifier) and the transaction number (some unique number).  These items, when used together, uniquely identify the transaction to the merchant.  Any merchant worth their salt keeps track of these in a database so they can later handle returns, re-issue receipts, track spending habits... whatever.  

Right now we have no way of conveying this information.  WIth the addition of this simple field, the payment app can now help its user keep track of where they spent what.  Feels like a win for everyone with almost no cost.

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