What happens when a partner is slow or down?
Calls to partners have timeouts, retries and a degraded mode, so customers see a clear pending state instead of an error, and a retry never sends a payment twice.
Fintech · banking
Banking-as-a-service accounts and payments in one system of record
Accounts, IBANs and payments come from one or more banking partners, each with its own API and its own view of what happened, and your partner bank wants proof that your records match theirs. We build the orchestration layer and the reconciliation in between, and the evidence your partner bank asks for.
Typical lengthweeks
From€10,000
Built onBanking-as-a-service, Double-entry ledgers, Sumsub
When teams call us
What usually triggers the work
It usually starts with a change. You are adding a second BaaS provider or leaving one, or your sponsor bank is tightening its checks after a run of US enforcement orders against sponsor banks and passing them down to you as due diligence.
If your product calls each provider directly, every new partner means rewriting product code, and nobody can show the bank a full trail. Customers see a payment stuck or a statement that disagrees with the app, finance sees totals that don't match, and the partner bank sees a fintech that can't answer its questions quickly.
What we deliver
In your repository, demoed every week
- Account opening, IBANs, payments and statements from one or several BaaS partnersOne internal model for accounts and payments, with an adapter for each partner behind it. You can see which partner holds each account and each payment.
- An orchestration layer with explicit states, idempotent commands and webhook replayAccounts and payments move through defined states, every command carries an idempotency key, and provider events are stored and can be replayed. You can replay a day of events in a test environment and get the same result.
- Reconciliation of every partner against your ledgerEach partner's statements and balances are matched against the ledger every day, and any difference opens a break with an owner. You see every break, its amount and its age.
- The evidence pack a partner bank asks for: flows, controls, audit trailFlow diagrams, the control behind each step and an exportable audit trail, kept in your repository and updated with the code. You can hand it to your partner bank as it is.
How it holds up
The questions a reviewer will ask, answered in the build
Can the records be rebuilt after an outage?
Every partner event is stored before it is processed. After an outage, missed events are fetched and replayed in order, and the reconciliation shows anything still out of line.
What happened to this payment?
Each payment has a full trail: the request, every change of state, the partner's events and the ledger postings, with who or what caused each step.
Proof
Where we have done this before
Banking orchestration
One system of record across Sumsub, Fireblocks, a ledger and banking-as-a-service partners, in production for a European payment platform.
Built on
- Banking-as-a-service
- Double-entry ledgers
- Sumsub
- Fireblocks
Often built together: ledger and reconciliation and KYC and KYB onboarding.
Price
What it costs
Banking-as-a-service builds start from €10,000 (£8,700 · $11,500). The price depends on how many partners and products you connect and how much of your current integration we can keep. typical duration
Most teams start with the Readiness Review: €4,900 (£4,250 · $5,500), fixed, 7 working days, with every fix priced. If you then build with us, the fee is credited to the build.
Questions
Before you book
Which BaaS providers have you integrated?
The banking orchestration platform in our case study connects several BaaS partners. The client is under NDA, so we don't name it or its partners; after an NDA is signed, we walk you through how the integrations work on a call. Account opening, IBANs, payments, statements and webhooks follow similar patterns across providers, and we read your provider's documentation before we quote.
Can we add a second banking partner without rebuilding?
Yes, if your product talks to your own account and payment model rather than to the provider directly. That is how we build it: each partner sits behind an adapter, so a new one means a new adapter, a new reconciliation feed and testing, not changes across the product. If your code calls the provider directly today, the first step is to put that model in between.
Will our partner bank accept you as a vendor?
Your partner bank is assessing your vendor risk, so it will ask about control, continuity and access. Our answers are written into the contract: named engineers with a key-person clause, your code and accounts in your name, a second engineer reviewing every change, and supplier terms for regulated clients. We fill in the bank's questionnaire with you and join the call if the bank wants to ask us directly.
Who owns the code and the IP?
You do, from the first commit. We work in your repository and your accounts, and the contract assigns the IP to you in the present tense, not at some later date.
Who will actually work on our project?
The engineers named in the proposal, and you meet them before you sign. A key-person clause means nobody is swapped without your written consent.
How do time zones work for a UK or US team?
We work on Lisbon time, which is the same clock as London: Mon–Fri, 08:00–18:00 UK time. That leaves about four working hours a day in common with the US East Coast. You get a demo of working software every week and a short written update every working day.
What contracts do you sign?
A master services agreement with a statement of work for each project, or your own paper if you prefer. A mutual NDA before we see anything, and a GDPR data processing agreement. US clients get a W-8BEN-E from us. Which law governs the contract is answered on Contracts & security.
How do we pay?
The fixed-price first step is paid upfront. Builds are billed by milestone, after you have seen the work running. Monthly care, if you want it, is billed at the start of each month. We invoice in euros, pounds or dollars.
Free 30-minute call
Tell us what has to work, and by when
You talk to an engineer who would work on it, not a salesperson. You leave the call knowing what it would take and what the first step costs, or we tell you that you don't need us.