Skip to content

Mobile to PAN API

New

Find the PAN that available information links to a consented mobile number, then prefill it in your onboarding flow for the customer to confirm.

Overview

A Mobile to PAN lookup finds the Permanent Account Number that available information links to a mobile number your customer has already given you, subject to their consent. Indian digital journeys usually open with a mobile number. The steps that follow are built around PAN. Asking for a PAN mid-journey is where typing errors and drop-off peak. An API lookup starts from what the customer has already given you and prefills the rest for them to confirm. The response is structured for your application to handle instead of a person. Available fields vary by data source and record. A number with no linked PAN in the available information simply returns no match. You need the customer's consent for this specific purpose, and an authorized business reason for the lookup.

Category
KYC Services
Coverage
PAN links available for Indian mobile numbers, subject to consent
Input
A consented mobile number
Output
Any linked PAN, in a structured response. Available fields vary by data source and record.
Typical users
Lenders and NBFCs, fintech and payment platforms, insurers, marketplaces, staffing and gig platforms
Coverage note
Limited to what available information links to the number you send. Scope depends on the selected service contract.

The overview and the sections after the reference are the FinSour API catalog’s own record for this service, rendered unaltered.

Reference in progress

The request and response reference for this endpoint is not published yet.

Everything below this block is the live catalog record for this service, and it is accurate. The platform’s published API contract does not include this service yet, so there is no request or response detail to document. Rather than fill these sections with a plausible example, the page lists what is missing:

Endpoint URL and method
The host, path and HTTP verb for this service.
Authentication
How a request identifies itself, and where credentials come from.
Request parameters
Field names, types, which are required, and validation rules.
Response schema
The success body, field by field, with a real example.
Error codes
What each failure means and which are worth retrying.
Rate limits
Request ceilings, and what happens at the ceiling.

No sample payload, URL, response body, error code, rate limit or latency figure appears anywhere on this site unless it has been supplied and attributed. Each item in this list is removed only when its own detail arrives; none of them is held back to wait for the rest, and none is ever placed beside a guess in the meantime.

Use cases

  • Lending and NBFC - prefill an applicant PAN before a credit assessment
  • Fintech and PSP - complete a user profile before transaction limits are raised
  • Insurance - prefill the proposer PAN on a proposal form
  • Marketplaces - complete a seller profile ahead of payout eligibility
  • Staffing and gig platforms - capture a worker PAN during onboarding
  • Real estate - collect a buyer PAN for a reportable transaction record

What this service does

  • Starts from the number you already hold

    You never ask for a new identifier part-way through a journey. The lookup works from a mobile number the customer has already submitted and consented to.

  • What a Mobile to PAN response returns

    Any PAN that available information links to the mobile number you submitted, in a structured format. The exact fields available may vary by data source and record.

  • No match means fall back to manual entry

    Where the available information holds no linked PAN, the response says so. Your flow can then offer manual entry.

  • The consent record travels with the check

    The check is designed to run only against a consented mobile number. That keeps the consent record, the lookup and the customer journey together for review.

How a check runs

  1. Agree what your contract covers

    Tell us about the onboarding flow you are building. We agree the services your contract covers and the steps to set up your environment.

  2. Record the customer's consent

    Show the customer what you look up and why. Record their consent before your application sends any request.

  3. Send the mobile number

    Your application sends the consented mobile number during the onboarding or profile-completion step that needs a PAN.

  4. Read the structured response

    The available information comes back in a structured response. It includes a clear no-match outcome where nothing is linked to the number.

  5. Confirm the PAN with the customer

    Show any returned PAN to the customer to confirm, then pass it into the onboarding, payout or reporting step that needed it.

Questions

What do I send to run a Mobile to PAN lookup?
One mobile number, collected from your customer and covered by consent for this specific lookup. Nothing else is needed to start the request.
What does a Mobile to PAN lookup return?
Any PAN that available information links to the number you submitted, in a structured response. The exact fields available may vary by data source and record, and the scope of a response depends on the selected service contract.
Do I need consent to look up a PAN from a mobile number?
Yes. Run the lookup only where the customer has been told what you look up and why, and has agreed to it for that specific purpose. Your business also needs a lawful, authorized reason to hold the result, and consent must stay specific and revocable.
What happens if no PAN is linked to the number?
The response says nothing was found. That is a normal outcome. Most teams fall back to manual entry so the customer can finish the journey.
Why do two Mobile to PAN lookups return different details?
What comes back depends on what the underlying records hold for that number. Two requests can legitimately return different amounts of information. Available fields vary by data source and record.
How do I get access to the Mobile to PAN API?
Use Get API to tell us about the workflow you are building. We discuss coverage, the service contract and the onboarding steps from there.

Catalog entry last updated .