Payments Introduction
This feature is scheduled for deprecation. We recommend contacting Mambu Support to discuss alternative options.
The Mambu Payment Gateway (MPG) provides a user interface that facilitates one-time and recurring transactions using the Single Euro Payments Area (SEPA) scheme. For more information, see Mambu Payment Gateway.
The Mambu Payments Gateway API allows you to make, receive, reject, and refund standards-based payments. For more information, see our Mambu Payments Gateway API Reference.
The MPG is tightly connected to Mambu's core banking features. Payments are routed to the correct Mambu accounts, payer and payee details are automatically inserted into SEPA messages when possible, and general ledger accounts are kept up to date both for payments and, if using Anti-Money Laundering (AML), for movements of funds into suspense accounts.
The core functionality of the MPG can be extended to support additional AML and suspense account flows, such as using a pre-built Mambu Connector running on the Mambu Process Orchestrator and a supported partner such as ComplyAdvantage.
Using the MPG, customers can quickly gain access to the entire market of more than 27 countries in the Eurozone.
Supported flows
The Mambu Payment Gateway has been built according to the guidelines set out in the 2021 SEPA Credit Transfer and 2021 SEPA Direct Debit Core rulebooks and handles the following flows and messages:
Credit Transfer
Pacs.008.001.02 - Incoming/Outgoing payment Camt.056.001.01 - Incoming/Outgoing Recall request Pacs.004.001.02 - Incoming/Outgoing Authorize recall request Camt.029.001.03 - Incoming/Outgoing Deny recall request Pacs.002.001.03 - Incoming rejection/Outgoing positive status report
Credit Transfer Inquiries
Camt.027.001.06 - Claim Non-Receipt Pacs.028.001.01 - Status update on Recall of SCT Pacs.028.001.01 - Status update on Inquiry for existing camt.087 or camt.027 Camt.087.001.05 - Claim value-date correction Pacs.004.001.02 - Positive response for Request for Status Update on Recall Camt.029.001.08 - Sepa Inquiries response - Only negative confirmation at the moment for camt.087
Direct Debit
Pacs.003.001.02 - Incoming/Outgoing collection Pacs.007.001.02 - Incoming/Outgoing Reverse collection (sent by Creditor to Debtor) Pacs.004.001.02 - Incoming/Outgoing Refund collection (sent by Debtor to Creditor) Pacs.002.001.03 - Incoming CSM rejection
General prerequisites
Before using Mambu Payment Gateway, you must have the following:
- SEPA registration
- A system to manage mandates for direct debit payments
- Access to an automated clearing house
- The ability to generate and register IBANs for accounts
Mambu Core Banking prerequisites
Our Getting Started article walks through configuring the items listed below.
In Mambu Core Banking, you will need:
- An API Consumer and API Key
- A Mambu user account with API Access rights
- Transaction Channels that follow the pattern
{BIC}-{PAYMENT-TYPE}-{SCHEME}-{CURRENCY-CODE}-{DIRECTION}. For more information, see Create the payment transaction channels. - If using AML functionality, you will need accounts set up to hold suspended payments while checks are being processed.
- Mambu accounts should be mapped to an IBAN using the appropriate External Account Representation (EAR) endpoint. For more information, see External Account Representation - createMappings in our Mambu Payments Gateway API Reference.