How to Lower Your KYC Cost Per Customer Without Increasing Fraud Risk
A low-cost phone signal that helps decide which signups warrant the expensive KYC check, without replacing it.
Rowan Haddad
Content & SEO Manager
Summary
KYC cost per customer rises with signup volume even when the number of legitimate customers doesn't, since every signup sent through a full identity verification workflow adds another per-check fee. The article explains how a low-cost phone layer, such as Prelude's Verify API (SMS OTP verification), Intel API (phone intelligence), and Watch API (signup risk assessment), can route risky signups away from that expensive check before they reach it, with practical breakdowns for gambling, banking, and debt collection.
One of the most effective ways to lower KYC cost per customer is to identify likely bots, duplicate accounts, and fraud attempts with a low-cost phone verification and risk check, such as Prelude’s Verify, Intel, and Watch APIs, before they reach a full, paid identity verification workflow.
A full identity verification workflow combining document verification, biometric matching, and AML screening is typically priced per check, and the cost varies widely by provider, market, and which checks are included. KYC and identity verification checks at onboarding were the most expensive single financial crime compliance process for UK financial institutions in 2023, at 15.4% of total compliance costs, according to LexisNexis Risk Solutions' True Cost of Financial Crime Compliance 2024 report.
For regulated platforms, that creates a familiar problem: verification spend scales with signup volume, not with the number of legitimate customers.
Banks, fintechs, gambling operators, and other regulated businesses have regulatory obligations to verify customers and conduct appropriate due diligence. But that doesn't mean every signup needs to be sent through the most expensive identity checks immediately.
A meaningful share of signup traffic may be bots, duplicate accounts, disposable numbers, or other fraudulent activity. If those users can be identified before they reach a paid identity verification workflow, the platform can avoid spending money on checks that were unlikely to produce a legitimate customer.
This isn't an argument for weaker KYC. It's an argument for better sequencing. A phone signal isn't responsible for proving identity; it's responsible for helping decide whether an expensive identity check should happen next.
Promotion Abuse is a Detection Problem; KYC Cost is a Sequencing Problem
We’ve previously discussed stopping promotion abuse with phone verification and risk signals. That use case is about detection: identifying fake accounts that attempt to farm sign-up bonuses, referral credits, or other incentives.
There's a related problem upstream of KYC: how many signups should reach an expensive identity verification workflow in the first place?
A phone number verification and risk check adds a low per-verification cost. Used as a pre-KYC layer, it can help identify and route traffic that shows strong risk signals, such as automation, disposable-number use, or other fraud indicators, before the platform pays for a more expensive check.
The goal isn't to replace KYC. It's to make sure KYC spend is focused where it has the most value.
How Phone Number Identity Verification Reduces KYC Cost
Phone number verification can provide an early signal before a full KYC check, but different phone-based signals establish different things.
For example, Prelude's Verify API sends an SMS OTP (one-time passcode), which can establish that the user has access to the phone number, providing a possession and reachability signal. Prelude's Intel API adds number intelligence, such as carrier, line type, portability, and whether a number appears to be temporary or virtual, giving context about the number itself. Prelude's Watch API can assess a signup as legitimate or suspicious, flagging risk factors such as automation, device reuse, or a disposable number. Together, these signals can help determine whether a signup should proceed directly to KYC, receive additional scrutiny, or stop before the more expensive identity verification step.
OTP alone does not establish identity or determine whether a customer is legitimate. Its role is narrower: it confirms that the person completing the flow can access the number. The cost-reduction opportunity comes from using that signal alongside phone intelligence and risk data to make a better routing decision before incurring the cost of full KYC.
The platform can turn these signals into a simple decision layer of its own:
Pass: continue to the existing KYC flow.
Fail: reject the signup or prevent it from progressing automatically.
Review: apply additional checks before deciding whether to incur the cost of full KYC.
This doesn't replace hard KYC. It sits in front of it. Users who need to complete regulatory KYC still go through the appropriate identity verification process. The difference is that the expensive check is no longer necessarily the first meaningful risk signal applied to every signup.
Some phone-based checks can go further than OTP and risk scoring and provide identity-related signals. Prelude's KYC Match, part of the Intel API, takes a phone number and claimed attributes, including name, address, date of birth, and email, and checks them against subscriber information held by the user's mobile operator. It returns a match result for each attribute, along with a similarity score where the match isn't exact, rather than only producing an overall risk score, giving a platform an additional identity-related signal before a document is uploaded.
KYC Match isn't available in every market and must be enabled on the account. It is a match signal, not a certified document or biometric identity verification product, so it is best understood as one component of a pre-KYC strategy, rather than a universal replacement for document-based identity verification.
The next three sections walk through what this looks like in practice, across three different regulated industries.
Gambling: Two KYC Moments, Both With Room for Better Sequencing
Gambling operators can face identity verification requirements at multiple points in the customer journey, particularly around onboarding and withdrawals.
In Great Britain, the UK Gambling Commission's Licence Condition 17.1.1 requires remote operators to verify a customer's name, address, and date of birth before the customer is permitted to gamble. It also says operators should not delay a withdrawal because of information they could reasonably have obtained earlier.
That creates an important operational consideration: collecting and verifying the right information early can prevent expensive or frustrating checks from reappearing later in the customer journey.
A pre-KYC phone layer can help at signup by identifying obvious fake accounts, automated traffic, disposable numbers, and other risky signups before the operator pays for a full identity verification attempt. Prelude's Verify API (SMS OTP) and Watch API (signup risk assessment) can provide this signal at signup, so customers who pass the initial check can continue through the operator's existing KYC process. Once appropriately verified, information collected earlier can also reduce unnecessary repetition later in the customer journey, subject to the operator's regulatory and risk requirements.
There's also a conversion benefit. Document upload and biometric verification introduce friction into signup. A phone-based pre-check can run in the background, allowing users who pass the initial signal to progress without adding another visible form or verification step before they reach the point where KYC is required.
The result is a more deliberate funnel: inexpensive signals first, expensive identity verification when appropriate.
Banking: Using Risk Signals Before the Expensive Checks
Banks and fintechs face the same KYC cost problem as gambling operators. Regulatory requirements vary by jurisdiction and institution, but customer due diligence rules generally mean institutions need appropriate processes for identifying and assessing customers, not that every customer must go through the same fixed or most expensive check. Risk-based controls and sequencing let institutions apply that scrutiny where it's warranted.
A pre-KYC phone layer can provide an additional risk signal before a customer reaches document or biometric verification. That gives a bank another input for its onboarding decisioning and can help distinguish straightforward applications from applications that warrant additional scrutiny.
The economics matter because fraud attempts can be expensive long before a customer becomes an active account holder. TransUnion's analysis estimated US lenders' synthetic identity fraud exposure at more than $3.3 billion for the year ending 2024.
Synthetic identity fraud is particularly relevant to KYC because it can involve real or manipulated information designed to create a plausible identity. Passing a document check does not necessarily mean an applicant is a legitimate customer.
Phone intelligence provides a different signal. Information associated with a phone number, such as its type and other carrier-related or behavioral signals, can complement document-based verification rather than trying to replace it.
Where Prelude's KYC Match is available, the signal becomes more specific. A bank can compare claimed attributes such as name, address, and date of birth with subscriber information associated with the applicant's phone number before moving to a document check. A mismatch doesn't prove fraud, but it can provide an early signal that the application deserves additional scrutiny before the institution spends more on verification.
Debt Collection: Protecting the Database, Not Just the Checkpoint
For debt collection agencies, KYC cost isn't the only expense at stake. A bad phone number also wastes collection effort for as long as the account stays in the database. Agencies work with portfolios of accounts, and the value of those portfolios depends partly on whether the contact information attached to each account is usable. A number that's invalid, recycled, disposable, or associated with suspicious activity can continue generating failed outreach attempts long after intake.
That creates operational costs that don't appear on the KYC invoice.
Synthetic identities can make the problem harder because fraudsters may build apparently legitimate profiles over time and associate multiple pieces of contact information with them. Running a live lookup on each number with Prelude's Intel API (carrier, line type, and temporary-number flags) as accounts are onboarded gives a collection business another opportunity to identify questionable contact information before an account enters the active workflow.
The benefit isn't just avoiding an unnecessary identity check. It's keeping the downstream database cleaner and reducing the amount of collection effort spent on accounts with questionable contactability or identity signals.
Where This Fits in an Existing Stack
A Prelude pre-KYC layer sits at a simple point in the existing architecture:
Phone number collected → phone verification and risk → KYC decision → existing identity verification
It doesn't require replacing the existing KYC provider. With Prelude, the phone check can combine Verify (SMS OTP), Intel (number intelligence), and Watch (signup risk assessment). In a typical implementation, the platform turns those signals into three possible outcomes:
Pass: send the user into the existing KYC flow.
Fail: reject the application or stop automated progression.
Review: apply a secondary signal or manual review before incurring the full KYC cost.
The exact thresholds depend on the business, regulatory requirements, risk appetite, and false-positive tolerance. The phone check shouldn't be treated as a definitive statement about whether someone is a legitimate person. It's a signal that can improve the decision about what happens next.
Technically, this can be a relatively small addition to an existing onboarding flow: collect the number, call the verification and intelligence layer, make a routing decision, and keep the existing KYC integration downstream.
What a Pre-KYC Layer Doesn't Replace
A pre-KYC phone layer, including one built on Prelude’s Verify, Intel, and Watch APIs, is a filter, not a substitute for regulatory compliance. If a customer is required to complete identity verification, adding a phone check doesn't remove that obligation, and a phone risk signal should never be treated as proof of identity on its own.
How Much Can a Pre-KYC Layer Save on KYC Costs?
As an illustrative example, a platform that receives 100,000 signups and pays $3 for every full identity verification attempt spends $300,000 running KYC indiscriminately. Routing away the 20% of those signups that show strong fraud, automation, duplicate-account, or invalid-number signals before they reach KYC, the kind of routing decision a Prelude pre-KYC layer is built to make, avoids 20,000 unnecessary checks and saves $60,000 in KYC spend, without changing the requirements applied to users who actually proceed through KYC.
The exact savings depend on the platform's KYC price, traffic mix, false-positive rate, and how effectively the pre-KYC layer routes traffic. But the principle is straightforward: don't use a $3 check to answer a question that a much lower-cost signal can answer first.
What is pre-KYC verification?
Pre-KYC verification, sometimes called "soft KYC", an informal term rather than an established regulatory category, is a low-cost verification and risk check, typically based on a phone number, that runs before a full, paid KYC or identity verification check. It helps identify signups that may warrant additional scrutiny, so the more expensive check is reserved for the cases that need it. Prelude supports this approach with SMS OTP verification through its Verify API, number intelligence through its Intel API, and signup risk assessment through its Watch API.
How much does a full KYC check cost?
It varies widely. A full identity verification workflow combining document verification, biometric matching, and AML screening is typically priced per check, and the cost depends on the provider, market, and checks involved. Prelude's phone verification and risk checks are designed to sit in front of that cost, so fewer signups reach the paid check unnecessarily.
Does OTP verification count as KYC?
No. OTP verification confirms that a user has access to a phone number, a possession and reachability signal. It does not establish a person's identity or satisfy KYC requirements by itself. The cost-reduction case for a Prelude pre-KYC layer depends on combining OTP with phone intelligence and risk signals, not on OTP alone.
Does phone verification replace full KYC?
No. A Prelude pre-KYC phone layer is a filter, not a substitute for regulatory compliance. Any user who is legally required to complete full KYC still has to complete it; the phone check only reduces how many people who were never going to pass it reach that step.
Start the Funnel With a Phone Number
Prelude's Verify API is a phone identity verification API designed to establish whether a number is valid and reachable, while Prelude's Intel API adds number intelligence and its Watch API assesses signup risk before a user reaches a document or identity verification workflow. Where supported, KYC Match can add another layer by comparing claimed customer attributes with subscriber information associated with the phone number.
Together, these capabilities give regulated platforms another way to structure their KYC funnel:
low-cost signal → risk decision → full KYC where appropriate
If your KYC cost per customer is increasing simply because signup volume is increasing, the answer may not be switching KYC vendors. It may be putting a lower-cost risk signal in front of the KYC check you already have.
One of the most effective ways to lower KYC cost per customer is to identify likely bots, duplicate accounts, and fraud attempts with a low-cost phone verification and risk check, such as Prelude’s Verify, Intel, and Watch APIs, before they reach a full, paid identity verification workflow.
A full identity verification workflow combining document verification, biometric matching, and AML screening is typically priced per check, and the cost varies widely by provider, market, and which checks are included. KYC and identity verification checks at onboarding were the most expensive single financial crime compliance process for UK financial institutions in 2023, at 15.4% of total compliance costs, according to LexisNexis Risk Solutions' True Cost of Financial Crime Compliance 2024 report.
For regulated platforms, that creates a familiar problem: verification spend scales with signup volume, not with the number of legitimate customers.
Banks, fintechs, gambling operators, and other regulated businesses have regulatory obligations to verify customers and conduct appropriate due diligence. But that doesn't mean every signup needs to be sent through the most expensive identity checks immediately.
A meaningful share of signup traffic may be bots, duplicate accounts, disposable numbers, or other fraudulent activity. If those users can be identified before they reach a paid identity verification workflow, the platform can avoid spending money on checks that were unlikely to produce a legitimate customer.
This isn't an argument for weaker KYC. It's an argument for better sequencing. A phone signal isn't responsible for proving identity; it's responsible for helping decide whether an expensive identity check should happen next.
Promotion Abuse is a Detection Problem; KYC Cost is a Sequencing Problem
We’ve previously discussed stopping promotion abuse with phone verification and risk signals. That use case is about detection: identifying fake accounts that attempt to farm sign-up bonuses, referral credits, or other incentives.
There's a related problem upstream of KYC: how many signups should reach an expensive identity verification workflow in the first place?
A phone number verification and risk check adds a low per-verification cost. Used as a pre-KYC layer, it can help identify and route traffic that shows strong risk signals, such as automation, disposable-number use, or other fraud indicators, before the platform pays for a more expensive check.
The goal isn't to replace KYC. It's to make sure KYC spend is focused where it has the most value.
How Phone Number Identity Verification Reduces KYC Cost
Phone number verification can provide an early signal before a full KYC check, but different phone-based signals establish different things.
For example, Prelude's Verify API sends an SMS OTP (one-time passcode), which can establish that the user has access to the phone number, providing a possession and reachability signal. Prelude's Intel API adds number intelligence, such as carrier, line type, portability, and whether a number appears to be temporary or virtual, giving context about the number itself. Prelude's Watch API can assess a signup as legitimate or suspicious, flagging risk factors such as automation, device reuse, or a disposable number. Together, these signals can help determine whether a signup should proceed directly to KYC, receive additional scrutiny, or stop before the more expensive identity verification step.
OTP alone does not establish identity or determine whether a customer is legitimate. Its role is narrower: it confirms that the person completing the flow can access the number. The cost-reduction opportunity comes from using that signal alongside phone intelligence and risk data to make a better routing decision before incurring the cost of full KYC.
The platform can turn these signals into a simple decision layer of its own:
Pass: continue to the existing KYC flow.
Fail: reject the signup or prevent it from progressing automatically.
Review: apply additional checks before deciding whether to incur the cost of full KYC.
This doesn't replace hard KYC. It sits in front of it. Users who need to complete regulatory KYC still go through the appropriate identity verification process. The difference is that the expensive check is no longer necessarily the first meaningful risk signal applied to every signup.
Some phone-based checks can go further than OTP and risk scoring and provide identity-related signals. Prelude's KYC Match, part of the Intel API, takes a phone number and claimed attributes, including name, address, date of birth, and email, and checks them against subscriber information held by the user's mobile operator. It returns a match result for each attribute, along with a similarity score where the match isn't exact, rather than only producing an overall risk score, giving a platform an additional identity-related signal before a document is uploaded.
KYC Match isn't available in every market and must be enabled on the account. It is a match signal, not a certified document or biometric identity verification product, so it is best understood as one component of a pre-KYC strategy, rather than a universal replacement for document-based identity verification.
The next three sections walk through what this looks like in practice, across three different regulated industries.
Gambling: Two KYC Moments, Both With Room for Better Sequencing
Gambling operators can face identity verification requirements at multiple points in the customer journey, particularly around onboarding and withdrawals.
In Great Britain, the UK Gambling Commission's Licence Condition 17.1.1 requires remote operators to verify a customer's name, address, and date of birth before the customer is permitted to gamble. It also says operators should not delay a withdrawal because of information they could reasonably have obtained earlier.
That creates an important operational consideration: collecting and verifying the right information early can prevent expensive or frustrating checks from reappearing later in the customer journey.
A pre-KYC phone layer can help at signup by identifying obvious fake accounts, automated traffic, disposable numbers, and other risky signups before the operator pays for a full identity verification attempt. Prelude's Verify API (SMS OTP) and Watch API (signup risk assessment) can provide this signal at signup, so customers who pass the initial check can continue through the operator's existing KYC process. Once appropriately verified, information collected earlier can also reduce unnecessary repetition later in the customer journey, subject to the operator's regulatory and risk requirements.
There's also a conversion benefit. Document upload and biometric verification introduce friction into signup. A phone-based pre-check can run in the background, allowing users who pass the initial signal to progress without adding another visible form or verification step before they reach the point where KYC is required.
The result is a more deliberate funnel: inexpensive signals first, expensive identity verification when appropriate.
Banking: Using Risk Signals Before the Expensive Checks
Banks and fintechs face the same KYC cost problem as gambling operators. Regulatory requirements vary by jurisdiction and institution, but customer due diligence rules generally mean institutions need appropriate processes for identifying and assessing customers, not that every customer must go through the same fixed or most expensive check. Risk-based controls and sequencing let institutions apply that scrutiny where it's warranted.
A pre-KYC phone layer can provide an additional risk signal before a customer reaches document or biometric verification. That gives a bank another input for its onboarding decisioning and can help distinguish straightforward applications from applications that warrant additional scrutiny.
The economics matter because fraud attempts can be expensive long before a customer becomes an active account holder. TransUnion's analysis estimated US lenders' synthetic identity fraud exposure at more than $3.3 billion for the year ending 2024.
Synthetic identity fraud is particularly relevant to KYC because it can involve real or manipulated information designed to create a plausible identity. Passing a document check does not necessarily mean an applicant is a legitimate customer.
Phone intelligence provides a different signal. Information associated with a phone number, such as its type and other carrier-related or behavioral signals, can complement document-based verification rather than trying to replace it.
Where Prelude's KYC Match is available, the signal becomes more specific. A bank can compare claimed attributes such as name, address, and date of birth with subscriber information associated with the applicant's phone number before moving to a document check. A mismatch doesn't prove fraud, but it can provide an early signal that the application deserves additional scrutiny before the institution spends more on verification.
Debt Collection: Protecting the Database, Not Just the Checkpoint
For debt collection agencies, KYC cost isn't the only expense at stake. A bad phone number also wastes collection effort for as long as the account stays in the database. Agencies work with portfolios of accounts, and the value of those portfolios depends partly on whether the contact information attached to each account is usable. A number that's invalid, recycled, disposable, or associated with suspicious activity can continue generating failed outreach attempts long after intake.
That creates operational costs that don't appear on the KYC invoice.
Synthetic identities can make the problem harder because fraudsters may build apparently legitimate profiles over time and associate multiple pieces of contact information with them. Running a live lookup on each number with Prelude's Intel API (carrier, line type, and temporary-number flags) as accounts are onboarded gives a collection business another opportunity to identify questionable contact information before an account enters the active workflow.
The benefit isn't just avoiding an unnecessary identity check. It's keeping the downstream database cleaner and reducing the amount of collection effort spent on accounts with questionable contactability or identity signals.
Where This Fits in an Existing Stack
A Prelude pre-KYC layer sits at a simple point in the existing architecture:
Phone number collected → phone verification and risk → KYC decision → existing identity verification
It doesn't require replacing the existing KYC provider. With Prelude, the phone check can combine Verify (SMS OTP), Intel (number intelligence), and Watch (signup risk assessment). In a typical implementation, the platform turns those signals into three possible outcomes:
Pass: send the user into the existing KYC flow.
Fail: reject the application or stop automated progression.
Review: apply a secondary signal or manual review before incurring the full KYC cost.
The exact thresholds depend on the business, regulatory requirements, risk appetite, and false-positive tolerance. The phone check shouldn't be treated as a definitive statement about whether someone is a legitimate person. It's a signal that can improve the decision about what happens next.
Technically, this can be a relatively small addition to an existing onboarding flow: collect the number, call the verification and intelligence layer, make a routing decision, and keep the existing KYC integration downstream.
What a Pre-KYC Layer Doesn't Replace
A pre-KYC phone layer, including one built on Prelude’s Verify, Intel, and Watch APIs, is a filter, not a substitute for regulatory compliance. If a customer is required to complete identity verification, adding a phone check doesn't remove that obligation, and a phone risk signal should never be treated as proof of identity on its own.
How Much Can a Pre-KYC Layer Save on KYC Costs?
As an illustrative example, a platform that receives 100,000 signups and pays $3 for every full identity verification attempt spends $300,000 running KYC indiscriminately. Routing away the 20% of those signups that show strong fraud, automation, duplicate-account, or invalid-number signals before they reach KYC, the kind of routing decision a Prelude pre-KYC layer is built to make, avoids 20,000 unnecessary checks and saves $60,000 in KYC spend, without changing the requirements applied to users who actually proceed through KYC.
The exact savings depend on the platform's KYC price, traffic mix, false-positive rate, and how effectively the pre-KYC layer routes traffic. But the principle is straightforward: don't use a $3 check to answer a question that a much lower-cost signal can answer first.
What is pre-KYC verification?
Pre-KYC verification, sometimes called "soft KYC", an informal term rather than an established regulatory category, is a low-cost verification and risk check, typically based on a phone number, that runs before a full, paid KYC or identity verification check. It helps identify signups that may warrant additional scrutiny, so the more expensive check is reserved for the cases that need it. Prelude supports this approach with SMS OTP verification through its Verify API, number intelligence through its Intel API, and signup risk assessment through its Watch API.
How much does a full KYC check cost?
It varies widely. A full identity verification workflow combining document verification, biometric matching, and AML screening is typically priced per check, and the cost depends on the provider, market, and checks involved. Prelude's phone verification and risk checks are designed to sit in front of that cost, so fewer signups reach the paid check unnecessarily.
Does OTP verification count as KYC?
No. OTP verification confirms that a user has access to a phone number, a possession and reachability signal. It does not establish a person's identity or satisfy KYC requirements by itself. The cost-reduction case for a Prelude pre-KYC layer depends on combining OTP with phone intelligence and risk signals, not on OTP alone.
Does phone verification replace full KYC?
No. A Prelude pre-KYC phone layer is a filter, not a substitute for regulatory compliance. Any user who is legally required to complete full KYC still has to complete it; the phone check only reduces how many people who were never going to pass it reach that step.
Start the Funnel With a Phone Number
Prelude's Verify API is a phone identity verification API designed to establish whether a number is valid and reachable, while Prelude's Intel API adds number intelligence and its Watch API assesses signup risk before a user reaches a document or identity verification workflow. Where supported, KYC Match can add another layer by comparing claimed customer attributes with subscriber information associated with the phone number.
Together, these capabilities give regulated platforms another way to structure their KYC funnel:
low-cost signal → risk decision → full KYC where appropriate
If your KYC cost per customer is increasing simply because signup volume is increasing, the answer may not be switching KYC vendors. It may be putting a lower-cost risk signal in front of the KYC check you already have.
Start optimizing your auth flow
Send verification text-messages anywhere in the world with the best price, the best deliverability and no spam.
