Process top-ups via Mobile Recharge API

1. Platform Overview & Business Architecture

The Mobile Recharge API is a high-speed telecommunications integration gateway. Interfacing with individual mobile networks, DTH providers, and utility billers to manage top-ups, dynamic plan lists, and transaction commissions is a significant development bottleneck. This API solves this by offering a standardized, real-time middleware layer that coordinates operator APIs, billing balances, and commissions.

Using our API, developers can check active plans and validity for any mobile number; query available top-up amounts; execute instant recharges; track operator transaction reference codes; and manage reseller commissions.

Security is critical for payment networks. The API uses secure OAuth2 authentication tokens and HTTPS/TLS 1.3 encryption to protect user identities and transaction details in compliance with data privacy regulations.

2. Mobile Recharge Features

3. API Reference & Technical Endpoints

The API operates over secure HTTPS. Below are the request and response configurations for executing mobile recharges.

{
  "operator_code": "JIO",
  "circle_code": "KOLKATA",
  "mobile": "9876543210",
  "amount": 299.00,
  "client_reference_id": "cli_txn_98273"
}

{
  "status": "success",
  "recharge_id": "rec_89271ac092",
  "operator_reference_id": "OPJIO89172839201",
  "mobile": "9876543210",
  "amount": 299.00,
  "commission_earned": 8.97,
  "balance_remaining": 15430.50
}

4. Dynamic Plan Verification & Fetch Flow

To prevent incorrect recharges, our gateway validates plan details dynamically:

How it works:

• Operator Lookups: When a user enters their mobile number, the API performs an operator and circle lookup to determine the correct network provider.
• Plan Queries: The engine queries active catalog databases to list valid talktime and data packs for that operator.
• Price Validations: If the client selects a plan, the system verifies the recharge amount to prevent operator rejections.

5. Security, Wallet Vaulting & Transaction Safeties

Processing transaction recharges requires maintaining high security and reliability standards:

• Double-Spend Prevention: Our database uses transaction locks to prevent double-spending or duplicate debit attempts.
• Encrypted Wallets: Reseller wallet balances are encrypted and stored in secure database tables, protected from unauthorized changes.
• API Endpoint Security: Requests are signed with client credentials. Tunnels use HTTPS/TLS 1.3 to protect transaction payloads.
• Failover Routes: If an operator's primary route experiences downtime, the system automatically redirects requests through backup routes.

6. Enterprise Use Cases

7. FAQ & Troubleshooting Guide