Release 2025.07

Learn about the new features, enhancements and updates that Payrexx has implemented in the July 22 2025 release.

Various existing features have been optimised in this release. New API interfaces and functions have also been introduced. The following points provide an overview of the new features.

Optimisations

Two-factor authentication (2FA) for more security

From 22 July 2025, two-factor authentication will be mandatory for all users. We are thus implementing a regulatory requirement for secure authentication and at the same time strengthening the protection of all Payrexx accounts.

If no 2FA method has been set up so far, email authentication will be activated automatically. You can switch to SMS or Authenticator App (TOTP) at any time in the settings.

New payment function: Click to Pay with Mastercard

Click to Pay with Mastercard is a new payment function that significantly simplifies the checkout process for customers. Card details no longer need to be entered continuously, as registered users are recognised automatically. The function is automatically available as soon as you have activated Mastercard via Payrexx Pay.

You can find more information about Click to Pay with Mastercard on the website. And you can find out exactly how to set up and use this function in the following article:

Click to Pay with Mastercard
Start des Bezahlvorgangs mit Click to Pay mit Mastercard
Start of the payment process with C2P with Mastercard

Transaction type can be filtered

The transaction overview in the merchant backend contains a new column with the transaction type.

This can be used to recognise whether a payment was made

  • online (e-commerce),

  • via smartphone app (tap to pay) or

  • via the card reader (POS terminal).

The type can also be displayed in the export and via webhooks.

New transaction view with filter by type
New transaction view with filter by type

The API reference field in the transaction export

The API reference is now also displayed in the transaction export. This shows which API key or which plugin was used to trigger a transaction.

Datatrans: Sofortüberweisung has been renamed Klarna

After the SOFORT payment method was renamed Klarna within Payrexx Pay Plus last year, the change has now also been made in the Datatrans view. For you as a merchant - apart from the name and the logo - nothing will change in terms of the functions and integrations.

Coming Soon: VERD.cash

VERD.cash will soon be available as a new payment method, making the community-orientated payment solution accessible to online merchants. More information will follow soon.

Plugins

WooCommerce

Previously, merchants always had to manually copy the API key from their Payrexx account and paste it into WooCommerce. This step will no longer be necessary in future. Instead, you simply click on the Connect button in WooCommerce and are forwarded directly to the Payrexx login. After logging in, the shop is automatically connected. In addition, the access data is checked directly in the plugin.

WooCommerce Connect button integrated
Integrated WooCommerce Connect button

Shopware 6

A rounding error in the calculation of the total amount (with floating point numbers) has been fixed.

JTL

Compatibility with version 5.5 has been ensured for the JTL plugin.

Shopify

The payment button before the checkout is now called "Pay online" / "Pay online" and takes customers directly to the Payrexx payment page.

Shopify button in the payment checkout
Shopify button in the checkout

POWERPAY and CembraPay implemented in all plugins

The payment methods POWERPAY and CembraPay are now available in all plugins and appear automatically during the payment checkout.

POWERPAY and CembraPay in the payment checkout
POWERPAY and CembraPay in the payment checkout

PHP SDK release version 2.0.0

The PHP SDK is now available in version 2.0.0. The updated version simplifies the integration of Payrexx and ensures a stable connection. Ideal for developers who want to integrate Payrexx securely and quickly.

Technical innovations:

  • Request body in JSON format

  • API key in HTTP header

  • Guzzle as HTTP client (cURL as fallback)

If you have any questions about the mentioned features and optimizations or any other concerns, please do not hesitate to contact us:

Last updated

Was this helpful?