Re: [w3c/webpayments-methods-tokenization] What to do if tokenized data looks like basic card data? (#21)

As part of current specification there is no dynamic CVV or expiry. There is cryptogram which the acquirer needs to send in authorization to Network (to issuer) along with token (16 -19 digit) and expiry of token. As of now there is no need of separate label. 


-- 
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-methods-tokenization/issues/21#issuecomment-342547408