> For the complete documentation index, see [llms.txt](https://docs.payrexx.com/merchant/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payrexx.com/merchant/english/integration/e-commerce/flow-shopsoftware.md).

# FLOW Shopsoftware

On this page, you will find information about FLOW Shopsoftware and learn how to connect the shop solution to Payrexx.

## General Information

FLOW Shopsoftware is a German solution specializing in user-friendly systems for online shops. FLOW Shopsoftware is characterized by its ease of use and high design flexibility.

FLOW Shopsoftware is available for merchants in the :flag\_eu: European Union and :flag\_ch: Switzerland.

### Links

* FLOW Shopsoftware [website](https://www.shopsoftware.com/)
* FLOW Shopsoftware [plugin download](https://shopsoftware.com/580/Module-Payrexx---Zahlungsartprovider-Fuer-Version-Extended)

{% hint style="info" %}
Please note that integration with FLOW Shopsoftware is only available in the Standard and Premium plans. [For more information](https://payrexx.com/en/prices)
{% endhint %}

## Setup

### Installation of FLOW Shopsoftware

FLOW Shopsoftware can be ordered on the provider's [website](https://www.shopsoftware.com/k1/FLOW-Shopsoftware). The merchant can choose whether to purchase or rent the software.

The rental solution includes hosting, ensures the software is always up to date, and is pre-configured.

With the purchase solution, the merchant receives a zip file and installs the software themselves. However, FLOW Shopsoftware also offers a free installation service.

### Configuration of Payrexx

{% hint style="info" %}
Make sure you're [logged in](https://login.payrexx.com/) to your Payrexx account before you begin. If you don’t have a Payrexx account yet, you can [register](https://signup.payrexx.com/) now.
{% endhint %}

To begin the integration of FLOW Shopsoftware, navigate to **Webhooks** in the main navigation of your Payrexx account and click on "Add webhook."

In the next step, configure the webhook according to the following instructions:

1. Assign a name to the webhook, for example, FLOW Shopsoftware.
2. Enter your own domain as the Webhook URL, followed by a slash and the parameter "payrexx\_notify," as shown in the following screenshot.
3. Ensure that all four checkboxes are checked.
4. Select "JSON" as the webhook content type and "2021-10-12" as the webhook version.

<div align="left"><figure><img src="https://1455115231-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MYJhU4qriZCz_Wxs0T0-887967055%2Fuploads%2FWjIXb4Exg9pIjPLWpujn%2Fimage.png?alt=media&amp;token=0c77710a-04f2-4c60-ab40-7e0929225936" alt=""><figcaption><p>Configuration of the webhook for connecting FLOW Shopsoftware to Payrexx</p></figcaption></figure></div>

Don't forget to complete the configuration by clicking the green "Add" button.


---

# 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.payrexx.com/merchant/english/integration/e-commerce/flow-shopsoftware.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.
