I think it is too early to say if we should have one or two or in fact many. on the many point, I could see an approach where we standardise a set of base data, but allow an arbitrary PMI to use the data.
This has a couple of benefits;
1. We can dispense with the tokenProviderURL param, instead using the PMI (which is a URL)
2. Providers can extend the base data to allow for innovation in the ecosystem
--
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/13#issuecomment-317779660