Skip to content

Published services, current details, and clear categories.

Explore APIs

PAN Account Linkage API

Check whether a submitted PAN and bank account appear linked in the available information, and settle it before a disbursal, settlement or payout run depends on the answer.

PANACCOUNT
Request and response

You confirm the required fields and consent steps with us during onboarding.

You send

A PAN, and the bank account it is checked against (account number and IFSC)

You receive

A linkage status for the submitted pair, in a structured response. Available fields vary by data source and record.

Coverage
Linkage status for a submitted PAN and Indian bank account
Typical users
Lenders and NBFCs, fintech and payment platforms, insurers, marketplaces, staffing and gig platforms, enterprise finance teams
Coverage note
Shows what available information holds for the submitted pair at the time of the check. The selected service contract sets the scope.
Overview

What you can do with the PAN Account Linkage API

A PAN account linkage check tells you whether a submitted Permanent Account Number and a submitted bank account appear linked in the available information. Banks hold a PAN against the accounts they open. Any process that pays money out assumes the receiving account belongs to the person whose PAN sits on the file. An API check reads that status inside the workflow that already holds both values. You get the answer while a correction is still cheap, instead of meeting it as a failed credit or a held settlement. Your application submits the PAN and the account details, and a linkage status comes back in a structured response. The question is narrower than account verification. Penny Drop and Penny Less show that an account exists and whose name the bank holds against it. This check reports whether that account and the PAN appear associated. Available fields vary by data source and record, and the scope of a response depends on the selected service contract.

  • One question: are they linked?

    The check reports whether the submitted PAN and bank account appear linked in the available information. It does not confirm identity, verify either value on its own, or describe the balance or state of the account.

  • How it differs from Penny Drop

    Penny Drop and Penny Less show that an account exists and whose name the bank holds against it. This check reports whether that account and the PAN appear associated, which is the part a payout run assumes and rarely checks.

  • Inconclusive gets its own answer

    A pair the available information holds nothing about comes back as inconclusive, not as a negative. Your workflow can route the two down separate paths, instead of treating a gap in the records as a decision against the customer.

  • Catch a mismatch before the payout

    Run the check while a file is being prepared and a mismatch becomes something the customer can correct. The same mismatch found after the payment is a reversed credit, a support ticket and a re-run.

How it works

The five-step PAN Account Linkage API workflow

Our team walks you through the exact request and response for this service during onboarding.

Step 1

Tell us what you are building

Tell us about the workflow you have in mind. We agree the services your contract covers and the onboarding steps for your environment.

Step 2

Check the consent covers both values

Confirm that the customer relationship, the consent and the business reason cover a check that relates a PAN to a bank account, before any request is sent.

Step 3

Send the PAN and the account

Your application sends the PAN with the bank account details it should be checked against, normally the account number and the IFSC. Both come from the workflow that already holds them.

Step 4

Read the linkage status

The available information comes back as a structured status for the submitted pair, with a clear inconclusive outcome where the records hold nothing about it.

Step 5

Split the three outcomes

Send a clear status, an inconclusive result and a mismatch down separate paths. Record the status against the file, and tell the customer what to correct where a mismatch is what holds the payment.

Industries

Where teams use PAN Account Linkage API

These sectors build the check into a decision they already make.

  • Lending and NBFCs

    Check the disbursal account against the applicant PAN before release

  • Fintech and payments

    Check a merchant settlement account during onboarding

  • Insurance

    Check the claimant account before a settlement reported for tax

  • Marketplaces

    Check a seller account before a payout is released

  • Staffing and gig platforms

    Check worker accounts ahead of a payout run

  • Enterprise finance

    Check a vendor account before the first payment is made

What Is a PAN Bank Account Linkage Check?

A PAN bank account linkage check tells you whether a submitted Permanent Account Number and bank account appear linked in the available information.

Banks hold a PAN against the accounts they open. Later processes then assume the account receiving the money belongs to the person whose PAN is on the file. Where the two are not linked, that assumption fails quietly, usually at the payment.

Running a PAN and Account Linkage Check Through an API

An API puts the check inside the flow that already holds both values, instead of leaving it to a failed credit or a reconciliation list.

Your application submits the PAN with the bank account details, and a linkage status comes back in a structured response.

The value shows at volume. One broken file can be sorted out by hand, while a payout run of several thousand cannot.

What You Send: A PAN and a Bank Account

You send a pair your workflow already holds: the PAN, and the bank account it is checked against. That normally means the account number and the IFSC that identifies the branch.

Both come from your own customer file, covered by the consent and authorization your relationship rests on. The fields available may vary with the data source and the record, and the scope of a response depends on the selected service contract.

Linkage Check, Account Verification and Name Match

Three questions get run together at payout time, and they are easy to confuse.

Account verification asks whether an account exists and can receive a credit. Penny Drop answers that by depositing a nominal amount and reading back the name the bank holds against it. Penny Less answers a similar question without moving money.

A linkage check asks something narrower: whether that account and the submitted PAN appear associated in the available information. It does not confirm identity, verify either value on its own, or describe the balance or state of the account.

Teams paying out at scale usually run both. The account has to be reachable, and it has to belong to the person the file is about.

Who Runs a PAN Linkage Check

  • Lending and NBFCs check the disbursal account against the applicant's PAN before release, so a mismatch surfaces while the file is still open.
  • Fintech and payment platforms check a merchant's settlement account at onboarding, before settlement instructions are set up.
  • Insurers check the claimant account ahead of a settlement that will be reported for tax.
  • Marketplaces, staffing and gig platforms check seller and worker accounts before a payout run, where one mismatched record can hold up a batch.
  • Enterprise finance teams check a vendor account before the first payment against a new master record.

How to Check PAN and Bank Account Linkage Online

  1. Collect the PAN and the bank account details on the same customer file.
  2. Confirm that consent and an authorized business purpose cover a check on both.
  3. Submit the pair through the API.
  4. Read the returned status, and send a mismatch to review.
  5. Ask the customer to correct the record, then re-check before the payment goes out.

Where the Linkage Check Sits in Your Payout Flow

Place the check before the first payment. A mismatch found while the customer is in the flow is a correction. The same mismatch found at disbursal is a reversed credit, a support ticket and a re-run.

Treat an inconclusive result as its own outcome. Records update on their own schedule, and a gap in the available information says nothing against the customer.

Keep the status with the file it justified, and re-check whenever a customer changes the account they want to be paid into.

A PAN and a bank account are both personal information, and relating them is more sensitive than reading either alone. Run the check only for customers you already hold a relationship with, for a purpose they were told about, with consent and authorization recorded.

Keep consent specific and revocable. Limit access to the team whose work needs it, and keep the status only as long as that purpose requires. Where a status affects something the customer experiences, such as a held payout, give them a route to correct their records.

FAQ

Common questions

What teams ask before they integrate PAN Account Linkage API.

A pair: the PAN, and the bank account it should be checked against, normally the account number with the IFSC. Both come from your own customer file, and both should be covered by the consent and authorization your relationship with that customer rests on.

Get started

Add PAN Account Linkage API to your workflow

Tell us how you plan to use it. Our team sets up API access, agrees your pricing and takes you through onboarding.