Identity matching
Name, address, date of birth and other detail matching.
Compare the details a customer gives you with the details on their records: name, address, date of birth, email, gender and father's name, each scored for how closely they agree. These checks are available on request. Tell us which you need and we set them up for your account.
- Checks
- 6 on request
- Consent
- Bound to every read
- Audit
- Every call in a hash-chained log
Available on request
We set these checks up for your account. Subscribe to the one you need and we will have it ready for you.
- On requestSubscribe
Name matching
Scores how closely two spellings of a person's name refer to the same person.
- On requestSubscribe
Address matching
Scores how closely two written addresses describe the same place.
- On requestSubscribe
Date of birth matching
Checks that two dates of birth from different records agree.
- On requestSubscribe
Email address matching
Checks that an email address belongs to the same person as the other details given.
- On requestSubscribe
Gender matching
Checks that the gender on two records agrees.
- On requestSubscribe
Father's name matching
Scores how closely two spellings of a father's name agree across records.
What teams use it for
Use cases for each Identity matching check. See how they combine with other products on the use cases page.
Name matching
On requestScores how closely two spellings of a name refer to the same person.
- Compare the name on an ID with the name the bank holds for an account.
- Handle initials, spelling differences and name order without manual review.
Address matching
On requestScores how closely two addresses describe the same place.
- Compare the address a customer typed with the one on their ID or bill.
- Check that two documents point to the same home or shop.
Date of birth matching
On requestChecks that two dates of birth from different records agree.
- Confirm the date of birth agrees across the ID, bank and other records.
Email address matching
On requestChecks that an email address fits the rest of the customer’s details.
- Flag sign-ups that use an email address unrelated to the applicant.
Gender matching
On requestChecks that the gender on two records agrees.
- Cross-check gender across ID documents and records during KYC.
Father’s name matching
On requestScores how closely two spellings of a father’s name agree.
- Confirm that two records belong to the same person.
- Tell apart people who share a common name.
How you get Identity matching
From a new account to a live call in four steps.
Create your account
Sign up with your work email. No API is active on a new account.
Subscribe to the check
Use Subscribe on the check you need. We confirm what it takes to set it up for your account.
Pay and start using it
Add money to your wallet. We switch the check on for your account after your payment.
Call it with your key
Once it is activated, it works like every other Grappi API: your key, a JSON request and a JSON reply.
Questions
How do I start?
Create an account and add money to your wallet. Then subscribe to this API in your dashboard and we switch it on for your account.
What comes with every API?
Auth, idempotency, consent and metering hooks, a unified error envelope, and a hash-chained audit trail, identical across every API on the platform.
What do I need to go live?
Subscribe to the API in your dashboard and we switch it on for your account after your payment. The request and reply format is the same in test and in production.
Is this compliant for regulated use?
Reads are consent-bound and DPDP and RBI-AA aligned. Every call lands in a hash-chained audit trail, and every API is switched on for your account individually.