Skip to content

Published services, current details, and clear categories.

Explore APIs

Mobile to VPA API

Find the UPI handle held against a mobile number your customer gave you. You can then address payouts and refunds without asking for bank details again.

MOBILEUPI ID
Request and response

You confirm the required fields and consent steps with us during onboarding.

You send

Customer-provided mobile number, collected with consent

You receive

The UPI handle or handles available against the number, with any name information the source provides

Coverage
India. UPI handles registered against a mobile number, where a record is available
Typical users
Payout, onboarding and claims teams across lending, insurance, marketplaces, logistics and gig platforms
Coverage note
Available fields vary by data source and record; a number may return one handle, several, or none
Overview

What you can do with the Mobile to VPA API

A mobile to VPA lookup starts from a mobile number the customer has already given you and returns the UPI handle available against it. If you hold that number on a policy file, a seller record or a rider roster, the lookup removes a typing step that is easy to get wrong. As an API, the lookup runs inside the system that needs it: an onboarding form, a claims queue or a scheduled payout run. The fields returned vary by data source and by record, and a number may resolve to one handle, to several, or to none at all. Use it with the customer's consent, for a stated payment purpose. Pair it with a name confirmation where the amount or the risk profile warrants a closer look.

  • Works from the number on your roster

    Most customers register a UPI handle against the mobile number attached to their bank account. A number you captured at onboarding can therefore become a payout destination, with no further request to the customer.

  • The handle, and any name the source holds

    The response carries the UPI handle or handles associated with the submitted number, together with any name information the source makes available. The exact fields returned vary by data source and by record, and some numbers return no handle at all.

  • One less handle to type by hand

    Handles collected by hand pass through forms, support calls and spreadsheets. Each step can introduce a character that later shows up as a failed or misdirected transfer. A lookup removes that step.

  • Runs on screen or in a batch

    The lookup can run while the customer is on screen, so a wrong number can be corrected. It can also run as part of a batch assembled ahead of a scheduled disbursement cycle.

How it works

The five-step Mobile to VPA API workflow

Our team walks you through the exact request and response for this service during onboarding.

Step 1

Collect the number under a payment notice

Capture the customer's mobile number for a stated payment purpose, with a notice that explains what the lookup is for.

Step 2

Send the number to the VPA lookup

Your application sends the mobile number through the API from the onboarding form, claims queue or payout run that needs the destination.

Step 3

Read the handle that comes back

The response carries the UPI handle or handles available against that number, with any name information the source provides.

Step 4

Let the customer confirm or change it

Show the resolved handle for confirmation where the journey allows it, and let the customer override it or supply a different one.

Step 5

Store the handle for the payout run

Keep the confirmed handle against the customer record with a timestamp, and refresh it when a payout fails or the customer changes their number.

Industries

Where teams use Mobile to VPA API

These sectors build the check into a decision they already make.

  • Lending

    Address a disbursement or refund using the handle resolved from the borrower's number

  • Insurance

    Prepare claim settlement and premium refund payouts from the number on the policy file

  • Marketplaces

    Resolve seller settlement and buyer refund destinations captured at registration

  • Logistics and fleet

    Pay riders and last-mile partners without collecting full bank details

  • Gig and staffing platforms

    Build frequent wage payout files from the roster already maintained

  • Telecom and travel

    Direct channel commissions and cancellation refunds to a resolved handle

What Is a Mobile to VPA Lookup?

A Virtual Payment Address, or VPA, is the readable UPI handle a person shares in place of an account number and IFSC code. A mobile to VPA lookup takes a mobile number and returns the handle available against it. You can then address a payout or a collection request from a detail already on file.

Most people in India register their UPI handle against the mobile number attached to their bank account. That makes the number a practical starting point for a business that already holds one. Examples are a rider on a delivery roster, a policyholder on a claim file, and a seller on a marketplace.

Resolving a UPI Handle Through an API

Collecting handles by hand does not scale. Someone has to ask, wait, chase the customers who never reply, and key the answer in. A payout cycle then moves at the pace of the slowest of those conversations.

An API moves the lookup into the software that already holds the number. An onboarding form, a claims queue or a scheduled payout run can request the handle at the point it is needed. It then stores the result against the customer record.

The Mobile Number the Lookup Starts From

The request begins with a mobile number the customer has already given for this purpose. That is the number on the loan file, the policy, the seller record or the rider roster.

That is the point of the service: no new field on the form, and no second conversation to arrange.

It is also the limit. The lookup can only speak to the number you send. A customer who banks on a different number, or whose number you captured years ago, may not resolve at all.

Available fields vary by data source and by record. Where a number is old, confirming it with the customer is worth more than re-running the lookup.

Where Mobile to VPA Fits Across Industries

  • Lending and NBFCs can address a disbursement, or a refund of an excess collection, to a handle resolved from the borrower's registered number. You do not have to interrupt the journey to ask for it.
  • Insurance teams settling a claim or refunding a premium can prepare the destination from the number already on the policy file.
  • Fintech and payment platforms can prefill a handle on the beneficiary-add screen. The customer then confirms a value instead of composing one.
  • Marketplaces hold a registration number for every seller and buyer, usually more current than payout details collected once and never revisited.
  • Logistics and fleet operators can turn a roster of numbers into a payout file, instead of chasing partners who spend their working day on the road.
  • Staffing and gig platforms running frequent wage payouts can build the payout file from the roster they already maintain.
  • Telecom and travel businesses pay distributors, agents and cancelled bookings from records built for contact, not payment. The number is the field those records reliably carry.

Each of these asks the same thing: where should this payment go, and can we address it without another round trip to the customer?

A UPI Handle or Full Bank Details?

You can address a payout to a UPI handle, or to an account number and IFSC code collected from the customer and checked separately. The lookup opens the first route from a number already on file. It suits long rosters of small, frequent payments, where re-collecting bank details is what holds everything up.

The second route still earns its place on large or one-off disbursements. On either route, most teams add a name confirmation against the destination before release. A resolved handle gives you the destination, and your own checks still decide whether to pay it.

Inline or Batch: Placing the VPA Lookup

Decide early whether the lookup runs inline, while the customer is on screen, or in a batch ahead of a payout cycle. Inline gives the customer a chance to correct a wrong number. Batch suits scheduled disbursement runs where the file is assembled in advance.

Whichever you choose, settle what happens to a record with no handle. Hold it where an operator can see and act on it, out of the payout file. Keep the resolved handle editable for a customer who supplies one directly.

The number you send and the handle that comes back are personal data about the same person, and the lookup is what joins them. Say what the lookup is for at the point you collect the number, and set a retention period against that purpose.

A clear notice, a lawful basis and limited retention are what India's data-protection framework expects.

Log who ran a lookup and why, and restrict access to the staff whose work requires it. Do not collect resolved handles into a directory for reuse outside the journey the customer agreed to. Which lookups are available to you depends on the selected service contract.

FAQ

Common questions

What teams ask before they integrate Mobile to VPA API.

An interface that takes a customer-provided mobile number and returns the UPI Virtual Payment Address available against it. A business can then address a payout or a collection request from a number it already holds, instead of collecting bank details separately.

Get started

Add Mobile to VPA API to your workflow

Tell us how you plan to use it. Our team sets up API access, agrees your pricing and takes you through onboarding.