Mobile To Account

Endpoint Overview

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

Description

This API endpoint enables you to retrieve bank account details associated with a provided mobile number. It serves as a verification tool that returns comprehensive banking information including the account holder's name, account number, IFSC code, and UPI ID linked to the specified mobile number. This service streamlines the verification process for financial transactions and user onboarding by eliminating the need for manual bank detail verification.

Key Benefits

Instant verification of bank account details using just a mobile number

Reduces fraud by confirming the link between mobile numbers and bank accounts

Simplifies user onboarding by auto-populating bank details

Enables seamless integration with UPI payment systems

Use Cases

Financial Services

E-commerce

FinTech

Verify customer bank details during loan application processing

Streamline KYC verification for new account openings

Validate payment recipient details before processing transactions

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 authentication (JWT format)
Content-Type	Yes	Application/json

Request Body

Parameter	Type	Required	Description
mobile_number	String	Yes	The mobile number for which bank account details are to be retrieved

Example Request

{
    "mobile_number": "7827215213"
}

Process Response

Response Parameters

Parameter	Type	Description
data	Object	Container for the response data
data.client_id	String	Unique identifier for the client request
data.mobile_number	String	Mobile number that was provided in the request
data.upi_id	String	UPI ID associated with the mobile number
data.full_name	String	Full name of the account holder
data.account_number	String	Bank account number linked to the mobile number
data.ifsc	String	IFSC code of the bank branch
status_code	Integer	HTTP status code of the response
success	Boolean	Indicates if the request was successful
message	String or null	Additional information about the response (if any)
message_code	String	Code indicating the status of the request

Example Successful Response

{
    "data": {
        "client_id": "mobile_to_account_qoOgfdmNryBsvlvqpGmg",
        "mobile_number": "7827215213",
        "upi_id": "7827215213@ptaxis",
        "full_name": "VISHAL SINGH",
        "account_number": "5729012511",
        "ifsc": "KKBK0001234"
    },
    "status_code": 200,
    "success": true,
    "message": null,
    "message_code": "success"
}

Possible Error Responses

Invalid Mobile Number

Authentication Error

Server Error

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

The mobile number provided is not in a valid format. Ensure it is a valid Indian mobile number.

Integration Best Practices

Security Recommendations

Store JWT tokens securely and never expose them in client-side code

Implement proper error handling to avoid exposing sensitive information

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

Implement rate limiting on your end to prevent abuse of the API

User Experience Guidelines

Implement proper validation for mobile numbers before making API calls

Display a loading indicator during API calls to improve user experience

Provide clear error messages to users when verification fails

Consider caching verified details (with appropriate TTL) to reduce redundant API calls

Code Samples

cURL

Python

Node.js

Related APIs

Account to IFSC Verification: Verifies bank account details using account number and IFSC code

UPI ID Verification: Validates UPI IDs and retrieves associated account information

Bank Statement Analysis: Analyzes bank statements for transaction patterns and account verification

Compliance and Legal Considerations

This API handles sensitive financial information and must be used in compliance with data protection regulations. Ensure you have proper consent from users before retrieving their bank account details. The use of this API may be subject to banking regulations and KYC/AML compliance requirements in your jurisdiction.

curl --location --request POST 'https://kyc-api.surepass.app/api/v1/bank-verification/mobile-to-account' \ --header 'Content-Type: application/json' \ --data-raw '{ "mobile_number": "7827215213" }'

{ "data": { "client_id": "mobile_to_account_qoOgfdmNryBsvlvqpGmg", "mobile_number": "7827215213", "upi_id": "7827215213@ptaxis", "full_name": "VISHAL SINGH", "account_number": "5729012511", "ifsc": "KKBK0001234" }, "status_code": 200, "success": true, "message": null, "message_code": "success" }

Mobile To Account

Mobile To Account#

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

Mobile To Account

Description

Use Cases

Technical Implementation

Request Headers

Request Body

Example Request

Response Parameters

Example Successful Response

Possible Error Responses

Integration Best Practices

Code Samples