UPI Verification Advance
Validate a UPI ID (VPA) and fetch the registered payee name before you send or collect money.
What is the UPI Verification Advance?
The BILAPI UPI Verification API checks that a UPI ID (Virtual Payment Address) is valid and active and returns the registered payee name — so you can confirm who you are paying or collecting from before the transaction happens.
Payments apps, collection platforms, lenders and marketplaces use it to reduce wrong-VPA transfers, display the correct payee name for confidence, and cut down on payment fraud and disputes.
Send a VPA and receive the payee name and validity status as JSON in milliseconds. Billed only on a successful verification.
What the UPI Verification Advance returns
Every successful call returns a clean, predictable JSON envelope. The data object includes the fields below (exact fields vary by record availability).
| Field | Description |
|---|---|
vpa | The UPI ID / VPA that was checked. |
payee_name | The name registered against the VPA. |
is_valid | Whether the VPA is valid and active. |
name_match | Match flag when you pass an expected name to compare. |
Sample request & response
Call the endpoint with your API key in the X-Bilapi-Api-Key header. The same request shape works in the free sandbox and in production.
POST https://api.bilapi.com/v1/upi-verification-advance
X-Bilapi-Api-Key: <your_api_key>
Content-Type: application/json
{
"vpa": "rahul@okhdfcbank",
"name": "Rahul Sharma"
}{
"status_code": 200,
"success": true,
"message": "VPA verified",
"data": {
"vpa": "rahul@okhdfcbank",
"payee_name": "RAHUL SHARMA",
"is_valid": true,
"name_match": true
}
}Key features
Real-time results
Sub-300ms median response so UPI checks never slow your onboarding funnel.
Predictable JSON
The same clean response envelope as every BILAPI endpoint — parse once, reuse everywhere.
Only pay for hits
Invalid inputs and failed lookups are never charged to your wallet.
Secure by design
TLS 1.3 in transit, PII tokenisation at rest and a full audit log on every request.
One key, every API
Sandbox to production on a single key — no per-vendor contracts or integrations.
Built to scale
99.9% uptime target with bulk and webhook-friendly workflows for high volume.
Where it's used
Customer onboarding
Auto-fill and validate identity during signup to cut drop-off and manual review.
Lending & underwriting
Add a verified data point to credit decisions and reduce first-party fraud.
Fraud & risk
Flag mismatches and synthetic identities before they enter your system.
Compliance & audit
Keep a tamper-evident trail of every verification for KYC/AML reviews.
How it works
Create a free account
Sign up on the BILAPI console and get a live API key instantly.
Send a request
POST the required UPI fields to the endpoint with your API key in the header.
Get structured JSON
Receive a clean, predictable JSON response in milliseconds.
Plug into your flow
Drop the result straight into onboarding, underwriting or risk decisioning.
Frequently asked questions
What does the UPI Verification API return?
It confirms whether a UPI ID (VPA) is valid and active and returns the registered payee name, with an optional name-match flag.
What is the input?
A UPI ID / VPA such as rahul@okhdfcbank, optionally with a name to match.
Why verify a UPI ID before paying?
It prevents transfers to the wrong VPA, lets you display the correct payee name for user confidence, and reduces payment fraud and disputes.
How fast is it?
VPA verification typically completes in well under 300ms at the median, so it fits inline in a payment flow.
Do I pay for an invalid VPA?
You are billed per successful verification; failed lookups are free. A free sandbox is included for testing.
Related UPI Verification APIs
Start verifying with BILAPI
One key, a free sandbox and a predictable JSON envelope across every endpoint.