Recharge Transaction (GET)

Initiate a mobile recharge transaction via a GET request. The system parses inputs from the query parameters, processes the request with the upstream provider, manages wallet debits/refunds, and awards commission.

Endpoint: /v1/recharge/transaction
Method: GET
Authentication: Required (Basic Auth via Header or Query Parameter)

Query Parameters

Parameter	Type	Required	Description
`operator_id`	string	Yes	The unique identifier of the recharge operator (e.g. `1`).
`number`	string	Yes	The target mobile number to recharge (e.g. `9876543210`).
`amount`	float	Yes	The recharge amount in INR.
`p_order_id`	string	Yes	A unique transaction identifier generated by you (the partner) to prevent duplicate submissions.
`authorization`	string	Optional	Can be used to authenticate the request if the `Authorization` header is not present (e.g. `Basic <base64_credentials>`).

URL Example

GET https://api.originbills.in/v1/recharge/transaction?operator_id=1&number=9876543210&amount=100.00&p_order_id=PARTNER_TXN_998877&authorization=Basic%20cGJfbGl2ZV9leGFtcGxlMTIzOnNrX2xpdmVfZXhhbXBsZTk4Nw==

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": "197.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-07-10 18:43:47"
  }
}

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

Query Parameters

URL Example

Response Scenarios

1. Success Response (200 OK)

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)

​Query Parameters

​URL Example

​Response Scenarios

​1. Success Response (200 OK)

​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)

Query Parameters

URL Example

Response Scenarios

1. Success Response (200 OK)

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)