> 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/transaction-control/implement-transaction-control.md).

# Implement Transaction Control

## Transaction Control Service

The Transaction Control service enhances the capabilities of existing legacy Authorisation Host servers by offering advanced features to improve user experience. Here are some of the key features:

### Features

* **Dynamic CVV2**: Enhances eCommerce security by supporting one-time-use CVV2, dynamically generated and displayed in the banking mobile application.
* **Domain Controls**: Allows for additional authorization controls performed by D1, which can be activated or deactivated in real-time by the issuer or the end user.
* **Spending Limits**: Enables spending limit controls by D1 during authorization processing. Limits can be updated in real-time by the issuer or the end user.

### Integration Model

The Transaction Control service is designed so that the issuer's legacy authorisation host manages the global authorization flow, while some additional controls are handled by D1. 

<figure><img src="/files/eggpnvnQFZ2BGsPdPz6x" alt=""><figcaption></figcaption></figure>

D1 performs specific EMV controls such as:

* Card PIN
* Dynamic CVV
* Domain Control
* Spending Limits

The issuer's Authorisation Host is responsible for other card controls. D1 provides the flexibility to define extra controls per card product.

To explore additional features, continue with the following pages:

* Dynamic CVV
* Domain Controls
* Spending Limits

**Authorization Sequence Diagram**

<figure><img src="/files/xT3yeBQesuwoglP0wVGb" alt=""><figcaption></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/transaction-control/implement-transaction-control.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.