> For the complete documentation index, see [llms.txt](https://docs.caf.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.caf.io/caf-api/connect/available-resources/transaction.md).

# Transaction

When you submit a query to the Anti-Fraud services, you create a Transaction. A transaction may contain the execution of one or more services configured in the query model or informed in the request body. These services may be internal analyses or external queries that are performed on the processing conveyor. After that, based on validation rules, the status is set for the transaction.

{% hint style="info" %}
*Services and validation rules can be configured only in the query template.*
{% endhint %}

A transaction is characterized by an endpoint where the required services can be informed and a set of rules validated.

{% hint style="info" %}
**Related documentation:**

* If you use Certta SDKs and need to link mobile tokens with transactions, access [Transaction linking](/caf-api/connect/transactions/transaction-linking.md)
* To understand the structure and services available in transaction responses, access [Transactions](/caf-api/connect/transactions.md)
  {% endhint %}

{% hint style="info" %}
**Transaction webhooks:** Transactions created directly through `POST /transactions` do not emit `TRANSACTIONPROCESSSTARTEDEVENT`. Use the transaction `id` returned by the creation request to correlate subsequent `TRANSACTIONSTATUSUPDATEDEVENT` and related events. See [Webhook Events](/caf-api/connect/webhook/events.md).
{% endhint %}

For details on authentication, access [Authenticating](/caf-api/connect/authentication/authenticating.md).

{% hint style="info" %}
**Authentication Requirements:**

* Regular endpoints use `OAuth2` authentication with base URL: `https://api.us.prd.caf.io`
* For enhanced security, some endpoints may also support `mTLS` authentication with base URL: `https://mtls.us.prd.caf.io`
* For information on implementing `mTLS`, access [Using mTLS](/caf-api/connect/authentication/using-mtls.md)
  {% endhint %}

## Supported endpoints

{% openapi src="/files/0h3YuWQJnj9hUFn19UQD" path="/" method="post" %}
[transactions-create.yaml](https://3218940882-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVxCOSyBojfSIE5fcpfH%2Fuploads%2Fgit-blob-b984301a8dba75b66948b310be0dbfca1f0b54b6%2Ftransactions-create.yaml?alt=media)
{% endopenapi %}

{% openapi src="/files/hhTdvSA39Z50BzG4sc0y" path="/files" method="post" %}
[transactions-files.yaml](https://3218940882-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVxCOSyBojfSIE5fcpfH%2Fuploads%2Fgit-blob-9e76c6b41d136390c25c0ec9876949c28e9e972c%2Ftransactions-files.yaml?alt=media)
{% endopenapi %}

{% openapi src="/files/7uwORj881sSekzC56Mu7" path="/" method="get" %}
[transactions-get-list.yaml](https://3218940882-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVxCOSyBojfSIE5fcpfH%2Fuploads%2Fgit-blob-4262575b9aecaefb412baa51866ba1335a7da360%2Ftransactions-get-list.yaml?alt=media)
{% endopenapi %}

{% openapi src="/files/XNtvc596walCnuDRTzl8" path="/{transactionId}" method="get" %}
[transactions-get-one.yaml](https://3218940882-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVxCOSyBojfSIE5fcpfH%2Fuploads%2Fgit-blob-cbe1ea142ff4ad47d25a3dcdd408cf3b554968ce%2Ftransactions-get-one.yaml?alt=media)
{% endopenapi %}

{% hint style="info" %}
Ensure your `OAuth2` client has the necessary permissions for each endpoint. Permissions are managed in **Trust**. Requests without proper permissions will result in a **`403 Forbidden`** error.
{% endhint %}


---

# 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.caf.io/caf-api/connect/available-resources/transaction.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.