PAN Account Linkage Verification

Endpoint Overview

POST /api/v1/pan/pan-account-linkage

Description

The PAN Account Linkage API enables financial institutions and businesses to verify the association between a customer's PAN (Permanent Account Number) and their bank account details. This API performs real-time validation to confirm whether a specific PAN is linked to the provided bank account number and IFSC code, returning comprehensive account information including the account holder's name, account type, and nature.

This verification is crucial for regulatory compliance, fraud prevention, and ensuring accurate customer identity validation in financial transactions and onboarding processes.

Key Benefits

Real-time verification of PAN-to-bank account linkage for fraud prevention

Comprehensive account information retrieval including holder name and account details

Streamlined KYC compliance for financial institutions and fintech companies

Automated validation reduces manual verification time and human errors

Use Cases

Banking & Finance

Fintech & Payment

Insurance & Investment

Account opening verification to ensure PAN matches bank account records

Loan application processing with automated account-PAN validation

Credit assessment workflows requiring verified account ownership

Digital banking onboarding with real-time account verification

Technical Implementation

Authentication

All API requests require authentication using a JWT Bearer token. Authentication follows these steps:

Obtain API Credentials: Register with Surepass to receive your API key.

Generate JWT Token: Use your API key to generate a JWT token.

Include in Requests: Add the token to the Authorization header as Bearer TOKEN.

Different authentication tokens are used for sandbox and production environments:

Sandbox: https://sandbox.surepass.io

Production: https://kyc-api.surepass.io

Request Parameters

Request Headers

Header	Required	Description
Authorization	Yes	Bearer token for API authentication (JWT format)
Content-Type	Yes	Must be set to `application/json`

Request Body

Parameter	Type	Required	Description
pan	string	Yes	10-character PAN number to verify (format: ABCDE1234F)
account	string	Yes	Bank account number to verify linkage with PAN
ifsc	string	Yes	IFSC code of the bank branch (11-character alphanumeric code)

Example Request

{
    "pan": "BQHPD5202R",
    "account": "925060049678785",
    "ifsc": "UBIN0569780"
}

Process Response

Response Parameters

Parameter	Type	Description
data	object	Contains verification results and account information
data.client_id	string	Unique identifier for this verification request
data.pan	string	PAN number that was verified
data.account	string	Bank account number that was verified
data.ifsc	string	IFSC code that was verified
data.linked	boolean	Indicates if PAN is linked to the provided account
data.full_name	string	Account holder's full name as per bank records
data.account_type	string	Type of account (e.g., "savings", "current")
data.account_nature	string	Nature of account (e.g., "single", "joint")
data.account_holder	string	Account holder status (e.g., "primary", "secondary")
status_code	integer	HTTP status code of the response
success	boolean	Indicates if the API call was successful
message	string/null	Additional message or error description
message_code	string	Machine-readable message code

Example Successful Response

{
    "data": {
        "client_id": "pan_account_linkage_WKVfwjqyocdmQZmOLfEz",
        "pan": "BQHPD5202R",
        "account": "925060049678785",
        "ifsc": "UBIN0569780",
        "linked": true,
        "full_name": "MUNNA SINGH",
        "account_type": "savings",
        "account_nature": "single",
        "account_holder": "primary"
    },
    "status_code": 200,
    "success": true,
    "message": null,
    "message_code": "success"
}

Possible Error Responses

Verification Failed

Internal Server Error

{
    "status_code": 422,
    "success": false,
    "message": "Verification Failed.",
    "message_code": "verification_failed"
}

This error occurs when the provided PAN and account details cannot be verified or are not linked in the banking system.

Integration Best Practices

Security Recommendations

Store JWT tokens securely and refresh them before expiration

Implement proper error handling for network timeouts and API failures

Log verification requests for audit trails while protecting sensitive data

Use HTTPS for all API communications to ensure data encryption in transit

User Experience Guidelines

Provide clear error messages to users when verification fails

Implement loading states during API calls to improve user experience

Cache successful verifications temporarily to avoid redundant API calls

Design graceful fallbacks for when the API is temporarily unavailable

Code Samples

cURL

Python

Node.js

Related APIs

PAN Verification: Verify PAN number validity and extract holder information
Bank Account Verification: Validate bank account details and account holder name
IFSC Code Verification: Verify IFSC codes and retrieve bank branch information
KYC Document Verification: Complete KYC document verification suite

Compliance and Legal Considerations

This API processes sensitive financial information and must be used in compliance with Indian data protection laws and RBI guidelines. Ensure proper data handling, storage, and retention policies are implemented. Organizations using this API must have appropriate regulatory permissions for accessing PAN and banking data. All verification requests should be logged for audit purposes while maintaining customer privacy and data security standards.

curl --location --request POST 'https://kyc-api.surepass.app/api/v1/pan/pan-account-linkage' \ --header 'Content-Type: application/json' \ --data-raw '{ "pan": "NHPQS8768L", "account": "5749218609", "ifsc": "KKBK00013459" }'

{ "data": { "client_id": "pan_account_linkage_WKVfwjqyocdmQZmOLfEz", "pan": "BQHPD5202R", "account": "925060049678785", "ifsc": "UBIN0569780", "linked": true, "full_name": "MUNNA SINGH", "account_type": "savings", "account_nature": "single", "account_holder": "primary" }, "status_code": 200, "success": true, "message": null, "message_code": "success" }

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

PAN Account Linkage

PAN Account Linkage Verification#

Description#

Use Cases#

Technical Implementation#

Request Headers#

Request Body#

Example Request#

Response Parameters#

Example Successful Response#

Possible Error Responses#

Integration Best Practices#

Code Samples#

Request

Responses