> For the complete documentation index, see [llms.txt](https://docs.payments.thalescloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payments.thalescloud.io/classic-tokenization/use-cases/card-enrolment/generic-enrollment-flow.md).

# Generic enrollment flow

### Green flow enrollment

In a *green flow* enrollment, the **Issuer** decides to digitize a card through the payment network **TSP** (for example, **VTS** or **MDES**) without **step-up authentication** of the **end user**.

The digitization process is:

<figure><img src="/files/h7hOXM8fl87j7a8BYTCC" alt=""><figcaption><p>Green flow enrollment (no step-up authentication).</p></figcaption></figure>

### Yellow flow enrollment

In a *yellow flow* enrollment, the **Issuer** decides to digitize a card through the payment network **TSP** (for example, **VTS** or **MDES**) with **step-up authentication** of the **end user**.

The step-up authentication method is also called an **ID\&V** (identification and verification) method.

#### SMS or email OTP step-up authentication

The **Issuer backend** sends an **OTP** generated by the payment network TSP to the end user. This OTP proves the end user’s identity and authorizes digitization.

<figure><img src="/files/Oxm7viwlLrmPYWDA6TpF" alt=""><figcaption><p>Yellow flow enrollment using SMS or email OTP.</p></figcaption></figure>

#### Issuer application step-up authentication

The end user is redirected from the wallet application to the **issuer application**. The end user then authenticates using their eBanking credentials.

<figure><img src="/files/lpR94BDCBRQmZ7hcUqZ9" alt=""><figcaption><p>Yellow flow enrollment using the issuer application.</p></figcaption></figure>

#### Customer service step-up authentication

If the end user selects the **Customer service** option, they are redirected to the call center and must identify themselves.

Customer service uses `getCardInfo` to identify the pending virtual card. Customer service then sends an `updateCard` request to resume the virtual card flow.

<figure><img src="/files/dkK79XFtXmsYRqq5UvCe" alt=""><figcaption><p>Yellow flow enrollment using customer service.</p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.payments.thalescloud.io/classic-tokenization/use-cases/card-enrolment/generic-enrollment-flow.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.