Mobile To Multiple UPI

Endpoint Overview

POST /api/v1/bank-verification/mobile-to-multiple-upi

Description

This API endpoint allows you to retrieve all UPI IDs (Unified Payments Interface identifiers) associated with a specific mobile number. It provides a secure and efficient way to verify and discover multiple UPI payment handles linked to a single mobile number, enabling seamless payment routing and verification in financial applications.

Key Benefits

Retrieve multiple UPI IDs linked to a single mobile number in one API call

Verify the existence and validity of UPI handles before initiating transactions

Reduce payment failures by identifying the correct UPI IDs for a recipient

Enhance user experience by providing payment method options without manual entry

Use Cases

Financial Services

E-commerce

Banking

Verify recipient UPI IDs before processing money transfers

Offer users a choice of their registered UPI handles during checkout

Validate customer identity by cross-referencing mobile and UPI information

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 to query for associated UPI IDs

Example Request

{
    "mobile_number": "8079012345"
}

Process Response

Response Parameters

Parameter	Type	Description
data	Object	Container for the response data
data.client_id	String	Unique identifier for the API request
data.mobile_number	String	The mobile number that was queried
data.name	String	Full name of the UPI user
data.upi_id	Array	List of UPI IDs associated with the mobile number
status_code	Integer	HTTP status code of the response
success	Boolean	Indicates if the request was successful
message	String	Human-readable status message
message_code	String	Machine-readable status code

Example Successful Response

{
    "data": {
        "client_id": "mobile_to_multiple_upi_SywuvzINnwnxauTksmqJ",
        "mobile_number": "8079012345",
        "name": "Mr. Vishal Rathore",
        "upi_id": [
            "8079012345@apl",
            "8079012345@paytm"
        ]
    },
    "status_code": 200,
    "success": true,
    "message": "Success",
    "message_code": "success"
}

Possible Error Responses

Invalid Mobile Number

Authentication Error

Server Error

{
    "errors": {
        "mobile_number": "Mobile Number Mobile should not start with 0 and should be of length 10"
    },
    "message": "Input payload validation failed"
}

The mobile number provided is not in a valid format. Ensure it contains only digits and is of the correct length.

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

Display all available UPI options to users when multiple IDs are returned

Implement proper loading states while waiting for API responses

Cache results temporarily to improve performance for repeated lookups

Provide clear error messages to users when UPI verification fails

Code Samples

cURL

Python

Node.js

Related APIs

Bank Account Verification API - Verify bank account details using account number and IFSC

UPI ID Verification API - Verify the validity of a single UPI ID

Mobile Number Verification API - Verify mobile number ownership through OTP

Compliance and Legal Considerations

When using this API, ensure you have proper consent from users before querying their mobile numbers. This API handles sensitive financial information and must be used in compliance with data protection regulations such as GDPR and local financial regulations. Ensure your privacy policy clearly discloses how this data is used and stored.

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

{ "data": { "client_id": "mobile_to_multiple_upi_SywuvzINnwnxauTksmqJ", "mobile_number": "8079012345", "name": "Mr. Vishal Rathore", "upi_id": [ "8079012345@apl", "8079012345@paytm" ] }, "status_code": 200, "success": true, "message": "Success", "message_code": "success" }

Mobile To Multiple UPI

Mobile To Multiple UPI#

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 Multiple UPI

Description

Use Cases

Technical Implementation

Request Headers

Request Body

Example Request

Response Parameters

Example Successful Response

Possible Error Responses

Integration Best Practices

Code Samples