User agreement consent in the payment widget
Your merchant can now display a user agreement consent block directly in the payment widget.
Before completing a payment, the customer can open the document, review the merchant’s terms, and confirm their agreement.
New API parameters allow you to configure this block precisely:
• set own text and link,
• define the default toggle position,
• skip the consent page when needed
Benefit: The consent block can now be shown both in the payment widget and in the hosted payment page flow. This allows merchants to consistently capture customer agreement across different checkout scenarios and use it in case of disputes.
More details in the Customer Portal: Edit shop details and settings
Virtual refunds for card integrations
Virtual refunds are now available for card integrations that support this option.
This feature resolves cases where a refund was completed by the acquirer or a payment network, but the PSP system still shows the transaction as successful.
Example scenario:
The customer requests a refund from their issuer → Visa initiates the refund → the acquirer returns the funds → but the PSP does not receive a corresponding update.
As a result, the merchant sees an incorrect transaction status, and financial reconciliation becomes inconsistent.
With virtual refunds, the PSP can mark such transactions as refunded without sending a new refund request to the provider.
This keeps statuses accurate and ensures financial records match what has already happened on the provider’s side.
If real refunds are not supported in an integration but virtual refunds are, the system will automatically use the virtual option.
Benefit: correct and consistent reconciliation when refunds are initiated outside the PSP system.
New route for aggregated reports in DWH
A new API route in DWH now allows you to generate aggregated reports on processed transactions.
Functionally, it is similar to the reports available in the backoffice (Accounting → Reports), but it uses DWH data and offers more flexible filtering options.
This is useful for analytics, internal monitoring, and process automation.
Benefit: deeper transaction insights and more reliable analytics based on DWH datasets.
More details in the Customer Portal: Get an aggregated report for processed transactions
Smart Routing for verify-p2p transactions
The beGateway platform supports P2P card-to-card transfers. For clients who use this functionality, we have extended Smart Routing capabilities.
Smart Routing is now available not only for the transfer request (p2p) but also for the preliminary step - verify-p2p, where the system checks the possibility of the transfer and calculates the commission.
This makes it possible to select the correct gateway in advance, based on card parameters or routing rules.
This is particularly important for projects using several gateways with different commission structures for different card brands.
For example:
• cards from specific sets are routed through gateway 1;
• other cards through gateway 2.
The commission is calculated correctly from the start, and the transaction is processed through the optimal route.
Benefit: accurate commission calculation and consistent routing for P2P operations without manual adjustments.
More details in the Customer Portal: Edit shop details and settings