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.
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
Read database views
Use a message queue
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.
What your bank can do with it
Launch an app on a batch core
Open accounts without new core screens
Send payments as files or messages
Keep a mainframe and still go mobile
What it changes for your bank
No core replacement project
Read only where it matters
Every mismatch is visible
From first call to live
- 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.
- 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.
- 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.
- Step 4: LaunchTwo people approve the live configuration, and your customers get your app.
In-house and legacy cores: what IT teams ask
Our core only produces end-of-day files. Is that enough for an app?
Which databases can the database bridge read?
Do you support IBM MQ?
Do you need software installed inside our network?
Other systems banks connect
Finastra Equation
Finastra Midas
Apache Fineract
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