VPA Verification

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…

📘

Authenticated verification

Send your issued secret from your registered backend IP. The partner account, KYC, wallet, API access and verification service must be active.

Verify a Virtual Payment Address (VPA) and retrieve the beneficiary details returned by the verification provider.

Endpoint

POST https://pay2new.in/apis/v1/verification/vpa

Authentication

Send your Pay2New-issued secret header. Requests must originate from an IP address registered on the partner account. The partner account, KYC, wallet, API access, and verification service must be active.

Send JSON with Content-Type: application/json.

Request fields

FieldTypeRequiredDescription
vpastringYesVPA to verify.
latitudedecimal stringYesCustomer/outlet latitude.
longitudedecimal stringYesCustomer/outlet longitude.
terms_agreestringYesY; send only after obtaining customer consent.
request_idstringYesYour unique reference, at least 8 characters.
ipstringYesValid customer/outlet IPv4 address. This does not replace source-IP registration.
product_codenumericNoThe service uses product code 282; the server selects this code.

Example request

All values below are illustrative. Replace them with the consenting customer's details and your issued credential.

curl --request POST \
  --url 'https://pay2new.in/apis/v1/verification/vpa' \
  --header 'secret: YOUR_PAY2NEW_SECRET' \
  --header 'Content-Type: application/json' \
  --header 'Accept: application/json' \
  --data '{
    "vpa": "sample-customer@upi",
    "latitude": "19.0760",
    "longitude": "72.8777",
    "terms_agree": "Y",
    "request_id": "VPA202609260001",
    "ip": "203.0.113.10"
  }'

Response

Read the JSON status and message, even when HTTP transport succeeds. A validation failure returns status: 2, message: "Invalid Parameters", and an errors object. Missing or invalid JSON also returns an application failure.

FieldTypeDescription
statusinteger1: successful verification; 2: failure; 3: unresolved processing outcome.
messagestringResult or failure description.
order_idstringPay2New transaction reference, when created.
request_idstringYour request reference, when a transaction is created.
txn_valuestringTransaction value formatted to two decimal places; grouping separators may be present.
balancestringFormatted wallet balance; grouping separators may be present.
api_idinteger or numeric stringProvider identifier when returned.
beneobject or nullProvider beneficiary details, when available.
bank_referencestring or nullProvider transaction reference, when available.
errorsobjectField validation messages on validation failure.

Not every response contains transaction or beneficiary fields. Charges depend on your configured package. For an unresolved outcome, retain the references and reconcile before submitting another chargeable request.

{
  "status": 2,
  "message": "Invalid Parameters",
  "errors": {
    "request_id": "The request_id field must be at least 8 characters in length."
  }
}

🚧

Reconcile unresolved results

A timeout or unresolved result does not confirm failure. Retain your request_id and any returned order_id and check the outcome before submitting another chargeable request.

Body Params
string
required

VPA to verify

string
required

Decimal latitude

string
required

Decimal longitude

string
required

Customer consent: Y

string
required

Unique reference, minimum 8 characters

string
required

Valid IPv4 address

int32

Server uses product code 282.

Headers
string
required

Pay2New-issued API secret; registered source IP required.

Response

Language
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json