Re: [w3c/payment-request] API Data Integrity (#31) from Marcos Cáceres on 2018-01-23 (public-webpayments-specs@w3.org from January 2018)

From: Marcos Cáceres <notifications@github.com>
Date: Tue, 23 Jan 2018 02:54:24 +0000 (UTC)
To: w3c/payment-request <payment-request@noreply.github.com>
Cc: webpayments-specs <public-webpayments-specs@w3.org>, Comment <comment@noreply.github.com>
Message-ID: <w3c/payment-request/issues/31/359657361@github.com>

Closing this, as it's outside the scope of the current API. 

This needs to be supported by particular payment methods (e.g., tokenized payments) instead. The API just provides the `.data` where the encrypted data lives, and based on the PMI used, a third-party is able to verify is the data in the `PaymentResponse` if legit or not. 

-- 
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/payment-request/issues/31#issuecomment-359657361

Received on Tuesday, 23 January 2018 02:54:58 UTC