# Issuer Enablement for Digital Commerce Experiences
source: https://developer.mastercard.com/issuer-enrollment/documentation/index.md

Issuer Enablement for Digital Commerce Experiences provides APIs that issuers and their service providers can use to create and manage digital payment credentials within Mastercard Credential Services. Once enabled, cardholders can discover and securely use an eligible payment credential across supported Digital Commerce Experiences without manually entering their card number. Network tokenization protects the underlying card information, and supported authentication options provide a foundation for strong cardholder authentication.

Issuers and service providers can integrate these capabilities into their applications and account management processes. The service supports issuer-initiated auto enablement, cardholder-initiated push provisioning, individual and batch enablement, and credential and profile lifecycle management. Issuers can also allow cardholders to create Mastercard payment passkeys through issuer channels and use device biometrics to authenticate during Click to Pay checkout, reducing friction and helping protect against fraud.

Supported Digital Commerce Experiences currently include Click to Pay, Card Add, Agentic Commerce, and Money Movement. Available capabilities vary by experience and are subject to applicable program rules, technical requirements, and regional availability.

## How it Works {#how-it-works}

While enabling credentials, issuers or their service providers connect to Mastercard Credential Services using various enrollment and lifecycle APIs that allow them to enroll their cardholder credentials and create a consumer profile.

![Issuer Enablement](https://static.developer.mastercard.com/content/issuer-enrollment/documentation/img/Issuer_Enablement_Flow.png "Mastercard Credential Directory Auto Enablement for Issuers")

1. **Enablement use cases:** An issuer identifies a new or existing consumer with a new or existing account as eligible for a supported Digital Commerce Experience.
2. **Technical enablement:** The issuer or its service provider uses the Issuer Enablement APIs to enable a single credential or process multiple credentials in a batch.
3. **Post enablement:** The consumer can use the enabled credential at checkout and in other supported Digital Commerce Experiences. Consumers can also keep their information and payment credentials current using the digital channels the issuer provides.

* **Issuer processor:** Performs enablement and credential lifecycle operations on an issuer's behalf, where delegated.
* **Service provider:** Integrates and uses Issuer Enablement capabilities to enable consumers, manage profiles and credentials, and support Digital Commerce Experiences through banking applications, self-service channels, and other issuer-facing solutions.
* **Mastercard Credential Services:** Tokenizes cards, hosts the credential directory, and enables credentials for supported experiences.
* **Consumer (Cardholder):** Discovers and uses the enabled credential at checkout, and may create a payment passkey.
After successful enablement:

* Mastercard Credential Services creates or updates the consumer profile and digital payment credential.
* The credential is enabled for applicable Digital Commerce Experiences.
* Supported experiences can find the credential using cardholder identifiers such as an email address or phone number.
* The cardholder can use the credential without entering the card number manually.
* Network tokenization helps protect the underlying card information.
* The cardholder can create or use a Mastercard payment passkey where supported.

## Good to Know {#good-to-know}

Before you begin your integration, review the following information:

* **Onboarding:** Onboard through Mastercard Connect: request the Mastercard Checkout Solutions app, enroll in the Issuer Enablement program, create a project, and generate your keys. View the [issuer onboarding steps](https://developer.mastercard.com/issuer-enrollment/documentation/tutorials-and-guides/index.md#issuer-onboarding).
* **Testing:** Use the sandbox to test API requests and validate your integration before moving to production. Review the [integration and testing guidance](https://developer.mastercard.com/issuer-enrollment/documentation/testing/index.md). Use the [Batch Enroll API](https://developer.mastercard.com/issuer-enrollment/documentation/use-cases/auto-enrollment/enroll_api_async/index.md) to submit multiple records and the [Batch Status API](https://developer.mastercard.com/issuer-enrollment/documentation/use-cases/auto-enrollment/batch_status/index.md) to monitor the results.
* **Regional availability:** Availability varies by market, program, and digital payment experience. Confirm the supported regions and capabilities with your Mastercard representative.

## Enablement Options {#enablement-options}

Mastercard Credential Services offers two mechanisms for enrolling consumers: Issuer auto enablement and push provisioning.

### Auto Enablement {#auto-enablement}

[Auto enablement](https://developer.mastercard.com/issuer-enrollment/documentation/use-cases/auto-enrollment/index.md) allows issuers or their service providers to add eligible cardholder information including their payment credentials into an issuer's designated partition, reffered to as the **Issuer Credential Directory**. Mastercard safeguards the data and applies applicable data, security, and privacy requirements when processing cardholder lookup, tokenization, usage and lifecycle events.

Auto enablement supports the following enrollment methods and lifecycle management APIs:

* **[Synchronous enablement](https://developer.mastercard.com/issuer-enrollment/documentation/use-cases/auto-enrollment/enroll_api_sync/index.md)** - Enable a single cardholder profile or credential and receive the processing result in the API response.
* **[Asynchronous (batch) enablement](https://developer.mastercard.com/issuer-enrollment/documentation/use-cases/auto-enrollment/enroll_api_async/index.md)** - Submit multiple cardholder and credential records for asynchronous processing and retrieve the processing status separately.
* **[Lifecycle management](https://developer.mastercard.com/issuer-enrollment/documentation/use-cases/auto-enrollment/life_cycle/index.md)** - Retrieve, update, or delete existing consumer profiles and credentials.

<br />

Key features:

#### Data ownership and processing {#data-ownership-and-processing}

Issuers retain full ownership and control over the data within their designated partitions. Mastercard processes data strictly in accordance with the agreed contractual terms between Mastercard and the issuer.

#### Directory profile management {#directory-profile-management}

Issuers manage their directory data through Issuer Enablement APIs. Mastercard may perform directory operations on the issuer's behalf where the applicable agreement supports that arrangement.

#### Terms and conditions {#terms-and-conditions}

The directory operation aligns with the terms and privacy policies agreed upon by the Issuer and Mastercard under the contractual agreement.

### Push Provisioning {#push-provisioning}

[Push provisioning](https://developer.mastercard.com/issuer-enrollment/documentation/use-cases/push-provisioning/index.md) is a cardholder-initiated process. The cardholder selects an eligible payment card through an issuer-provided application or website and chooses to add it to a supported digital payment experience.

Push provisioning enables a single cardholder credential at a time and supports issuer-controlled enablement journeys.

Key features:

#### Simplify {#simplify}

Push tokenized payment credentials into Mastercard Digital Enablement Service (MDES)-enabled merchants, issuer wallets, third-party wallets, and devices.

#### Customize {#customize}

For issuers, use Mastercard APIs to shape the user experience and extend the functionality of your existing solution.

#### Secure {#secure}

For integrators, validate that you're receiving unaltered data from legitimate issuers using signature support.
Note: Push provisioning does not currently support Money Movement. Mastercard plans to add this capability in a future release.

## Mastercard Payment Passkeys {#mastercard-payment-passkeys}

A Mastercard payment passkey is a secure, user-friendly way to authenticate online transactions using familiar biometric methods like fingerprint or face recognition.

Issuers offer cardholders the option to create a Mastercard payment passkey through their digital channels at participating Click to Pay merchants.

Key features:

#### Added security and convenience {#added-security-and-convenience}

Mastercard's multi-factor authentication method uses the passkeys already available on a consumer's device. Consumers create a payment passkey with Mastercard and use it to perform biometric authentication across all merchants and checkout options.

#### Improved transaction quality {#improved-transaction-quality}

Transactions authenticated with Mastercard payment passkeys, compliant with our Token Authentication Framework, include enriched data such as Authentication Data, Advanced Digital Transaction Data and Digital Transaction Insights​.

#### Enhanced issuer controls {#enhanced-issuer-controls}

Receive a unique device identifier for each device bound to the payment passkey at the time of creation and each time the passkey is used for transaction authentication​.

## Who This is For {#who-this-is-for}

|       Audience        |                                                                                                      What they do with Issuer Enablement                                                                                                       |
|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| **Issuers**           | Enable eligible payment credentials and manage consumer profiles and credentials across supported Digital Commerce Experiences.                                                                                                                |
| **Issuer processors** | Perform enablement and credential lifecycle operations on an issuer's behalf.                                                                                                                                                                  |
| **Service providers** | Use Issuer Enablement APIs to enable consumers, manage profiles and credentials, and support Digital Commerce Experiences on behalf of clients. Incorporate enablement capabilities into banking applications and other self-service channels. |

## Next Steps {#next-steps}

#### Quick start {#quick-start}

Set up your environment, generate keys, and make your first Issuer Enablement API call.

[Begin the Issuer Enablement quick start](https://developer.mastercard.com/issuer-enrollment/documentation/quick-start-guide/index.md)

#### Onboarding steps {#onboarding-steps}

Follow the steps to onboard your institution for auto enablement and push provisioning.

[View the issuer onboarding steps](https://developer.mastercard.com/issuer-enrollment/documentation/tutorials-and-guides/index.md)

#### API basics {#api-basics}

Review core API concepts, authentication, and integration prerequisites.

[Read the API basics guide](https://developer.mastercard.com/issuer-enrollment/documentation/api-basics/index.md)

#### API reference {#api-reference}

Browse endpoint documentation, request/response schemas, and error codes.

[Open the API reference](https://developer.mastercard.com/issuer-enrollment/documentation/api-reference/index.md)

#### Use cases {#use-cases}

Explore Issuer Enablement scenarios such as auto enablement, push provisioning, and passkey registration.

[Explore Issuer Enablement use cases](https://developer.mastercard.com/issuer-enrollment/documentation/use-cases/index.md)

#### Integration and testing {#integration-and-testing}

Test your integration in the sandbox and validate it before go-live.

[See integration and testing methods](https://developer.mastercard.com/issuer-enrollment/documentation/testing/index.md)