# Pull Provisioning from Wallet
source: https://developer.mastercard.com/mdes-token-connect/documentation/use-cases/pull-from-wallet/index.md

Available for Use By:

* Issuers,
* Token Requestors

Regional Availability:

* Global

## Scenario {#scenario}

Susan opens her digital wallet app to view a list of eligible issuers that support digital card provisioning on her device. If an eligible issuer app is detected on her device, it automatically opens when she selects the issuer. If not, she's redirected to the issuer's website for authentication and card selection. This new pull provisioning functionality enables Susan to digitize her cards directly through the issuer's app, eliminating the need to manually enter card details.

![alt text](https://static.developer.mastercard.com/content/mdes-token-connect/documentation/use-cases/img/pull_provisioning_image_new.png "Scenario")
Note: Token Connect Pull Provisioning currently supports only MDES for Devices (M4D) Token Requestors. Secure Card on File (SCOF) and MDES for Merchants (M4M) merchants are not included currently.

## Pre-requisite {#pre-requisite}

* Consumer sign-in to the mobile banking app.

## User Experience {#user-experience}

1. [Consumer views eligible issuers supporting digital card provisioning on the device.](https://developer.mastercard.com/mdes-token-connect/documentation/use-cases/pull-from-wallet/index.md#show-eligible-issuers-and-cardholder-selects-issuer-to-fetch-card-details)
2. [Fetches and open selected issuer app or redirects to website for authentication.](https://developer.mastercard.com/mdes-token-connect/documentation/use-cases/pull-from-wallet/index.md#issuer-authenticates-the-cardholder-and-display-eligible-list-of-cards)
3. [Consumer selects card for digitization via issuer app.](https://developer.mastercard.com/mdes-token-connect/documentation/use-cases/pull-from-wallet/index.md#cardholder-selects-the-card-for-tokenization)

### Show eligible issuers and cardholder selects issuer to fetch card details {#show-eligible-issuers-and-cardholder-selects-issuer-to-fetch-card-details}

Wallet obtains the eligible list of issuers from Mastercard, where the cardholder can select from available cards for provisioning.

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

#### Integration {#integration}

Diagram pull_provisioning_flow_fetch_eligi_issuer_list

1. Wallet sends a request to MDES to retrieve a list of eligible issuers.
2. MDES provides the list along with the following details for each issuer:
   * **Logo**: An image representing the issuer.
   * **Name**: The issuer's display name.
   * **URI**: A redirect URL leading to the issuer's app or web portal for authentication.
   * **Country Code**: The issuer's country represented using the ISO 3166-1 alpha-2 format (for example, "US" for the United States, "IN" for India).
3. Cardholder selects the required issuer.

### Issuer authenticates the cardholder and display eligible list of cards {#issuer-authenticates-the-cardholder-and-display-eligible-list-of-cards}

Once the cardholder selects their issuer, the wallet redirects them to the issuer's authentication flow. The cardholder is authenticated in the Issuer App which is provided by the Wallet app. This results display of eligible list of cards.

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

#### Integration {#integration-1}

Diagram pull_provisioning_integration_flow

1. The cardholder initiates authentication through the issuer's app or web portal using the following information:
   * **Session ID**: A unique identifier for the current provisioning session.
   * **TRID (Token Requestor ID)**: Identifies the wallet or digital service requesting the token.
   * **Wallet Callback URL**: A URL provided by the wallet where the issuer should redirect the cardholder after successful authentication.
2. Upon successful authentication, the issuer displays the list of cards eligible for provisioning.

### Cardholder selects the card for Tokenization {#cardholder-selects-the-card-for-tokenization}

The user selects the specific card they wish to add to their digital wallet from the list of eligible cards. Once the selection is made, the standard card provisioning process---commonly referred to as Business-As-Usual (BAU) provisioning---continues seamlessly. During this process, the card is securely tokenized and added to the wallet, enabling the user to make contactless payments and perform other digital transactions using their device.

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

#### Integration {#integration-2}

Diagram pull_provisioning_flow_selc_card_tokenization

1. The issuer UI sends a request to the issuer backend to push the selected card. This includes:
   * Session ID
   * Wallet Callback URL
   * FPAN (Full Primary Account Number)
2. The issuer sends the card data to MDES for tokenization. This includes:
   * FPAN
   * TRID (Token Requestor ID)
3. MDES responds with a Push Account Receipt. This includes:
   * Signature Data
   * Tokenization Metadata
4. The issuer UI prepares the response and redirects back to the wallet.
5. The user is redirected back to the wallet app with the push account receipt.
6. The wallet verifies the push account receipt with MDES.