It's a common worry, and an honest one: you're topping up a relative's phone from thousands of miles away, typing a long international number from memory or a messy WhatsApp thread, and you hit pay before double-checking. So what actually happens if the number was wrong?
Why a wrong number isn't the same as a failed order
Top-ups to Afghan networks are delivered instantly and automatically. The moment you confirm payment, the credit is sent straight to whatever number you entered — there's no manual review step where a human checks whether that number "looks right" or belongs to your relative.
That means:
- If the number you typed is a real, active number on Roshan, AWCC, Etisalat, Salaam, or ATOMA, the credit is delivered successfully. To the system, that's a completed transaction, no different from one that went exactly where you intended.
- If the number doesn't exist at all (wrong length, invalid prefix), the order typically fails rather than delivering — which is a different situation, covered below.
Why this means it's generally not refundable
As ReloadJet's terms explain it: because digital top-ups are delivered instantly, transactions are generally non-refundable once they've successfully reached the destination number. A top-up to a wrong-but-valid number has, from a technical standpoint, successfully delivered — it just delivered to the wrong person. That's treated the same as any other successful delivery, which is why it falls outside the refund window.
This is the single most important thing to understand before you pay: once you hit confirm, there's no "undo" button, because the credit is already in a stranger's account within seconds.
When it is refundable
It's worth being clear about the difference, because it's easy to conflate the two:
- Wrong but valid number, delivered successfully — not eligible for a refund, since the transaction completed as instructed.
- Transaction that actually failed — on ReloadJet's end or the carrier's end, meaning the credit never reached any number — is eligible for a refund.
If you're not sure which happened, that's exactly what support is for.
What to do if you think you sent it to the wrong number
- Don't pay a second top-up in a panic. Check your email confirmation first for the number on record.
- Contact support right away with your order reference number. Acting quickly doesn't guarantee a different outcome, but it's always the right first step.
- Describe exactly what happened — which digit you think you got wrong, and what the correct number should have been. Support can confirm whether the transaction delivered successfully or actually failed.
- If it failed on ReloadJet's or the carrier's side, you'll be guided through the refund process. If it delivered to a valid-but-wrong number, support can tell you clearly why a refund isn't available.
A quick checklist before you pay
- Confirm the number has the correct country code, +93, at the start.
- Count the digits — Afghan mobile numbers have a fixed length, and one missing or extra digit is the most common mistake.
- Read the number back from your source (text message, contact card, previous receipt) digit by digit rather than typing from memory.
- Check the auto-detected network on the recharge widget — if your relative is on Roshan and the widget shows Etisalat, that's a signal something's off with the number.
- If this is the first time topping up this number, send a smaller amount first to confirm it's correct before sending more.
Frequently asked questions
Can ReloadJet reverse a top-up sent to the wrong number?
No. Delivery to any valid number is instant and final, so there's no way to pull the credit back once it's landed, even if the number was incorrect.
How do I know if the network auto-detected the number correctly?
The checkout widget shows the detected network (Roshan, AWCC, Etisalat, Salaam, or ATOMA) before you pay. If it doesn't match the network you expected for your relative, double-check the digits before continuing.
What if the number is correct but just didn't go through?
That's a failed transaction, not a wrong-number issue, and it's handled differently — contact support with your order reference and it will be reviewed for a refund.
I don't have an order reference — can support still help?
Reach out to support anyway with your payment details and the approximate time of the transaction. It's easier with a reference, but that's not the only way to look up an order.
Is there a way to verify a number before paying?
The checkout page shows the detected network as soon as you enter the number, which is a useful sanity check, but the final responsibility for entering the correct digits is on the sender — there's no independent verification of who owns the number.