Choisissez votre pays ou votre région

A modern app on your legacy core, without a rewrite.

Your core may be decades old, built in-house or running on a mainframe. We connect to it through what it already does well: files, database views and message queues.

The connector for In-house and legacy cores is built and ready to configure for your bank.

Core banking

How we connect to In-house and legacy cores

Many banks run a core built in-house or one whose vendor no longer ships new APIs. These systems often exchange data through overnight files, a reporting database or a message queue. Our bridges use those same channels, so your core keeps working the way your team knows.

Exchange ISO 20022 files

We read camt.052, camt.053 and camt.054 statements and pain.002 and pacs.002 status reports, and write pain.001 payment files, over SFTP or Amazon S3, with optional PGP.

Read database views

Your team publishes read-only PostgreSQL views of accounts, balances and transactions. We read them with a user that cannot write, and we check the column mapping before use.

Use a message queue

We talk to your core over AMQP 0-9-1, for example RabbitMQ or Amazon MQ. Duplicate messages are dropped, and a message we can’t read goes to a dead-letter queue for a person.
Data

What moves between In-house and legacy cores and your app

  • Accounts and balances, from statements, views or messages
  • Transactions, with their status and reference
  • Payment instructions to your core as pain.001 files or queue messages
  • Payment status back from pain.002 and pacs.002 reports
  • Reconciliation cases when a figure doesn’t match, for your team to review

Your core keeps every balance and posting. We never write to your database, and a mismatch opens a case for your team rather than changing money.

Use cases

What your bank can do with it

Launch an app on a batch core

If your core updates overnight, the app shows balances as of the last file and says how fresh they are. Customers never see a guessed figure.

Open accounts without new core screens

Customers apply online and pass identity checks. Your team approves in the staff portal, and the account is opened through the channel your core accepts.

Send payments as files or messages

Approved payments leave as pain.001 files or queue messages your core already processes, and their status comes back the same way.

Keep a mainframe and still go mobile

The mainframe stays your book of record. The app reads what it publishes and sends instructions in a format it accepts.
Why it matters

What it changes for your bank

No core replacement project

You keep your core and your team’s knowledge of it. The app is built around what it already exchanges.

Read only where it matters

Database bridges read views, never tables, and writes go through files or messages your core validates.

Every mismatch is visible

Reconciliation compares what we sent with what your core reports, and opens a case your team closes.
Rollout

From first call to live

  1. Step 1: Map what your core exchangesWe list the files, views and queues your core already has, and agree which ones carry balances, transactions and payments.
  2. Step 2: Configure the bridgeWe set the SFTP or S3 location, the view mapping or the queue names for your bank, and allow-list each destination.
  3. Step 3: Test on your sandboxA conformance run reads accounts and sends test payments to a test copy of your core, kept separate from the live system.
  4. Step 4: LaunchTwo people approve the live configuration, and your customers get your app.
Questions

In-house and legacy cores: what IT teams ask

Our core only produces end-of-day files. Is that enough for an app?
Yes. The app shows balances as of the latest statement and tells the customer when they were updated. Intraday camt.052 reports, if your core produces them, make them fresher.
Which databases can the database bridge read?
PostgreSQL views today. Other databases are built during your programme if your core needs one, with the same read-only rule.
Do you support IBM MQ?
Not yet. The message-queue bridge speaks AMQP 0-9-1 today. IBM MQ needs IBM’s client under IBM’s licence terms, so we add it when a bank needs it.
Do you need software installed inside our network?
No. The bridges connect from our environment to the endpoints you expose, over pinned, allow-listed connections. If your security team prefers another set-up, we agree it in discovery.
Related

Finastra Equation

Equation has run your bank for years. We connect to it through its APIs or the files it already exchanges, and your customers get an app in your brand.
Read more

Finastra Midas

Keep Midas as your book of record. Your customers get a branded app on web, iPhone and Android that reads from it live.
Read more

Apache Fineract

Your customers open accounts, check balances and pay from one app in your brand. Fineract stays your book of record, and our connector talks to it through its REST API.
Read more
Pilot programme

Running In-house and legacy cores? Let's map it.

Tell us your version and how your teams use it. We'll show where it plugs in and what your customers get.

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