Skip to main content
Follow the steps in Get started with connectors before proceeding. Mambu access: An active account in the Mambu production or sandbox environment. Network connectivity: Verify that your network routes traffic between the Mambu environment and Banking OS Connectivity. For supported options, see Network connectivity. Environment details: You need the following environment details from Mambu:

​
Prepare the connector

Backbase deploys this connector. To share connectivity details and provide the environment details, follow these steps:
  1. Share connectivity details. Share connectivity details between Banking OS and Mambu as described in Network connectivity.
  2. Send environment details to Backbase. Send mambu.baseUrl, mambu-user-id, and mambu-password to your Backbase support team.
For property names and defaults, see Reference.

​
Testing your integration

To use the Payments Unified API, include your Banking OS subscription key in the request header. If you don’t have a key, contact your Backbase support team to request one. Test the API using the Postman collection.

​
Troubleshooting

If your connector isn’t responding as expected, check these common scenarios.
Cause: The Banking OS gateway cannot establish a handshake with the Mambu endpoint. This typically indicates an upstream service outage at Mambu or a network routing failure.Solution: Verify the operational status of the Mambu environment. Check the Mambu status page or contact Mambu support.
Cause: The request to Mambu exceeded the configured timeout period. This may indicate performance issues at Mambu or network latency problems.Solution: Verify the operational status of the Mambu environment and check for any performance degradation.
Cause: The user-id or password provided during setup is incorrect, expired, or the user lacks the required permissions in Mambu.Solution: Re-verify your credentials with your Mambu administrator and ensure the user has the required permissions. Contact your Backbase support team to update the connection credentials if needed.
Cause: The number of incoming requests exceeds the defined threshold for your subscription tier. This “429 Too Many Requests” response protects the stability of the Banking OS and Mambu infrastructure.Solution: Review your app’s request patterns to identify unexpected spikes. If you need higher throughput, contact your Backbase support team to request a higher rate limit.