Hi @rvm4, As mentioned on today's call, part of the answer lies in the algorithms of the spec. See, for example: 8.2 Steps to check if an instrument is supported https://w3c.github.io/webpayments-methods-tokenization/index.html#steps-to-check-if-an-instrument-is-supported I adapted that text from Basic Card, but it has not been well-reviewed and may need work. It currently says: If types is empty and networks is empty, return true. It might need to say: If types is empty and networks is empty and cryptograms is empty, return true. I am inclined to make that change (for consistency with types and networks). Comments welcome! Ian -- 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/48#issuecomment-412936938
Received on Tuesday, 14 August 2018 16:40:56 UTC