Re: [w3c/webpayments-crypto] Partial vs. full encryption of response data (#7)

Plain data is required for display purposes or for tracking where, for example, the payment is being processed by a third party but the merchant wants access to some data like a tx id.

I do think we should make this simpler though, I think that the way this is done in the tokenization spec is best. i.e. Define two schemas; a clear-text schema which contains unencrypted data (at least one data element is the encrypted data in the form of a JWT) and a data schema for the data that is encrypted inside the JWT.

See my proposal in #13 

-- 
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/webpayments-crypto/issues/7#issuecomment-393733305