Re: [w3c/browser-payment-api] Propose a payment method specification that includes an example of field level security (#141)

I think actually if there is any encryption beyond TLS, it would necessarily be on the merchant side when initiating the request.  If I care about encrypting my content, I surely do not want to expose it to the user agent.  I want to pass the encrypted blob to the payment app along with some sort of an indication of how to decrypt it.

I also think this is out of scope for what we are designing right now, but I could be wrong.

---
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/issues/141#issuecomment-212035508