اختر بلدك أو منطقتك

Keep your core. Put a new app on top of it.

Connectors, ISO 20022 files and database bridges: how a new app runs on the core you already have.

By Everbranch team · Published · Updated · 5 min read

Most small banks don’t lose customers because of their core banking system. They lose them because of the app in front of it. The core keeps the money, the accounts and the rules your regulator already checked. The app is what your customers judge you by every day.

So the question is rarely “should we replace the core?” It is “can we give customers a modern app without touching it?” For most banks, the answer is yes. This guide explains how: which ways a new app can connect to an older core, what stays in the core, and how you test it before a single customer sees it.

Why replacing the core is the wrong first step

A core replacement touches every account, every product and every report. It is a multi-year project with a long tail of risk, and while it runs, your customers still use the old app. A new app on the existing core turns that order around: customers get the better experience first, and the core question can wait until it has its own business case.

It also keeps your accounting where it belongs. A core banking system is the system of record for balances and ledgers. An app layer that adds its own ledger creates a second version of the truth, and two versions of a balance is a reconciliation problem waiting to happen. Everbranch keeps no ledger: balances and transactions are read live from your core, and a core that doesn’t answer shows “not available”, never zero.

Four ways an app can reach an older core

Cores differ more than their brochures suggest. A bank in Lagos may run a vendor core with a modern API; a bank in Khartoum or Erbil may run a system from the 2000s that only exchanges files at night. A good integration layer meets the core where it is. These are the four routes we use, chosen per bank in discovery.

1. A direct API connector

When the core has an API, the app talks to it directly: open accounts, read balances and transactions, send payments and track them. A connector for the open-source Apache Fineract core is already built, and connectors for vendor cores such as Temenos Transact, Oracle FLEXCUBE or Path Solutions iMAL are built in your programme with the same connector kit.

2. ISO 20022 files

Many older cores can still produce and read standard bank files. ISO 20022 is the international standard for financial messages: statements, payment instructions and status reports in a shared format. The file connector reads statements and payment reports from your core and writes payment files back, over SFTP with pinned host keys, object storage or a shared folder, encrypted with PGP if you want.

3. A database bridge

Some cores have neither an API nor files, but they do have a database. The database bridge reads read-only views your IT team creates, with every name mapped and checked. It never writes to your core with SQL: payment instructions go back through the file or message channel instead.

4. A message queue

If your core already publishes events to a message queue, the message-queue bridge listens on it. Each message is processed once even if the queue delivers it twice, and a message that can’t be read goes to a dead-letter queue and to a person, never into a customer’s balance.

What moves between the app and the core – and what doesn’t

Whatever the route, everything lands in one banking model. Your app, your online account opening and your staff portal all talk to that model, not to the core’s quirks. That is why the same app can run on a modern API core in Riyadh and a file-based core in Juba.

  • Account opening at approval, recorded once even if the request is retried
  • Balances and transactions, read live from the core when the customer looks
  • Payment instructions, sent once and tracked until the core confirms or refuses them
  • Statement entries, matched to the payment they belong to

Money never moves on our side. Amounts are exact strings in minor units, never floating point, and every change carries a unique key so a retried request can’t pay twice. When a file entry and a payment don’t match, a reconciliation case goes to your staff. Nothing is fixed silently.

Connections are configured per bank, with two people

A connection to your core is a control, not a setting. Each one is a versioned configuration for your bank alone: the endpoint, the credentials, the settings your connector needs. Credentials are sealed with your bank’s own encryption key and dropped whenever the endpoint changes, so nobody can point your secrets at a different host.

Publishing a configuration needs a second, independent person, a step-up check and a review of the exact content. Rolling back works the same way. Every outbound connection is then checked against your bank’s list of allowed destinations, which your team can read. More on these controls on our security page.

Test against your sandbox before customers do

Before launch, every connector runs a conformance kit against your core’s test system: reading accounts, balances and transactions, and – only on a sandbox proven separate from every live endpoint – sending test payments. A production configuration is only ever read, never written to. Runs are bounded in time and calls, and each result is kept as evidence for your launch-readiness checklist.

That evidence is part of the implementation programme our team runs with yours: discovery, mapping your core and tools, building connectors, designing the experience, testing on your sandbox, then launch. How it works walks through each phase.

Questions to ask any vendor about your core

Whether you work with us or not, these questions sort a real integration from a slide:

  • Does the app keep its own ledger, or read balances from our core?
  • What happens to a customer’s balance when our core is down?
  • If our core has no API, can you read files, database views or a message queue?
  • How do you stop a retried payment from paying twice?
  • Who can change the connection to our core, and does it need a second person?
  • Can we run your tests against our sandbox before launch?

If you are weighing a ready-made app from your core vendor against a separate app layer, our core vendor comparison sets out both sides. For the money side, what a bank mobile app costs covers how pricing usually works, and our pricing page explains ours.

Pilot programme

Show us your oldest system.

Tell us your core and its version, and we’ll show you exactly where it plugs in.

  • Your name and colours in the demo
  • Straight answers for risk, compliance and IT
  • No commitment