Re: [w3c/webpayments-crypto] Mapping between claims and response data elements (#13)

@adrianhopebailie, in general I support the idea, which I understand to be: provide a convenience for naming a single blob but also allow payment methods to map data to specific claims.

If I understand, the payment_response is encrypted. But that name suggests it is the entire response, rather than just the encrypted portion. Could we change it to encrypted_payment_response?

In terms of spec edits, it seems that:
 * the encryption spec would need to speak about this in the section "5. How to Use this Specification within a Payment Method Specification". It may also be that section 3.3 (Plaintext encryption) goes away in favor of section 5.
 * the current Tokenized Card Payment specification would then say that the encryptedDetails value is encrypted data (per the encryption spec) where the encrypted_payment_response claim data has the form EncryptedTokenizedCard.

Is that how you imagine this being organized?




-- 
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/13#issuecomment-394369161