JustSwitch
API Access
Recharge & Bill Payments

Recharge Status Check API

GET /api/v1/mobile-recharge/recharge-status-check

Last recharge transaction ka status check.

Last recharge transaction ka status check.

  • Real-time recharge for mobile recharge data with sub-300ms median latency
  • Production-grade REST JSON with sandbox & webhook support
  • UIDAI / NPCI / MCA aligned partner routing where applicable
  • Audit logs, idempotency keys & enterprise SLA on JustSwitch
Get API keys Developer docs
Latency
400–800 ms
Uptime SLA
99.9%
Format
REST / JSON
Sandbox
Included

What is Recharge Status Check?

Last recharge transaction ka status check.

Every request is authenticated with API keys, logged for audit, and routed through regulated partner rails where required. Responses follow a consistent `{ ok, data, message }` envelope so you can ship once and reuse the same error-handling patterns across all JustSwitch endpoints.

Recharge APIs return operator, circle, plan metadata, and live status — ideal for retailer apps, super-apps, and white-label distributors.

Developers choose JustSwitch for Recharge Status Check because we aggregate multiple upstream providers behind one contract, one wallet settlement, and one support desk — so you launch faster while your compliance team retains full audit visibility through dashboard logs and exportable reports.

Retail POS Super apps Distributors Fintech wallets

Technical specification

Endpoint details for Recharge Status Check integration on JustSwitch.

GET /api/v1/mobile-recharge/recharge-status-check
Protocol HTTPS REST / JSON
Authentication Bearer API Key + IP allow-list
Sandbox Available — no live debits
Median latency 400–800 ms
Rate limits Burst-friendly — contact for enterprise tiers
Webhooks Yes — signed callbacks
Idempotency Supported via idempotency_key
API slug recharge-status-check

Request parameters

reference_id string required

Your unique transaction or session reference for reconciliation

consent boolean required

User consent flag — required for regulated KYC / verification flows

amount number required

Recharge amount in INR

operator string required

Operator code from lookup API

Response fields

status string

success | pending | failed

reference_id string

Echo of your request reference

verified_at datetime

ISO-8601 timestamp of completion

txn_id string

JustSwitch transaction identifier

utr string

Bank / NPCI reference when available

message string

Human-readable result or error detail

Key features

REST + JSON

HTTPS POST/GET with UTF-8 JSON bodies and predictable status codes.

Sandbox mode

Test end-to-end without debiting wallet or hitting live rails.

Webhooks

Async callbacks for pending states — payments, recharge, KYC, payouts.

Dashboard logs

Searchable request history with filters for support & audits.

Low latency

Median sub-300 ms for verification-class endpoints in production.

Enterprise SLA

99.9% uptime target with redundant routing and monitoring.

Who uses Recharge Status Check?

Re

Retailer apps

POS recharge & bill pay with commission tracking.

Su

Super apps

Embed utilities inside loyalty & wallet experiences.

Fi

Fintech wallets

Cross-sell bill payments to improve retention.

B2

B2B distributors

White-label APIs for downstream agents.

How it works

  1. 01

    Obtain sandbox keys from the JustSwitch developer console.

  2. 02

    POST input identifiers; handle validation errors in-line.

  3. 03

    Map response fields into your workflow & go live with production keys.

API reference

Request & response specification

Integrate Recharge Status Check through the JustSwitch REST API — parameters and sample JSON responses below.

Endpoint

POST https://console.justswitch.in/api/v1/mobile-recharge/recharge-status-check

Content-Type

application/json

Developer console

Get API keys on console.justswitch.in →

Request headers

Header Type Description
Authorization required string Bearer token from your JustSwitch console API credentials
Content-Type required string application/json

Request body (JSON)

mobile string required

10-digit mobile or subscriber id

Response examples

Sample JSON from the JustSwitch API for this service.

Success HTTP 200 
{
    "ok": true,
    "message": "Done Successfully",
    "data": {
        "service": "Recharge Status Check API"
    }
}
Failed / validation HTTP 422 
{
    "ok": false,
    "message": "Please check with all required parameters",
    "data": {
        "Errorcode": 104,
        "Status": "Failed",
        "Message": "Please check with all required parameters"
    }
}

Sample integration

Illustrative JSON for Recharge Status Check — see developer docs for live schemas.

GET Request
{
    "mobile": "9876543210",
    "operator": "jio",
    "circle": "delhi",
    "amount": 299
}
200 Response
{
    "ok": true,
    "message": "Success",
    "data": {
        "status": "success",
        "reference_id": "JS-1QOQHYZP",
        "verified_at": "2026-06-26T10:36:36+00:00"
    }
}

Business benefits

  • Reduce manual ops cost by up to 70% on verification-heavy journeys
  • Improve conversion with inline validation instead of offline turnaround
  • Single contract & settlement across 200+ Indian fintech APIs
  • Audit-ready logs exported from the admin console
  • Dedicated solutions engineering for enterprise rollouts

Frequently asked questions

What is Recharge Status Check used for?

It automates Prepaid / Postpaid workflows so your application can verify or transact in real time without building direct integrations with multiple upstream providers.

How do I integrate Recharge Status Check in my app?

Sign up on JustSwitch, obtain sandbox API keys, call the REST endpoint with JSON body, handle the unified response envelope, then switch to production keys after UAT sign-off.

How do I authenticate requests?

Use Bearer API keys from the JustSwitch dashboard. Sandbox and production keys are separated; rotate keys anytime without downtime.

Is there a sandbox for testing?

Yes — every API supports sandbox mode with simulated responses so engineering, QA, and compliance can sign off before go-live.

What about webhooks and async status?

Long-running operations (payments, recharge, some KYC steps) emit webhooks to your HTTPS endpoint with signed payloads for replay protection.

Is Recharge Status Check compliant for regulated use in India?

JustSwitch routes requests through authorised AUA/KUA, NPCI, MCA and partner networks. Your legal team should map consent, data retention and licence obligations to your use case.

Related Prepaid / Postpaid APIs

Explore more endpoints in the same verification category.

Mobile Plan Fetch

The Mobile Plan Fetch from JustSwitch lets product teams fetch mobile numbers in real time through a single REST integration. Designed for t...

View API details →

Mobile Recharge Plan

The Mobile Recharge Plan from JustSwitch lets product teams recharge mobile numbers in real time through a single REST integration. Designed...

View API details →

Operator & Circle Check

The Operator & Circle Check from JustSwitch lets product teams integrate mobile recharge data in real time through a single REST integration...

View API details →

Operator List

The Operator List from JustSwitch lets product teams integrate mobile recharge data in real time through a single REST integration. Designed...

View API details →

Operator Plan Fetch

The Operator Plan Fetch from JustSwitch lets product teams fetch mobile recharge data in real time through a single REST integration. Design...

View API details →

R-OFFER Check

The R-OFFER Check from JustSwitch lets product teams integrate mobile recharge data in real time through a single REST integration. Designed...

View API details →

Start building with Recharge Status Check

Sandbox keys in minutes. Production access with compliance review for regulated endpoints.

Create free account Browse Prepaid / Postpaid