> 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-3-present-terms-and-conditions.md).

# Step 3 – present terms and conditions

Present the terms and conditions to the end user. Capture their consent before Tokenization.

### What happens in this step

The token requestor presents the terms and conditions.

The payment network **TSP** provides them (for example, **VTS** or **MDES**).

The end user reviews and accepts them in the wallet application or issuer application.

### Who does what

* **Token requestor**
  * Display the terms and conditions to the end user.
  * Capture an explicit accept/decline action.
  * Stop the enrollment flow if the end user declines.
* **Issuer backend**
  * Ensure the right configuration is used in step 2 (for example, by returning `productId`).
  * Do not approve the digitization request until consent is captured.

### Implementation notes

* The token requestor defines the rendering rules.
* The payment network TSP defines the content format.
* Treat consent as a required precondition for the digitization approval step.

### Next step

After consent is captured, continue to [Step 4 – approve the digitization request](/classic-tokenization/use-cases/card-enrolment/generic-enrollment-flow/step-4-approve-the-digitization-request.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.payments.thalescloud.io/classic-tokenization/use-cases/card-enrolment/generic-enrollment-flow/step-3-present-terms-and-conditions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.