Re: [w3c/browser-payment-api] put request id in details dictionary (#426)

Looks like you're passing in a `paymentRequestID` to the constructor, but remove its accessors and don't mention where this identifier is going.

If you expect the merchant website to read this identifier, please expose it through an accessor in `PaymentResponse` interface. Depending on your use-case, you may want to expose the identifier through an accessor in `PaymentRequest` interface as well.

If you expect the payment app to read the identifier, please add a note somewhere that it should be sent to the payment app.

-- 
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/426#issuecomment-281797666

Received on Wednesday, 22 February 2017 20:45:44 UTC