Bank simulator
Learn how to use the bank simulator to test and validate your Mambu Payments (formerly Numeral) integration
The bank simulator allows customers to simulate payments, payment status reports (PSRs), and account statements received from partner banks, CSMs, or connectivity providers to create payments, balances, and transactions as well as update payment statuses.
The bank simulator can be used in two different ways:
- Using built-in scenarios like creating incoming payments, updating payment statuses, or creating balances and transactions
- Uploading a bank or CSM message to trigger the creation of incoming payments, balances, and transactions or update of related payments
1. Built-in scenarios
The bank simulator supports the the following built-in scenarios, with more scenarios added on a regular basis:
- Create incoming payment
- Update payment status to executed, rejected, or pending
- Create balance
- Create transaction
Built-in scenarios are supported in the API and dashboard. Built-in scenarios are only supported for Mambu Payments (formerly Numeral)'s internal mock bank Demo Bank.
Contact [email protected] if you would like us to support more scenarios.
2. Message upload
You can use the Simulate message received API endpoint to upload a message.
The bank simulator uses standard XML messages, Swift MT messages, and Bacs Standard 18 messages. For corporate customers, standard ISO 20022 XML messages are supported. For SEPA indirect or direct participant customers, standard EPC XML messages are supported.
Message upload is only supported in the API. Message upload is compatible with Mambu Payments (formerly Numeral)'s internal mock bank Demo Bank as well as banks supported.
Contact [email protected] if you need technical support to use the bank simulator.
Header
The content type differs based on the type of message. For XML messages, use Content-Type: "application/xml". For other types of messages like Swift MT messages or Bacs Standard 18 messages, use Content-Type: "text/plain".
Query params
Param | Description |
|---|---|
id | The ID of the connected account used to receive the message and create or update the corresponding Mambu Payments (formerly Numeral) object. |
bank_service | The bank service to use, e.g., |
file_name | The unique file name to generate with up to 35 characters. The file name might or might not include a file extension. |
Body params
Param | Description |
|---|---|
data | The raw content of the message to be sent. |
Test packs
Get in touch with your Delivery Manager or Integration Consultant to receive readily-available test packs, including sample messages and Postman collections.
Updated 11 days ago
