Free demo hits. Pay when you go live. Request access
Business & KYB

TAN Verification API

Confirm a TAN is genuine and see the company or entity it belongs to. Essential wherever tax deduction at source is part of the relationship: payroll vendors, contractors, landlords and financial counterparties.

Response
Real-time
Inputs
1 required
Consent
Not required
Billing
Per successful call
POST /v1/tan-verification
Sandbox · Production
  1. Your application sends

    • TAN*
  2. emver API

    Validates the request, queries the source, normalises the answer and logs the call. Billed only on success.

  3. Verified with

    Income Tax Department TAN records

  4. You receive

    • TAN status
    • Registered company / deductor name
tan-verification Full reference
Overview

What the TAN Verification API does

TAN identifies the entity responsible for deducting and depositing tax at source. When a counterparty quotes a TAN on a certificate or contract, the TAN Verification API confirms it exists and returns the registered name, so you can be sure the deductor is who they say they are.

It is a small check that prevents a large class of errors in Form 16, Form 16A and TDS reconciliation, and it rounds out entity verification alongside PAN and GSTIN.

Benefits

Why teams use the TAN Verification API

Validate a Tax Deduction Account Number and resolve the deductor.

Prevents TDS mismatches

Confirm the deductor before certificates and reconciliations go wrong.

Entity resolution

Map a TAN to the company behind it in one call.

Real-time

Fits inside vendor and contractor onboarding forms.

Low cost

A quick, inexpensive addition to any KYB bundle.

Use cases

Where it's called

Where the TAN Verification API is typically called, and what it settles there.

Contractor and vendor onboarding

Verify the TAN of entities that will deduct tax on your invoices.

Lease and rental agreements

Confirm the tenant entity's TAN for rent TDS.

Employer verification

Corroborate a previous employer's existence via the TAN on a Form 16.

Financial counterparties

Validate deductor details in lending and treasury operations.

How it works

Four steps, one response envelope

Request and response details, environments and a ready-to-import collection are in the developer console.

  1. 01

    Authenticate

    Call with your organisation API key. Sandbox and production use the same contract.

  2. 02

    Send the inputs

    TAN as a JSON body. Optional fields sharpen the match.

  3. 03

    We verify at source

    emver queries the authoritative record, normalises the answer and logs the request.

  4. 04

    Act on the result

    A verification status plus the fields listed above, in the same response envelope as every other API.

Privacy and security built in

Consent recorded · Payloads not retained beyond your retention window · Every request traceable

FAQ

TAN Verification API: frequently asked questions

What teams ask before adding the TAN Verification API to their integration.

Yes. The TAN printed on a Form 16 resolves to the deductor's registered name, which is a useful corroboration during employment verification.

No. PAN identifies a taxpayer; TAN identifies an entity that deducts tax at source. Many businesses hold both, and emver lets you verify each with its own API.

Related

APIs that run alongside it

Usually called with the TAN Verification API, on the same key.

All APIs
Access usually set up within one working day

Start verifying with emver today.

Tell us which APIs and what monthly volume. We set up your organisation, approve the APIs with demo hits and share per-call pricing.