# MDES Token Connect
source: https://developer.mastercard.com/mdes-token-connect/documentation/index.md

## Overview {#overview}

The MDES Token Connect API provides a set of inbound web requests to allow issuers to securely push Account information to eligible token requestors and create new tokens for Push Provisioning and Pull Provisioning use cases. Wallets, Merchants, Payment Service Providers are collectively referred to as token requestors. This documentation is a technical specification of the MDES Token Connect API.

For details on MDES participants and interaction, refer to [MDES Issuer Implementation Guide](https://trc-techresource.mastercard.com/r/bundle/m_mdes_iss_impl_en-us/page/d/en-US/ovo1732530667092.html)

MDES Token Connect API provides the following services to issuers:

|                                                          Service                                                          |                                                                                                                          Description                                                                                                                           |
|---------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| [Get Eligible Token Requestors](https://developer.mastercard.com/mdes-token-connect/documentation/api-reference/index.md) | Returns the list of token requestors that are enabled for one or more account ranges of the issuer. For each returned token requestor, metadata (such as name, image asset ID, Token Connect capabilities) is also supplied.                                   |
| [Get Assets](https://developer.mastercard.com/mdes-token-connect/documentation/api-reference/index.md)                    | Returns the logo of a token requestor, in PNG and SVG format.                                                                                                                                                                                                  |
| [Push Multiple Accounts](https://developer.mastercard.com/mdes-token-connect/documentation/api-reference/index.md)        | Triggers issuer-initiated digitization of a card or financial account to a target token requestor. The issuer obtains a receipt for their request, as well as the token requestor URI(s) where they should redirect the consumer to complete the provisioning. |

## Key Benefits {#key-benefits}

### Issuers {#issuers}

* **Push Provisioning:** Appeal to digital account holders by providing a new service to push provision payment cards and accounts into all participating token requestors with a single integration.
* **Pull Provisioning:** Appeal to digital account holders by providing a new service to pull provision payment cards from issuer app to the wallet.
* **Scalable and Interoperable Framework:** No need for multiple proprietary APIs between issuers and token requestors. Once you are connected to the Token Connect framework, you can connect with any MDES token requestor that has implemented the service.

### Cardholders {#cardholders}

* **Instant:** Account holders can use their digital card account as soon as they have been approved and before their plastic card has been shipped.
* **Convenient:** Load new cards into favorite merchants and digital wallets simply and easily. Rather than entering their card details manually, cardholders simply select the card or account they want to digitize and choose from an up-to-date list of enabled merchants, digital wallets and commerce platforms.
* **Secure:** Payments that are provisioned are tokenized so account holders can shop online, in-apps and in-stores knowing their transaction is secure.

## How It Works {#how-it-works}

MDES Token Connect is a consumer-facing facility that supports digitization through issuer system. When integrating to MDES Token Connect framework, the issuer must enhance their banking app and online banking web site, as applicable, to allow account holders to push/pull payment details to token requestors. A token requestor can be any participating merchant, digital wallet, or commerce platform. The Token Connect framework allows an account holder to checkout anywhere in a secure and convenient way using any payment method they choose.

### Push Provisioning {#push-provisioning}

The account holder starts their journey from an issuer banking app or an online banking website and selects a payment account to push with a specific token requestor. The following diagram illustrates integration of the MDES Token Connect framework with an issuer for push provisioning:

![alt text](https://static.developer.mastercard.com/content/mdes-token-connect/documentation/img/how-it-works.png "HowItWorks Push Provisioning")

1. Using the MDES Token Connect API, the issuer requests to push the selected account to the target token requestor.
2. If the request is valid, MDES generates and returns a PushAccountReceipt(s) (a string voucher) to be used by the token requestor for tokenization of the account(s).
3. The issuer then redirects the account holder to the URL provided in the MDES response.
4. Once the token requestor receives the PushAccountReceipt from the issuer, the token requestor initiates the tokenization service to receive the token from MDES.

### Pull Provisioning {#pull-provisioning}

The account holder starts their journey in a wallet app and selects an issuer banking app or an online banking website to choose and add a payment account to the issuer wallet. The following diagram illustrates integration of the MDES Token Connect framework with an issuer for pull provisioning:

![alt text](https://static.developer.mastercard.com/content/mdes-token-connect/documentation/img/how-it-works.png "Need to change")

1. The account holder selects issuer from the list to add selected account(s) to the wallet.
2. The wallet redirects the account holder to the issuer app.
3. After authenticating the cardholder (if required), the cardholder selects the account to the wallet.
4. Using the MDES Token Connect API, the issuer requests to push(pull) the selected account to the target token requestor.
5. If the request is valid, MDES generates and returns a PushAccountReceipt(s) (a string voucher) to be used by the token requestor for tokenization of the account(s).
6. The issuer then redirect back the account holder to the URL provided in the MDES response.
7. Once the wallet receives the PushAccountReceipt from the issuer, the token requestor initiates the tokenization service to receive the token from MDES.

Note: Support of Token Connect Push Provisioning is a pre-requisite for Pull Provisioning use case.

For more information on how to implement the Token Connect framework, refer to the [Use Case](https://developer.mastercard.com/mdes-token-connect/documentation/use-cases/index.md) section.

## Next Steps {#next-steps}

Refer to the [API basics](https://developer.mastercard.com/mdes-token-connect/documentation/api-basics/index.md) and [Getting Started](https://developer.mastercard.com/mdes-token-connect/documentation/getting-started/index.md) sections to find out more about what to do next.