We have launched the ability to schedule payment orders for future execution using the requested_execution_date field. This allows for automated warehousing of payments until they are ready for processing.
Starting from today, the events delivery retry strategy uses a base-2 exponential back-off (10s, 20s, 40s, 80s…), replacing the previous base-10 progression. This provides faster initial retries while still spacing out later attempts.
You can now configure Mambu Payments to generate IBANs or domestic account numbers when creating internal accounts.
You can now contact other VOP participants directly from the Mambu Payments dashboard, reducing manual data entry and speeding up resolution times.
You can now use Mambu Payments to forward any message to your partner bank, CSM, or the Swift network. This includes messages that might not be natively supported by Mambu Payments and might be generated by another system. Messages can be forwarded using the dashboard or API.
To improve the clarity of errors related to TLS when sending VOP requests, we have added 3 new status details:
Direct participants in payment networks can now configure specific holidays that impact payment operations.
Starting from January 19, 2026, a new status and related transitions will be added to the lifecycle of incoming direct debit payments.
You can now add a notification email to your webhooks. If your webhook is paused due to repetitive errors, we'll send an alert to this address. Learn more here.
We release a number of improvements to our VOP product. In particular, we:
