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.

What teams use it for

Use cases for each Identity matching check. See how they combine with other products on the use cases page.

How you get Identity matching

From a new account to a live call in four steps.

  1. Create your account

    Sign up with your work email. No API is active on a new account.

  2. Subscribe to the check

    Use Subscribe on the check you need. We confirm what it takes to set it up for your account.

  3. Pay and start using it

    Add money to your wallet. We switch the check on for your account after your payment.

  4. 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.