---
title: "UPI ID (VPA) Verification API Reference"
description: "Validate a UPI Virtual Payment Address (VPA) and retrieve the registered payee name and mobile number in real time."
canonical: "https://eps.eko.in/docs/upi-validate-vpa"
---


> **Canonical URL:** https://eps.eko.in/docs/upi-validate-vpa
> This is a machine-readable Markdown version of the page for AI agents and LLMs. The primary (HTML) version lives at the canonical URL above.

# UPI ID (VPA) Verification API Reference

`POST https://staging.eko.in/ekoapi/v3/customer/payment/upi/validate-vpa`

Validate a UPI Virtual Payment Address (VPA) and retrieve the registered payee name and mobile number in real time.

Confirms whether a UPI ID (VPA) is active and returns the verified recipient name and registered mobile number. Use this before initiating any UPI transfer to reduce wrong-payee failures and payment fraud.

> View product & pricing details: [UPI ID (VPA) Verification](https://eps.eko.in/products/upi-verification-api.md)

## Body parameters

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| initiator_id | string | yes | Registered mobile number of the API user (see Platform Credentials). e.g. 9962981729 |
| user_code | string | yes | User code of the retailer/agent the service is run for. e.g. 20810200 |
| client_ref_id | string | no | Unique reference id per API call, generated by your system. e.g. REQ-20260101-001 |
| customer_vpa | string | yes | The UPI Virtual Payment Address (VPA / UPI ID) to validate, e.g. rajesh.kumar@okicici. e.g. rajesh.kumar@okicici |
| recipient_mobile | string | yes | Mobile number of the recipient linked to the VPA, used for additional verification. e.g. 9876543210 |
| name | string | yes | Name of the recipient as expected — returned for match validation against the bank-verified payee name. e.g. Rajesh Kumar |
| latlong | string | yes | Geo-coordinates of the request origination point (latitude,longitude). e.g. 28.6139,77.2090 |

## Headers

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| developer_key | string | yes | Static API key issued to your account after KYC. |
| secret-key | string | yes | Dynamic per-request signature: base64(HMAC-SHA256(timestamp, base64(access_key))). |
| secret-key-timestamp | string | yes | Current time in milliseconds since UNIX epoch, used to compute secret-key. Must match server time. |
| content-type | string | yes | application/json e.g. application/json |

## Response

⭐ marks fields highlighted as verifiable.

| Field | Type | Description |
| --- | --- | --- |
| status | number | Primary success indicator (0 = success). |
| message | string | Human-readable response / error message. |
| response_status_id | number | Granular status id; see the shared error-codes table. |
| response_type_id | number | A unique id for every possible response shape (success or error) — useful for client logic branching and analytics. |
| data | object | API-specific response payload. |
| data.vpa ⭐ | string | The validated UPI Virtual Payment Address (VPA / UPI ID) exactly as registered. |
| data.valid ⭐ | boolean | Whether the VPA is active and valid. true = valid VPA; false = invalid or inactive. |
| data.recipient_name ⭐ | string | Verified payee name as returned by the UPI network — use this for name-match checks before payment. |
| data.mobile_number ⭐ | string | Registered mobile number linked to the VPA. |
| data.transaction_id | string | Unique transaction / verification request ID generated by Eko's system for audit and support reference. |

## Example request

```json
{
  "initiator_id": "9962981729",
  "user_code": "20810200",
  "client_ref_id": "REQ-20260101-001",
  "customer_vpa": "rajesh.kumar@okicici",
  "recipient_mobile": "9876543210",
  "name": "Rajesh Kumar",
  "latlong": "28.6139,77.2090"
}
```

## Example response

```json
{
  "status": 0,
  "response_status_id": 0,
  "message": "VPA validation successful",
  "response_type_id": 1388,
  "data": {
    "vpa": "rajesh.kumar@okicici",
    "valid": true,
    "recipient_name": "Rajesh Kumar",
    "mobile_number": "9876543210",
    "transaction_id": "3560508954"
  }
}
```

## Error scenarios

| Status | Scenario |
| --- | --- |
| 200 | Invalid or non-existent VPA |
| 403 | Authentication failure — wrong secret-key or stale timestamp |
| 200 | User (retailer) not found |