> 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/setup.md).

# VR Payment Setup

Search for **VR Payment Setup**. The page is a card without insert/delete – there is exactly one setup record.

#### General

| Field            | Meaning                                                                     |
| ---------------- | --------------------------------------------------------------------------- |
| **Enabled**      | Turns the integration on or off.                                            |
| **Sandbox mode** | Uses the test Space ID and appends PREVIEW parameters to payment-link URLs. |

#### API settings

| Field             | Meaning                                  |
| ----------------- | ---------------------------------------- |
| **API base URL**  | Default `https://gateway.vr-payment.de`. |
| **Space ID**      | Live space when sandbox is off.          |
| **Test Space ID** | Test space when sandbox is on.           |
| **User ID**       | Application user ID.                     |
| **API key**       | Authentication key, stored masked.       |

How to obtain the values: [VR Payment account and API access](/vr-payment-gateway/vr-payment-gateway_en_us/getting-started/vr-payment-account.md).

{% hint style="success" %}
**Test connection (debug)** verifies JWT authentication without leaving the page. The message shows URL, space, user, and any errors – it does not throw a blocking error.
{% endhint %}

#### Payment links

| Field                                 | Default / note                                                           |
| ------------------------------------- | ------------------------------------------------------------------------ |
| **Create payment link automatically** | When posting a sales invoice.                                            |
| **Payment link validity (days)**      | Default 30, range 1–365.                                                 |
| **Show payment status in lists**      | Column on order, quote, and posted invoice. Default on.                  |
| **Respect customer flag**             | Default off. If on, the customer must have **Allow VR Payment QR code**. |
| **Respect responsibility center**     | Default off. An empty RC does not block while the switch is off.         |
| **Respect payment terms**             | Default on. Direct debit typically stays without QR.                     |
| **Send expiry reminder by email**     | Optional.                                                                |
| **Reminder days before**              | Default 3.                                                               |

#### Actions on the setup page

* **Test connection (debug)**
* **Synchronize** – pull transactions from the API now
* **Activate / deactivate / open job queue**
* **Prepare payment terms** – sets the QR flag on all terms except direct debit
* **Allow all responsibility centers**
* **Close overdue payment links**
* **Remove old Azure webhook** – only visible if a former listener still exists

{% hint style="info" %}
Status comes from the job queue directly from VR Payment. A former Azure webhook is no longer required.
{% 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.solutioo.de/vr-payment-gateway/vr-payment-gateway_en_us/configuration/setup.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.