> 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/troubleshooting-and-support/support.md).

# Contact support

Get in touch with our support team.

<h2 align="center"><i class="fa-comment">:comment:</i> Contact form</h2>

{% @dynamics-contact-form/dynamics-form url="<https://assets-eur.mkt.dynamics.com/4fdafba7-58a0-439d-ac40-8b9307b6aa29/digitalassets/standaloneforms/26148488-e600-f111-8407-7ced8d493772>" %}

***

<h3 align="center">Before you contact us</h3>

<p align="center">To help you quickly, please have the following ready:</p>

<table data-view="cards"><thead><tr><th></th></tr></thead><tbody><tr><td><strong>Your Business Central version</strong></td></tr><tr><td><strong>VR Payment Gateway version</strong> (Extension management, currently 1.18.1.0)</td></tr><tr><td><strong>Description of the issue</strong></td></tr><tr><td><strong>Error messages</strong> (if any)</td></tr><tr><td><strong>Output of “Test connection (debug)”</strong> without the API key</td></tr></tbody></table>

{% tabs %}
{% tab title="VR Payment help" %}
Questions about the gateway, spaces, and the application user:

<a href="https://gateway.vr-payment.de" class="button primary">VR Payment Gateway</a>
{% endtab %}

{% tab title="About solutioo" %}
Solutioo builds extensions for Microsoft Dynamics 365 Business Central.

<a href="https://www.solutioo.de/en/" class="button primary">solutioo.de</a>
{% endtab %}
{% endtabs %}

***

**If you are happy:**

⭐ Rate us on Microsoft AppSource.

⭐ Recommend us.

⭐ Share your success story.


---

# 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/vr-payment-gateway_en_us/troubleshooting-and-support/support.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.
