> 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/transactions/transaction-linking.md).

# Transaction linking

For clients using Certta SDKs who subsequently create transactions to perform additional validations, it is crucial to link the session tokens with these transactions to ensure full traceability of the user journey.

{% hint style="warning" %}
This process applies exclusively to clients who use both the SDK for a user session and the API for subsequent validations. If you only use our APIs directly, this step is not necessary.
{% endhint %}

This linkage is done by sending the **Mobile Token** (Session Token) at the time of transaction creation. Specifically, include the mobile token in the request body using the parameter `referenceToken` when calling the endpoint.

Check out [Transaction Creation Integration](/caf-api/connect/available-resources/transaction.md) for more details on how to create transactions.

{% hint style="info" %}
By associating the transaction with the mobile token, you enable a complete audit trail that connects user authentication sessions with subsequent transaction validations, enhancing security and monitoring capabilities.
{% 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 dynamically by asking a question.

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

```
GET https://docs.caf.io/caf-api/connect/transactions/transaction-linking.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.