> For the complete documentation index, see [llms.txt](https://docs.payrexx.com/platform/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/platform/english/use-cases.md).

# Use Cases

<table data-full-width="true"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td>💻 <strong>SaaS &#x26; SaaP</strong></td><td><p><strong>Monetize your platform with integrated payments</strong></p><p></p><p>Our white-label solution allows you to embed payments directly into your software or platform – including custom fee models and branding.</p><p></p><ul><li>New revenue stream through your own transaction fees</li><li>Customers remain fully within your ecosystem</li><li>Fully scalable without additional development effort</li></ul></td></tr><tr><td><strong>🛒 Marketplaces and platforms</strong></td><td><p><strong>Smart payments for multi-merchant systems</strong></p><p></p><p>With our marketplace solution, payments are automatically split between sellers and platform operators – transparent and efficient.</p><p></p><ul><li>Split payments and mixed carts with automatic allocation</li><li>You receive commissions, merchants receive their revenue</li><li>Smooth checkout experience for end customers</li></ul></td></tr><tr><td><strong>🏛️ Public institutions</strong></td><td><p><strong>Unified, secure payments for municipalities and authorities</strong><br></p><p>A centralized payment platform under your brand enables efficient management and transparent processes.</p><p></p><ul><li>Unified solution instead of isolated systems</li><li>Central management of departments, municipalities &#x26; e-services</li><li>Highest level of security and data protection</li></ul></td></tr><tr><td><strong>🌐 Agencies and IT service providers</strong></td><td><p><strong>Turnkey payment solution for your clients</strong><br></p><p>Offer your clients a complete all-in-one solution – web presence including payments. With our white-label payment solution, you can deliver everything from a single source and position yourself as a true full-service provider.</p><p></p><ul><li>Strengthen your role as a full-service provider</li><li>Recurring revenue through split payments</li><li>Added value for your clients with an immediately deployable solution and a single point of contact</li></ul></td></tr><tr><td><strong>🏦 Banks and financial institutions</strong></td><td><p><strong>Digitize your offering with a secure payment platform</strong></p><p><br>Expand your portfolio with an e-commerce solution under your brand – trustworthy and PCI DSS Level 1 certified.</p><p></p><ul><li>Strengthen your brand with white-label</li><li>Highest compliance and security</li><li>Increased customer retention through modern services</li></ul></td></tr><tr><td><strong>💳 Acquirers and PSP</strong></td><td><p><strong>Innovative payment platform with your own payment services</strong></p><p><br>Offer your merchants innovative tools such as QR Pay, payment links, one-page shops, and additional payment options – all under your brand and with your acquiring, ready for immediate deployment.</p><p></p><ul><li>Platform and tools in your look &#x26; feel</li><li>Centralized management of your merchants and payments</li></ul></td></tr></tbody></table>


---

# 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.payrexx.com/platform/english/use-cases.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.