>From discussions it seems that there are two use cases to take into account: * The payee wants a "full payload" of token, cryptogram, and other information used for authorization. * The payee only wants some sort of reference in the payment method response. The payee (or their PSP) will use this reference on the backend to retrieve the remaining information required for authorization. I welcome comments here to help identify the data model for this "lighter" payment method. -- 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/46
Received on Tuesday, 7 August 2018 22:29:14 UTC