> For the complete documentation index, see [llms.txt](https://docs.kleos.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kleos.io/for-contractors-1/checking-the-status-of-a-swift-payment.md).

# Checking the Status of a SWIFT Payment

Our contractors expect to receive funds in their bank accounts as quickly as possible, and as a payroll service, we aim to support that expectation efficiently. However, in some cases, withdrawals may be delayed due to currency control regulations in certain countries, which require manual review of international transfers.

In this article, we'll explain how to track a withdrawal sent from the Kleos platform to your bank account.

Currently, only USD transfers can be tracked. Although we cannot provide a full step-by-step tracking solution, we recommend using a useful tool that allows you to check the status of your transfer.

To track your transfer, you'll need two things:&#x20;

• UETR&#x20;

• Access to the Deutsche Bank website and [**its tracking feature**](https://corporates.db.com/solutions/client-access-solutions/international-payment-tracking/) (no sign up required)&#x20;

**What is UETR?**&#x20;

* UETR is a unique code used to identify an outgoing money transfer within the SWIFT system. It helps the recipient of the funds track their transaction at all stages, in all banks and financial institutions.

Here is an example of what a UETR might look like:

{% code fullWidth="false" %}

```
43cb2c74-9712-43d4-aa84-7e4567358c12
```

{% endcode %}

Where can I find the UETR for my payout?

* Currently, you can obtain the UETR for your transfer by contacting our Support team at <support@kleos.io>

Once you obtain the UETR for your transfer, copy it and navigate to the Deutsche Bank website. Scroll down to the Payment Status Search section. Paste your UETR into the **Unique End-to-End Transaction Reference** field and press the **Search** button.

<figure><img src="/files/68y8Oh16AqZfSvOC7RlZ" alt=""><figcaption><p>Entering your UETR</p></figcaption></figure>

The **Payment Status** page will open, and it will display information about the status of your transfer.&#x20;

<figure><img src="/files/vJByFownWyIYMtimiyb5" alt=""><figcaption><p>Example of a payment that is still in progress</p></figcaption></figure>

If your Payment Status page looks like this, it means that the transaction is still in progress.&#x20;

<figure><img src="/files/Q5XsFEO6DhylBdpyOUE8" alt=""><figcaption><p>An example of a rejected transaction</p></figcaption></figure>

A transaction can be rejected for various reasons. The most common one is compliance — in other words, the bank’s internal policies regarding certain types of transfers. Banks may refuse to process a payment if it doesn’t meet their compliance requirements.

{% hint style="info" %}
We strongly recommend keeping accounts with multiple banks as this can help avoid unnecessary delays
{% endhint %}

<figure><img src="/files/Yb5V2KaRAYjA09XbK8P9" alt=""><figcaption><p>A payout completed successfully</p></figcaption></figure>

This status means that the funds have been successfully transferred to the recipient’s account.

If you have any questions regarding your transfers, feel free to contact our Support team — we’ll be happy to help. Our email is <support@kleos.io>


---

# 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.kleos.io/for-contractors-1/checking-the-status-of-a-swift-payment.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.
