Winter is almost over, which means new beginnings are on the horizon. Thus, let's take a deep breath and take a look back at the features and improvements our team made in February.

✔︎ February, 2026

Dashboard features

◦ Welcome block

New Organisation users now see a Welcome block and a Getting Started checklist outlining four activation steps, with the first step marked as completed by default. The block also provides links to documentation and a Contact Support button for quick access to help and support chat.

◦ Checkout Method conditions

Currency & Amount: The functionality enables specifying Currencies and Amounts used from the Payment Request in the Payment method condition to control the visibility for the Method with the specified values.
Country: The functionality enables setting a Country defined from the client active Checkout session for a Payment method condition.
Device: The functionality enables selecting Devices defined from the client active Checkout session in a Payment Method conditions.
IP: The functionality enables adding IP addresses defined from the client active Checkout session to the Payment method condition.
Metadata: The functionality enables specifying Metadata used from the Payment Request in a Payment method condition.

Merchant portal features

◦ Events list

Merchants can now monitor all Events across an Organisation, with the ability to filter them by categories including All, Merchant, Customer, and Transactions.

◦ Events actors details

Admin: Users can now view detailed information for Events triggered by an Admin actor by opening the Event from the list.
API: Users can view detailed information for Events triggered by the Server (API) actor by opening them directly from the events list. This provides better visibility into API activity and integrations.
System: Users can open and review detailed information for events triggered by a System actor directly from the Events list.
User: Users can view detailed information for Events triggered by a User actor when opening the Event directly from the list.

◦ Manual Payout Request

Merchant context: The block enables specifying the Request type.
Destination: The block enables selecting a Customer and Payout method when creating a Payout Request.
Details: The block enables adding specific details for Payout Request such as Description, Referenced ID or Origin ID.
Flow options: The block enables setting up flow options configuration for a new Payout Request.
Metadata: The block enables specifying Metadata keys and Values.

◦ Payout Request overview

Merchants can view detailed information for Payout Requests, allowing them to open a Request and manage all related data in one place.

◦ List of Payout Requests

Merchants can access a comprehensive list of Payout Requests, with options to sort and filter for easier management and tracking of Requests.

◦ Customer Payouts

Merchants are allowed to view all Payout Requests associated with a specific Customer directly from the Customer overview. This shows a complete view of all Payouts related to that Customer for smooth tracking and management.

◦ Payout Commit overview

Merchants can now view Payout Commit details, allowing them to open a specific Commit and manage all related information in a single view.

Major Improvements

◦ Tooltip on Payment scheme

The tooltip that appears when you hover over the Payment method in the grid now shows only activated Routes.

◦ Changed minimum password length

The minimum required password length is 12 under PSS DSS regulations.

◦ Updated modal image

The image in the following modal has been enhanced: Your session has expired.

◦ "actor_context" filtering for Merchant portal events by "actor_id": "mb_..."

For the GET /api/v1/event/events endpoint, the actor_context field is now hidden for Events triggered from the Dashboard (where actor_id has the mb_ prefix). This change prevents exposure of private user information and improves data security.

◦ Changed the Add domain modal

The Add domain modal at the Merchant portal configurator has been improved with the Merchant API option and a respective tooltip.

◦ Changed limit for invalid login attempts

The maximum number of failed login attempts has been increased from 5 to 10 across the Dashboard and Merchant portal. After the 10th failed attempt, the account should be locked by IP for 30 minutes to enhance security.