> 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-pay-integration/konfiguration/erste-schritte-quickstart.md).

# Erste Schritte: Quickstart

So richten Sie die VR Pay Integration in 5 Minuten ein

{% stepper %}
{% step %}

#### **VR Pay Einrichtung öffnen**

Suchen Sie nach *"VR Pay Einrichtung"* in der BC-Suchleiste.
{% endstep %}

{% step %}

#### **Zugangsdaten eingeben**

* **Instance Name**: Ihr VR Pay Instanzname (von VR Pay erhalten)
* **API Secret**: Ihr API-Schlüssel (von VR Pay erhalten)
  {% endstep %}

{% step %}

#### **Lizenzserver verbinden**

Klicken Sie auf *"Standard-Lizenzserver setzen".*
{% endstep %}

{% step %}

#### **Installation registrieren**

Klicken Sie auf *"Installation registrieren".*
{% endstep %}

{% step %}

#### **Aktivierung durch Solutioo**

Wir aktivieren Ihre Installation im Admin-Portal. Danach klicken Sie auf *"Lizenz prüfen".* Nun sollte der Status sollte auf *"Aktiv"* wechseln.
{% endstep %}

{% step %}

#### **Automatischen Webhook-Abruf einrichten**

Klicken Sie auf *"Automatischen Webhook-Abruf einrichten".* So werden Zahlungsbestätigungen automatisch alle 5 Minuten abgerufen.
{% endstep %}
{% endstepper %}

&#x20;**Fertig!** <i class="fa-right">:right:</i> Sie können jetzt QR-Codes und Zahlungslinks erstellen.


---

# 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-pay-integration/konfiguration/erste-schritte-quickstart.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.
