# Enroll User to Click to Pay
source: https://developer.mastercard.com/mastercard-checkout-solutions/documentation/use-cases/push-prov/prov-click-to-pay/index.md

On the issuer's banking website or mobile application, consumer's can enroll in to Master Card Click to Pay in just a few clicks

## Benefits {#benefits}

###### Convenience {#convenience}

Streamlines traditional consumer checkout option found at ecommerce sites, by enrolling in Mastercard Click to Pay to check out with ease.

###### Security {#security}

Intelligent security based on EMVCo standards helps users provision tokenized cards so they can shop securely online.

###### Control {#control}

Load and manage Mastercard credentials from issuer's mobile banking app securely into one secure payment profile

#### Adding cards to Mastercard Click to Pay via Push Provisioning {#adding-cards-to-mastercard-click-to-pay-via-push-provisioning}

![Provision cards into SRC](https://static.developer.mastercard.com/content/mastercard-checkout-solutions/documentation/images/demo_provision_cards_src_returntoappR3.png)
Note:   
To enable cardholders to add their cards in Mastercard Click to Pay, issuers need to be enrolled in Mastercard Digital Enablement System (MDES) and should support the MDES Token Connect framework.   
For more information on how to integrate with MDES and MDES Token Connect framework, refer to [MDES for Financial Institutions](https://developer.mastercard.com/product/mdes/#financial-institutions) and [Push Provisioning with MDES Token Connect](https://developer.mastercard.com/mdes-digital-enablement/documentation/use-cases/push-provisioning-merchant-use-case/).

## Step 1. Present Mastercard Click to Pay {#step-1-present-mastercard-click-to-pay}

1. After the consumer logs into their mobile banking application or website, issuers can check if Mastercard Click to Pay is enabled for consumer's account range.
2. If eligible, then the issuer must inform the consumer about the ability to add their cards in Mastercard Click to Pay.
3. To learn more about the APIs used to present Mastercard Click to Pay for eligible accounts, refer to [Get Eligible Token Requestors](https://developer.mastercard.com/mdes-token-connect/documentation/) and [getAsset](https://developer.mastercard.com/mdes-token-connect/documentation/api-reference/).

<br />

Following is an example of how issuers can present Mastercard Click to Pay in their banking application: ![](https://static.developer.mastercard.com/content/mastercard-checkout-solutions/documentation/images/push_provisioning_show_src_onapp.png)

## Step 2. Consumer Selects Eligible Cards to Provision into Mastercard Click to Pay {#step-2-consumer-selects-eligible-cards-to-provision-into-mastercard-click-to-pay}

Issuers must allow consumers to add eligible cards into Mastercard Click to Pay.
Note: Consumers can provision only one card at a time. Provisioning of financial accounts into Mastercard Click to Pay is currently not supported.

1. Consumer selects the card they want to provision and consumer's choice is sent from the issuer's user interface to issuer's backend.
2. Issuer's backend triggers push provisioning by calling the [pushMultipleAccounts](https://developer.mastercard.com/mdes-token-connect/documentation/api-reference/) function in [MDES Token Connect API](https://developer.mastercard.com/mdes-token-connect/documentation/), The Token Requestor Identifier (TRID) for Click to Pay and the card details to be provisioned are passed as parameters to MDES.
3. The response from MDES includes a `pushAccountReceipt`, `signature` for the card being provisioned and Click to Pay URI for web browser experience.

![](https://static.developer.mastercard.com/content/mastercard-checkout-solutions/documentation/images/consumer_enroll_src_profile_add_cards.png) The current implementation supports the following experiences:
> * **App to Web** - communication on a mobile device (Android or iOS) between an issuer application and Click to Pay's web browser.
> * **Web to Web** - communication on the same device (mobile or desktop) between an issuer website and Click to Pay's web browser.

The following sequence shows the steps involved in issuer receiving the `pushAccountReceipt`, `signature` and`Click to Pay URI` when the consumer selects Click to Pay and the card to provision into Click to Pay.

## Step 3. Consumer is Sent to Mastercard Click to Pay {#step-3-consumer-is-sent-to-mastercard-click-to-pay}

* The [pushMultipleAccounts](https://developer.mastercard.com/mdes-token-connect/documentation/api-reference/) function returns `tokenRequestorSignatureSupport`, `callbackURL`, `pushAccountReceipt` and `signature` if `tokenRequestorSignatureSupport` is `true` and at least one pushAccountReceipt is successfully returned.

* Issuers then need to build the redirection URL, by appending the following query string parameters in the Click to Pay URI:`pushAccountData` or `pushAccountReceipt`,`callbackURL` and other parameters such as `completeIssuerAppActivation`,`completeWebsiteActivation`,`accountHolderDataSupplied` and `locale`.

* For more information on how to build the redirection URL, please refer to [Append Parameters to Token Requestor URI](https://developer.mastercard.com/mdes-token-connect/documentation/tutorials-and-guides/issuer-implementation-guide/).

**Use Case 1 : Passing pushAccountReceipt to Click to Pay**

1. Consumer selects a card from Issuer's app to push to Mastercard Click to Pay. Issuer sends one **pushAccountReceipt** to Mastercard Click to Pay. Multiple funding accounts are not supported by Click to Pay.
2. The Issuer calls [pushMultipleAccount](https://developer.mastercard.com/mdes-token-connect/documentation/api-reference/) and supplies account holder data along with the funding account information.
3. Issuer receives a **pushAccountReceipt** and the Click to Pay URI for web browser redirection in the [pushMultipleAccount](https://developer.mastercard.com/mdes-token-connect/documentation/api-reference/) response.
4. The Issuer builds the redirection URL that sends the Consumer to Mastercard Click to Pay.  

> * The locale information must be set, for example, `locale=en_US`.
> * The `extFlow=true` parameter must be included to enable the "Remember Me" experience.

Upon completion of push provisioning, Mastercard Click to Pay redirects the Consumer to the Issuer's app with tokenization results at the `https://partnerbank.com/tokenization-results` callbackURL.

**Example: Sample redirection URL sent out by Issuer:**

```curl
 https://src.mastercard.com/provision?pushAccountReceipts=MCC-STL-04FB7337-2308-4312-9433-C608BC1C391B&accountHolderDataSupplied=true&locale=en_US&completeIssuerAppActivation=false&completeWebsiteActivation=false&extFlow=true&callbackURL=https%3A%2F%2Fpartnerbank.com%2Ftokenization-results
```

Note: Issuers must pass **locale** information in the Click to Pay URI to provide a seamless experience for their consumers.

**Use Case 2 : Passing signature to Click to Pay**

1. The Issuer calls [pushMultipleAccount](https://developer.mastercard.com/mdes-token-connect/documentation/api-reference/) and provides the Consumer's data along with the information for one funding account. Multiple funding accounts are not supported by Click to Pay.
2. Issuer receives a **pushAccountReceipt** , **signature** , and the Click to Pay URI for web browser redirection in the [pushMultipleAccount](https://developer.mastercard.com/mdes-token-connect/documentation/api-reference/) response.
3. The Issuer builds the redirection URL that sends the Consumer to Mastercard Click to Pay.

> * Issuer needs to pass **signature** in the `pushAccountData` parameter for enhanced security.
> * The `extFlow=true` parameter must be included to enable the "Remember Me" experience.

Upon completion of push provisioning, Mastercard Click to Pay redirects the Consumer to the Issuer's app with tokenization results at the `https://partnerbank.com/tokenization-results` callbackURL.

**Example: Sample redirection URL sent out by Issuer:**

```curl
 https://src.mastercard.com/provision?pushAccountData=eyJhbGciOiJSUzI1NiIsImtpZCI6IjIwMjEwOTI3MDkxMzQwLU1ERVMtdG9rZW4tY29ubmVjdC1tdGYifQ.eyJwdXNoQWNjb3VudFJlY2VpcHRzIjpbIk1DQy1TVEwtREMzNTEyNkMtMjgwQS00MDc3LThGNDMtOEZDRDAwQUU3MjQxIl0sImNhbGxiYWNrVVJMIjoiaHR0cHM6Ly9zdGFnZS50b2tlbmNvbm5lY3QubWNzcmN0ZXN0c3RvcmUuY29tL3Rva2VuaXphdGlvbi1yZXN1bHRzIiwiY29tcGxldGVXZWJzaXRlQWN0aXZhdGlvbiI6dHJ1ZSwiYWNjb3VudEhvbGRlckRhdGFTdXBwbGllZCI6dHJ1ZSwibG9jYWxlIjoiZW5fVVMifQ.FFEJjbOoEiJV18lTGlnlvjDt-b7s4DvGef5WMq-Ncm1neh5PXE-srcqBt_01tvDgXcAN_izj_624KPeEBbQg_F2EZ5CDmKC0GLNbZhWuefv1gT9pGE0wX_-e6Nz7wF6X8vRXE8uaulz7g-30wYz-Ek4vjIc_rSESP2_oZFCxbPLq-FVTls2QA3x8DF_mH8GBAVNe2pkT-Eh_IsnQ5OhrG3liVVVeshNqxmUmMgSdNdf-m6s5WE_fCytQ_Jrf4gH-Vq3pZMifko7uYxYK5cz6OsZ1O7UA_Pyes8UCFYrMPI9M8iEdoav6tsfpXyCA9rmufEOa-YnREwc4swjgbtXDSA&extFlow=true
```

## Step 4. Consumer is Returned to the Issuer App or Website {#step-4-consumer-is-returned-to-the-issuer-app-or-website}

* Issuers that have supplied a `callbackURL` in the redirection URL expect Mastercard Click to Pay to send the consumer back to their app or website after provisioning the cards.
* When this is the case, Mastercard Click to Pay will also provide the result of the card provisioning.
* For more information on how to receive results from Mastercard Click to Pay, please refer to [Receive response from Integrator](https://developer.mastercard.com/mdes-token-connect/documentation/tutorials-and-guides/issuer-implementation-guide/#receive-response-from-token-requestor).

**Example:**

1. The Partner Bank has included a **callbackURL** in the redirection URL to Mastercard Click to Pay: `callbackURL=https%3A%2F%2Fpartnerbank.com%2Ftokenization-results`
2. Click to Pay has successfully tokenized **pushAccountReceipt** `MCC-STL-04FB7337-2308-4312-9433-C608BC1C391B`, creating a **token** with reference `DWSPMC000000000132d72d4fcb2f4136a0532d3093ff1a45`.  

   The Click to Pay website calls out the following URL to return the consumer back to the issuer:

```curl
https://partnerbank.com/tokenization-results?results%5BMCC-STL-04FB7337-2308-4312-9433-C608BC1C391B%5D=APPROVED%7CDWSPMC000000000132d72d4fcb2f4136a0532d3093ff1a45
```

## Next Steps {#next-steps}

A user can encounter different scenarios while provisioning their cards into Mastercard Click to Pay, refer to [Click to Pay - Issuer Provisioning Guide]() for more details.