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

I would advocate that we do not have an identifier for the **financial transaction** but for the **payment request**.

These are subtly different.

We have no scope to define transaction ids, as these are very specific to the payment processing, however we are attempting to provide a robust messaging infrastructure in which a request may be passed via the API and responded to via another channel.

I see the request ID (and I recommend changing the name) as a short lived identifier that allows a merchant to reconcile requests and responses on different channels. For this reason it seems like a good idea for the browser to generate this id using a well known format (128-bit UUID seems like a good option) and only accept a merchant provided ID in the same format.

Payments apps, merchants and PSPs should take responsibility for keeping track of which requests (identified by a request id) resulted in actual payments (identified by a tx id).

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