> For the complete documentation index, see [llms.txt](https://docs.solutioo.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.solutioo.de/vr-payment-gateway/vr-payment-gateway_en_us/configuration/automatic-sync.md).

# Automatic synchronisation

Job queue every 15 minutes – transactions, refunds, payouts, tokens, and reminders.

Payment status comes directly from the VR Payment API. Setup creates a job queue entry for that.

#### Activate the job queue

1. Open **VR Payment Setup**.
2. Choose **Activate job queue**.
3. The entry runs every **15 minutes**, every day of the week, with up to 3 retries.

The page shows **Job queue status**, **Last run**, and the **last error** if any.

#### What each run does

1. Synchronise transactions
2. Synchronise refunds
3. Synchronise payouts / bank transactions
4. Synchronise payment tokens
5. Match open links against customer ledger entries (**Paid externally**)
6. Close expired links
7. Send expiry reminders (if enabled)

You can also run **Synchronize** at any time or **Synchronize everything with VR Payment** from the role center.

{% hint style="info" %}
A former Azure webhook listener is no longer required. If setup still shows **VR Payment webhook configured**, remove it with **Remove old Azure webhook**.
{% endhint %}

{% hint style="warning" %}
The integration must be **Enabled**. Otherwise the job exits immediately without calling the API.
{% 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.solutioo.de/vr-payment-gateway/vr-payment-gateway_en_us/configuration/automatic-sync.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 `build a script that syncs our docs to a CMS` 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.