Connector · Cloud core banking platform

Mambu, mirrored by your ledger.

How our Ledger module works with Mambu when it is your core banking system: what stays in Mambu, what the module mirrors for your apps, and how we get you live.

Website
mambu.com
Modules
Ledger
Contract
We help you get it

Who Mambu is

Mambu is a cloud banking platform founded in Berlin in 2011 and now headquartered in Amsterdam. It provides lending, deposits and payments as software-as-a-service, and calls its approach composable: institutions combine its core with the other providers they choose.

Its customers range from fintechs and challenger banks to established financial institutions. When a client already runs Mambu as its book of record, our Ledger module works alongside it, which is why Mambu is one of the core banking systems it connects to.

What it does in your platform

  • Ledger

    Mambu stays the book of record for your accounts and loans. The module posts the platform's transactions to Mambu, mirrors the resulting balances for your apps and keeps the two in sync, so the apps show the numbers Mambu holds.

How the connection works

One connector in the Ledger module calls Mambu's API with an API key issued to a dedicated API consumer, and receives Mambu's events by webhook or through its Streaming API.

  1. A customer pays

    A customer sends money from your app, and the module posts the transaction to their account in Mambu through the API.

  2. Mambu books it

    Mambu records the transaction on the account and, for products linked to your general ledger, logs the journal entries automatically.

  3. The event comes back

    A Mambu webhook, or an event from the Streaming API, tells the module the transaction is booked. With idempotency keys enabled, a retried webhook carries the same key, so a repeat is recognised.

  4. The ledger mirrors it

    The module records the same movement as balanced entries and updates the balance your app shows.

  5. Both sides agree

    The module keeps its mirror in sync with Mambu, and any difference goes to a queue in the backoffice.

Next to other providers

With Mambu as the core, the module's other connectors work as usual: bank statements, card processor files and blockchain confirmations are still matched entry by entry, and your accountants still get the numbers in the tools they use.

If you later move from Mambu to another core, or let the ledger become your core, your apps keep talking to the same module and do not change.

When Mambu fits best

A strong fit when

  • You are a bank, lender or e-money institution that already runs Mambu as its core.
  • You want your core banking system run as a cloud service, not as software you operate.
  • Your lending and deposit products are already configured in Mambu.

Also worth a look

  • Thought Machine, a cloud-native core whose products are written as smart contracts.
  • The Ledger module itself as your core, if you do not need a separate core banking system.

How we get you live

  • The contract

    We help you get your Mambu account and contract in place, or connect the Mambu tenant you already run.

  • The products

    We map your Mambu products, accounts and general ledger accounts to the module, and agree which events Mambu sends by webhook or stream.

  • The keys

    API keys from a dedicated API consumer stay in your platform's secrets, with only the access the connector needs.

  • A full test run

    Everything runs first on your Mambu sandbox tenant, an isolated testing space with the full Mambu API, before production.

Questions

Asked about this connector.

How do we get started with Mambu?

Talk to us. We help you get your Mambu account and contract in place, or connect the tenant you run, map your products to the module and test the whole flow on your sandbox tenant first.

Which system is the book of record?

Mambu. The module mirrors its balances for your apps and keeps the two in sync, so customers see the numbers Mambu holds.

Webhooks or the Streaming API?

Mambu offers both. Webhooks push each event to one destination, while the Streaming API lets several consumers pull high volumes of events; we choose with you based on your volumes.

Can the module become our core later?

Yes, the module can also run as your core. The apps talk to the same module either way, so changing what sits behind it does not change what customers see.

Start your project

Tell us the idea. We'll show you the platform.

One call is enough to map your product to the modules that already exist.

  • Response in under one business day
  • NDA on request
  • No obligation
What are you building?