> 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/step-4-approve-the-digitization-request.md).

# Step 4 – approve the digitization request

Approve (or reject) the digitization request. Return the step-up authentication options when needed.

### What happens in this step

The TSH backend asks the issuer backend to approve Tokenization for a card.

The request includes signals to support your decision:

* [Device information](/classic-tokenization/get-started/key-concepts/tokenization-decision/device-information.md) (not provided for e-commerce)
* [Scoring information](/classic-tokenization/get-started/key-concepts/tokenization-decision/scoring-information.md)

You return one of these decisions:

* **green**: Approve without **step-up authentication**.
* **yellow**: Approve with **step-up authentication**. Return an **ID\&V** method list.
* **red**: Decline Tokenization.

<figure><img src="/files/ADv8P33y133MDDvFZd0F" alt=""><figcaption><p>Digitization approval flow.</p></figcaption></figure>

See `requestCardDigitization` in the [API reference](/classic-tokenization/api-reference/issuer-gateway-api/outbound-to-issuer.md).

### Request parameters

| Parameter             | Required | Description                                                                                                                                                                                                                                              |
| --------------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `x-correlation-id`    | Required | Correlates the enrollment session. Use the same value received in `requestCardEligibility` (step 2).                                                                                                                                                     |
| `cipheredCardInfo`    | Required | Same value received in `requestCardEligibility` (step 2).                                                                                                                                                                                                |
| `authenticationValue` | Optional | Contains **CVV2** when provided by the token requestor. Encrypt it with `cipheredCardInfo` using the issuer public key (PKCS#7). In practice, token requestors provide it when the end user entered card details manually or captured them from a photo. |

### Response parameters

| Parameter       | Required            | Description                                                                                                               |
| --------------- | ------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| `levelOfTrust`  | Required on success | Decision for this digitization request: `green`, `yellow`, or `red`.                                                      |
| `idvMethodList` | Conditional         | Return only when `levelOfTrust` is `yellow`. The list defines the available **ID\&V** methods for step-up authentication. |

### Decisioning guidance

* Use the device and scoring signals to select `green`, `yellow`, or `red`.
* When returning `yellow`, include only the step-up methods you can support end-to-end.
* Stop the enrollment flow when returning `red`. Show a decline message to the end user.

### Next step

Continue to [Step 5 – activate the token](/classic-tokenization/use-cases/card-enrolment/generic-enrollment-flow/step-5-activate-the-token.md).

If you returned `yellow`, the end user completes step-up authentication using one of these paths:

* [Option B: activate with SMS or email OTP](/classic-tokenization/use-cases/card-enrolment/generic-enrollment-flow/step-5-activate-the-token/option-b-activate-with-sms-or-email-otp.md)
* [Option C – activate in the issuer application](/classic-tokenization/use-cases/card-enrolment/generic-enrollment-flow/step-5-activate-the-token/option-c-activate-in-the-issuer-application.md)
* [Option D – activate via customer service](/classic-tokenization/use-cases/card-enrolment/generic-enrollment-flow/step-5-activate-the-token/option-d-activate-through-customer-service.md)


---

# 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/step-4-approve-the-digitization-request.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.