The RPACPC 206AB Compliance Status API enables businesses to retrieve PAN-related tax information, including PAN operational status, PAN–Aadhaar linkage status, financial year, PAN allotment date, and the applicability indicator returned by the source.
Integrate tax verification information into vendor onboarding, supplier verification, accounts payable, and tax review workflows.
The 206AB Compliance Status API is part of the RPACPC Tax & Compliance Verification Suite. It accepts a PAN identifier and returns available PAN-linked information in a structured JSON response.
The API includes an aplicable_flag field that indicates Section 206AB applicability according to the configured source logic.
The API response may include the following information, depending on the response received:
PAN identifier associated with the verification request.
Name returned by the source, subject to masking policies.
Date of PAN allotment, available as a timestamp and formatted string.
Financial year associated with the verification result.
Operational status returned by the source.
Linkage status code returned by the source.
Applicability indicator returned in the API response.
Request identifiers, sequence information, and request/response timestamps, when provided.
Provide the PAN identifier and required consent fields.
RPACPC processes the request through the configured verification service.
Receive the available PAN status, Aadhaar linkage information, financial year, and applicability indicator.
Review the PAN-linked name, allotment date, operational status, and other available verification details.
Use the returned information in your tax review or verification workflow, considering the relevant financial year and applicable tax requirements.
| Parameter | Type | Description |
|---|---|---|
| request_id | String | Unique identifier supplied by the client for request tracking. |
| consent | String | Consent indicator supplied with the request. |
| consent_text | String | Consent statement associated with the request. |
| user_id | String | PAN identifier used for the lookup. |
{
"request_id": "REQ206AB001",
"consent": "Y",
"consent_text": "I hereby declare my consent for fetching my information via RPACPC API",
"user_id": "XXXXX1234X"
}| Field | Description |
|---|---|
| status | Overall API response status. |
| status_code | Response status code. |
| message | Message returned by the API. |
| billable | Billable indicator returned by the service. |
| error | Error information, if available. |
| data.user_id | PAN identifier associated with the result. |
| data.pan_name | PAN-linked name returned by the source. |
| data.pan_alotment_date | PAN allotment date represented as a timestamp. |
| data.pan_allotment_date_string | PAN allotment date in formatted text. |
| data.financial_year | Financial year associated with the returned information. |
| data.pan_aadhaar_link_status | PAN-Aadhaar linkage status code. |
| data.pan_status | PAN status returned by the source. |
| data.aplicable_flag | Indicator used by the configured source logic to represent Section 206AB applicability. |
| request_id | Client request identifier. |
| sequence_id | Request or transaction tracking identifier. |
| request_time | Timestamp associated with the request. |
| response_time | Timestamp associated with the response. |
{
"status": "SUCCESS",
"status_code": "200",
"message": "Data fetch successfully",
"billable": "Y",
"error": null,
"data": {
"user_id": "XXXXX1234X",
"pan_name": "A**** S****",
"pan_alotment_date": 1381516200000,
"financial_year": "2024-25",
"pan_aadhaar_link_status": "LK",
"pan_status": "Operative",
"aplicable_flag": "N",
"pan_allotment_date_string": "12-10-2013"
},
"request_id": "REQ206AB001",
"sequence_id": "MASKED-SEQUENCE-ID",
"request_time": "2026-10-09T10:00:00.000Z",
"response_time": "2026-10-09T10:00:00.200Z"
}The API field names retain the original spelling, including pan_alotment_date and aplicable_flag, for compatibility with the supplied schema.
Retrieve PAN-linked tax information as part of vendor onboarding and supplier verification workflows.
Integrate tax verification information into internal payment review processes and vendor records.
Include PAN status and available tax-related information in onboarding workflows where relevant.
Use the returned financial year, PAN status, and applicability indicator as inputs to internal tax review processes.
Connect the API with ERP, accounting, vendor management, and compliance applications to reduce manual data entry.
Common questions about the 206AB Compliance Check — what it returns, how fast it is, and how to integrate.
Government ID Check API helps banks, FinTechs, and NBFCs streamline KYC with faster identity verification and reduced manual work.
Read More
Empower your applications with India's Enterprise Verification Intelligence Platform for faster, more reliable verification.