March, 2026

This blooming release brings a series of enhancements across the Dashboard and Merchant portal, designed to improve usability, security, and control over payment and payout flows. 🌸

Thus, we can admit that the beginning of a new season is fruitful and invite you to read and examine the updates.

✔︎ March, 2026

Dashboard Features

◦ Global search

Users can now access a Full-screen search page, offering an expanded and focused search experience for easier navigation and results discovery.

◦ Feature management for Payment/Payout method

Payment and payout methods now support configurable Processing features, allowing users to set each feature as Required, Optional, or Disabled based on backend-defined validation. Updated feature settings are saved as a new method revision, with ECI Mode also supporting dedicated options such as Only 3DS, Acquirer Only 3DS, and Non-3DS.

◦ Google Analytics for Checkout

You can configure a Google Analytics 4 (GA4) Measurement ID for each Checkout in the Integrations tab, enabling Checkout funnel tracking directly from the Checkout version. Once enabled, the platform injects GA4 gtag.js into eligible Checkouts and sends a limited set of platform-controlled analytics events.

◦ Firewall rules for Payouts

Firewall rules support Payout triggers, allowing users to create and configure Firewall logic specifically for payout flows. This expands Rule coverage and gives more control over payout-related processing.

◦ The Default Policy on Firewall add-on

Payment managers can now configure a Default policy for Firewall rules in the add-on settings, defining how transactions are handled when no rule explicitly accepts or blocks them. The policy supports both Accept and Block modes, with clear descriptions to help control fallback transaction behaviour.

◦ The Accept option for Firewall rules

Payment managers can use the Accept option in Firewall rules to create a whitelist of allowed transactions that is evaluated before Block and other Rule actions. This update also introduces a contextual Info block for supported Rule options and displays the selected Default policy in the add-on configuration.

◦ PCI DSS security improvement

Users without 2FA enabled must update their passwords every 90 days to improve account security. When the password expires, they are prompted to update it after login through a dedicated flow, with confirmation shown once the password is successfully changed.

Merchant portal features

◦ Branded emails

Users can now receive service emails with branded PSP icons. Uploaded icons are displayed alongside the Merchant portal name; if no icon is uploaded, the email should be sent without a logo, using the full CDN URL.

Merchant portal & Dashboard features

◦ Left members management

Payment managers and Merchants can now manage previously removed Organisation Members in the Inactive section, where users with inactive or left statuses are displayed separately. Members marked as left can be restored using the new Restore action, making it easy to reinstate access when needed. The feature is available on the Dashboard and in the Merchant portal.

Major Improvements

◦ Improved Fields tab for Payment method conditions

The Fields tab UI of the Payment method conditions functionality was updated.

◦ Improved visual tags on the Add-on installation page

Tag display and styles have been refreshed. Add-ons now show a secondary tag indicating enabled when active and disabled when inactive.

◦ Optimised Transactions (Payments) module

The Requests grid in the Transactions (Payments) module has been optimised by removing several non-essential columns and related data queries to improve performance and simplify the view. In addition, the Payment Transaction Amount column now uses the paid_amount attribute from the Payment Request.

◦ Additional CVV codes for Test Connector

Cascading behaviour has been improved for internal validation by ensuring processing stops on specific decline resolutions, including Insufficient Funds, Invalid Card Expire Date, Invalid Pan, and Card Expired. To support this testing flow, new resolution codes have been added to the Test Connector to more accurately simulate these scenarios.

◦ Updated Processing public url & Merchant api context

Updated endpoint references: processing.eu.corefy… is now pay.eu.corefy…, and merchant-api has been simplified to merchant or api for clarity.

◦ Changed text in an alert at Checkout

Users can now see an updated alert on the Checkout page for Merchant accounts in created status: This account is in Created status and is inactive for Live payments. When the account is set up and ready to go live, "contact your support", with the support email automatically pulled from the add-on configuration.

◦ Updated option to recreate the invite for Merchant members

Users can now resend or recreate user invites without duplication errors. The system regenerates the invite, sends the email, and updates its expiration, following the same logic as organisational Members, while duplicate emails are handled via a dedicated resend endpoint.

📚Docs

New Articles

  1. Payout Routing attributes
  2. Payout Trigger attributes
  3. Configure Hosted Fields SDK
  4. Configure Self-Hosted Merchant Documentation
  5. Apply Checkout Method conditions