Re: [w3c/payment-request] Passing a transaction id to a payment request (#911)

Adding an informative note about `id` in `PaymentDetailsInit` sounds good to me.\

> I'm not aware of concrete use case of this, but I have seen somewhere that detailsPromise was defined so that a merchant can let the browser wait until they determine the total cost. This means at the same time that the merchant won't know the transaction id until then. And the merchant has to be able to pass a transaction id along with the PaymentDetails object by resolving detailsPromise. That's why I asked.

This would involve adding `id` to `PaymentDetailsUpdate`. It seems OK, but I'd like to see evidence from a real world use case before we change the spec.

-- 
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/payment-request/issues/911#issuecomment-624922651