Integration settings
The Mambu Core settings page lets you configure how Mambu Payments connects to your Mambu Core tenant and how transactions are booked against deposit and loan accounts.
Connectivity
| Field | Description |
|---|---|
| API URL | The base URL of your Mambu Core tenant API, e.g. https://{tenant}.mambu.com/api. |
| API key | The API consumer key used to authenticate every request to Mambu Core. Displays Configured when a key is stored. Contact your Mambu Payments account team to rotate it. |
The API consumer must have the following permissions on deposit accounts: view, make deposit, make withdrawal, intra-client transfers, inter-client transfers, apply adjustments, backdate transactions, bulk corrections, early withdrawals. It also needs create, edit, and view permissions on holds.
General
These settings control how Mambu Payments behaves when booking transactions in Mambu Core.
| Field | Description |
|---|---|
| Suspense account | The Mambu Core deposit account ID used to book irrejectable incoming payments (e.g. classic SCT) when the intended recipient account is unavailable or rejected by Mambu Core. The account must already exist in Mambu Core. See more on the dedicated page. |
| Timezone | The timezone used when computing transaction timestamps sent to Mambu Core. |
| Delete authorization before booking | When Enabled, Mambu Payments deleted any authorization hold before posting the final transaction. |
Lending integration
Controls how loan disbursements and repayments are turned into payments.
Disbursement
| Field | Description |
|---|---|
| Default payment type | The payment type used when disbursing a loan. |
| Booking trigger | The payment order status and event that triggers the CBS transaction in Mambu Core. |
Repayment by debit
| Field | Description |
|---|---|
| Default payment type | The payment type used for collections. |
| Fetch installments | When Yes, Mambu Payments fetches the installment schedule from Mambu Core to determine due dates and amounts automatically. |
| Collection lead time | How many days before the due date Mambu Payments initiates the collection. For example, 2 days before due date submits the debit early enough to meet scheme processing windows. |
| Timezone | The timezone used to evaluate installment due dates. |
| Installment reference | The reference string attached to each collection. |
| Booking trigger | Same as disbursement; the status that triggers the CBS repayment booking in Mambu Core. |
Others
| Field | Description |
|---|---|
| Booking trigger | The trigger for payment captures. |
Transaction channels
The transaction channels table maps each combination of payment attributes to a Mambu Core transaction channel. When Mambu Payments books a transaction, it looks up the matching row here to determine which channel to post under.
| Column | Description |
|---|---|
| Connected account | The Mambu Payments connected account the payment moves through. |
| Direction | Whether the payment is a credit (incoming) or debit (outgoing). |
| Nature | An optional payment nature filter. Leave blank to match any nature. |
| Payment type | The scheme (e.g. SEPA Credit Transfer, SEPA Direct Debit, SEPA Instant Credit Transfer). |
| Currency | The payment currency. |
| Transaction channel | The Mambu Core transaction channel that will be used when posting the matching transaction. |
Every combination of payment attributes you expect to process must have a matching row. An unmapped combination causes the booking to fail.
Updated 11 days ago
