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

@zkoch my intention was that the callbackURL be passed something structurally the same as the PaymentResponse. It is true that every payment app will have its own payload, but we have already accounted for that in the PaymentResponse object with a freeform place to put whatever you want.

I think for the purposes of this PR I'm happy just getting the transactionID in there. We can continue talking about how best to accomodate server callbacks in our weekly calls.

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