Interbank payments switch
The bridge that connects your payments platform to any banking rail
ARMADILLO2 is the switch that translates, authorizes and settles transactions between a payments platform and the bank. It replaces custom integrations with a single, production-proven component that speaks the language of every rail so your team doesn't have to.
What it is
The piece that sits between your payments platform and the banking system.
Transactional switch
Authorizes, settles, reconciles and notifies every movement of money, with the protocol and timing the bank requires.
Infrastructure, not an app
It's not an end-user product: it's the layer that turns a transaction started in an app into a real credit in a bank account.
Traceable and reconcilable
Every operation is recorded end to end, ready to match against what the bank confirms.
What it solves
The part nobody wants to build twice.
Authorization and settlement
Credits and debits against the banking rail, with automatic retry when the response doesn't arrive in time.
Reconciliation
Matches what the platform believes happened against what the bank confirms, surfacing any discrepancy before it becomes an accounting problem.
Operational reporting
Generates settlement reports for operations and finance, without asking anyone to cross-check spreadsheets by hand.
Webhook notification
The result of each operation reaches the originating system as soon as it's available, not at the next batch window.
Maintainer portal
A dedicated interface to retry, clear cache or check the state of a transaction without touching the database.
Who it's for
For anyone moving money between a platform and a bank.
Payment platforms and wallets
That need to connect to a banking rail without building that integration from scratch.
Financial institutions
That need their own settlement component, not dependent on a third party.
Teams with fragile integrations
That today maintain hand-built bank connections with no visibility into errors or retries.
How it's built
Independent services by responsibility, not a monolith.
Independent services
Authorization and settlement, movement extraction, report generation, notification and maintainer portal, each with its own responsibility.
Batch with retry
Reconciliation and extraction cycles run in batches, with configurable retry windows.
Isolated banking rail
The SOAP/XML integration with the bank stays behind a dedicated layer, so the rest of the platform never needs to know that protocol exists.
Why it matters
The alternative to your own switch is depending on the integration built by whoever needed it first, with no clear owner and no room to evolve. ARMADILLO2 comes out of years of real operation solving exactly this problem: rewritten, documented and packaged so any institution can adopt it without inheriting that debt.
Have a bank integration you need to keep alive?
Let's talk about how ARMADILLO2 can replace it with infrastructure that has an owner.
Let's talk