| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Verify a bank account and IFSC and retrieve the available beneficiary information.
Endpoint
POST https://pay2new.in/apis/v1/verification/bankAccount
Headers
| Header | Required | Value / description |
|---|---|---|
secret | Yes | Your Pay2New API secret. Keep it on your server. |
Content-Type | Yes for JSON requests | application/json |
Accept | Optional | application/json |
Authentication
Use an active Pay2New partner account with verified KYC, an active wallet and API access. Send requests from your registered IP address. Enable the relevant service where applicable; offer services may also require an active plan.
Request body
| Field | Type | Required | Description |
|---|---|---|---|
account_number | string | Yes | Bank account number. Send as a string to preserve leading zeroes. |
ifsc | string | Yes | Bank IFSC. Required to verify the account. |
latitude | decimal string | Yes | Customer/outlet latitude as a decimal value. |
longitude | decimal string | Yes | Customer/outlet longitude as a decimal value. |
terms_agree | string | Yes | Customer consent. Send Y. |
request_id | string | Yes | Unique client reference for this request. Store it for reconciliation and support. Minimum 8 characters. |
product_code | string | No | Optional; the verification product is selected automatically. You can omit this field. Use numeric characters. |
ip | string | Yes | End-user IPv4 address. |
Request example
Illustrative values
All identifiers, identity data, amounts and IP addresses in these examples are synthetic. Replace the secret, product/customer references and sample inputs with the values for your integration before sending a request.
curl --request POST \
--url 'https://pay2new.in/apis/v1/verification/bankAccount' \
--header 'secret: <YOUR_PAY2NEW_SECRET>' \
--header 'Content-Type: application/json' \
--data '{
"account_number": "1234567890",
"ifsc": "ABCD0123456",
"latitude": "19.0760",
"longitude": "72.8777",
"terms_agree": "Y",
"request_id": "EXAMPLE202609260001",
"ip": "203.0.113.10"
}'
Response fields
| Field | Type | Description |
|---|---|---|
status | integer | 1: successful operation; 2: failed/rejected operation; 3: pending or indeterminate where returned. |
message | string | Human-readable result or error message. |
order_id | string | Pay2New transaction/order reference. Store it for reconciliation. |
txn_value | string | Verification transaction value/charge as a formatted string. |
balance | string | Wallet balance as a formatted string; may contain commas. |
request_id | string | Client request reference associated with the operation. |
api_id | number / string | Provider identifier when returned. It is not needed to initiate verification. |
bene | object / null | Beneficiary details when available; can be absent or null. |
bank_reference | string / null | Bank/provider reference when available; can be absent or null. |
Response example
{
"status": 1,
"message": "Transaction Successful!",
"order_id": "P2N_EXAMPLE_ORDER",
"txn_value": "2.00",
"balance": "1,000.00",
"request_id": "EXAMPLE202609260001",
"api_id": "EXAMPLE_PROVIDER",
"bene": {
"name": "SAMPLE CUSTOMER"
},
"bank_reference": "EXAMPLE_REFERENCE"
}
Integration notes
Send IFSC and consent along with the account number. The verification product is selected automatically, so product_code can be omitted. A repeated verification request can create a new chargeable verification; do not assume duplicate request IDs are idempotent for this operation.
Integration notes
Formatted monetary fields are strings with two decimal places and may use Indian comma grouping, for example 1,23,456.78. Remove grouping separators before numeric calculations. Illustrative balances or charges are not pricing commitments.
Errors
Application failures return status: 2 and a message. Invalid fields can also be identified in an errors object. Authentication, IP registration, service access and product availability can prevent processing. Other response fields may be absent when processing fails before a transaction is created. Evaluate the JSON result even when the HTTP request completes successfully. Preserve your request and order references when an outcome is pending or indeterminate.
{
"status": 2,
"message": "Invalid Parameters",
"errors": {
"account_number": "Illustrative field validation message"
}
}