Authentication, request conventions, service guides, and transaction handling for Pay2New API integrations.
Integrate Pay2New wallet, recharge, bill payment, verification, onboarding, AePS, DMT, UPI ATM, and payout services using the reference pages in this developer hub.
Before you start
| Step | Requirement |
|---|---|
| 1. Activate your account | Your partner account, KYC, wallet, and API access must be active. |
| 2. Enable your services | Activate the services needed for your integration. Access is checked for the requested service. |
| 3. Register your source IP | Register the public IP address of the backend that will call Pay2New. |
| 4. Obtain your credential | Use the secret supplied for your Pay2New partner account. |
| 5. Read the endpoint contract | Use that page's exact method, path, headers, required fields, and response handling. |
Call from your backend
Keep the
secreton your server. Send it exactly as issued. The JSONipfield represents the customer/outlet IP where requested; it does not replace the registered source-IP check.
Authentication and request headers
| Header | Requirement | Value |
|---|---|---|
secret | Required | Your issued Pay2New API secret. |
Content-Type | For JSON request bodies | application/json |
Accept | Recommended | application/json |
outletId | Endpoint-specific | Pay2New customer/outlet ID where the endpoint requires it. |
Some services require outletId in a header; others require it in the JSON body. Follow the individual endpoint table. Do not substitute an upstream provider's outlet ID.
First request: wallet balance
GET https://pay2new.in/apis/v1/balance
curl --request GET \
--url 'https://pay2new.in/apis/v1/balance' \
--header 'secret: YOUR_PAY2NEW_SECRET' \
--header 'Accept: application/json'
Illustrative successful response:
{
"status": 1,
"message": "Transaction Successful!",
"balance": "1,000.00"
}
Balance and transaction-value fields formatted by the service are strings and may contain grouping separators. See Main Wallet Balance for its contract.
Understand the result
| Result | How to interpret it |
|---|---|
| HTTP response | Indicates the transport result. Always inspect the JSON body as well. |
Top-level status | Describes the requested operation. Its meaning depends on the endpoint. |
Transaction status | 1: success, 2: failure, 3: pending/unresolved where a transaction is being reported. |
| Status lookup | Top-level success means the lookup succeeded. Read order.status for the payment result. |
| DigiLocker status | Read data.status and consented documents before fetching documents. |
| DMT onboarding | OTP and next-action states are possible; follow the DMT endpoint instructions. |
| UPI ATM Generate QR | Creating a QR is not completion of the withdrawal. Check the QR/transaction status before disbursing cash. |
Do not infer payment success from HTTP 200
Authentication and validation failures can be returned as JSON application failures. Keep
request_idand any returnedorder_id. If a chargeable request times out or remains unresolved, check its status before submitting another transaction.
Choose a service
| Service | Start here |
|---|---|
| Available services and products | Services List · Product / Operator List |
| Recharge | Mobile & DTH Recharges |
| Bill payments | Bill Fetch · Bill Payment |
| Identity verification | Verification Integration Guide |
| DigiLocker | DigiLocker API overview |
| UPI ATM | UPI ATM Integration Guide |
| DMT | Introduction |
| Payouts | Bank Account · UPI Payment |
| Reconciliation | Transaction Status · Webhooks |
Integration support
Contact [email protected] for account activation, IP registration, environment/test-access details, and service support. Include the endpoint and transaction references; exclude secrets and sensitive customer data.