Skip to content

KYC Software in 2026: Architecture, Vendors & Build Cost

KYC software verifies who your users are and screens them against sanctions and watchlists. Here's how the pipeline works, what to build vs buy, the regulations that shape it, and the cost.

Artem Zaitsev
Artem ZaitsevCTO · Idealogic
Author: Artem ZaitsevPublished: Updated: Reading time: 27 minHow we write →
On this page
Idealogic guide to how KYC software works and how to build it

KYC software is the system that verifies who your users are and checks them against sanctions and watchlists before, and after, you let them transact. Know your customer is a regulatory obligation for any product that touches money, and KYC software is how that obligation becomes code: capture an identity document, confirm a real person is behind it, screen the name against sanctions and politically exposed person lists, score the risk, and keep watching the account once it is live. Most "best KYC software" pages stop at a feature list. This guide is for the team that has to build it. It covers how the verification pipeline fits together, what to build versus integrate, which regulations shape the decisions, and what a system costs.

Most teams meet KYC as a box to tick on the way to launch, then find out how much of the product depends on it. Every new user passes through it, so a slow flow costs conversion. It carries regulatory weight, so a gap can cost a fintech its banking partner. And it never finishes, because a customer screened once at signup can land on a sanctions list the next day. If you're a founder or product leader putting identity verification into a financial product, this is the engineering and compliance framing we use when we scope one. You can reuse the same pipeline if your product also signs documents, a case our guide to e-signature software development works through.

The short version

  • KYC software verifies a user's identity, screens them against sanctions and watchlist data, and keeps monitoring the account after onboarding rather than checking once.
  • The process runs in four regulatory stages: a Customer Identification Program, Customer Due Diligence, Enhanced Due Diligence for higher-risk cases, and ongoing monitoring for the life of the account.
  • The system is a pipeline of six components: identity and document verification, biometric liveness, AML, sanctions, and PEP screening, risk decisioning, case management, and ongoing monitoring.
  • Most fintechs land on a hybrid: integrate the commodity pieces (document verification, liveness, watchlist data) and build the policy pieces (risk decisioning, case management, monitoring) in-house.
  • Regulation is the spec: FATF sets the global baseline, with the Bank Secrecy Act and CIP in the US, the AML Directives in the EU, and GDPR governing the personal data collected.
  • Cost tracks how much of the system you own, from a weeks-long API integration to a multi-quarter, multi-jurisdiction platform with data residency.

What KYC software does, and where it fits in a fintech stack

KYC software does three jobs: it verifies a customer's identity, it screens that customer against sanctions and watchlists, and it monitors the relationship over time for changes that matter. Those jobs map to two moments. Verification and screening happen at onboarding, when you decide whether to let someone in; monitoring runs for the entire life of the account, because risk isn't a property you measure once. KYC verification is the front half, confirming a real, identifiable person or business is behind an application, and it is the part users see as the onboarding flow.

In a fintech stack, KYC sits at the boundary between the outside world and your regulated core, with your product above it and the systems that move money below. KYC software decides who gets through and on what terms, then keeps a record an auditor can later inspect. Set it too strict and you reject good customers. Set it too loose and you admit the people the rules exist to stop. Calibrating that takes engineering and policy together, which is why a drop-in widget rarely covers it.

KYC verification software vs KYC tools vs AML software

KYC verification software is the onboarding layer that captures an ID document, confirms liveness and returns a verified identity. KYC tools is the looser term for the same stack plus screening and case management. AML software is a different job: it watches what a verified customer does over time, screening parties and transactions against sanctions lists. In a fintech build the three share data and run as one pipeline.

The KYC process end to end: CIP, CDD, EDD, and ongoing monitoring

The KYC process is a lifecycle with four stages: a Customer Identification Program that confirms identity, Customer Due Diligence that assesses risk, Enhanced Due Diligence for the higher-risk cases, and ongoing monitoring that runs for the life of the account. These stages aren't a vendor's invention. They come straight out of the global anti-money-laundering framework set by the Financial Action Task Force (FATF) Recommendations, whose Recommendation 10 defines customer due diligence as the baseline every regulated firm must perform.

Start with the Customer Identification Program. In the United States this is a legal requirement under the Bank Secrecy Act. The CIP rule for banks (31 CFR 1020.220), enforced by the Financial Crimes Enforcement Network and the federal banking regulators, requires covered institutions to collect and verify identifying information (name, date of birth, address, and a government identifier) before opening an account. The FinCEN Customer Due Diligence Rule (31 CFR 1010.230) adds beneficial ownership checks for legal-entity accounts. In software terms, CIP is the capture-and-verify step. Customer Due Diligence is the next layer up. Where CIP asks "is this a real person," CDD asks "how risky is this relationship," building a risk profile from who the customer is, where they are, and what they say they will do.

Enhanced Due Diligence is CDD turned up for the cases that warrant it. When a customer scores as higher risk, a politically exposed person, a high-value account, an unusual jurisdiction, the FATF framework expects deeper checks: source-of-funds questions, additional documentation, senior sign-off. The fourth stage, ongoing monitoring, is the one teams most often underbuild. The same FATF Recommendation 10 expects firms to keep due diligence current and scrutinize transactions across the life of the relationship. KYC software that models only the first three stages and skips the fourth is compliant at signup and out of compliance a month later.

The core components of a KYC system

KYC software is built from six core components, each a distinct piece of engineering you either build or integrate: identity and document verification, biometric liveness, AML and sanctions and PEP screening, risk decisioning, case management, and ongoing monitoring. You're responsible for all six even when a vendor runs some of them, so treat the list as an architecture and not as checkboxes on a vendor comparison.

Identity verification and biometric liveness

Identity and document verification is the capture-and-prove layer, aligned with assurance frameworks such as NIST SP 800-63A-4 Enrollment and Identity Proofing: it reads a government identity document, checks it is genuine and unaltered, and extracts the data on it. Biometric liveness sits next to it and answers a narrower question tested under ISO/IEC 30107-3 biometric presentation attack detection (PAD): is a live human present, and do they match the document, rather than a photo of a photo or a deepfake.

Screening and risk decisioning

AML, sanctions, and PEP screening checks the verified identity against sanctions lists, watchlists, and politically exposed person databases. Risk decisioning then takes the signals from verification and screening, applies your policy, and produces an outcome: approve, reject, or escalate.

Case management and ongoing monitoring

The last two components separate a demo from a system that survives an audit. Case management is the workbench your compliance team works at, where flagged applications land, get investigated with the evidence attached, and get resolved with a recorded decision and reason. Without it, a flagged case is just an alert nobody can act on or account for. Ongoing monitoring runs after onboarding closes, re-screening customers as lists change and watching transactions for patterns that warrant a second look. Each of these six carries its own build-or-buy decision, which the sections below work through.

KYC verification software architecture: the identity-verification pipeline

KYC verification software is architected as a pipeline: capture flows into document and biometric verification, then screening, then risk decisioning, which routes to case management, all wrapped by a monitoring loop that runs for the life of the account. Each stage takes the output of the one before it, does one job, and passes a result forward, and keeping those stages cleanly separated is most of what makes the system testable, auditable, and able to swap any single piece.

Risk decisioning is the orchestration core: a rules and scoring engine that combines verification confidence, screening hits, and customer attributes into one outcome, approve, reject, or escalate, by policy you can read and change. Cases that escalate route to a human; clean cases proceed straight into the product. The monitoring loop then re-screens and re-scores on a schedule and on events for as long as the account exists.

Waterfall routing escalates friction and vendor cost only as risk signals require
Pipeline stageWhat it does
CaptureCollects the identity document and a selfie or short video, usually on a phone, and validates the inputs
Document and biometric verificationConfirms the document is genuine and a live person matches it; returns a verified identity or a reason for failure
Sanctions and PEP screeningChecks the verified identity against sanctions, watchlist, and PEP data; returns any matches to review
Risk decisioningA rules and scoring engine combines verification, screening, and attributes into approve, reject, or escalate
Case managementEscalated cases land on the compliance workbench, get investigated with evidence, and are resolved with a recorded decision
Ongoing monitoringRe-screens and re-scores the account on a schedule and on events for the entire life of the relationship

Two architectural properties matter more than any single stage. The first is that the decisioning engine should be configuration instead of hardcoded logic. Your risk policy changes often, and a rule change shouldn't need a deploy and a regression suite every time. The second is scalability with backpressure: verification and screening call external services with their own latency and rate limits, so the pipeline runs the slow stages asynchronously, queues work, and degrades gracefully rather than timing out a user's onboarding because a downstream provider got slow.

AML, sanctions and PEP screening: how it actually works

AML screening works by matching every customer, and often every transaction party, against curated lists of sanctioned and high-risk entities, then surfacing the matches a human must clear. The lists are the foundation: the main sanctions sources are the US Treasury OFAC sanctions lists, the United Nations consolidated list, the European Union consolidated list, and the UK Sanctions List. A serious KYC AML software build screens against every list its markets require. Keep the copies current, too: a screen run against a stale list passes people it should have stopped.

The matching itself is harder than it sounds, which is why this is real engineering rather than a database lookup. Names don't arrive clean: they are transliterated from other alphabets, abbreviated, reordered, misspelled, and shared by thousands of unrelated people, so the screening engine uses fuzzy name matching, comparing for similarity rather than exact equality, to catch "Mohammed" against "Muhammad" and "Jon A. Smith" against "Smith, John Andrew." Fuzzy matching is a sensitivity setting. A looser match catches more real hits and more false positives, and a tighter one misses name variants. Most of the screening work goes into tuning that setting.

Two screening types go beyond plain sanctions. PEP screening checks whether a customer is a politically exposed person, someone in a prominent public role whose position carries a higher corruption risk, which the FATF framework addresses in Recommendation 12 by calling for enhanced measures on PEPs and their close associates. A PEP isn't a sanctioned person and isn't blocked by default. A PEP hit triggers enhanced due diligence, and the customer can still be approved. Adverse-media screening is the other, scanning news and public sources for credible negative coverage (fraud, money laundering, criminal proceedings) tied to the customer. Idealogic builds these as part of full fintech KYC and AML pipelines, wiring identity verification, sanctions screening, and the monitoring that follows into one system with audit-grade reporting, so every hit and decision is recorded for an examiner.

Ongoing monitoring and perpetual KYC (pKYC)

Ongoing monitoring means re-checking a customer after onboarding, on a schedule and whenever something changes, so your view of their risk stays current instead of frozen at signup. The traditional model is periodic review: every customer gets re-screened on a fixed cadence, often annually for standard risk and more frequently for higher risk. It works, but it is blunt: a customer who becomes sanctioned the day after their annual review stays invisible to you for nearly a year.

Perpetual KYC, usually shortened to pKYC, is the event-driven answer to that gap. It is an industry term for risk-based ongoing monitoring, not a separate legal regime. Instead of waiting for the calendar, a pKYC system watches for triggers and re-screens the moment one fires: a sanctions list adds a name that matches an existing customer, a customer moves to a high-risk jurisdiction, an ultimate beneficial owner (UBO) changes, a burst of unusual activity appears. The engineering shape is an event pipeline: list and account changes become events, a rules layer decides which warrant a re-check, and the re-check feeds the same decisioning and case-management stages onboarding uses, so the risk view moves in close to real time rather than annual steps.

The third leg is transaction monitoring, its own discipline that lives next to KYC and shares its plumbing. Transaction monitoring software watches the flow of money for patterns that suggest laundering or fraud, the pattern-detection problem our fraud detection software guide covers in its own right: structuring deposits under reporting thresholds, sudden spikes, money moving in and straight back out, flows to or from high-risk regions. Rules catch the known patterns and anomaly models flag the unusual ones, and a hit raises an alert into the same case-management workbench a screening hit would. Build monitoring, pKYC, and transaction monitoring as one connected system rather than three tools, because they all answer the same question, has this customer's risk changed, and all need to land their findings in one place a human can act on and an auditor can review.

Tuning false positives: risk scoring, thresholds, and alert fatigue

Tuning KYC software means setting the risk weights and score thresholds so the pipeline catches real risk without burying your compliance team in false alarms, and it is the hardest and most underestimated part of the whole build. Screening engines are naturally noisy. A loosely tuned sanctions screen against a common name can generate dozens of "hits" for one applicant, almost all of them different real people who happen to share a name with someone on a list. At volume a poorly tuned system produces thousands of alerts a day a team can't clear, which is alert fatigue: the failure mode where the genuine hit is missed because it was the four-hundredth alert in a queue of noise.

The tuning levers are risk weights, score thresholds, and match sensitivity. Risk weights decide how much each factor contributes to a customer's overall score: a sanctions hit weighs far more than an unusual login time. Score thresholds set the cut points between approve, escalate, and reject, and moving a threshold a few points reshapes how much work flows to humans. Match sensitivity, the fuzzy-matching dial from the screening section, governs how close a name has to be to count as a hit. These three interact, so tuning is iterative against real data rather than guesses.

Underneath the tuning is the precision-versus-recall trade-off that no clever model removes, only manages. Recall is catching every true risk; precision is not flagging the innocent. Recall near 100 percent floods the queue with alerts. Raising precision means missing some real hits, which a regulator won't accept. So hold recall high where a miss is unrecoverable, sanctions above all, and trade it for precision where a missed flag can be caught later. This is the work Idealogic does on fintech KYC and AML pipelines: tuning them for false-positive control and pairing them with audit-grade reporting, so the team can clear the alert queue and every decision in it is recorded for the examiner who later asks why.

Building KYC or AML into your product?
We design the verification pipeline, the screening, and the decisioning around your real flow, with the audit trail an examiner expects.
Talk through your build

Build vs buy vs API: a decision framework

The build-versus-buy-versus-API choice in KYC comes down to how much control and scale you need against how fast you need to launch, and most fintechs end up with a blend of KYC tools and APIs they buy and policy logic they build. A full vendor platform gets you live fastest and carries the compliance machinery for you, at the cost of fitting your policy into their model and paying per-check forever. Building in-house gives you total control of the logic and data and better unit economics at scale, at the cost of time, specialist effort, and owning the maintenance. The API or hybrid middle path, integrate the commodity pieces and build the policy around them, is where most serious products land. The decision is a function of four variables: volume, control, time-to-market, and total cost of ownership, and the matrix lays out when each approach makes sense.

ApproachWhen it fitsThe trade-off
Buy a full vendor platformLow to moderate volume, need to launch now, standard risk policyFastest to live and lowest build effort, but per-check pricing and your policy bent to fit theirs
Build in-houseHigh volume, non-standard risk logic, data and unit economics matterTotal control and better economics at scale, but the longest build and you own the upkeep
API or hybridMost fintechs: integrate commodity checks, build the decisioningControl where it counts plus speed where it does not, at the cost of integration and orchestration work

The variable that usually decides it is volume against control. At low volume with a standard policy, a vendor platform is almost always the right first move, because building your own pipeline to run a few hundred checks a month is effort spent in the wrong place. As volume climbs and your risk policy diverges from anything off the shelf, both the economics and the control argument swing toward building the decisioning yourself while still integrating the commodity checks. Time-to-market is the early tiebreaker; total cost of ownership is the later one, when per-check fees at scale dwarf what an in-house engine would have cost. The same buy-the-commodity, build-the-differentiator logic runs through every serious software decision, and we lay out the full framework in our guide to build versus buy for software.

What to build versus what to integrate

The clean line in a KYC build is this: integrate the components that depend on data and signals you can't economically reproduce, and build the components that encode your own policy. Document verification, biometric liveness, and watchlist data sit firmly on the integrate side. Each is a full product in its own right, current document-format coverage across countries, an anti-spoofing arms race against deepfakes, sanctions sources ingested and reconciled worldwide every day, run by specialists at a scale a single fintech can't match.

The build side is everything specific to you. Risk-decisioning logic is your policy made executable, and no vendor knows your risk appetite, customer mix, or regulator's expectations the way you do, so it belongs in-house where you can read, version, and change it. Case management is your compliance team's workflow, shaped by how they investigate and what your auditors want to see. Ongoing monitoring orchestration, which events trigger which re-checks and how they route, is your operating model in code.

Integrate specialist capture and watchlist feeds while owning policy, routing, and audit controls
ComponentBuild or integrateWhy
Document verificationIntegrateNeeds current coverage of thousands of identity-document formats across countries
Biometric livenessIntegrateA device-fraud and anti-spoofing arms race against deepfakes, run by specialists
Sanctions and watchlist dataIntegrateLists must be ingested, reconciled, and kept current worldwide, every day
Risk decisioningBuildEncodes your own risk policy; no vendor knows your appetite and regulator
Case managementBuildFollows your compliance team's real investigation workflow and audit needs
Ongoing monitoring orchestrationBuildYour operating model in code: which events trigger which re-checks, and routing

On the integrate side, the vendors named here are functional options, not recommendations. Specialist providers such as Jumio, Onfido, Sumsub, Trulioo, and Persona supply document verification, biometric liveness, and screening as APIs, and which one fits depends entirely on your geographies, your document mix, and your economics. We deliberately don't rank them, because the right answer is the one whose coverage and pricing match your specific flow, and that is a discovery exercise, not a leaderboard.

Treat the vendor API call as the easy hour and spend the effort on the decisioning, the case management, and the audit trail. Verifying a document takes a second. Proving to an examiner why you approved this customer and flagged that one is most of the build.

The regulations and data residency that shape a KYC build

KYC software exists because regulation requires it, so the rules are the spec the system is built to. The global baseline is the FATF 40 Recommendations, the standard that defines customer due diligence, ongoing monitoring, and the risk-based approach that every major jurisdiction translates into its own law.

The regional layers add specificity on top of that baseline. In the United States, the Bank Secrecy Act and its Customer Identification Program rule (31 CFR 1020.220 for banks), enforced by FinCEN and the federal banking regulators, require regulated firms to collect and verify identifying information before opening an account, the legal force behind the CIP stage. In the European Union, the Anti-Money-Laundering Directives set the due-diligence and beneficial-ownership obligations today. The single-rulebook EU Anti-Money Laundering Regulation (Regulation (EU) 2024/1624) will apply from 10 July 2027, so a build that goes live now should plan for both. Supervision is national, guided by the European Banking Authority guidelines, and EU-level coordination is moving from the EBA to the new authority, AMLA. A system serving both markets usually needs a decisioning layer that applies different rules by jurisdiction rather than one global policy.

Two cross-cutting requirements shape the build as much as the AML rules do. The first is data protection. KYC collects exactly the sensitive personal data privacy law cares most about, identity documents, biometrics, addresses, so in Europe the General Data Protection Regulation (GDPR) governs how it is processed, stored, and retained, and that pulls in data residency: certain data may need to be kept and processed in-region rather than shipped elsewhere. For a multi-jurisdiction product, residency becomes an architecture constraint, because where the data physically lives drives how you deploy. The second is the audit trail. Every regulator expects you to prove what you did and why, so an append-only, immutable record of every check, score, and decision is a core requirement. Idealogic builds to PCI DSS, SOC 2, ISO 27001, GDPR, and KYC and AML standards, which means implementing the technical controls and producing the evidence an audit needs. We build the controls and the evidence; the client achieves the certification with their own assessors. No agency can hand you a "KYC certification". Your own organization earns it in front of its assessors.

What KYC software costs to build and run

KYC software cost depends almost entirely on how much of the system you own, so the clearest way to model it is in scope tiers, recognizing that the recurring bill is as much per-check vendor volume and compliance operations as upfront engineering. Integrating a verification API behind a light due-diligence flow is a different undertaking from a full in-house KYC and AML platform, which is different again from a multi-jurisdiction build with data residency.

Scope tierWhat you buildTimeline and team shape
Integrate an API plus light CDDA verification API behind an onboarding flow, with basic due-diligence logic and an audit log2 to 4 weeks; a small senior squad
Full in-house KYC and AML platformSanctions and PEP screening, a risk-decisioning engine, case management, and ongoing monitoring3 to 5 months; a senior squad with compliance input
Multi-jurisdiction with data residencyPer-region rules, in-region data processing, broader list coverage, and deeper audit and reporting5 to 7+ months; a standing team with compliance and reliability roles

That table is the coarse view. The last section of this guide prices the same build in five narrower tiers, so its timelines are shorter per tier.

The biggest cost lever is the one that drives the architecture: how much you own. Sitting on a vendor keeps the build small because you are renting the regulated commodity, and the cost lives in per-check fees that scale with volume. Building the decisioning, case management, and monitoring in-house moves cost up front into engineering and then into the standing compliance and reliability work of running it, which is the real recurring expense. One of our own builds shows how this plays out: Chaindoc, an eIDAS-qualified e-signature platform where KYC identity checks run inside the same regulated flow as the agreements and the Stripe Connect payment collection, so a user verifies, signs, and pays without leaving the document and the flow stays auditable. Swissy, one of the types of digital wallets, is a lighter case where the identity work sits inside the onboarding flow. KYC rarely ships alone, so read it next to the rest of this fintech cluster: our payment gateway integration guide covers the money movement it sits in front of, and our embedded finance guide covers the larger pattern of putting regulated finance inside a non-financial product. When you are ready to plan, a scoped discovery against our custom software development team sets the architecture and compliance ownership correctly from day one, and platforms shipping this as a SaaS product start at tier one and grow into tier two as volume justifies it.

KYC software vendors compared and what a custom orchestration layer costs

Persona, Sumsub and Onfido (Entrust) price and package identity checks differently, which is why teams at scale avoid depending on one of them. Our Persona vs Sumsub comparison goes through the contracts line by line. The short view:

  • Persona has low-code inquiry flows and US/global KYB templates. Pricing is quote-based with annual commitments.
  • Sumsub covers global fintech and crypto, including Travel Rule checks under Regulation (EU) 2023/1113 and AML screening. Its published plans run from $1.35 to $1.85 per verification with $149 to $299 monthly minimums, and enterprise pricing is custom above that.
  • Onfido (Entrust) sells enterprise document OCR and biometric liveness APIs, tested against presentation attacks, under annual volume contracts.

Vendor prices were checked in November 2026 and change often, so confirm them on the vendor's page before you model anything.

Why a waterfall costs less than a single vendor

Take 250,000 checks a year, or 750,000 over 36 months. Sending every signup straight to a biometric check at a $1.80 average costs $1,350,000. A custom multi-vendor KYC waterfall runs passive database, telecom, and bank-account ownership checks first (see Plaid vs Stripe), escalates about 45% of sessions to liveness biometrics, and fails over across providers during regional outages.

The per-check prices here are illustrative modeling assumptions, not vendor quotes: $0.15 to $0.35 for a passive check and $1.20 to $2.50 for liveness biometrics. At the midpoints, the cost per signup is $0.25 plus 45% of $1.85, about $1.08 against $1.80, a 40% saving. In our model that puts the saving in a 35% to 50% band, or $472,500 to $675,000 over three years. Your numbers will move with your vendor quotes and your escalation rate.

Custom KYC orchestration cost by tier

The 2026 cost table below compares our fintech CEE squads with US rates. CEE is $75/hr blended across $50 to $75/hr, and the US figure is $165/hr blended across $150 to $220/hr. Dedicated Squads start at $18,000/mo CEE versus $39,600+/mo US for 2 to 3 engineers, or $39,600+/mo CEE versus $87,120+/mo US for a 4-to-5-engineer pod.

KYC / KYB Build TierCore Engineering ScopeCEE Build (@$75/hr)US Build (@$165/hr)3-Yr Vendor / Data-Feed + CEE Total
1. KYC Discovery Sprint (2 to 3 wks, 240 to 333 hrs)CIP/CDD/AMLR threat model, GDPR PII vault design, waterfall math & vendor RFP$18,000 to $25,000$39,600 to $55,000Blueprint deliverable credited toward build
2. Multi-Vendor KYC Waterfall MVP (8 to 12 wks, 733 to 1,267 hrs)Passive DB/bank step-up before $1.20 to $2.50 liveness biometrics, dual-vendor failover, audit log$55,000 to $95,000$121,000 to $209,000$675,000 to $877,500 API spend (750k checks, 35% to 50% saved) -> $730,000 to $972,500
3. KYB UBO + Sanctions Workbench (12 to 18 wks, 1,267 to 2,067 hrs)Registry graph, 25%+ UBO KYC cascade, OFAC/EU sanctions matcher, analyst case queue$95,000 to $155,000$209,000 to $341,000$90,000 to $180,000 watchlist/infra feeds ($2.5k to $5k/mo; excl. per-IDV checks) -> $185,000 to $335,000
4. Ongoing Monitoring & SAR Engine (18 to 28 wks, 2,067 to 3,200 hrs)Real-time velocity rules, pKYC triggers, FinCEN BSA E-Filing and national-FIU (goAML) STR connectors, regional KMS vaults$155,000 to $240,000+$341,000 to $528,000+$126,000 to $216,000 monitoring/infra feeds ($3.5k to $6k/mo; excl. per-IDV checks) -> $281,000 to $456,000+
5. Single-Vendor Biometric Baseline (2 to 4 wks, 200 hrs SDK setup)100% of signups sent to $1.80 avg biometric check + $1,000/mo platform minimum$15,000$33,000$1,386,000 vendor fees (750k checks: $1,350k + $36k base) -> $1,401,000

For most fintechs the answer is a hybrid. Buy document verification, liveness and watchlist data. Build the risk decisioning, case management and monitoring, because that is where your policy lives. Custom KYC software on that model starts at $55,000 to $95,000 for a multi-vendor waterfall MVP and reaches $155,000 to $240,000+ once ongoing monitoring and SAR filing are in scope.

Building KYC or AML into your product? Get the pipeline and compliance right from the start
Scope your fintech build

Occasional field notes on building software, no spam

Protected by Cloudflare Turnstile · Privacy · Terms

Artem Zaitsev
Artem ZaitsevCTO · Idealogic Development OÜ

CTO and Co-founder at Idealogic. Directing engineering, systems architecture, security, and full-stack delivery across web, mobile, and blockchain.

Frequently asked questions

  • No, they overlap but answer different questions. KYC software verifies who a customer is at onboarding and keeps that identity record current. AML software watches what that customer does over time, screening parties and transactions against sanctions lists and flagging suspicious patterns. In a real fintech build the two share data and run as one pipeline, since sanctions screening at onboarding is a KYC step and a monitoring step at once.

  • KYC verifies an individual person; KYB verifies a business and the humans behind it. KYB pulls a company's registration and ownership records, identifies the beneficial owners who control it, and runs KYC-style checks on each of them. A platform that onboards companies needs both, because verifying a business means verifying the people who own and direct it. The plumbing is shared, but KYB adds an ownership-resolution layer on top of individual identity checks.

  • It depends on scope. Integrating a verification API behind a light onboarding flow takes 2 to 4 weeks, while a custom multi-vendor KYC waterfall MVP ships in 8 to 12 weeks. A full KYB beneficial-owner and sanctions case-management workbench runs 12 to 18 weeks, and a regulated multi-jurisdiction ongoing transaction monitoring and SAR platform takes 18 to 28 weeks with dedicated compliance and reliability engineering.

  • Partly. You can and usually should build the decisioning, risk scoring, case management, and monitoring logic in-house, because that is where your product's policy lives. Document verification, biometric liveness, and watchlist data are different. They rely on device-fraud signals, identity-document coverage, and continuously maintained sanctions data that take specialist scale to keep current, so most teams integrate those from a vendor rather than build them. The realistic answer is a hybrid, not all or nothing.

  • The core mandate traces to the FATF Recommendations, the global anti-money-laundering standard that defines customer due diligence and ongoing monitoring. In the United States the Bank Secrecy Act and the Customer Identification Program rule (31 CFR 1020.220 for banks), enforced by FinCEN and the federal banking regulators, require regulated firms to verify customer identity. In the European Union the Anti-Money-Laundering Directives set equivalent obligations today, supervised nationally with EU-level coordination moving from the EBA to the new authority, AMLA. The single-rulebook EU AML Regulation applies from 10 July 2027. GDPR then governs how the personal data those checks collect is processed and stored.

  • In 2026, a 2-to-3-week compliance and KYC architecture Discovery Sprint costs $18,000 to $25,000 with an Idealogic CEE squad ($75/hr blended versus $39,600 to $55,000 at $165/hr US rates). A multi-vendor KYC waterfall MVP runs $55,000 to $95,000, a KYB beneficial-owner and OFAC/EU sanctions case-management workbench costs $95,000 to $155,000, and a full ongoing transaction monitoring and SAR engine ranges from $155,000 to $240,000+.

  • Perpetual KYC (pKYC) replaces fixed annual or multi-year periodic reviews with continuous, event-driven risk monitoring across the account lifecycle. It is an industry term for risk-based ongoing monitoring, not a separate legal regime. Instead of waiting for a calendar review date, the pipeline listens for material trigger events such as sanctions list updates, beneficial ownership changes, address updates, or unusual transaction velocity. When a trigger fires, the orchestration engine automatically re-screens the customer, recalculates their risk score, and routes only genuine risk changes to a compliance analyst.

  • Reducing false positives requires combining secondary identifiers with tuned fuzzy-matching thresholds and risk-weighted scoring rules. Rather than matching on name strings alone, a well-tuned screening pipeline filters out impossible hits using date of birth, nationality, and country of residence before alerting a human analyst. Pairing biometric presentation attack detection under ISO/IEC 30107-3 with configurable match sensitivity keeps recall high on true sanctions hits while preventing alert fatigue in the case queue.

  • Start with geography, document mix and volume. Persona is strong on configurable onboarding flows and US or global KYB templates, with quote-based pricing and annual commitments. Sumsub has broad global document coverage, crypto Travel Rule checks and AML screening, and publishes plans from $1.35 to $1.85 per verification with $149 to $299 monthly minimums. Onfido (now Entrust) sells document OCR and biometric liveness APIs under annual enterprise contracts. At high volume, a fintech usually integrates two providers behind its own waterfall router for failover and cost control.

  • In our model, by 35% to 50%. Sending every signup straight to biometric document verification at a $1.80 average costs $1,350,000 over 36 months at 250,000 checks a year. A custom KYC waterfall engine ($55,000 to $95,000 CEE build) runs passive database, telecom, or bank-account checks first and escalates about 45% of sessions to liveness biometrics, which saves $472,500 to $675,000 of that spend. The per-check prices behind it ($0.15 to $0.35 passive, $1.20 to $2.50 biometric) are illustrative modeling assumptions, so rerun the math with your own vendor quotes.

Still unanswered
Ask us directly

A senior engineer replies under 4 hours.