Push to token requestors (Token Connect)
Push to token requestors (Token Connect)
Use this guide to push a card from the issuer application to a token requestor using Mastercard MDES Token Connect.
Token requestors can include e-commerce merchants and wallet providers.
For Mastercard product documentation, see MDES Token Connect overview.
Overview
With Token Connect, the issuer application:
Retrieves the list of eligible token requestors for a card.
Requests a push URL for the selected token requestor.
Redirects the End User to the token requestor experience to complete Tokenization.
End-user experience
The diagram below illustrates a representative Token Connect flow. The same pattern applies to any Token Connect-compliant token requestor.
Flow
Retrieve eligible token requestors
Push to a token requestor
Sequence diagrams
Push a card to a token requestor
After the End User selects a token requestor, the issuer application requests a push URL by calling addDigitalCardToScheme().
The issuer application then redirects the End User to the token requestor using the returned push URL.
What happens next
The D1 SDK returns a push URL.
The issuer application opens the push URL in the token requestor application or in a web view.
The token requestor performs the Tokenization flow.
When the flow completes, the token requestor redirects the End User back to the issuer application using the
appURL.
For a full access to the D1 SDK, please check API reference.
Last updated
Was this helpful?