Choose your country or region

Integrations

Don’t replace your core. Connect it.

We plug your core banking system and your providers – identity checks, sanctions screening, company registry, email – into one customer app and one staff portal. Your core keeps the money.

Adapters

Swap a provider. Nothing else moves.

Each system plugs in through its own adapter. Change your screening provider and your app, your staff screens and your data stay exactly as they are.

Core banking

Open accounts, read live balances and transactions, send payments and track them.

Identity verification

Check applicants are who they say they are, through your provider.

Screening

Sanctions, politically exposed persons and adverse media, through your provider.

Company registry

Confirm a business and who owns it, through a registry or know-your-business (KYB) provider.

Payee name check

Warn customers when a payee’s name doesn’t match the account.

Malware scanning

Scan every uploaded document before staff can open it.
Your core

Legacy core? Good. We speak files.

No usable API? Your core can still exchange files. We read and write standard ISO 20022 bank files, encrypted if you want.

Modern core with an API? We connect to it directly – a connector for the open-source Apache Fineract core is already built. Either way, balances are read from your core, never copied.

  • ISO 20022 files over SFTP, S3 or a shared folder
  • No ledger here – your core keeps the money
  • Mismatches go to your staff, never fixed silently
What your IT team sees

New API or old file. Same clean answer.

Whatever your core speaks, it ends up in one banking model – with every connection checked and logged.

Modern API

A modern core answers directly. Amounts arrive as exact strings – never rounded, never floating point.

Decades-old files

ISO 20022 statements arrive overnight. Each entry is matched to the payment it belongs to.

Live status

Every connection is checked and every call logged. Anything that doesn’t match goes to a person.
Connector directory

Global, regional and local. And anything else you run.

Core banking, identity, screening, payment systems, mobile money, cards and more, across your country, your neighbours and the world. Some connectors exist today; we build the rest in your programme with the same connector kit.

143 systems

  • PostgreSQL database viewsRead-only views of accounts and transactionsFiles and legacy bridges
  • RabbitMQ and Amazon MQRequests and payments over AMQP message queuesFiles and legacy bridges
  • IBM MQMessage queues on IBM middlewareFiles and legacy bridges
  • VeriffDocument, selfie and liveness checksIdentity verification
  • Dow Jones Risk & ComplianceSanctions, PEP and adverse media screeningScreening and fraud
  • LexisNexis Risk SolutionsScreening and identity dataScreening and fraud
  • FeedzaiFraud and transaction monitoringScreening and fraud

Not on the list? We'll connect it.

If your system has an API, exchanges files or exposes a database or message queue, we can connect it. Custom connectors are part of your programme.

Connections

Every system. One place to watch it.

Core, files, checks, email and sign-on plug into the same model – so your team watches one set of signals, not ten.

Every category, one model.Each kind of system has its own adapter. Swap a provider and nothing else moves.
Calls, retries and failures, in view.Every provider call is logged without its data, with metrics for your monitoring dashboards and alerts.
Built to be safe

Systems fail. Money stays right.

Retry without harm

Every change carries a unique key, so a repeated request never acts twice.

Log every call, not the data

Each provider call is logged with its outcome and timing – never the personal data inside.

Refuse test providers in production

Production won’t start on simulated providers. Real customers never get fake checks.
Honest status

What’s built. What we build for you.

Adapters and test providers are built and tested. The connector for your exact core and providers is built during your implementation.

  • BuiltAdapters and test providersOne adapter per kind of system, tested end to end
  • BuiltEmail (SMTP)Customer and staff emails through your mail server
  • BuiltClamAV malware scanningEvery upload scanned before staff can open it
  • Built with youYour core banking systemConnected by API or files during your programme
  • Built with youYour KYC and screening providersWired to the checks you already use
  • Built with youSigned webhooks for your systemsEvents pushed to your systems, signed
  • Built with youAPI access for bank systemsYour own systems calling ours, safely
Questions

What IT teams ask first.

Do you integrate with our core banking system?
Yes. Search for it in the directory above; if it isn't there, we still connect it, by its API, by files, through database views or a message queue. We build the connector during implementation. Tell us your core and version and we'll scope it with you.
Can we change providers later?
Yes. Switching a provider means switching its adapter. Your app, staff screens and data stay the same.
Is there an API?
Everything the screens do runs through a documented REST API. API access for your own systems is on the roadmap.
Pilot programme

Show us your oldest system.

Your core, your providers, your strangest file format. We’ll show where each one plugs in.

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