# Enroll API
source: https://developer.mastercard.com/issuer-enrollment/documentation/use-cases/push-provisioning/enroll-api/index.md

## Enrollment Steps {#enrollment-steps}

Ensure to read the [pre-requisites](https://developer.mastercard.com/issuer-enrollment/documentation/getting-started/index.md#before-you-start) before the enrollment steps.

#### Step 1. Issuer prompts cardholder to enroll in Click to Pay {#step-1-issuer-prompts-cardholder-to-enroll-in-click-to-pay}

Once cardholder logs into with the Issuer (app/website) they are presented the option to enroll in Click to Pay.

#### Step 2. Cardholder selects the card to add in Click to Pay. {#step-2-cardholder-selects-the-card-to-add-in-click-to-pay}

Cardholder reviews the pre-populated data and provides consent.

#### Step 3. Cardholder's card is enrolled in Click to Pay {#step-3cardholders-card-is-enrolled-in-click-to-pay}

Enroll cardholder into Click to Pay using the [Enroll API-Synchronous](https://developer.mastercard.com/issuer-enrollment/documentation/api-reference/apis/index.md#enroll-api-synchronous), following either of the 2 methods:
1. Call [Enroll API - Synchronous](https://developer.mastercard.com/issuer-enrollment/documentation/api-reference/apis/index.md#enroll-api-synchronous) to enroll consumers into Click to Pay.
2. Pass the `encryptedCard` object where the card must be encrypted using these [request parameters](https://developer.mastercard.com/mastercard-checkout-solutions/documentation/sdk-reference/enroll-card/#request-parameters).
3. Click to Pay calls MDES for tokenizing the card with `encryptedCard` object, and Issuer approves the tokenization request.
4. Click to Pay receives the tokenization response, enrolls the card, creates the profile, and responds back to the Issuer with the [Enroll API response](https://developer.mastercard.com/issuer-enrollment/documentation/api-reference/apis/index.md#enroll-api-synchronous).
5. To push provision in Click to pay using PAN based enrollment, Issuer must ensure to pass [Terms and Conditions](https://www.mastercard.com/global/click-to-pay/country-listing/terms.html) and [Privacy Policy](https://www.mastercard.com/global/click-to-pay/country-listing/privacy.html) URLs as part of compliance settings.
1. While calling Enroll API ensure to provide Consumer's first name, last name, email, phone number, [Terms and Conditions](https://www.mastercard.com/global/click-to-pay/country-listing/terms.html) and [Privacy Policy](https://www.mastercard.com/global/click-to-pay/country-listing/privacy.html) URLs.
2. Call `pushMultipleAccount` endpoint with card and billing information to get `pushAccountReceipt` from MDES Token Connect.
3. Call [Enroll API](https://developer.mastercard.com/issuer-enrollment/documentation/api-reference/apis/index.md#enroll-api-synchronous) and pass `pushAccountReceipt` within `EnrolmentReferenceData` to enroll consumers in Click to Pay.
4. Click to Pay calls MDES for tokenizing the card with `pushAccountReceipt` object, and Issuer tokenizes the card.
5. Click to Pay receives the tokenization response, enrolls the card, creates the profile and responds back to the Issuer with the [Enroll API response](https://developer.mastercard.com/issuer-enrollment/documentation/api-reference/apis/index.md#enroll-api-synchronous).

Note: If using Enroll API for PUSH_ACCOUNT_RECEIPT based enrollment, it's a pre-requisite to call `GetEligibleTokenRequestors` endpoint, and `GetAsset` endpoint from the [MDES Token Connect API](https://developer.mastercard.com/mdes-token-connect/documentation/api-reference/) to present Click to Pay in the Issuer app/website.   
Diagram consumer-is-enrolled

#### **URLs for Compliance Settings** {#urls-for-compliance-settings}

Issuer must refer to the static [Terms and Conditions](https://www.mastercard.com/global/click-to-pay/country-listing/terms.html), and [Privacy Policy](https://www.mastercard.com/global/click-to-pay/country-listing/privacy.html) URLs as part of the `ComplianceSettings` object during enrollment in Click to Pay.

It is recommended to pass the `locale` at the end of the URL, which allows Consumers to directly view the Click to Pay Terms and Privacy Policies in that language.

Use the following URI where xx is the ISO-639 language code and YY is the ISO-3166 format country code.

```curl
https://www.mastercard.com/global/click-to-pay/country-listing/privacy.html?locale=xx_YY
```

```curl
https://www.mastercard.com/global/click-to-pay/country-listing/terms.html?locale=xx_YY
```

<br />

## User Experience {#user-experience}

To initiate push provisioning, Issuers can present Click to Pay on the banking app/website through a selected interface.

Following are the examples of how Click to pay can appear in the banking app/website:

### Click to Pay Button {#click-to-pay-button}

Tip: Position the **Click to Pay** button at parity with other digital wallet enrollment options.

![Click to Pay button](https://static.developer.mastercard.com/content/issuer-enrollment/documentation/img/click-to-pay-button-r5.png "Click to Pay button")

### Click to Pay In-App Banner {#click-to-pay-in-app-banner}

Tip: In-app banners help achieve up to 6 times the volume of Click to Pay Push Provisioning, while also increasing the overall conversion rate.

![Click to Pay banner](https://static.developer.mastercard.com/content/issuer-enrollment/documentation/img/banner-r5.png "Click to Pay banner")
Note: The UX images used in the documentation are for illustration purpose only. Contact a Mastercard representative for more information.