API Reseller
Recharge API
Operator and circle detection, live plan listings and recharge submission for every major prepaid and DTH operator, with the operator reference returned for your own dispute handling.
What you get
- Automatic operator and circle detection from a number
- Live plan catalogue per operator and circle
- Recharge submission with operator reference returned
- Explicit pending state for a delayed operator response
- Automatic reversal on a confirmed operator refusal
The contract
- Auth
- Issued credentials per key pair, over TLS. Signed requests where the rail requires it.
- Detection
- Operator and circle resolved from the number before submission.
- Catalogue
- Live plan listing per operator and circle.
- Reference
- The operator's own reference is returned for your dispute handling.
- Failure
- A confirmed operator refusal reverses automatically. A delay stays pending.
- Webhook
- Signed, with replay protection. Retried until your endpoint returns 2xx.
- Environments
- Sandbox mirrors production semantics, including failures.
FAQ
About recharge api
The recharge is pending. Should I retry it?
No. A pending recharge may still complete, and a retry against a new reference will top the number up twice. Wait for the confirmed status: a refusal reverses automatically, and a success returns the operator reference.
Why does the operator reference matter?
It is what an operator's own support will ask for when a customer disputes a top-up. We return it so the dispute can be pursued with the operator directly rather than through us, which is faster.