> 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/erste-schritte/vr-payment-konto.md).

# VR Payment Konto und API-Zugang

Space ID, Application User und API-Schlüssel im VR Payment Backoffice.

Die App authentifiziert sich per JWT (HS256) gegen die VR Payment Gateway REST API v2.0. Dafür brauchen Sie drei Werte aus dem VR Payment Backoffice.

{% stepper %}
{% step %}

#### Backoffice öffnen

Melden Sie sich unter <https://gateway.vr-payment.de> an. Für Tests nutzen Sie den Test-Space, für den Produktivbetrieb den Live-Space.
{% endstep %}

{% step %}

#### Space ID notieren

Jeder Space hat eine numerische **Space ID**. Tragen Sie die Live-ID ins Feld **Space ID** und die Test-ID ins Feld **Test Space ID** der VR Payment Einrichtung ein.
{% endstep %}

{% step %}

#### Application User anlegen

Legen Sie einen Application User an und notieren Sie **User ID** sowie den **Authentication Key** (API-Schlüssel). Den Schlüssel trägt die App als **API-Schlüssel** (maskiert).
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
Behandeln Sie den API-Schlüssel wie ein Passwort. Geben Sie ihn nicht ins Ticket, ins Chatprotokoll oder in eine E-Mail im Klartext weiter.
{% endhint %}

{% hint style="info" %}
Im **Sandbox-Modus** verwendet die App die Test Space ID und hängt PREVIEW-Parameter an Payment-Link-URLs. Sandbox und Test-Space müssen zusammenpassen.
{% endhint %}

Die Standard-API-URL ist `https://gateway.vr-payment.de`. Ändern Sie sie nur, wenn VR Payment Ihnen eine andere Basis-URL mitteilt.


---

# 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 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/erste-schritte/vr-payment-konto.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 `automate deployments from our CI pipeline` 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.