> 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/release-notes/release-notes-2026/release-2026.06.md). # Release 2026.06 This release focuses on improvements to design and security. ## Optimizations ### Comprehensive redesign The overall look and feel of the Payrexx account has been redesigned. This is evident, for example, in the individual buttons and tabs: they now feature new, friendly colors and rounded shapes, in line with our corporate design introduced in 2025. This update not only gives the Payrexx account a more modern look, but also provides merchants with a better, more user-friendly, and, above all, consistent user interface.

### Optimized configuration view for PP and PPP The previously rather unstructured configuration view of Payrexx Pay (PP) and Payrexx Pay Plus (PPP) has been significantly improved. Secondary sections (such as transaction fees or the terms and conditions) are now hidden behind a drop-down bar, so that important settings—such as the enabled payment methods—can be viewed and edited more quickly. This improved overview allows merchants to configure the payment provider more quickly and efficiently. It also helps them better understand the product and how to use it.

Find out more about how to configure PP and PPP: {% embed url="" %} ### Default import option for the Paylink tool You can now import the necessary data for a Paylink—specifically email addresses, amounts, and currencies—via a CSV file, even if no Paylink has been created yet. Previously, this option was only available if the tool had already been used. This allows merchants to use the tool as efficiently as possible right from the start and send their invoices in an organized manner with minimal manual effort.

New import feature in the Paylink tool's welcome screen

Find out more about paylinks: {% embed url="" %} ### Introduction of a password history Going forward, passwords that have already been used by merchants will be stored and blocked for future use. If a user changes their password in the future, they will not be able to reuse a previously used password but will be prompted to set a new one. This feature not only enhances security for individual merchants, but also improves security across the entire platform. --- # 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/merchant/english/release-notes/release-notes-2026/release-2026.06.md?ask=&goal= ``` `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.