Re: [webpayments] How are cloud-based payment instruments supported? (#16)

> The only thing I would add is that these payment instrument should be able to be specified by the merchant as well as the client. A use case for this is where the merchant has a nominated token service provider. The client would not know or want to know about this.

I think this information would be in the payment request and would be another piece of data in the "acceptedPaymentScheme" entry. That is, the merchant would say "I accept tokenized card transactions and here is my TSP". The buyer would select their "tokenized card" payment instrument, which would then redirect to the payment instrument issuer, which would then redirect to the merchant's TSP.

The upside is that all payment instruments would follow simple redirect logic. The downside being that there is one extra redirect w/ a TSP-based payment instrument.

Just a thought, not really married to the idea.

If we decide to have ad-hoc payment instruments, which is I think where @mattsaxon is saying, we'd have to think a bit more in depth about it as that's one flow we (the Web Payments CG) haven't really thought through and I'd defer to @mattsaxon since I know next to nothing about how TSPs work.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webpayments/issues/16#issuecomment-161501389