Services & institutional customers
Sections ↑Mambu offers SaaS core banking components that financial institutions can configure for deposits, lending and accounting. Unlike a retail broker’s client terminal, it supplies an internal system of record on which a bank or fintech can build its own product, app and operating processes. The customer remains responsible for legal permissions and for the services provided by connected partners.[1]
The platform exposes programmatic operations to create clients, savings and loan accounts, book transactions, configure interest rates and manage general-ledger records. These are powerful administration and booking capabilities; bank-grade entitlement controls and reconciliation are essential because an API event can alter financial records rather than simply display information.[3]
In September 2026 Mambu introduced Intelligent Core as a strategy combining Mambu Core, Payments and its Agentic layer. The announcement establishes product direction and availability claims; it does not mean every tenant has all AI functions or autonomous actions enabled under its existing contract.[5]
Core banking records and functions
| Area | Documented API scope |
|---|---|
| Customers | Client and group records.Source 3 |
| Deposits and savings | Accounts and transaction operations.Source 3 |
| Lending | Loan accounts and servicing actions.Source 3 |
| Accounting | Journal entries and ledger-related configuration.Source 3 |
| Administration | Roles, permissions, tasks and product configuration.Source 3 |
Intelligent Core product layers
| Layer | September 2026 positioning |
|---|---|
| Mambu Core | Core banking foundation.Source 5 |
| Mambu Payments | Connected payment capabilities.Source 5 |
| Mambu Agentic | AI-oriented layer in the Intelligent Core strategy.Source 5 |
| Entitlement | The announcement does not establish that every existing tenant receives every module automatically.Source 5 |
Platforms & integrations
Sections ↑Mambu documents separate production and sandbox tenant URLs, with UI and API access to the same core banking features. API keys, user roles and tenant configurations are part of the integration; applications should not rely on unrestricted administrative keys for routine customer actions.[2]
A key 2026 continuity issue is the Mambu Ecosystem notice that prebuilt connectors are being phased out and Mambu Process Orchestrator is scheduled for decommissioning. Existing customers should obtain their notice and migration plan, then identify whether direct API, webhooks or a replacement integration service owns each event.[7]
API versions and delivery mechanisms
| Interface | Published position |
|---|---|
| API v2 | Recommended for new integrations.Source 3 |
| API v1 | Legacy interface no longer actively developed.Source 3 |
| Streaming API | Separate enterprise event-feed capability.Source 3 |
| API references | Endpoint permissions and version conventions remain relevant even when UI and API expose similar functions.Source 4Source 3 |
Payments-to-core connection requirements
| Requirement | Purpose |
|---|---|
| API credentials and roles | Permit the intended loan/deposit account operations.Source 8 |
| Whitelisted connectivity | Allow the approved network path.Source 8 |
| Transaction-channel mapping | Map payment operations to the correct core booking channel.Source 8 |
| Account reference and currency | Identify the account and value being posted.Source 8 |
Legacy ecosystem changes
| Component | Published direction | Operational consequence |
|---|---|---|
| Prebuilt connectors | Being phased out. | Inventory dependencies before replacing individual connections.Source 7 |
| Mambu Process Orchestrator | Scheduled for decommissioning. | A supported replacement must own each orchestration step.Source 7 |
| Direct API/event integration | Separate integration route. | Migration needs application and event-handling work; it is not just a hostname change.Source 3Source 7 |
Pricing & commercial terms
Sections ↑Mambu describes a composable, usage-scaled commercial model. That does not supply a public core-banking subscription price suitable for every institution. Pricing scope has to identify active products, account or transaction metrics, environments, implementation, support and the payment or analytics modules purchased.[1]
Mambu Insights has documented subscription and consumption components. The fixed annual fee is tiered by transactions per second. Variable credits pay for certain storage and computing work; documentation includes a storage rate of 100 credits per terabyte per month, and compute charges depending on worker size and runtime. Credits are not a stated dollar or euro price.[6]
Insights fixed annual subscription
| Dimension | Published charging model |
|---|---|
| Tier basis | Transactions per second.Source 6 |
| Included foundation | UI, licensing, security operations and Core Engine.Source 6 |
| Streaming | Includes the described streaming component.Source 6 |
| Tenant | The stated fixed scope includes one production tenant.Source 6 |
Insights consumption units
| Usage | Published rule | Important distinction |
|---|---|---|
| Compressed storage | 100 credits per TB per month, measured on the first day. | Credits are not a currency price.Source 6 |
| Compute | MCU consumption varies with worker size and runtime. | Workload shape changes consumption.Source 6 |
| Runtime minimum | One-minute minimum applies to the described compute charging. | Short jobs still meet the minimum.Source 6 |
| Cash quotation | Contracted credit price and purchase terms are needed. | The documentation alone does not provide total cash cost.Source 6 |
Implementation & delivery
Sections ↑Core booking versus payment movement
| Event | What it establishes |
|---|---|
| Payment message accepted | The connected payment process has accepted a message.Source 8 |
| Core account posted | A ledger event has been booked to the mapped account/channel.Source 8 |
| External settlement | Funds movement through the payment arrangement is a separate event.Source 8 |
| Reconciliation | Account and payment records must be joined before treating all stages as complete.Source 8 |
Migration acceptance — editorial guidance
| Workstream | Concrete reconciliation |
|---|---|
| Product configuration | Interest, fees, currencies and account rules.Source 2 |
| Opening positions | Balances, accrued interest and pending transactions.Source 2 |
| Permissions | API keys restricted to the intended activities.Source 3 |
| Connector replacement | Delivery, duplicate handling, monitoring and recovery for each event.Source 7 |
Support & contacts
Sections ↑The public documentation provides developer conventions and product administration material. Production incident response, service credits, support hours and escalation depend on the selected enterprise agreement. A sandbox being reachable or an API appearing in docs does not establish support entitlement for every module.[2]
Published contact and documentation routes
Scope Use current API conventions, versioning and authentication guidance.
Scope Discuss bank/lender operating model and commercial entitlements.
Scope Check the particular fixed/variable data platform units.
Permissions & service scope
Sections ↑Mambu is a banking software supplier, not a substitute for a banking licence. An institution using it to hold account records still requires its own legal authorisation and arrangements with payment networks, custodians, deposit protection schemes or lending entities where applicable.[1]
API actions such as loan disbursements and withdrawals require permissions, safeguards and reconciliation appropriate to the regulated institution. Mambu’s ability to post a ledger entry is not evidence that a transaction has been externally settled through a payment rail.[8]
Software access and banking authority
| Capability | Boundary |
|---|---|
| Deposit account record | A software record does not itself confer deposit-taking permission.Source 1 |
| Loan servicing API | Booking or disbursement functions require the institution’s approved lending process.Source 3 |
| Payment integration | Connected payment partners and scheme arrangements remain separate.Source 8 |
| Agentic layer | Product strategy does not establish permission for unrestricted autonomous actions on every tenant.Source 5 |
Operator & evidence
Sections ↑Mambu’s corporate strategy positions the platform around composable core banking and open integrations. The Intelligent Core announcement marks an evolution toward connected analytics and AI; specific implementation and product rights should be linked to the customer’s contract and release status.[5]
Published corporate identity
- Operator
- Mambu B.V. is the published website operator; service contracting entity is specified in the agreement
- Service scope
- Composable SaaS core banking infrastructure for deposit, lending and general ledger products, supported by API v2, payments gateways, streaming and integrations.
- Customer types
- Banks; Credit unions; Lenders; Fintech firms; Embedded-finance platforms; Banking technology partners
- Delivery
- SaaS; API; Hosted
- Pricing publication
- Public and quoted pricing
- Platforms
- Mambu Core; Mambu Payments; Mambu APIs; Mambu Insights; Mambu Agentic
- Integrations
- API v2; Payments API; Streaming API; OpenAPI specifications; API keys and webhooks
- Implementation
- Configurable cloud tenant and separate production/sandbox environments, system and account configuration, API roles, payment scheme arrangements, and migration from legacy API or connector features.
- Support
- Enterprise support and account assistance; feature-specific developer documentation provides migration guidance but does not itself establish contracted incident SLAs.
- Permissions and regulatory scope
- Core banking software does not confer deposit-taking, lending, payment-services or other financial permissions. A regulated institution must operate its own approved banking and payment partner relationships.
Provider metadata checked 26 Oct 2026Source 1Source 2Source 3Source 4Source 5Source 6Source 7Source 8Source 9
Sources & further reading
- Mambu composable banking product overview Mambu · Accessed 22 Oct 2026
- Mambu platform and environment documentation Mambu · Accessed 22 Oct 2026
- Mambu API v1/v2, Payments and Streaming distinctions Mambu · Accessed 22 Oct 2026
- Current Mambu API reference Mambu · Accessed 22 Oct 2026
- Mambu Intelligent Core launch Mambu · 2 Sep 2026 · Accessed 22 Oct 2026
- Mambu Insights pricing and consumption rules Mambu · Accessed 22 Oct 2026
- Mambu Ecosystem connectors and MPO decommission notice Mambu · Accessed 22 Oct 2026
- Mambu Payments integration and account permissions Mambu · Accessed 22 Oct 2026
- Mambu imprint Mambu · Accessed 26 Oct 2026
This profile reports dated public information, including provider-published services and terms. It does not independently test or guarantee service delivery, integrations or performance. Inclusion is not an endorsement. Permissions and protections apply only to the named legal entity, service and client category; check the current official records and your contract.