Overview

The UPI Multiple Mobile Verification API enables you to fetch all UPI handles/VPAs associated with a mobile number. This is useful when customers have multiple UPI IDs linked to the same phone number.

Endpoint Details

POST /verification/upimobile_multiple

Headers

client-id: Your unique Client ID (required)
client-secret: Your unique Client Secret (required)
Content-Type: application/json (required)

Request Body

Parameter	Type	Required	Description
`consent`	string	Yes	Must be "Y" for consent
`vpa_mobile`	string	Yes	Mobile number to verify
`clientData`	object	Yes	Client reference data
`clientData.client_id`	string	Yes	Unique client identifier

Request Example

{
    "consent": "Y",
    "vpa_mobile": "9999999999",
    "clientData": {
        "client_id": "942wdq5142dxssasdx82"
    }
}

Response

Success Response (101)

{
    "status": "success",
    "statusCode": "101",
    "partner_id": "ARNPY17627619425159",
    "name": "RAKESH MITTAL",
    "vpa": "9999999999@kotak",
    "vpaList": [
        "9999999999@kotak",
        "9999999999@hdfc"
    ],
    "count": 2,
    "description": "UPI ID(s) found linked to the mobile number.",
    "accountStatus": "VALID",
    "clientData": {
        "client_id": "942wdq5142dxssasdx82",
        "mobile": "9999999999"
    },
    "message": "UPI handles fetched successfully."
}

Response Fields

Field	Type	Description
`status`	string	API call status ("success" for successful calls)
`statusCode`	string	HTTP status code ("101" for success)
`partner_id`	string	Unique partner transaction ID
`name`	string	Account holder name associated with the mobile number
`vpa`	string	Primary VPA ID linked to the mobile number
`vpaList`	array	List of all VPA IDs linked to the mobile number
`count`	number	Total number of VPAs found
`description`	string	Status description
`accountStatus`	string	Account validation status
`clientData`	object	Echo of client data from request
`message`	string	Success message

Error Responses

Invalid Mobile Number

{
    "status": "failed",
    "statusCode": "400",
    "message": "Invalid mobile number format",
    "clientData": {
        "client_id": "942wdq5142dxssasdx82"
    }
}

No VPA Found

{
    "status": "failed", 
    "statusCode": "404",
    "message": "No UPI ID found linked to the mobile number",
    "clientData": {
        "client_id": "942wdq5142dxssasdx82"
    }
}

Use Cases

Customer Onboarding: Verify customer's UPI capabilities during registration
Payment Setup: Allow customers to choose from multiple VPA options
Account Verification: Validate UPI account details before transactions
KYC Compliance: Verify customer identity through UPI account validation

Best Practices

Always obtain user consent before verification
Store the partner_id for transaction tracking
Handle cases where multiple VPAs are returned
Implement proper error handling for failed verifications
Use secure HTTPS connections for all API calls

200OK

400Bad Request

404Not Found