# Push Provisioning for Issuers
source: https://developer.mastercard.com/mastercard-checkout-solutions/documentation/use-cases/push-prov/index.md

## Overview {#overview}

Cardholders can enroll in Mastercard Checkout Solutions via Push Provisioning within their issuer's banking application or website in just a few clicks. Once enrolled, consumers can easily pay without manually entering their card details or a password when they see the payment icon where Mastercard is accepted and save the Mastercard on file by leveraging tokenization capabilities.

## Use Cases {#use-cases}

|                                                                                       Use Cases                                                                                       |                                              Description                                              |
|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------|
| [**Enroll User to Click to Pay**](https://developer.mastercard.com/mastercard-checkout-solutions/documentation/use-cases/push-prov/prov-click-to-pay/index.md)                        | Enroll a user in to Click to Pay for faster checkouts                                                 |
| [**Saving Card on File using Push Account Receipt**](https://developer.mastercard.com/mastercard-checkout-solutions/documentation/use-cases/push-prov/scof-push-acc-receipt/index.md) | Enroll a card into Secure Card on File to generate a relevant token for the PAN during a transaction. |

### Prerequisite {#prerequisite}

* **Mastercard Digital Enablement** - Issuers must be enrolled in [Mastercard Digital Enablement (MDES)](https://developer.mastercard.com/product/mdes/#financial-institutions)to activate payment cards to receive token requests from Mastercard Secure Remote Commerce.
* Issuers must perform strong cardholder authentication prior to initiating Mastercard Click to Pay push provisioning and not request additional cardholder authentication during push provisioning.
* To learn about the requirements and best practices for issuers to participate in the Mastercard Checkout Solutions, refer to the Issuer Requirements section in [Mastercard Secure Remote Commerce Program Requirements](https://techdocs.mastercard.com/bundle/mc_click_to_pay_reqs/page/rfh1615997307367.html) document available in the [Technical Resource Center](https://techdocs.mastercard.com/). To access the document, ensure you are logged into Mastercard Connect.

### Regional Availability {#regional-availability}

|             Region              |                                                 Country                                                  |
|---------------------------------|----------------------------------------------------------------------------------------------------------|
| North America                   | Canada, United States                                                                                    |
| Europe                          | United Kingdom, Spain, Sweden, Ireland, Italy, Netherlands, Switzerland, Germany, Norway, Czech Republic |
| Asia Pacific                    | New Zealand, Australia, Singapore, Hong Kong, Malaysia                                                   |
| Middle East and Africa          | United Arab Emirates, Qatar, Kuwait, Saudi Arabia, South Africa                                          |
| Latin America and the Caribbean | Mexico, Brazil, Argentina, Colombia                                                                      |

## APIs {#apis}

|         Region         |                                                                                                                                                                                                  Country                                                                                                                                                                                                   |
|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| **MDES Token Connect** | The [MDES Token Connect API](https://developer.mastercard.com/mdes-token-connect/documentation/) provides a set of inbound web requests to allow issuers to securely push account information to token requestors.                                                                                                                                                                                         |
| **Push Account**       | The [pushAccount](https://developer.mastercard.com/mdes-token-connect/documentation/) API allows issuers to push an eligible card to Mastercard Click to Pay. Issuers allowing consumers to add cards to Mastercard Click to Pay must send all relevant account holder Personally Identifiable Information (PII) using the **pushAccount** API in order to provide a seamless experience for the consumer. |

### Next {#next}

Review [Use Cases](https://developer.mastercard.com/mastercard-checkout-solutions/documentation/use-cases/push-prov/index.md#use-cases) to learn how as an issuer you can allow your consumers to provision cards in Mastercard Checkout Solutions for Click to Pay and Card on File.