What is a Mobile to PAN lookup?
A Mobile to PAN lookup finds the Permanent Account Number that available information links to a mobile number a customer has submitted, with that customer's consent.
Almost every Indian digital journey opens with a mobile number. You create the account against it and build the customer record around it.
The steps that follow need a PAN instead, for a credit assessment, a payout account or a settlement reported for tax. Your business has to bridge the gap between the two.
How the Mobile to PAN API works
The API makes the lookup part of a flow you already run, instead of a separate task for an operations team.
Your onboarding screen sends the number it already collected. Whatever the available information links to it comes back as structured data, which the customer confirms before the rest of the form is built on it.
Running the check inside the flow means every applicant meets the same rules. That is one consent wording, one way of handling a no-match, and the same record of why you asked.
What you send: one consented mobile number
The request starts from a single mobile number you collected from the customer, covered by consent for this specific purpose.
Not every number carries a link. Where the available information holds none, you get a plain no-match. Build your journey to expect it.
The exact fields available may vary by data source and record, and the scope of a response depends on the selected service contract.
Treat a returned PAN as a value for the customer to confirm. Where the decision that follows needs a validated PAN, add a PAN verification step.
Who uses a Mobile to PAN lookup
Lending and NBFC platforms can prefill an applicant's PAN at the top of a loan application. The credit assessment can then start without a borrower retyping a ten-character code on a phone screen.
Fintech and payment service providers can complete a user or merchant profile when a PAN becomes necessary. That is often before transaction limits are raised or a payout account is enabled.
Insurers can prefill the proposer's PAN on a proposal form, supporting premium processing and the tax-linked reporting that follows.
Marketplaces can complete a seller profile before payout eligibility is granted. Staffing and gig platforms can capture a worker's PAN during onboarding. Deductions and payout records are then right from the first cycle.
Real estate platforms can collect a buyer's PAN where a reportable transaction calls for it.
How to run a Mobile to PAN check online
Most of the work is decided before the first request.
- Pick the step that genuinely needs a PAN and put the lookup there, not at sign-up.
- Write consent wording a customer will read, naming what you look up and why.
- Decide what a returned PAN can settle on its own, and what still needs a verification step.
- Build the manual-entry path first, then treat the lookup as the shortcut past it.
- Set a retention period for the result, and name the teams allowed to see it.
Where the PAN lookup sits in your flow
Most teams put the lookup behind their own onboarding service instead of calling it from a browser. Consent state, retries and logging then stay in one place.
Treat a no-match as a routing decision, and keep the manual path as well maintained as the automated one.
Availability, request volumes and the fields a response can carry depend on the selected service contract.
Consent rules for a Mobile to PAN lookup
A PAN is sensitive personal information. Run the lookup only where the customer has given informed consent for that specific purpose, and where your business has a lawful, authorized reason to hold the result.
Keep consent specific and revocable. Limit retention to what the process needs, and restrict access to the people whose work requires it.
Your business stays responsible for how a result is used and for the obligations that apply in your own sector.