Changelog

Account objects now support bank_name and bank_address that are sometimes required when initiating cross-border payments.

You can now define and see the details of intermediary agents of a payment in the dashboard.

Account objects now support account_number_format and bank_code_format to enable format-specific validation for additional countries.

requested_execution_date enables scheduling payment orders for future processing. Payment orders with a future execution date are warehoused until they are ready for submission.

Webhook event retries now use base-2 exponential back-off (10s, 20s, 40s, 80s…), replacing the previous base-10 progression. Initial retries are faster while later attempts remain spaced out.

Mambu Payments can generate IBANs and domestic account numbers when you create internal accounts.

A Contact button is now available on incoming and outgoing VOP request pages. It opens your default email client with a pre-composed message.

Forward any message to a partner bank, CSM, or the Swift network through the API or the dashboard. This includes messages not natively supported by Mambu Payments, such as messages generated by another system.

Three new status details clarify TLS failures on outgoing VOP requests. See the full list of VOP failure codes and status details.

Configure scheme-specific bank holidays that affect payment processing timelines. This feature is available to direct participants only.