In brief: name match compares the name a customer gives you with the name held on an official record and scores how closely they agree, instead of requiring an exact match.
On this page
What is name matching?
Name matching is the comparison of a name supplied by a customer against the name held in an authoritative record — the bank’s account records, a government registry, a sanctions list or an employer database. It is the step where most verification flows silently succeed or fail, because almost every check ultimately reduces to “is this the same person?”
Exact string comparison is unusable in the Indian context. The same individual legitimately appears as Rajesh Kumar Sharma, Sharma Rajesh K, R K Sharma and RAJESHKUMAR SHARMA across four different records, none of which is wrong.
Why names diverge across records
- Transliteration — names originally written in Indian scripts have several accepted Roman spellings.
- Field structure — some systems store a single name string, others split given, middle and surname, and the ordering convention varies by region.
- Initials and expansions — initials are expanded in one record and abbreviated in another, particularly with South Indian naming conventions where the initial may be a place or parent name.
- Titles and honorifics — Mr, Smt, Dr and suffixes leak into the name field.
- Truncation — legacy core banking fields cut long names at a fixed character limit.
- Marriage and legal changes — surnames updated in one registry and not another.
How matching is scored
A workable matcher normalises first — case, punctuation, honorifics, multiple spaces — then compares tokens rather than the whole string, allows for reordering, and applies a phonetic or edit-distance measure to each token. The output is a similarity score, not a yes or no.
That score then meets policy. High scores auto-approve, low scores reject, and a deliberate middle band goes to manual review. Where you set those two thresholds is a business decision about the relative cost of a wrongly rejected genuine customer versus a wrongly accepted fraudulent one — and it should be reviewed against real outcome data, not set once at launch.
Where name match decides the outcome
Penny drop and penny-less account checks return the account holder name from the bank, and the entire value of the check rests on comparing it correctly. The same applies to PEP and sanctions screening, to KYB checks matching a signatory to a registered entity, and to employment verification against EPFO records.
Setting up name match in a verification flow
Indian names vary across records for many legitimate reasons: initials instead of full names, a father’s name or surname included on one record and not another, different spellings across languages, and changes after marriage. A strict text comparison treats all of these as failures, which is why name match uses scoring instead.
Normalise before you compare
- Convert both names to the same case and remove punctuation and extra spaces.
- Strip titles such as Mr, Mrs, Dr and Shri.
- Handle initials, so that a single letter can match the full word it stands for.
- Ignore the order of name parts, since records order them differently.
Choosing thresholds
Set a score above which name match is accepted automatically, a band that goes to a reviewer, and a level below which the customer is asked to check their details. Start with conservative bands, look at real cases for a few weeks, and adjust. The right thresholds depend on which two records you are comparing: a PAN name and a bank account name diverge more often than two government records.
Keep the evidence
Store both names, the name match score and the decision. When an auditor or a customer asks why an application was stopped, that record answers the question immediately. Name match is one of the checks referenced throughout KYC processes under the RBI’s KYC Directions for NBFCs, which sets out the identification requirements these comparisons support.
Name match score threshold for bank account verification
There is no universal name match score threshold for bank account verification. Providers score on different scales, and the right cut-off depends on your customers, the banks they use and what a wrong payout costs you. Set your own thresholds from your own data instead of copying a number from a blog, including this one.
- Collect a sample. Take a few hundred past bank account checks with the name you sent, the name the bank returned, the score and what finally happened (paid correctly, corrected, or confirmed wrong).
- Sort by score and read the cases. Look at where genuine customers sit and where wrong accounts sit. Genuine customers with low scores usually have initials, a missing middle name or a truncated name.
- Set the upper threshold at the score above which your sample contains no wrong accounts. Checks above it can be approved automatically.
- Set the lower threshold at the score below which almost every case was a real mismatch. Below it, ask the customer to re-enter or correct their details.
- Send everything in between to manual review, and size that band to what your reviewers can clear in a day.
- Re-check on real outcomes. Review both thresholds after the first few weeks, and again whenever you add a new customer segment or a new check.
Cases that belong in manual review
- Joint accounts, where the bank returns one holder’s name or both names together.
- Business accounts, where the bank holds a trading or firm name and the customer gave the proprietor’s name.
- Initials and truncated names, where the bank’s record is shorter than the name on the customer’s identity document.
Use stricter bands where a mistake costs more
One pair of thresholds rarely suits every flow. A large loan disbursal can justify a narrower auto-approve band than a small refund. Record which thresholds applied to each decision, so a later review can tell a policy problem from a matching problem.
For the full flow around the check, read the bank account verification API integration guide.
Related terms
- Penny Drop Verification
- Penny-less Verification
- PEP (Politically Exposed Person)
- KYB (Know Your Business)
- KYC (Know Your Customer)
Verify it with Veriqos Technologies
These checks return the name held by the source authority, so you can compare it against what the customer told you:
- Bank Account Verification API — Instantly confirm the authenticity of any bank account with Veriqos Technologies’ Bank Account Verification API — account number, holder name, and status in real time.
- Penny-less Bank Account Verification API — Verify bank accounts in real time using the account number, IFSC code, and account holder name — without sending or depositing any money.
- UAN Verification API — Veriqos Technologies’ UAN Verification API lets you confirm employee details in real time using trusted EPFO records — for onboarding, banking, or employment verification.
- Signature Match API — Veriqos Technologies Signature Validation API enables banks, insurance companies, and digital platforms to compare & verify signatures in seconds — checking similarity, flagging mismatches, and automating manual verification.
See how these checks are applied in Banks & NBFCs, Fintech & Digital Lending.
