Release 2026-09-07

1. Multiple Adyen/Stripe merchant accounts per tenant

   You can now configure more than one Adyen or Stripe merchant account within a single tenant. In the Payment Poviders settings, Adyen and Stripe has its own panel where additional merchant accounts can be added and given a descriptive identifier, for example "Adyen-B2C". This makes it possible to run several business cases — or several currencies — side by side without setting up separate tenants.

2. Further areas with configuration transfer

   Configuration Transfer has been enhanced and is now available for additional configuration areas. In addition to SSO Configuration, Tax Rules and others, the following configurations can now be transferred between tenants and environments:

   • Billing Groups
   • Customer Tax Classification
   • Document Provisioning Configuration
   • Document Translations
   • Tax Exemptions
   • Operation Sites

   Existing configurations can be exported as a JSON file and imported into another tenant or environment, making it easier to reuse established setups.
   Detailed instructions can be found in the documentation.

3. Data Report for Payment Intents

   The data area "Contracts" is now available for reports created in Reportfiles and Scheduled Reports.
   When creating a report, Contracts can be selected from the Data Area dropdown in the creation dialog. Reports created with this data area contain Contract data based on the Creation Date.
   This extends the existing reporting functionality by adding Contracts as a new available data area alongside Documents and Payment Intents. Further information on Data Reports.

   Please Note: We have only been collecting data for this report since the feature was introduced. Therefore, we are unable to provide reports containing data prior to 5 September 2026.

4. Improved schema handling for nullable and polymorphic types
   
   Schema definitions have been updated to properly handle nullable and polymorphic data types. This resolves serialization and parsing issues, ensuring strict contract compliance and reliable payload validation across API integrations.

Webportal Improvements

• Column names in the OPOS case detail view have been reworked so that dunning fees and chargeback fees can be read correctly. Balances are now colour-coded — settled in green, underpayment in red, overpayment in blue — and the total row is highlighted. (Hint: Dunning fee and chargeback fee features are coming soon)