What is a recharge API and how does it work?
A plain-language walk through a recharge request, from your server to the operator and back, including the three states you must handle.
Add mobile recharge to your app, website or software with one REST integration, status checks and callbacks.
A recharge API lets your own platform send prepaid mobile recharge requests to A1 Top Up Services and receive the result, without you managing operator connections yourself. Your developers integrate once and your users recharge from your app, portal or WhatsApp flow.
Your server sends a recharge request with the mobile number, operator, circle and amount. We return a reference straight away and the final status when the operator responds. If a request stays pending, you can check its status by reference or wait for the callback.
Operator and circle coverage, limits and commission depend on the account you sign up for. Your account manager confirms these before you go live.
JSON requests over HTTPS, with documentation and sample requests for the common flows.
Look up any transaction by reference, or receive the result on your callback URL.
Recharges are funded from your account balance, with a balance-check endpoint.
API credentials are issued per account, with restrictions your team can agree with us.
Skip building operator connectivity. Focus on your app and your customers.
Every request has a reference and a status you can show to your users or support team.
Our team answers integration questions while you build and test.
Tell us about your business and expected volume.
Send sample requests and handle each response state.
Receive production credentials and start with a small volume.
Mobile apps where users top up their own or family numbers.
Web portals where retailers recharge for walk-in customers.
Messaging flows that collect a number and amount, then call the API.
A1 Top Up Services Private Limited provides recharge APIs, utility bill payment APIs, recharge software and white label solutions for businesses that want to offer recharge and bill payment services.
A sandbox is provided during onboarding so your developers can test requests, responses and callbacks before going live. Ask for sandbox access when you request API access.
A pending status means the final result has not yet arrived from the operator. You can check the status by reference, or wait for the callback to your server. Your integration should treat pending as an in-progress state, not as a failure.
A plain-language walk through a recharge request, from your server to the operator and back, including the three states you must handle.
Pending is a normal state, not an error. Here is how to design status checks, callbacks and customer messages around it.
Request API access and test recharge, status and callback requests before any real money moves.