This April release is rich in improvements across the Merchant portal, Dashboard, and core platform experience, focusing on better usability, stronger security, and more efficient payment and integration flows.

Make sure you haven’t missed an important update or improvement. 💡

✔︎ April, 2026

Merchant portal features

◦ GA4 for Checkout

Merchants can now enable Google Analytics 4 (GA4) tracking for each Checkout by adding a Measurement ID in the Integrations tab. Once configured, GA4 is injected into the Checkout to track funnel events using platform-controlled data without sending any sensitive information.

◦ Time to update your password modal

Users without MFA enabled are now required to update their password every 90 days, with a prompt shown after login to guide them through the update process. After successfully changing the password, users are redirected to the login page with a confirmation alert.

◦ Initiate New Refund

Merchants can now initiate Refunds directly from the Payment Request overview, with support for both Full and Partial refunds. The new flow ensures accurate processing by validating Refund amount limits and maintaining the original transaction currency.

Dashboard features

◦ Quick search

You can now use Quick search from any page in the Dashboard, enabling faster navigation and instant access to relevant data and resources.

Major Improvements

◦ Improved minimal size for UiSelect on Firewall rules

The current select display has been improved, as it previously did not clearly expose all attributes. The solution updates the select option to display the attribute with the longest label for better readability and completeness.

◦ USD, CAD, AUD currencies for Unity Finance

Support for USD, CAD, and AUD currencies has been added for the Provider connection. The update ensures correct Routing per currencies.

◦ Domain manager CNAME's settings

The domain connection flow has been improved to make CNAME record setup clearer and more user-friendly. This update includes a new alert, a redesigned records display (removing unnecessary TTL details), and dynamic tooltips showing the user's connected domain for a smoother UX.

◦ Improvement for Hosted fields

An improvement has been implemented to allow Merchants to collect Customer fields independently within a single session. This enables step-by-step input for card details such as card number, expiry date, CVV, and cardholder name, improving flexibility in custom Checkout flows.

◦ Added Processing triggers for Firewall

New Firewall triggers have been implemented for key payment flows, including Payout attempt, Payout routing, Payout creation, and Refund. The Firewall now evaluates the selected Trigger conditions and blocks entity creation when rules are violated, returning the appropriate resolution.

◦ Alert for Members without permissions to set up an add-on

For users without Write access to the add-on setup, the Install button is now displayed as disabled. An alert has also been added to clearly indicate insufficient permissions.

◦ Optimised Customer lists

The Customer lists retrieval flow has been optimised by introducing filtering by Merchant account ID at the list-items level. This prevents loading irrelevant lists across the system, improves pagination reliability, and reduces database load while ensuring only lists relevant to the specific Merchant account or Customer type are returned.

◦ Optimised Merchant activation flow

The Merchant activation flow has been simplified by automatically creating new Merchant accounts with active test flows for payments and payouts. When a Merchant account is created via the API or Merchant portal, the system now sets operating_mode: "test" by default, ensuring immediate availability for testing across both dashboards and Organisation creation flows.

📚Docs

New Articles

1. Card method
2. Open Banking method
3. Justipay (integration guide)
4. Spoynt (integration guide)
5. Salt Edge (integration guide)

API References & Recipes

1. Create Payment Request (Hosted fields)
2. Process Payment Commit via Token (Hosted fields)
3. Create Payment Request with Hosted Fields (Recipe)
4. Process Payment Commit via Token (Hosted fields recipe)