UPI To Account

Endpoint Overview

POST /api/v1/bank-verification/upi-to-account

Description

The UPI to Bank Account Verification API enables real-time verification and retrieval of bank account details associated with a UPI ID. This endpoint performs a small verification transaction (₹0.01) to validate the UPI ID and returns comprehensive banking information including the account holder's name, account number, and IFSC code.

This API bridges the gap between UPI identifiers and traditional banking details, providing businesses with a seamless way to verify customer banking information without requiring manual data entry. The verification process is instant, secure, and complies with banking regulations while maintaining user privacy.

Key Benefits

Instant Verification: Real-time validation of UPI IDs with immediate response containing bank account details

Reduced Fraud: Authenticate user identity by matching UPI-linked bank accounts against provided information

Seamless Onboarding: Eliminate manual bank account entry errors and streamline customer verification workflows

Cost-Effective: Minimal verification amount (₹0.01) ensures affordability while maintaining compliance

Use Cases

Financial Services

E-commerce & Marketplaces

Gig Economy & Payroll

Loan Disbursement Verification: Verify borrower's bank account details through their UPI ID before processing loan disbursements

Investment Account Setup: Validate investor banking information during account opening and KYC processes

Insurance Claim Processing: Authenticate beneficiary bank accounts for claim settlements using UPI 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.app

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

Request Parameters

Request Headers

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

Request Body

Parameter	Type	Required	Description
upi_id	string	Yes	Valid UPI ID to be verified. Format: `{identifier}@{bankcode}`. Example: `9999966666@axis`

Example Request

{
    "upi_id": "9999966666@axis"
}

Process Response

Response Parameters

Parameter	Type	Description
data	object	Contains the verification result and bank account details
data.client_id	string	Unique identifier for this verification transaction
data.upi_id	string	The verified UPI ID that was submitted in the request
data.full_name	string	Full name of the account holder as registered with the bank
data.account_number	string	Bank account number linked to the UPI ID
data.ifsc	string	IFSC code of the bank branch where the account is held
data.amount	number	Verification transaction amount (always 0.01)
data.payment_mode	string	Payment method used for verification (UPI)
status_code	integer	HTTP status code of the response (200 for success)
success	boolean	Indicates whether the API request was successful
message	string	Human-readable message describing the result
message_code	string	Machine-readable code for programmatic handling

Example Successful Response

{
    "data": {
        "client_id": "upi_to_account_bmtmpdocilrlGuBTBScI",
        "upi_id": "9999966666@axis",
        "full_name": "AMBIGA DEVI",
        "account_number": "159488920019",
        "ifsc": "INDB0000148",
        "amount": 0.01,
        "payment_mode": "UPI"
    },
    "status_code": 200,
    "success": true,
    "message": "Success",
    "message_code": "success"
}

Possible Error Responses

Authentication Failed

Service Unavailable

{
    "data": null,
    "status_code": 401,
    "success": false,
    "message": "Authentication failed. Invalid or expired token",
    "message_code": "authentication_failed"
}

This error indicates that the Bearer token is missing, invalid, or has expired. Generate a new JWT token and retry.

Integration Best Practices

Security Recommendations

Secure Token Storage: Never expose JWT tokens in client-side code or version control systems. Store tokens securely in environment variables or secure vaults

Token Rotation: Implement regular token refresh mechanisms to minimize security risks from compromised credentials

HTTPS Only: Always use HTTPS endpoints for API calls to ensure data encryption in transit

Input Validation: Validate UPI ID format on the client side before making API calls to reduce unnecessary requests

Rate Limiting: Implement rate limiting on your application to prevent abuse and comply with API usage policies

Audit Logging: Maintain logs of all verification requests for compliance and troubleshooting purposes

User Experience Guidelines

User Consent: Always obtain explicit user consent before performing UPI verification, explaining that a small amount will be transacted

Transaction Notification: Inform users they will receive a ₹0.01 transaction notification from their bank/UPI app

Error Handling: Provide clear, user-friendly error messages when verification fails, with guidance on corrective actions

Loading States: Display appropriate loading indicators during API calls as verification may take a few seconds

Data Privacy: Clearly communicate how the retrieved bank account information will be used and stored

Retry Mechanism: Allow users to retry verification if it fails due to temporary issues, but limit retry attempts to prevent abuse

Code Samples

cURL

Python

Node.js

Related APIs

Bank Account Verification API: Directly verify bank account details using account number and IFSC code for traditional banking verification workflows.

Penny Drop Verification API: Perform small-value transactions to verify bank account ownership and validate account status before larger transactions.

IFSC Code Lookup API: Retrieve detailed bank branch information using IFSC codes to validate banking details and display branch information to users.

UPI ID Validation API: Check UPI ID format validity and active status without performing financial transactions for pre-validation scenarios.

Compliance and Legal Considerations

This API performs financial transactions and must be used in compliance with applicable banking regulations and data protection laws. Ensure you have proper user consent before initiating verification transactions. The ₹0.01 verification amount is compliant with RBI guidelines for account verification purposes. Maintain proper records of all verification requests for audit purposes as required by financial regulations. Users must be informed about the verification transaction through your application's terms of service and privacy policy. Data retrieved through this API should be handled according to PCI DSS standards and stored securely with appropriate encryption. Ensure compliance with the Digital Personal Data Protection Act (DPDP) when processing and storing user banking information.

{ "data": { "client_id": "upi_to_account_bmtmpdocilrlGuBTBScI", "upi_id": "9999966666@axis", "full_name": "AMBIGA DEVI", "account_number": "159488920019", "ifsc": "INDB0000148", "amount": 0.01, "payment_mode": "UPI" }, "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