# Card Enrollment
source: https://developer.mastercard.com/mastercard-agent-pay/documentation/use-cases/card-enrollment/index.md

Before participating in Agent Pay transactions, a cardholder must complete a one-time card enrollment process. During enrollment, the Agentic Commerce Provider (ACP) tokenizes the payment credential, verifies the cardholder's identity, and obtains a Level 1 (L1) Selective Disclosure JWT that represents the authenticated user.

Once completed, the tokenized payment credential and L1 SD-JWT can be reused across future Agent Pay transactions, eliminating the need for repeated enrollment.

### Benefits {#benefits}

Card Enrollment enables ACPs to:

* Tokenize payment credentials using Mastercard's trusted tokenization infrastructure.
* Verify cardholder identity through Mastercard authentication services.
* Establish a reusable user identity for Verifiable Intent registration.
* Support frictionless future transactions by eliminating the need for repeated enrollment.
* Optionally register a Mastercard Payment Passkey during identity verification.

Diagram card-enrollment

The following steps break down the card enrollment process.

## Step 1: Capture Card Details {#step-1-capture-card-details}

The cardholder provides their payment card details to the Agentic Commerce Provider (ACP).

## Step 2: Tokenize the Card {#step-2-tokenize-the-card}

The ACP calls the Mastercard Checkout Solutions (MCS) Card Enrollment API to tokenize the card using the existing Agent Pay and Secure Card on File (SCOF) tokenization flow.

## Step 3: Receive Token Reference {#step-3-receive-token-reference}

Upon successful tokenization, MCS returns a response containing a srcDigitalCardId. The ACP stores this identifier and uses it to reference the tokenized credential in future Agent Pay interactions.

## Step 4: Initiate Cardholder Verification {#step-4-initiate-cardholder-verification}

The ACP calls the MCS Authentication APIs to start cardholder Identification and Verification (ID\&V).

## Step 5: Display Authentication Experience {#step-5-display-authentication-experience}

The ACP presents the Mastercard authentication experience to the cardholder.

## Step 6: Verify Identity {#step-6-verify-identity}

The cardholder completes the verification process and may optionally register a Mastercard Payment Passkey during this step.

## Step 7: Receive Authentication Result {#step-7-receive-authentication-result}

After verification is completed, MCS returns control to the ACP.

## Step 8: Generate the User L1 SD-JWT {#step-8-generate-the-user-l1-sd-jwt}

The ACP calls the MCS Authentication APIs to generate a Level 1 (L1) SD-JWT for the authenticated user.

## Step 9: Receive User Credential {#step-9-receive-user-credential}

MCS returns the L1 SD-JWT to the ACP.

The ACP can subsequently use this L1 SD-JWT when creating Verifiable Intents for Agent Pay transactions.

### Enrollment Outcome {#enrollment-outcome}

After enrollment, the ACP has:

* A tokenized payment credential that can be used in future Agent Pay transactions.
* A verified cardholder identity.
* A reusable L1 SD-JWT for Verifiable Intent registration and transaction processing.
* The ability to support future purchases without requiring the cardholder to repeat the enrollment process.

Note: The L1 SD-JWT has a default validity period of one year and can be reused across multiple Agent Pay transactions without requiring the cardholder to repeat the enrollment process.

## Next Steps {#next-steps}

Now that you've enrolled your card, you can explore the [Agentic Transaction Flow](https://developer.mastercard.com/mastercard-agent-pay/documentation/use-cases/agentic-transaction/index.md) section to follow the Agent Pay transaction flow.