PAN To CIN

Endpoint Overview

POST /api/v1/corporate/pan-to-cin

Description

The PAN to CIN Conversion API enables businesses to retrieve Corporate Identification Number (CIN) and comprehensive company details using a company's Permanent Account Number (PAN). This endpoint seamlessly converts PAN numbers to CIN while simultaneously fetching official company information registered with the Ministry of Corporate Affairs (MCA).

This API serves as a critical tool for corporate verification, regulatory compliance, and business intelligence operations. By providing instant access to verified corporate data, it eliminates the need for manual lookups and reduces verification time from hours to seconds. The service ensures data accuracy by retrieving information directly from official government databases.

Key Benefits

Instant Corporate Verification: Convert PAN to CIN and retrieve company details in real-time with sub-second response times

Regulatory Compliance: Streamline KYC and due diligence processes with verified corporate information

Data Accuracy: Access authoritative company data directly from MCA records, ensuring up-to-date and reliable information

Simplified Integration: Single API call replaces multiple manual verification steps, reducing operational complexity

Use Cases

Financial Services

E-commerce & Marketplaces

Legal & Compliance

Corporate Onboarding: Verify company credentials during business account opening processes

Loan Application Processing: Validate corporate borrowers and retrieve official company details for credit assessment

Vendor Payment Verification: Confirm corporate vendor identities before establishing payment relationships

Investment Due Diligence: Quickly retrieve corporate structure information for investment evaluations

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.app

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

Request Parameters

Request Headers

Header	Required	Description
Authorization	Yes	Bearer token for authentication. Format: `Bearer {JWT_TOKEN}`
Content-Type	Yes	Must be set to `application/json`

Request Body

Parameter	Type	Required	Description
pan_number	string	Yes	Valid PAN (Permanent Account Number) of the company. Must be 10 characters alphanumeric format (e.g., AAACM3484F)

Example Request

{
    "pan_number": "AAACM3484F"
}

Process Response

Response Parameters

Parameter	Type	Description
data	object	Container object holding all company information
data.client_id	string	Unique identifier for this API request transaction
data.cin_number	string	Corporate Identification Number assigned by MCA
data.company_name_search	string	Company name as registered in search records
data.company_name	string	Official registered company name
data.company_type	string	Type of company entity (e.g., "ltd" for Limited)
status_code	integer	HTTP status code of the response (200 for success)
success	boolean	Indicates whether the request was successful
message	string/null	Additional message or error description (null on success)
message_code	string	Status code identifier (e.g., "success")

Example Successful Response

{
    "data": {
        "client_id": "corporate_pan_cin_wNdvfmZTEyDBaiNAeZdg",
        "cin_number": "L64200MH1986PLC041370",
        "company_name_search": "TECH MAHINDRA LIMITED",
        "company_name": "TECH MAHINDRA LIMITED",
        "company_type": "ltd"
    },
    "status_code": 200,
    "success": true,
    "message": null,
    "message_code": "success"
}

Possible Error Responses

Invalid PAN Format

Authentication Error

{
    "data": null,
    "status_code": 400,
    "success": false,
    "message": "Invalid PAN number format",
    "message_code": "invalid_input"
}

Occurs when the provided PAN number doesn't match the required alphanumeric format or length.

Integration Best Practices

Security Recommendations

Secure Token Storage: Store JWT tokens securely using environment variables or secure vault services. Never hardcode tokens in source code or commit them to version control

HTTPS Only: Always use HTTPS endpoints to ensure encrypted data transmission. Never make API calls over unsecured HTTP connections

Token Rotation: Implement regular token rotation policies and refresh tokens before expiration to maintain uninterrupted service

Input Validation: Validate PAN format on the client side before making API calls to reduce unnecessary requests and improve user experience

Error Handling: Implement comprehensive error handling to manage authentication failures, network issues, and invalid responses gracefully

Request Logging: Maintain audit logs of API requests (excluding sensitive tokens) for security monitoring and troubleshooting purposes

User Experience Guidelines

Progressive Loading: Display loading indicators during API calls to provide visual feedback to users

Input Formatting: Implement auto-formatting for PAN input fields (e.g., uppercase conversion) to reduce user errors

Validation Feedback: Provide immediate client-side validation feedback before submitting PAN numbers to the API

Clear Error Messages: Translate technical error codes into user-friendly messages that guide users toward resolution

Caching Strategy: Cache successful responses appropriately to reduce redundant API calls for the same PAN within a reasonable timeframe

Retry Logic: Implement exponential backoff retry logic for transient failures to improve reliability

Code Samples

cURL

Python

Node.js

Compliance and Legal Considerations

This API retrieves data from official government databases and should be used in compliance with applicable data protection regulations including the Information Technology Act, 2000 and data privacy laws. Users must:

Obtain necessary consent from entities before retrieving their corporate information

Use retrieved data solely for legitimate business purposes such as verification, compliance, and due diligence

Implement appropriate data security measures to protect corporate information

Comply with data retention policies and delete information when no longer needed

Ensure usage aligns with KYC/AML regulations and corporate verification standards

Organizations using this API for regulated activities should consult with legal counsel to ensure compliance with sector-specific regulations.

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

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

curl --location --request POST 'https://kyc-api.surepass.app/api/v1/corporate/pan-to-cin' \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data-raw '{ "pan_number": "AAACM3484F" }'

{ "data": { "client_id": "corporate_pan_cin_wNdvfmZTEyDBaiNAeZdg", "cin_number": "L64200MH1986PLC041370", "company_name_search": "TECH MAHINDRA LIMITED", "company_name": "TECH MAHINDRA LIMITED", "company_type": "ltd" }, "status_code": 200, "success": true, "message": null, "message_code": "success" }

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