Recharge Transaction (POST)

Initiate a mobile recharge transaction. The system automatically processes the request with the upstream provider, manages wallet debits/refunds, and calculates commission.

Endpoint: /v1/recharge/transaction
Method: POST
Content-Type: application/json
Authentication: Required (Basic Auth)

Request Body Parameters

Field	Type	Required	Description
`operator_id`	string	Yes	The unique identifier of the recharge operator (e.g. `"1"`, `"2"`).
`number`	string	Yes	The target mobile number to recharge (e.g. `"9876543210"`).
`amount`	float	Yes	The recharge amount in INR (must be greater than 0).
`p_order_id`	string	Yes	A unique transaction identifier generated by you (the client/partner) to identify this order.

Request Body Example

{
  "operator_id": "1",
  "number": "9876543210",
  "amount": 100.00,
  "p_order_id": "PARTNER_TXN_998877"
}

Response Scenarios

Depending on the response from the telecom provider, the transaction will settle into one of three statuses: success, pending, or failed.

1. Success Response (200 OK)

Returned when the recharge is successfully processed by the telecom network.

{
  "success": true,
  "status": "success",
  "orderId": "PARTNER_TXN_998877",
  "operatorRefId": "REF1234567890",
  "message": "Recharge completed successfully",
  "data": {
    "number": "1234567890",
    "amount": 199,
    "operator_id": "43",
    "operator_name": "Jio",
    "debit_amount": "97.50",
    "opening_bal": "15450.75",
    "closing_bal": "15353.25",
    "order_id": "7662d558-86d1-4d37-8e68-07e052445b23",
    "partner_order_id": "PARTNER_TXN_998877",
    "operator_ref_id": "REF1234567890",
    "commission_amount": "2.50",
    "timestamp": "2026-06-10 15:43:47"
  }
}

Response Data Fields:

Field	Type	Description
`success`	boolean	Overall transaction outcome flag.
`status`	string	Transaction status (`success`).
`orderId`	string	The partner order ID passed in the request.
`operatorRefId`	string	Reference ID returned by the telecom operator.
`data.debit_amount`	string	Actual amount debited from your wallet after adjusting for the commission earned.
`data.opening_bal`	string	Wallet balance before the transaction.
`data.closing_bal`	string	Wallet balance after the transaction and commission payout.
`data.order_id`	string	Internal system transaction UUID.
`data.commission_amount`	string	Commission earned on the transaction.
`data.timestamp`	string	Execution time in Indian Standard Time (IST).

2. Pending Response (200 OK)

Returned when the provider request times out or is held in queue. Check the status later using the Recharge Status API.

{
  "success": true,
  "status": "pending",
  "orderId": "PARTNER_TXN_998877",
  "message": "Recharge is pending processing"
}

3. Failed Response (400 Bad Request)

Returned when the recharge fails. Any debited funds will be automatically refunded to your wallet.

{
  "success": false,
  "status": "failed",
  "message": "Transaction failed from provider"
}

Validation & Business Errors

Insufficient Balance (400 Bad Request)

{
  "error": "Insufficient balance"
}

Invalid Parameters (400 Bad Request)

{
  "error": "Invalid request parameters"
}

Unknown Operator (400 Bad Request)

{
  "error": "Biller not found or inactive"
}

Getting Started

Balance API

Recharge API

BBPS API

Request Body Parameters

Request Body Example

Response Scenarios

1. Success Response (200 OK)

Response Data Fields:

2. Pending Response (200 OK)

3. Failed Response (400 Bad Request)

Validation & Business Errors

Insufficient Balance (400 Bad Request)

Invalid Parameters (400 Bad Request)

Unknown Operator (400 Bad Request)

​Request Body Parameters

​Request Body Example

​Response Scenarios

​1. Success Response (200 OK)

​Response Data Fields:

​2. Pending Response (200 OK)

​3. Failed Response (400 Bad Request)

​Validation & Business Errors

​Insufficient Balance (400 Bad Request)

​Invalid Parameters (400 Bad Request)

​Unknown Operator (400 Bad Request)

Request Body Parameters

Request Body Example

Response Scenarios

1. Success Response (200 OK)

Response Data Fields:

2. Pending Response (200 OK)

3. Failed Response (400 Bad Request)

Validation & Business Errors

Insufficient Balance (400 Bad Request)

Invalid Parameters (400 Bad Request)

Unknown Operator (400 Bad Request)