PAN To Email Mobile

Endpoint Overview

POST /api/v1/pan-to-email-mobile/verification

Description

The PAN to Email and Mobile Retrieval API enables businesses to retrieve contact information (email addresses and mobile numbers) associated with a given PAN (Permanent Account Number). This endpoint queries official databases to fetch all registered email IDs and mobile numbers linked to a specific PAN card, providing essential contact details for communication and verification purposes.

This API is particularly valuable for organizations that need to establish contact with PAN cardholders, verify communication channels, or enhance their customer profiles with accurate contact information. The service returns multiple email addresses and phone numbers if they exist in the records, ensuring comprehensive data retrieval for effective customer outreach and verification workflows.

Key Benefits

Comprehensive Contact Discovery: Retrieve all registered email addresses and mobile numbers associated with a PAN in a single API call

Enhanced Customer Profiling: Enrich existing customer data with verified contact information from official sources

Multi-Channel Communication: Access multiple communication channels to reach customers through their preferred contact methods

Streamlined Onboarding: Accelerate customer onboarding by auto-populating contact fields with verified information

Use Cases

Banking & Finance

Insurance & Wealth Management

E-commerce & Marketplaces

Customer Reactivation: Retrieve contact details of dormant account holders for reactivation campaigns

Loan Collections: Obtain verified contact information for borrowers to facilitate loan recovery processes

Account Updates: Reach out to customers for mandatory KYC updates or account maintenance notifications

Cross-Selling Campaigns: Access accurate contact details for targeted product offers and financial advisory services

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	JWT Bearer token for authentication. Format: `Bearer {TOKEN}`
Content-Type	Yes	Must be set to `application/json`

Request Body

Parameter	Type	Required	Description
id_number	string	Yes	Valid PAN card number in the format: 5 letters, 4 digits, 1 letter (e.g., ABCPD1234F)

Example Request

{
    "id_number": "ABCPD1234F"
}

Process Response

Response Parameters

Parameter	Type	Description
data	object	Contains retrieved contact information associated with the PAN
data.client_id	string	Unique identifier for this retrieval request generated by Surepass
data.id_number	string	PAN card number for which contact details were retrieved
data.email_id	array	List of email addresses registered with the PAN (may contain multiple entries)
data.mobile_number	array	List of mobile numbers registered with the PAN (may contain multiple entries)
status_code	integer	HTTP status code indicating the result of the API call
success	boolean	Indicates whether the retrieval was successful (true/false)
message	string	Additional message providing context about the response
message_code	string	Code representing the status of the operation (e.g., "success")

Example Successful Response

{
    "data": {
        "client_id": "pan_to_email_mobile_dEONf",
        "id_number": "ABCPD1234F",
        "email_id": [
            "MUNNATRIPATHI@GMAIL.COM",
            "MUNNA1234@GMAIL.COM"
        ],
        "mobile_number": [
            "9876543210"
        ]
    },
    "status_code": 200,
    "success": true,
    "message": "Success",
    "message_code": "success"
}

Possible Error Responses

Invalid PAN Format

Authentication Failed

Verification Error

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

This error occurs when the PAN number doesn't match the required format (5 letters + 4 digits + 1 letter).

Integration Best Practices

Security Recommendations

PII Protection: Treat retrieved email and mobile data as Personally Identifiable Information (PII) and encrypt it both in transit and at rest

Access Controls: Implement strict role-based access controls to limit who can retrieve contact information

Audit Logging: Maintain comprehensive logs of all API calls including timestamps, user IDs, and PAN numbers accessed for compliance purposes

Secure Token Storage: Never expose JWT tokens in client-side code or public repositories; store them securely in environment variables or secure vaults

Data Minimization: Only retrieve contact information when absolutely necessary and delete it when no longer needed

HTTPS Only: Always use HTTPS endpoints to encrypt data in transit and prevent interception of sensitive contact details

User Experience Guidelines

Consent Management: Always obtain explicit user consent before retrieving their contact information from PAN records

Data Transparency: Inform users about the source of retrieved contact information and how it will be used

Multiple Contact Handling: Design your UI to gracefully handle multiple email addresses and phone numbers in the response

Empty Array Handling: Implement proper handling for cases where no contact information is available (empty arrays)

Verification Workflow: Consider implementing additional verification steps (OTP, etc.) when using retrieved contact details

Progressive Disclosure: Use retrieved contact information to enhance user experience by pre-filling forms while allowing users to verify and update

Code Samples

cURL

Python

Node.js

Compliance and Legal Considerations

This API retrieves personal contact information (email addresses and mobile numbers) which is classified as sensitive personal data under various privacy regulations. Organizations using this API must:

Obtain explicit consent from individuals before retrieving their contact information linked to PAN records

Comply with the Information Technology Act, 2000, and the Personal Data Protection Bill regarding collection and processing of personal data

Implement purpose limitation principles - use retrieved contact information only for the specific purpose disclosed to the user

Maintain data security measures as mandated by the IT Act (Reasonable Security Practices and Procedures) Rules, 2011

Provide users with the right to access, correct, and delete their personal information as per applicable privacy laws

Ensure compliance with telecom regulations (TRAI guidelines) when using retrieved mobile numbers for marketing or promotional communications

Maintain detailed audit trails of all contact information retrievals for regulatory compliance and dispute resolution

Not share or sell retrieved contact information to third parties without explicit user consent

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/pan-to-email-mobile/verification' \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data-raw '{ "id_number": "ABCPD1234F" }'

{ "data": { "client_id": "pan_to_email_mobile_dEONf", "id_number": "ABCPD1234F", "email_id": [ "MUNNATRIPATHI@GMAIL.COM", "MUNNA1234@GMAIL.COM" ], "mobile_number": [ "9876543210" ] }, "status_code": 200, "success": true, "message": "Success", "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