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

@rvm4 In general I really like this but I'm not sure I see the value of the callback if it's in the `Payment MethodData`.

As a merchant, the advantage of this for me is that I only implement a single public facing endpoint to process callbacks. These requests are always `PaymentResponses` so the outward facing code I must deploy will seldom , if ever, change even if I add support for new payment methods.

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