Choisissez votre pays ou votre région

Your Equation core can still power a modern app.

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.

We build the Finastra Equation connector during your implementation programme, with the same connector kit as our existing connectors.

Core banking

How we connect to Finastra Equation

Finastra Equation, formerly Misys Equation, is a core banking system used by banks in the Middle East, Africa and Asia. It was built for IBM’s midrange servers (iSeries, now IBM i), and Finastra’s Equation Service Composer lets banks build their own services from Equation APIs.

Use Equation services

We call the services your bank exposes from Equation APIs, for example through Service Composer, for accounts, balances and payments.

Exchange files with its batch

Statements and payment files over SFTP fit Equation’s end-of-day cycle, through our existing ISO 20022 file connector.

Use a message queue

If your bank already sends Equation messages over a queue, the connector can use it. Today we speak AMQP 0-9-1, and IBM MQ is added when a bank needs it.
Data

What moves between Finastra Equation and your app

  • Accounts and balances, live where Equation answers in real time, else as of the last statement
  • Transactions with their references
  • Payment instructions, as service calls or pain.001 files
  • Payment status, from replies or pain.002 reports
  • Reconciliation cases when our records and Equation’s differ

Equation keeps every balance and posting, on your own servers. We keep only a reference to each account.

Use cases

What your bank can do with it

Run the app through end of day

While Equation runs its overnight batch, the app shows the last known balance with its time, and a payment shows as sent only once Equation accepts it.

Go mobile before a core move

Launch the app on Equation now. If you later move to another core, customers keep the same app and only the connector changes.

Open accounts online

Customers apply and pass identity checks in the app. Your team approves in the staff portal, and the account is opened in Equation.

Approve business payments

Business customers set approvers and limits in the app, and Equation receives only approved payments.
Why it matters

What it changes for your bank

No change on your IBM i

We use services and files Equation already supports, so your midrange team writes no new core code for us.

Honest balances

When Equation can’t answer, the app says the balance is not available. It never shows a stale figure as current, or zero.

A path off the old channel

Customers move to the new app at their pace, while your old internet bank keeps working.
Rollout

From first call to live

  1. Step 1: DiscoveryWe map your Equation release, its services, files and batch window with your midrange team.
  2. Step 2: Build the connectorWe build the Equation connector with our kit, using services where they exist and files elsewhere.
  3. Step 3: Test through a batch cycleConformance runs on your test system, including a full end-of-day, so the app behaves during the batch.
  4. Step 4: LaunchTwo people approve the live configuration, and your app goes to the stores.
Questions

Finastra Equation: what IT teams ask

Can customers pay while Equation runs its overnight batch?
A payment is marked as made only when Equation accepts it. Each one carries a unique key, so a retry after the batch never posts it twice.
Do we need a newer Equation release first?
Usually not. We use what your release exposes and fill gaps with files, and we tell you in discovery if a service is missing.
We plan to replace Equation. Is an app worth it now?
Yes, if customers need it now. The app sits on our normalised model, so moving cores means a new connector, not a new app.
Do you have RPG or IBM i developers?
We don’t change Equation’s code. Your midrange team or Finastra keeps that work, and we connect to what Equation already exposes.
Related

Finastra Fusion Essence

Keep Essence as your core. Your customers get one app in your brand, connected through Essence’s published APIs.
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

In-house and legacy cores

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.
Read more
Pilot programme

Running Finastra Equation? 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