Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292)

Well.... hmm.  The problem I was trying to solve in the first place when I brought this up was that the payment app needs a way to help consumers track their transactions.  Not just a short lived way.  A long-term way.  And that way cannot be inside of the payment method data envelope.  We don't look in there!  I don't mind if we call it a payment request ID or whatever.  But it is a way to correlate merchants / requests with actual payments that were made.  Right now the Payment App (a smart wallet, remember) can't really be smart about this at all.

-- 
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/pull/292#issuecomment-260373066