Skip to main content
  1. Home
  2. Blog
  3. Recharge API
  4. Recharge Disputes: How a Dispute API Saves Your Support Team Hours

Recharge Disputes: How a Dispute API Saves Your Support Team Hours

Support dashboard tracking recharge disputes with open, refunded and not accepted statuses

Some recharges go through on the operator side but the customer insists nothing arrived. Some are marked success but really did fail. Either way, the retailer calls you, you call your API provider, and somebody sends screenshots on WhatsApp.

Multiply that by a busy network and support becomes a full-time job. A dispute API turns it into a process your software can run.

What a dispute API does

  1. Raise a dispute for a transaction, using the transaction ID or your own order ID, with a short remark
  2. Track it by checking its status, or wait for the result on your callback URL
  3. Settle it in your system: refund if accepted, keep as success if not

The statuses to plan for

With A1Topup's Dispute API v2, a dispute is always in one of four states:

StatusWhat it meansWhat your system does
openWith the operator. The recharge shows Pending until settledShow "under review" to the retailer
refundedAccepted. Amount refunded, recharge is FailureRefund the retailer's wallet
not_acceptedNot accepted. Recharge stays SuccessClose it and show the operator ID as proof
rejectedThe operator refused the request when it was raisedShow the reason, no refund

Disputes can be raised within 10 days of the recharge, with up to 10 open at a time. The full request and reply format is in the API documentation.

Build it into the retailer's screen

  • A "raise complaint" button on each successful transaction in the history
  • Block a second dispute on the same transaction while one is open
  • A clear status badge, so the retailer stops calling to ask
  • Automatic wallet refund when the result is refunded, recorded in the ledger
Before raising anything: check the operator ID. Many "not received" complaints are solved by asking the customer to check their balance or SMS with that ID in hand.

Mistakes that make disputes harder

  • Raising a dispute on a pending recharge. Wait for the final status first. Pending is not a complaint, it is a recharge still in progress.
  • Refunding the retailer before the result. If the dispute is not accepted, you have paid twice. Refund only on the refunded status.
  • Losing the link to your order. Store your own order ID with every transaction, so you can raise and track disputes with it.
  • Waiting too long. Disputes have a time window. Make raising one a single tap, so retailers do it the same day.

Why it is worth the work

Retailers trust a network that settles complaints visibly. When they can see "under review" and then "refunded" on their own screen, they stop moving to a competitor after one bad experience.

For the bigger picture of pending and failed recharges, read our pending, failed and refund guide. Want the dispute flow in your platform? WhatsApp us.

Frequently asked questions

What is a recharge dispute API?
An API to raise a complaint on a recharge transaction, track its status and receive the final result, so refunds happen without manual follow-up.
How long do I have to raise a recharge dispute?
With A1Topup’s Dispute API v2, within 10 days of the recharge, with up to 10 disputes open at a time.
What happens if a dispute is accepted?
The status becomes refunded, the amount is refunded and the recharge is treated as Failure. Your system should then refund the retailer’s wallet.

Have a question? Talk to our team

We respect your privacy. Your details are only used to contact you about A1Topup.

Related articles

WhatsApp