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.
Related terms
- Penny Drop Verification
- Penny-less Verification
- PEP (Politically Exposed Person)
- KYB (Know Your Business)
- KYC (Know Your Customer)
Verify it with Veriqos
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’ 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’ 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 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.