Much of what is proposed would be reflected in the token domain restriction controls that are bound to the Token Requestor ID. The proposed information would then be communicated to the TSP in one of two ways. 1. Merchant as the Token Requestor registers with the TSP outside of W3C Tokenisation resulting in a TRID unique to that merchant for each TSP representing specific payment token requirements. this would require including a TRID field on the request. 2. Merchant provides this information in the W3C interfaces to a Token Requestor who has previously registered with each TSP. The TR using their TRID requests the payment token at a transactional level relaying the payment token request parameters to the TSP resulting in the issuance of a payment token for a specific use. In the EMV® Payment Tokenisation Specification the parameters to consider may be found as distinctions between Cardholder initiated transactions and Merchant initiated Transactions. Transaction types may be found in EMV® Best Practices Document - Recommendations for EMV Processing for Industry-Specific Transaction Types. -- 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/25#issuecomment-363506135
Received on Tuesday, 6 February 2018 17:48:43 UTC