The connector directory
Every pre-built connector across banks, PSPs, open banking, and digital-asset rails. Filter by category and capability, or build your own on the Generic Connector framework.
Adyen payment and settlement data in the uniform model, from authorization through payout batch.
Marketplace wallets, pay-ins, and payouts from Mangopay, mapped to ledger accounts per buyer and seller.
Routable accounts payable and mass payouts, ingested and initiated.
Charges, refunds, and payout events from Stripe normalized into the uniform model, with transfer execution through the same interface.
Bank balances and transactions across thousands of institutions via Plaid, for reconciliation and cash visibility.
Bank account aggregation via Powens, bringing French and European bank activity into the ledger's view.
European bank connectivity via Tink: account data and transactions for reconciliation across your banking footprint.
Corporate bank connectivity through Atlar: statements in, payments out.
Accounts, collections, and payouts on Banking Circle rails, reconciled continuously against ledger state.
Column bank accounts, ACH, and wires, ingested and executed through one interface.
Increase accounts and US rails (ACH, wires, RTP) with per-transaction ingestion into the ledger.
Modulr accounts and UK and EU rails (Faster Payments, SEPA) in the uniform model.
Qonto business accounts and transactions in the uniform model.
Bitstamp trades, deposits, and withdrawals in the uniform model.
Coinbase Prime portfolios, wallets, and transactions reconciled alongside your fiat flows.
Fireblocks vaults, balances, and transactions synced into the ledger on schedule.
Kraken Pro accounts, balances, orders, and conversions for exchange reconciliation.
Named accounts, conversions, and payouts via CurrencyCloud, with FX legs booked explicitly.
FX conversions and cross-border payments through Moneycorp, with rates and settlement captured per transfer.
Multi-currency balances and cross-border transfers through Wise, with fees and rates captured per movement.
The framework for everything else: implement the translation layer for any provider in typically 2 to 4 weeks, on Formance scaffolding.
Trusted by builders
“Formance enabled us to ship new lending products faster by providing a customizable foundation that let us reliably express the complexities of our flow of funds.”
Embedded finance · reconciliation across 14 countries
See customer story“Formance is the foundation of our Financial OS, the open-source approach lets us retain control over this key component.”
Healthcare · Financial OS
“Formance helped us kick off our move into fintech, with robust infrastructure and intuitive developer tooling.”
Benefits · fintech infrastructure
Built for regulated money.
Enterprise controls, the certifications auditors ask for, and an immutable record, out of the box.
09:41:07Z AUDIT gateway POST /api/ledger/v2/main/transactions 200 sub:ops@acme.io
09:41:09Z LOG id:4093 NEW_TRANSACTION ledger:main
09:41:12Z LOG id:4094 SET_METADATA ledger:main
09:41:15Z LOG id:4095 REVERTED_TRANSACTION ledger:main
09:41:18Z AUDIT gateway GET /api/ledger/v2/main/logs 200 sub:audit@acme.io
Keep going
Everything you need to evaluate and build on Formance.
Questions, answered
01 / WHAT IF MY PROVIDER IS NOT LISTED?
Use the Generic Connector framework (typically 2 to 4 weeks to implement), co-develop with Formance, or request it. New connectors are added continuously and all are open source.
02 / CAN I REALLY SWAP PROVIDERS?
Yes. Your integration targets the uniform model, not the provider's API. Moving from one PSP to another is a connector configuration change; your flows and reconciliation logic stay intact.
03 / DO CONNECTORS EXECUTE PAYMENTS?
Yes. Connectivity is bidirectional: it ingests transaction data and executes transfers and payouts, and a payment can be the entry point or a step of a Flow.
04 / HOW DOES THIS FEED RECONCILIATION?
Connector data lands already normalized and linked, so reconciliation policies match external statements against ledger state continuously, with drift alerts instead of month-end surprises.
Integrate once, swap freely
See the catalog against your stack: start building or book a demo.


