Skip to content

PAN-to-GST Lookup API

New

Find the GST registrations recorded against a PAN, including ones in states you did not know about, and put the right GSTIN on a merchant or vendor record.

Overview

A GSTIN is issued state by state, so one business can hold several registrations against a single PAN. There is one for each state it is registered in, and in some cases more than one within a state. A PAN-to-GST lookup returns the registrations recorded against a PAN. The lookup is a discovery step. It shows which registrations exist and lets a reviewer pick the one that belongs on an invoice, a contract or a vendor record. A separate GST verification check covers the registration profile in depth. The set of fields differs from one data source and one record to the next, and access depends on the service contract you select. A PAN identifies a person where the holder is a proprietor. Run the lookup with consent and for a stated business purpose.

Category
KYB Services
Coverage
GST registrations recorded against a PAN across Indian states and union territories
Input
A PAN
Output
The GST registrations recorded against the PAN, with state and status where available
Typical users
Vendor onboarding, accounts payable, merchant operations, tax and credit teams
Coverage note
Registrations across Indian states and union territories. The fields returned vary by data source and by the individual record.

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

Endpoint URL and method

POSThttps://gateway.staging.finsour.io/v1/business/gstin-by-pan

Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.

Authentication

Scheme API key travels in the X-Api-Key header

Send your API key in this header on every call, from your own server: a key sent from a browser is refused. A key starting fs_test_ calls the sandbox and one starting fs_live_ calls production, at the same address. Create keys in the FinSour console.

Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.

Request parameters

Content type application/json

Headers

NameTypeRequiredDescriptionConstraints
Idempotency-KeystringRequiredA key you generate for each attempt. Sending the same key again returns the first answer instead of running the check twice; the same key with a different body is refused.8 to 255 characters. Matches ^[A-Za-z0-9._:-]+$

Body

NameTypeRequiredDescriptionConstraints
inputobjectRequiredThe details to check.—
input.panstringRequired—Matches ^[A-Z]{5}[0-9]{4}[A-Z]$. Exactly 10 characters
optionsobjectOptionalSettings for this call.—
options.referencestringOptionalYour own reference for this call. It comes back unchanged as meta.reference.1 to 128 characters
options.consentobjectOptionalThe person's consent to this check.—
options.consent.obtainedbooleanRequiredSend true once the person has agreed to the check.Always true
options.consent.atstring (date-time)RequiredWhen the person gave consent.—
options.consent.purposestringRequiredWhat the check is for, for example kyc.1 to 64 characters

Request samples

cURL

curl -X POST https://gateway.staging.finsour.io/v1/business/gstin-by-pan \
  -H "X-Api-Key: $FINSOUR_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{
  "input": {
    "pan": "<pan>"
  }
}'

Node.js

const response = await fetch("https://gateway.staging.finsour.io/v1/business/gstin-by-pan", {
  method: "POST",
  headers: {
    "X-Api-Key": process.env.FINSOUR_API_KEY,
    "Idempotency-Key": crypto.randomUUID(),
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    "input": {
      "pan": "<pan>"
    }
  }),
});

console.log(response.status, await response.json());

Python

import os
import uuid

import requests

response = requests.post(
    "https://gateway.staging.finsour.io/v1/business/gstin-by-pan",
    headers={
        "X-Api-Key": os.environ["FINSOUR_API_KEY"],
        "Idempotency-Key": str(uuid.uuid4()),
    },
    json={
        "input": {
            "pan": "<pan>",
        },
    },
    timeout=30,
)

print(response.status_code, response.json())

Generated from the fields above. Replace each value in angle brackets with your own; the key is read from FINSOUR_API_KEY.

Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.

Response schema

Status 200 · content type application/json

NameTypePresentDescriptionConstraints
dataobjectAlwaysThe result of the check.—
data.foundbooleanAlways——
data.maskedPanstringAlwaysThe PAN sent, as its display form.Matches ^[A-Z]{3}X{5}[0-9][A-Z]$
data.gstinsarray of objectsAlwaysOne entry per registration, in the order the registry lists them; empty when there is none.—
data.gstins[].gstinstringAlways—Matches ^[0-9]{2}[A-Z]{5}[0-9]{4}[A-Z][0-9A-Z]Z[0-9A-Z]$. Exactly 15 characters
data.gstins[].statestring or nullAlwaysThe state the registration is in, as the registry names it (for example Karnataka).—
data.gstins[].statusstring or nullAlwaysThe registration's status word (for example ACTIVE, INACTIVE), upper-cased, as given.—
data.sourceobjectAlways——
data.source.fetchedAtstringAlwaysWhen the answer was fetched: RFC 3339 UTC with a Z, never an epoch or an IST offset.Matches ^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d{1,9})?Z$

Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.

Error codes

CodeStatusMeaningRetrying
API_VERSION_UNSUPPORTED400That API version is no longer supported.Do not retry automatically
IDEMPOTENCY_KEY_INVALID400That Idempotency-Key does not meet the required format.Do not retry automatically
IDEMPOTENCY_KEY_REQUIRED400An Idempotency-Key header is required for this request.Do not retry automatically
REQUEST_MALFORMED400The request could not be parsed.Do not retry automatically
AUTH_KEY_EXPIRED401The API key is not valid.Do not retry automatically
AUTH_KEY_INVALID401The API key is not valid.Do not retry automatically
AUTH_KEY_MISSING401No API key was presented.Do not retry automatically
AUTH_KEY_REVOKED401The API key is not valid.Do not retry automatically
INSUFFICIENT_BALANCE402The available balance is not enough for this request.Do not retry automatically
AUTH_IP_NOT_ALLOWED403This API key may not be used from this address.Do not retry automatically
ENTITLEMENT_MISSING403This organization is not entitled to that product in this environment.Do not retry automatically
ORGANIZATION_SUSPENDED403This organization is not active.Do not retry automatically
PRODUCT_NOT_AVAILABLE403That product is not available.Do not retry automatically
PRODUCT_RETIRED403That product has been withdrawn.Do not retry automatically
SCOPE_INSUFFICIENT403This API key does not carry the scope this product requires.Do not retry automatically
PRODUCT_NOT_FOUND404No such product.Do not retry automatically
IDEMPOTENCY_KEY_REUSED409That idempotency key was already used for a different request.Do not retry automatically
PRICE_UNAVAILABLE409No active price covers this product right now.Safe to retry
REQUEST_IN_PROGRESS409An earlier attempt with this key is still running.Safe to retry
SETTLEMENT_PENDING409This request is awaiting reconciliation by an operator.Do not retry automatically
API_VERSION_SUNSET410That API version passed its announced sunset date.Do not retry automatically
REQUEST_TOO_LARGE413The request body is too large.Do not retry automatically
UNSUPPORTED_MEDIA_TYPE415That content type is not accepted on this route.Do not retry automatically
SANDBOX_FIXTURE_MISSING422No sandbox fixture exists for this input. Use a different test value.Do not retry automatically
UPSTREAM_REJECTED422The upstream source rejected the input.Do not retry automatically
VALIDATION_FAILED422The request payload is invalid.Do not retry automatically
CONCURRENCY_LIMIT429Too many simultaneous requests.Safe to retry
QUOTA_EXCEEDED429The allowance for this window is spent.Do not retry automatically
RATE_LIMITED429Too many requests.Safe to retry
INTERNAL_ERROR500An unexpected error occurred.Safe to retry
OUTCOME_UNCERTAIN502The outcome of this request is not yet known. Retry with the same Idempotency-Key.Do not retry automatically
UPSTREAM_UNAVAILABLE502The upstream source is unavailable. Retry shortly.Safe to retry
MAINTENANCE_MODE503The service is in a maintenance window.Safe to retry
NO_PROVIDER_AVAILABLE503No provider can serve this product right now.Safe to retry
SERVICE_OVERLOADED503The service is shedding load. Retry shortly.Safe to retry
UPSTREAM_TIMEOUT504The upstream source did not respond in time.Safe to retry

Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.

Rate limits

ScopeLimitWindowAt the limit
Your API key, within your organisation's limitThe figure in X-RateLimit-LimitPer minute429 RATE_LIMITED, with Retry-After in seconds. Every answer past authentication carries X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset.

Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.

Use cases

  • Fintech and payments: find a merchant's GSTIN for the state where supply is made
  • Marketplaces: discover seller registrations across fulfillment states at signup
  • Procurement: pick the correct vendor GSTIN before an invoice is booked for credit
  • Lending and NBFC: map the states an MSME borrower is registered in
  • Logistics and freight: complete consignor and consignee registrations at booking
  • Real estate: collect contractor registrations before a site vendor account opens

What this service does

  • One PAN, every registration on it

    GST registration is state-wise. A business can hold several GSTINs against one PAN. The lookup returns the registrations recorded against the number, including any the counterparty did not quote.

  • The GSTINs the response carries

    You get the GSTINs recorded against the PAN, with the state each one belongs to and the status recorded for it where the underlying source carries that. The exact fields available vary by data source and by the individual record.

  • Discovery first, verification after

    The lookup finds the registrations. A separate GST verification check starts from a GSTIN and covers the registration profile in depth. Many teams run the two together.

  • Signup lookups and periodic sweeps

    Registrations are added and surrendered over time. The same lookup completes a counterparty record at signup, and sweeps an existing merchant, seller or supplier base later on.

How a check runs

  1. Tell us where the lookup fits

    Use Get API to start the conversation. We agree the service contract once we know where the lookup sits in your onboarding or vendor workflow.

  2. Add the lookup to your vendor flow

    Connect the lookup to your onboarding form, vendor master, procurement system or review dashboard, following the technical documentation we provide at onboarding.

  3. Send the PAN

    Your application sends the PAN as the counterparty provided it, once you have captured consent at the point of collection.

  4. Read the list of registrations

    The GST registrations recorded against the number come back in a structured response, with state and status information where it is available.

  5. Pick the GSTIN you will use

    Select the registration that belongs on the invoice, contract or vendor record. Store the full result with its timestamp for later review.

Questions

Why does one PAN have more than one GSTIN?
A business registers separately in each state it operates in, because GST registration is state-wise. In some cases it holds more than one registration within a state. Every one of those numbers is built around the same PAN, which is why a PAN-based lookup can return several.
How is a PAN-to-GST lookup different from GST verification?
This lookup starts from a PAN and discovers which registrations exist. GST verification starts from a GSTIN and covers the registration profile in depth. Teams often run the lookup first, then verify the registration they will actually use.
Can the lookup return cancelled GST registrations?
It can, where the underlying source records them. A registration that has been surrendered or cancelled may still appear in the list. Read the status recorded for a registration before you put it on an invoice or a contract.
What does it mean when no GSTIN is found on a PAN?
No registration was found against the number in the information available. A business may sit below the turnover level at which registration is required, may not be registered, or may have surrendered its registrations. An empty result is a normal outcome, and on its own it says nothing negative about a counterparty.
Is consent needed for a PAN-based GSTIN search?
The registrations describe a business, and the PAN you start from is personal data where the holder is a proprietor. Collect consent at the point you capture the PAN, run the lookup only for the stated business purpose, and handle the result under your existing counterparty data rules.
How do I set up the PAN-to-GST lookup?
Use Get API to tell us about your workflow and volumes. The service contract then sets your access, the attributes available to you and the integration documentation.

Catalog entry last updated .