The native integration to between Mambu Core and Mambu Payments automatically books payments processed in Mambu Payments in the relevant customer accounts in Mambu Core.

Deposits integration

Workflows

Deposit accounts mapping

To use a deposit account from Mambu Core within Mambu Payments, you must first create a corresponding internal_account including:

• The account_number used for payment routing used to route payments across partner banks and payment schemes
• The cbs_account_id used to book payments in the relevant deposit account in Mambu Core

ℹ️

The internal_account ID is deterministically generated from the cbs_account_id and your Mambu Payments tenant ID eliminating the need to store the mapping.

🗓️

Automatic synchronisation of your Mambu Core deposit accounts with Mambu Payments internal_account is planned for release in early 2026.

Payments flows

Outbound payments:mambu_authorization validation

When you create a payment_order from an internal_account linked to Mambu Core, Mambu Payments automatically triggers a mambu_authorization validation to check that the corresponding deposit account account:

• Status: Ensures the account is active and not frozen or closed.
• Balance: Checks for available funds to cover the transaction amount.
• Authorized operations: Confirms the account is permitted to perform the requested type of payment.

If these checks are valid, the payment proceeds to the next step. If any check fails, the payment_order is automatically moved to a canceled status with a detailed failure reason, preventing any transactions to be booked incorrectly.

Incoming payments: real-time acceptance

Conversely, when an incoming payment is received on an internal_account, we perform a real-time query to Mambu Core to determine if the funds should be accepted (or debited, in case of an incoming direct debit). Based on the status and configuration of the deposit account in Mambu, our system will either accept the credit or reject the incoming transaction.

Direct debits

Payment order is canceled because Mambu Core did not allow it (closed account, unauthorised operation, insufficient funds, etc.)

sequenceDiagram

participant C as You
participant N as Mambu Payments
participant M as Mambu Core
participant S as Payment scheme
C->>N: Initiate payment order
N-->>C: pending_approval
N->>+M: Create authorization hold
M->>-N: Block payment
N->>N:Cancel payment
N-->>C: canceled

Payment order is rejected by the sponsor bank or the scheme. No transaction is booked on the deposit account.

sequenceDiagram

participant C as You
participant N as Mambu Payments
participant M as Mambu Core
participant S as Payment scheme
C->>N: Initiate payment
N-->>C: pending_approval
N->>+M: Create authorization hold
M->>-N: Validate payment
N-->>C: approved
N-->>C: processing
N->>+S: Forward payment
N-->>C: sent
S->>-N: Reject payment
N-->>C: rejected
N->>M: Cancel authorization

Payment order is successfully executed by the sponsor bank or the scheme. The authorization hold is settled.

sequenceDiagram

participant C as You
participant N as Mambu Payments
participant M as Mambu
participant S as Payment scheme
C->>N: Initiate payment
N-->>C: pending_approval
N->>+M: Create authorization hold
M->>-N: Validate payment
N-->>C: approved
N-->>C: processing
N->>+S: Forward payment
N-->>C: sent
S->>-N: Notify payment execution
N-->>C: executed
N->>M: Settle authorization

Credit transfer / instant payment received

Incoming payment is rejected because Mambu Core did not allow it (account closed, operation not authorized, funds insufficient, etc.)

sequenceDiagram

participant C as You
participant N as Mambu Payments
participant M as Mambu
participant S as Payment scheme
S->>N: Forward incoming payment
N-->>C: pending_approval
N->>+M: Create authorization hold
M->>-N: Block payment
N-->>C: rejected
N->>S: Reject payment

Incoming payment is received and booked on an internal account.

sequenceDiagram

participant C as You
participant N as Mambu Payments
participant M as Mambu
participant S as Payment scheme
S->>N: Forward incoming payment
N-->>C: pending_approval
N->>+M: Create authorization hold
M->>-N: Validate payment
N->>S: Confirm payment
N-->>C: received
N->>M: Settle authorization

Internal transfer

If the originating and receiving accounts of a payment are deposit accounts both managed in Mambu Core, Mambu Payments will book them directly in the relevant deposit accounts in Mambu Core and execute an end-to-end payment on the scheme.

sequenceDiagram

participant C as You
participant N as Mambu Payments
participant M as Mambu Core
participant S as Payment scheme
C->>N: Initiate payment order
N-->>C: payment_order:pending_approval
N->>+M: Create authorization holds
M->>-N: Validate payment
N->>N:Settle authorization
N-->>C: payment_order:executed

Loans integration

Workflows

🚧

This feature is still under development and will be documented soon.

Integration technical architecture and configuration

Mambu Payments and Mambu Core integrate using their respective public APIs, API keys, and webhooks. To configure your Mambu Core integration, you will need:

• An API key from your Mambu Core tenant. We recommend creating a new API consumer named Mambu Payments
• Transaction channel IDs in Mambu Core mapped with key attributes of your payments in Mambu Payments (connected account, payment type, direction, and currency) to determine the transaction channel to use when booking a transaction for a specific payment
• If needed, the Mambu Core ID of your suspense account