# Push Provisioning to Token Requestor using Proprietary Communication
source: https://developer.mastercard.com/mdes-token-connect/documentation/use-cases/push-to-tr-propritarycommunication/index.md

Available for Use By:

* Issuers
* Issuer Processors
* Online \& Mobile Banking Vendors

Regional Availability:

* Global

## Scenario {#scenario}

Susan opens her issuer's mobile banking app to check her account balance. She sees there is a new service available that lets her load her payment cards or account into leading digital wallets and merchants. Susan likes the convenience of making purchases online and with apps using her mobile phone. And she uses a digital wallet on her mobile phone to make contactless payments in stores. So she decides to opt in to the new service and loads her card into her favorite digital wallet. She can now shop knowing her purchases are convenient and secure.

![alt text](https://static.developer.mastercard.com/content/mdes-token-connect/documentation/use-cases/img/CompleteFlowWallet.png "Scenario")

## Pre-requisite {#pre-requisite}

* Consumer sign-in to the mobile banking app and selects the card to provision.

## User Experience {#user-experience}

1. [Issuer fetches eligible token requestors.](https://developer.mastercard.com/mdes-token-connect/documentation/use-cases/push-to-tr-propritarycommunication/index.md#fetch-eligible-token-requestors)
2. [Consumer chooses card(s) and a token requestor.](https://developer.mastercard.com/mdes-token-connect/documentation/use-cases/push-to-tr-propritarycommunication/index.md#consumer-selects-cards-and-destination-in-issuer-interface)

### Fetch Eligible Token Requestors {#fetch-eligible-token-requestors}

Before consumers can begin to provision their payment cards and accounts you'll need to display a consumer-friendly list of eligible Token Requestors to which consumers can push their account to.

* When enabled for Token Connect, you must retrieve from MDES the Token Connect parameters of each Token Requestor for which you have enabled your account range(s) in MDES.
* Periodic maintenance of Token Requestor information is required, and it is recommended that you perform a refresh bi-weekly.

#### Integration {#integration}

![alt text](https://static.developer.mastercard.com/content/mdes-token-connect/documentation/use-cases/img/retrieves-token-requestor-data.png "Integration")

1. Fetch the details of the Token Requestors with your enabled account range(s) by sending applicable accountRanges to the [getEligibleTokenRequestors](https://developer.mastercard.com/mdes-token-connect/documentation/api-reference/index.md) request. MDES returns information about eligible Token Requestors in the response including:
   * the user-friendly name for the Token Requestor;
   * the type of Token Requestor (wallet or merchant);
   * the imageAssetID - the reference of the Token Requestor logo to display to the consumer.
2. Retrieve the logo of each eligible Token Requestor by sending the *imageAssetID* in a [getAsset](https://developer.mastercard.com/mdes-token-connect/documentation/api-reference/index.md) request. MDES supplies the Token Requestor logo in two formats: .SVG (rescalable) and .PNG (192 x 192 pixels). The images are square with a white background.
3. Cache the details of the eligible Token Requestors and their logos in your back-end server.

### Consumer selects Card(s) and Destination in Issuer Interface {#consumer-selects-cards-and-destination-in-issuer-interface}

The consumer logs into your online or mobile banking app and navigates to an area where they can see information about the features and benefits of push provisioning. They are invited to select the card(s) they wish to push provision. Note that financial accounts may also be eligible for push provisioning. Next, they select from a list of available merchants, digital wallets and commerce platforms.

#### User Experience Design Guidelines {#user-experience-design-guidelines}

Request the consumer to select one or more card(s) or financial account(s).

Present the list of Token Requestors to which consumers can push their card(s) or financial account(s) for tokenization.

* **Token Requestor Logo**
* **Token Requestor Name:** the user-friendly name for the Token Requestor
* **Token Requestor Type:** digital wallet or merchant

Prompt the consumer to select one Token Requestor (wallet or merchant) from this list.

#### Integration {#integration-1}

![alt text](https://static.developer.mastercard.com/content/mdes-token-connect/documentation/use-cases/img/SingleIntegration.png "Integration")

1. The consumer is logged in their Issuer app/web site.
2. While navigating, they select the target Token Requestor as well as the card(s) or account(s) to push. Targeted Token Requestor supports Issuer Initiated Digitization Data (supportIssuerInitiatedDigitizationData = true)
3. The Issuer app or browser calls the Issuer back-end with consumer's choice.
4. Using MDES Token Connect API, the Issuer contacts MDES to request the push of the selected card(s) or account(s) to the target Token Requestor and request for issuer initiated data. The Issuer may append account holder data (for instance, billing address) to the request, if supported by the Token Requestor. If the request is valid, MDES generates issuer initiated digitization data valid for the next 15 minutes to be used by the target Token Requestor for the tokenization of the card(s) or account(s).
5. The Issuer returns the issuer-initiated digitization data to the Issuer interface on the device.
6. The Issuer interface redirects the consumer to the Token Requestor using the Token Requestor's proprietary communication method and pass issuer initiated digitization data as per their spec.
7. Token Requestor completes tokenization as per their BAU process.