> For the complete documentation index, see [llms.txt](https://docs.lhv.com/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lhv.com/home/connect/services/indirect-scheme-access/rtf-routing-table-files-message.md).

# RTF - Routing Table Files message

## Service description

Routing Table Files (RTFs) provide a complete list of direct and indirect participants for each supported payment scheme. The files are generated and delivered automatically to the message queue of LHV's Indirect Scheme Participants. Files cannot be requested via API or triggered manually.

All RTFs are provided in a machine-readable format and contain the full dataset (i.e., complete files rather than deltas or incremental updates).

RTF contents include:

* Participant BIC
* Participant name
* Start and end validity dates for the participant
* BIC of the associated direct participant (if applicable)
* Settlement BIC
* Current status
* Supported payment types

**Files are available for following schemes:**

* SEPA Credit Transfers - STEP2 SCT
  * Updates typically occur once a month. 
  * RTFs are sent one week prior to the change date.
  * There are two files: one for direct members, and one for indirect members.
* SEPA Instant Credit Transfers - RT1
  * Updates are made weekly.
  * RTFs are delivered before each change date. By default, the change date is Tuesday, and files are typically sent on Monday.
  * There are two files: one for direct members, and one for indirect members.
*  SEPA Instant Credit Transfers - TIPS
  * RTFs are sent daily.
  * There is one file containing both direct and indirect members.

## How to Start Receiving Routing Table Files

To start receiving RTFs for a specific payment scheme, please contact your Relationship Manager. File delivery will be enabled based on your service agreement and scheme participation.

## Request <a href="#virtual-iban-open" id="virtual-iban-open"></a>

Not applicable – files are delivered automatically, no request is required.

## Response message

Files can be requested by the Messages services - [Messages Services](/home/connect/services/messages.md)

{% hint style="info" %}
HTTP Header Message-Response-Type: AGENT\_REPORT
{% endhint %}

### Content Types

Content type property in the message header indicates the payment scheme:

<table><thead><tr><th>Content type</th><th width="327.99609375">Payment scheme</th></tr></thead><tbody><tr><td><ul><li>application/vnd.lhv.step2.di.rtf - direct members</li><li>application/vnd.lhv.step2.in.rtf - indirect members</li></ul></td><td>SEPA Credit Transfers - STEP2 SCT</td></tr><tr><td><ul><li>application/vnd.lhv.rt1.di.rtf - direct members</li><li>application/vnd.lhv.rt1.in.rtf - indirect members</li></ul></td><td>SEPA Instant Credit Transfers - RT1 SCT Inst</td></tr><tr><td><ul><li>application/vnd.lhv.tips.rtf - indirect and direct members</li></ul></td><td>SEPA Instant Credit Transfers - TIPS</td></tr></tbody></table>

## Samples

The files provided in this section are synthetic examples intended to illustrate the format of the RTFs. They do not contain real scheme data or actual participants. Production and test files follow the same structure and can be enabled for delivery upon request via Relationship Manager.

:arrow\_down: application/vnd.lhv.step2.di.rtf - STEP2 SCT direct participants&#x20;

{% file src="/files/FGFswVqovQSAg0R4CnsS" %}

:arrow\_down: application/vnd.lhv.tips.rtf - SEPA Instant Credit Transfers - TIPS

{% file src="/files/8slhUyZNtgwBFwOA49hO" %}

***


---

# 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.lhv.com/home/connect/services/indirect-scheme-access/rtf-routing-table-files-message.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.