Can an account open without approval?
No. An account can only become active through an approved compliance decision, and that rule is enforced in the code, not in a checklist.
Fintech · onboarding
KYC and KYB onboarding that only opens the accounts compliance approved
Customers get stuck half-onboarded, a result goes missing, and nobody can say why an account was opened. We build Sumsub KYC, KYB and AML screening into your customer lifecycle, so an account opens, and stays open, only in a state your compliance team approved.
Typical lengthweeks
From€10,000
Built onSumsub, KYC, KYB
When teams call us
What usually triggers the work
The work usually starts when something forces it. A partner bank's questionnaire asks how you identify customers and how you prove it. Customers stall between steps and support can't see why. Or a change of KYC provider has sat on the roadmap for months, because the old checks are wired into everything.
Left as it is, onboarding gets fixed by hand. Compliance approves people in the provider's dashboard while your database says something else, results that arrive late are lost, and a reviewer finds accounts that are open without a recorded decision. That is what partner banks and auditors look for first.
What we deliver
In your repository, demoed every week
- Sumsub KYC, KYB and AML screening mapped onto explicit customer statesEach Sumsub result moves the customer to a defined state, and each state says what the account may do. You can read the full map of states and the rule behind every move.
- Webhooks verified, stored and replayable, so no result is lostEach webhook's signature is checked and the webhook is stored before anything acts on it, so it can be replayed after an outage. You can see every webhook received and what it changed.
- Ongoing monitoring and re-checks wired to account limitsWhen monitoring flags a customer or a document expires, the account moves to a review state and its limits change with it. You can test every case in a test environment before it goes live.
- A back-office view for compliance with every decision and its reasonCompliance sees each customer's history: checks, results, decisions, who made them and why. Nothing is approved without a recorded reason.
How it holds up
The questions a reviewer will ask, answered in the build
What if a result never arrives?
Pending checks have a time limit. If a result is late, the system asks the provider again and support can see the delay, so no customer waits without anyone knowing.
Who decided, and on what evidence?
Every decision records who made it, when, and which provider result it relied on, so you can answer a partner bank's sample check straight from the record.
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
- Sumsub
- KYC
- KYB
- AML screening
Often built together: banking-as-a-service integration and a ledger with daily reconciliation.
Price
What it costs
KYC and KYB builds start from €10,000 (£8,700 · $11,500). The price depends on how many customer types and countries you onboard and how much of your current flow 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
We use a different KYC provider. Can you still help?
Yes. The pattern is the same with any provider: its results mapped onto your own customer states, verified webhooks and a record of every decision. Sumsub is the provider we have built on in production; with another one we start from its documentation and test environment, and tell you what is new to us.
Can you move us from one KYC provider to another?
Yes. First we put your own customer states between your product and the provider, so the switch happens behind them. The new provider then runs for new customers while existing customers are re-checked or carried over, on rules your compliance team sets.
Who decides what a compliance status allows?
Your compliance team. We turn their policy into states and rules in the code and show it back to them in writing before it goes live. A compliance specialist on our side helps translate the policy, but the decisions stay with you.
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.