> 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.09.md).
# Release 2026.09
New features, enhancements, and updates that Payrexx implemented with the release on September 22, 2026.
## Optimizations
### Software Update for Payrexx Naka Card Readers (N5, N6, N86)
A software update for the Naka N5, N6, and N86 card readers will be available starting September 29. This update will modify the user interface on the device. The existing functions will remain unchanged.
After the update, a prompt will appear on the screen that must be confirmed by clicking the “Activate” button in order to complete the update.
### Validation of Phone Numbers on Payrexx Payment Pages
The process for entering phone numbers on Payrexx payment pages has been improved. Phone numbers are now checked for a valid format before the form can be submitted.
Both local and international phone number formats are supported. Entries that are clearly invalid are rejected with a corresponding message.
### 3-D Secure Information for Card Payments
For card payments made with **Payrexx** **Pay**, the transaction details page now shows whether a 3-D Secure verification was performed and exactly which method was used.
Starting with API version 1.17, this information can also be retrieved via the [Transaction API](https://payrexxserviceapi.readme.io/reference/retrieve-transaction).
To find out exactly what 3-D Secure is and how it works, visit:
{% embed url="" %}
### Clearer Navigation Through the Verification Process
The verification process has been revised and restructured for greater clarity. A new dashboard provides a better overview of the verification process and the current status of each step.
Navigation between the individual steps has also been improved, making it easier and more intuitive to complete the verification process.
To find out exactly how the verification process works and what you need for it, go to:
{% embed url="" %}
### Proof of a bank account is required
If changes are made to an already verified bank account, a supporting document is now required. This confirms that the specified bank account belongs to the company. The supporting document can be submitted directly while updating the bank account information in the payout settings.
This requirement applies only to bank accounts whose verification has already been accepted and that are subsequently updated. No supporting document is required when adding a bank account for the first time.
The document must show the account and the merchant’s name. It can be a PDF or an image, but it must not be a screenshot. It must be a document (PDF or scan). The document must not be older than 3 months.
---
# 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/release-notes/release-notes-2026/release-2026.09.md?ask=&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.