Skip to main content

Name Mismatch: The verified name does not match the applicant's declared name

Common reasons names differ across sources - and when you should investigate.

Jacob avatar
Written by Jacob
Updated over 2 weeks ago

Summary

Sometimes the name returned by Konfir won’t exactly match the name you entered or the applicant declared. This is not uncommon and reflects how names are stored across different official records.

Each source (Banking, HMRC, Payroll) returns data differently, which can affect how names appear. Examples include:

  • Initials instead of full names

  • Nicknames recorded at bank or payroll level

  • Partial or missing names due to how the institution stores them

  • Additional names - if a joint bank account is connected


Common Reasons for Mismatches

1. Name variations

When you initiate your verification, the name you or your applicant provided may not perfectly match their official records. For example:

  • Shortened names (e.g. Ben instead of Benjamin)

  • Missing names (e.g. omitting a middle name)

  • Changed names (e.g. via marriage or deed poll)

  • Typos or mistakes when entering details

Konfir standardises what’s available and highlights only significant discrepancies. Name mismatches do not influence the verification result.

2) Joint bank accounts

If an applicant connects a joint bank account via Open Banking, some banks may return one or both account holders’ names. This can cause a spouse/partner name to appear in the verification output.

This is not a security issue:

  • Under PSD2 and UK Open Banking regulations, either authorised account holder can give consent for data access via Open Banking.

  • All Open Banking connections require Strong Customer Authentication (e.g. biometrics, passcodes, 2FA), so the applicant themselves will have directly authenticated with their bank.

The returned data is still lawful, accurate, and valid for verification.

Did this answer your question?