- From: Jeff Burdges <notifications@github.com>
- Date: Mon, 14 Mar 2016 11:15:28 -0700
- To: w3c/browser-payment-api <browser-payment-api@noreply.github.com>
Received on Monday, 14 March 2016 18:15:58 UTC
Just allow fields to be base64 encoded encrypted blobs if the payment app supports it perhaps? It's only really a problem if the spec says some field is required, and some payment app says that field needs to be private when turned over to the PSP or whoever, possibly for legal reasons btw. As long as any field that needs protection from some party isn't required in the first place then it's probably not a problem anyways. --- Reply to this email directly or view it on GitHub: https://github.com/w3c/browser-payment-api/issues/55#issuecomment-196450920
Received on Monday, 14 March 2016 18:15:58 UTC