How does Mambu handle reconciliation?

Mambu is an API-first platform. It does not have a built-in reconciliation module for external bank statements. Instead, it relies on 'Process Orchestrators' (like MPO) or external tools like Reconwizz to consume its Webhooks and perform the matching externally.

What is the best integration method for Oradian?

For Oradian, which serves many offline-first markets, a hybrid approach works best: scheduled API calls for real-time data, backed by daily CSV exports for comprehensive end-of-day verification.

Blog Post

Core Banking Integration
December 14, 2025

Seamless Reconciliation for Mambu / Oradian Core Banking Users

The banking world is splitting into two camps: those stuck on legacy mainframes (like T24/Temenos) and those migrating to "Composable" cloud-native cores like Mambu and Oradian. While legacy systems struggle with data extraction, modern cores are API-first. However, this flexibility creates a new problem: how do you reconcile a high-velocity stream of JSON webhooks against a traditional bank statement? This guide explains how to bridge the gap using modern reconciliation architecture.

The "Composable" Advantage (and Headache)

Diagram of a Composable Banking architecture with Mambu at the center.

Visualizing Webhooks vs Batch Processing.

Systems like Mambu are designed to be the "ledger" and nothing else. They don't want to be your reconciliation engine. They expect you to plug in a specialized tool for that.

The Data Flow: When a loan is repaid via Stripe, Stripe sends a webhook to Mambu to update the balance. But what if the webhook fails? What if Stripe says "Success" but the settlement file says "Failed"? Without a reconciliation layer sitting between the Gateway and the Core, you risk ledger drift.

Mambu Integration: The Webhook Strategy

Mambu emits "Opt-In" webhooks for every transaction creation or state change.

1. Capture: Configure Reconwizz to listen to the Mambu `Transaction Created` webhook. This builds your "Internal Ledger" view in real-time.
2. Compare: Asynchronously, ingest the settlement file (CSV/MT940) from your payment partner (e.g., Flutterwave or Citibank).
3. Match: The system matches the real-time webhook ID against the batch settlement ID. Any missing webhooks are flagged immediately as "System Failures."

Oradian Integration: The Hybrid Approach

Oradian is popular with MFIs in emerging markets where internet connectivity can be spotty.

The Sync Challenge: Transactions might be recorded offline on a tablet and synced hours later. A real-time webhook approach might miss these.

The Solution: Use a hybrid model. Use APIs for real-time checks during the day, but enforce a "Hard Close" at night where Reconwizz pulls a full "Daily Transaction Report" from Oradian via API or SFTP. This catches any offline transactions that synced late, ensuring the EOD process is accurate.

Handling Value Dates

A common issue with modern cores is the difference between "Booking Date" (when the API call happened) and "Value Date" (when the money effectively moved). Mambu supports both. Ensure your reconciliation rules match on Value Date to avoid interest calculation errors during the month-end close.

Conclusion: Don't Build It Yourself

Because Mambu and Oradian have open APIs, the temptation is to write a custom Python script to reconcile them. As we discussed in our Build vs. Buy guide, this is a trap. Maintenance of custom API connectors is expensive. Using a pre-integrated platform like Reconwizz allows you to go live in weeks, not months, and ensures your "Composable" bank remains agile.

Temenos T24 Integration Previous Post Solving the Card Settlement Challenge Next Post