KYBTAN Verification

TAN Verification — Tax Deductor Lookup

Verify a TAN and retrieve the deductor's name, category, and status. Essential for TDS compliance and vendor verification.

curl -X GET "https://production.deepvue.tech/v1/verification/tax-payer/tan?tan_number=example_string" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN (JWT)" \
  -H "x-api-key: YOUR_API_KEY"
{
  "code": 200,
  "timestamp": 1738561863604,
  "transaction_id": "2ee6595b-5ce6-42a1-9660-a7092f5cd1d1",
  "data": {
    "nameOrgn": "AMAZON SELLER SERVICES PRIVATE LIMITED",
    "addLine1": "26/1 8TH FLOOR",
    "addLine2": "BRIGADE GATEWAY",
    "addLine3": "DR.RAJKUMAR ROAD",
    "addLine5": "BANGALORE",
    "stateCd": 15,
    "pin": 560055,
    "phoneNum": "9xxxxxxxx9",
    "dtTanAllotment": 1293691500000,
    "emailId1": "RxxxxxxxxxxxxxxxxxM"
  },
  "message": "TAN Verified Successfully"
}
GET
/v1/verification/tax-payer/tan
GET
Bearer Token (JWT)
Bearer Tokenstring
Required

ACCESS_TOKEN generated from the authorize endpoint. Should be included in the header as Bearer .

ACCESS_TOKEN generated from the authorize endpoint. Should be included in the header as Bearer .
API Key (header: x-api-key)
x-api-keystring
Required

The CLIENT_SECRET provided to you. This header parameter is required for authentication purposes.

The CLIENT_SECRET provided to you. This header parameter is required for authentication purposes.
Request Preview
Response

Response will appear here after sending the request

Authentication

header
Authorizationstring
Required

Bearer token (JWT). ACCESS_TOKEN generated from the authorize endpoint. Should be included in the header as Bearer .

header
x-api-keystring
Required

API Key for authentication. The CLIENT_SECRET provided to you. This header parameter is required for authentication purposes.

Query Parameters

Responses

codeinteger
timestampinteger
transaction_idstring
messagestring
dataobject

Overview

This API enables verification of Tax Deduction and Collection Account Numbers (TANs) and retrieves associated organizational details from authoritative sources.

The endpoint accepts a 10-digit alphanumeric TAN number as input. Upon successful verification, it returns organizational information including:

  • Organization name
  • Complete address (multiple lines)
  • State code and PIN
  • Contact details (phone and email)
  • TAN allotment date

The API handles two primary outcomes: successful TAN verification returning full organizational data, or a "no record found" response when the TAN does not exist in the system.