What is a PAN-to-GST lookup?
GST registration in India is state-wise. A business that operates in several states holds a separate GSTIN in each of them, and every one of those numbers is built around the same PAN. That is what makes the PAN a workable starting point.
A PAN-to-GST lookup submits the PAN and returns the GST registrations recorded against it. You then see the states a counterparty is registered in, instead of the single number that happened to be typed into a form.
How the PAN-to-GST API works
Collecting GSTINs by asking is slow and incomplete. A supplier sends the registration for its head office. A seller quotes the state it signed up from, and the registration that matters for a particular transaction never reaches the record.
An API lookup puts the discovery step inside the software where you create the counterparty. A marketplace can resolve a seller's registrations during signup. A procurement system can resolve a supplier's registrations before a purchase order is raised, and an accounts payable team can resolve them before an invoice is booked.
What you send to find GSTINs on a PAN
You send the PAN on its own. The API processes the number and returns the GST registrations recorded against it, in a structured response. That response can include the state each registration belongs to and the status recorded for it.
A GSTIN carries the PAN inside it. You can reconcile the returned numbers against the identity details a counterparty has already submitted. The set of fields differs from one data source and one record to the next.
What the GSTIN list covers, and what GST verification adds
The lookup tells you which registrations exist against a PAN, and it stops there. A separate GST verification check starts from a GSTIN and goes deeper. It carries the legal and trade names, the constitution of the business, the registration date, the jurisdiction and the filing behavior recorded for a registration.
Many teams run the two together. The lookup finds the registrations, and the verification step then runs against the one you will use. The record ends up carrying both a complete list and a checked profile.
Who looks up GSTINs by PAN
- Fintech and payment service providers: resolve a merchant's registration for the state where supply is made, before settlement and tax reporting are configured.
- Marketplaces: discover a seller's registrations across the states it fulfills from. Invoicing is then raised against the correct one.
- Procurement and manufacturing: pick the right vendor GSTIN before an invoice is booked. Input tax credit depends on the invoice carrying the registration that matches the place of supply.
- Lending and NBFC: map the states an MSME borrower is registered in, as part of understanding the business behind a credit file.
- Logistics and freight: complete consignor and consignee registration details at booking, since the movement documentation raised later depends on them.
- Real estate: collect contractor and material-supplier registrations before a site vendor account is opened.
How to find GST registrations by PAN
Most teams settle four questions before they automate this lookup.
- Where you collect the PAN, and where you capture the consent that goes with it.
- Which returned registration becomes the default on the record, and who decides when there is more than one.
- What an empty result means for the journey, since a business may not be registered at all.
- How often you look up an existing counterparty again, because registrations are added and surrendered over time.
Where the GSTIN lookup sits in your vendor flow
Connect the lookup to an onboarding form, a vendor master, a procurement system, an accounts payable queue or an internal review dashboard. The result then lands where your reviewing team already works.
Two patterns are common. A lookup at onboarding completes the counterparty record before anyone uses it. A sweep across an existing base surfaces registrations you never collected, and states nobody knew a supplier had.
Consent rules for a PAN-to-GST lookup
A GST registration describes a business. The PAN the lookup starts from identifies a person where the holder is a proprietor. Collect consent at the point you capture the PAN, state the purpose in plain language, and run the lookup only for that purpose.
Keep the returned registrations inside the systems that need them, and apply the retention rules you already apply to counterparty records. Store what came back and when. A later reviewer can then see the basis for the GSTIN on file.
Access depends on the service contract you select. The response does not replace your own tax assessment.