Direct airtime or universal vouchers? A buying guide for South African businesses
With direct recharge, you send airtime to a number you’ve verified. With a universal voucher, you can send the person a PIN even if you don’t know their network. They redeem it on a supported prepaid network.
For a campaign with 1,200 recipients, ask which job your team can handle better: checking 1,200 mobile records up front, or sending and tracking 1,200 PINs. Both take staff time.
Quick decision
- Choose direct recharge when you have the correct mobile number and network, and your process should send airtime to that number without asking the recipient to redeem a PIN.
- Choose a universal voucher when you want to order one voucher type across supported networks and let each recipient redeem the PIN on their own network.
- Price data separately if the reward needs to cover a specific bundle. Check what the recipient can buy with the airtime before promising that bundle.
By Freepaid · Published
What changes between the two options?
With direct recharge, your business supplies the recipient’s mobile number and the recharge amount. In an automated workflow, your application submits the order and tracks its status. SIMcloud’s airtime API documents a queued order and status polling. The published request includes a number, network, amount and reference. SIMcloud airtime API overview · SIMcloud airtime API documentation
With a universal voucher, your business orders PINs for a chosen value and quantity. You distribute each PIN, and the recipient redeems it on a supported prepaid network. The AllNet Airtime business page describes this PIN-based model and the supported networks. Its vendor registration page sets out ordering and distribution terms. Check current commercial and redemption terms there before budgeting a live campaign.
With direct recharge, your operations team or system resolves the network before placing the order. With a voucher, the recipient selects the network during redemption.
A worked example for 1,200 customer rewards
Suppose a retailer plans a campaign for 1,200 customers, with a reward of R25 airtime for each eligible purchase. Assume every eligible customer receives one reward at a face value of R25. The calculation excludes fees and staff time.
Reward face value · 1,200 × R25 = R30,000.
If the retailer chooses direct recharge, it needs a usable mobile number for each customer and the correct network for each order. It should decide how the number is collected, validated and matched to the purchase, then test how the system handles queued, successful and failed orders. If a customer enters the wrong number, the campaign team needs a defined correction and support process.
If it chooses universal vouchers, it orders 1,200 PINs at R25 each, then distributes them through its own channel or an available delivery service. The team does not need to split voucher stock by recipient network, but it must deliver the right PIN to the right eligible person and explain how to redeem it. Check the current terms and add applicable delivery or redemption charges to the R30,000 face value.
Measure the handling time in a pilot. If 48 mobile records need two minutes of manual review each, allow 96 minutes for that task on the direct route. If the voucher pilot shows that matching and issuing each PIN manually takes 10 seconds, allow three hours and 20 minutes for that task across 1,200 recipients. These are illustrative workloads for individual steps. Include the remaining fulfilment, reconciliation and support work in both estimates before comparing total costs.
Check the evidence a buyer will receive
For an automated SIMcloud direct recharge, the acknowledgement can show that the order was queued. Keep the returned order identifier and check the final status before counting delivery. For AllNetAirtime, issuing the voucher and redeeming it are separate events. Its published vendor API describes status retrieval for vouchers in the vendor's own account. Agree whether your campaign will measure issuance, recipient receipt or redemption and confirm which of those you can observe. SIMcloud Airtime API · AllNetAirtime API documentation
In the 1,200-recipient example, suppose 1,140 direct recharges are confirmed and 60 are still being checked. Record 1,140 confirmed recharges. If 1,200 voucher PINs are issued and 912 have verified redemption records at the same cut-off, record 1,200 issued and 912 verified redemptions. These are hypothetical results. Use the same reporting deadline, and report each milestone separately so the buyer can compare it with the campaign objective.
Procurement comparison
| Buying consideration | Direct airtime recharge | Universal airtime voucher |
|---|---|---|
| What you order | Airtime for a specified mobile number and network | A PIN at a selected value and quantity |
| Recipient network | Your organisation must identify the network for the recharge workflow | Recipient chooses their supported network when redeeming |
| Recipient action | No voucher PIN redemption step is part of the direct recharge flow | Recipient must receive and redeem the PIN |
| Useful when | You have validated numbers and want to trigger fulfilment from a portal, batch or integrated system | You need a common voucher stock across supported networks and can manage PIN distribution |
| Main data or control need | Accurate mobile number, network and duplicate-order controls | Secure PIN handling, recipient-to-PIN matching and redemption instructions |
| Check before purchase | Supported networks, order states, funding, pricing and exception handling | Supported networks, PIN values, delivery options, charges, expiry or other terms, and redemption support |
Ask each supplier for the fees, settlement timing, redemption rules and service levels that apply to your account and campaign.
What to check before you order
- Write the reward requirement in one sentence. State the product, value, recipient count, trigger and deadline. If the requirement is a specific data bundle, evaluate data products separately.
- Check the recipient record. For direct recharge, confirm that the number is current, belongs to the intended recipient and can be mapped to a supported network. For vouchers, confirm that you can securely deliver one unique PIN to each eligible person.
- Choose who handles redemption. If the business expects fulfilment to target a number, assess direct recharge. If the recipient can accept and redeem a PIN, assess a universal voucher.
- Map the operating flow. Record who approves orders, who funds them, how status is checked, how failures are handled, and how finance reconciles the final quantity and value.
- Request written commercial terms. Ask about the exact products and values, any delivery or redemption charges, funding and invoicing, support route, and the terms that govern unredeemed or incorrectly distributed vouchers. Confirm these before committing campaign funds.
- Run a small acceptance check. Use an approved test case to check ordering, order status or PIN delivery, recipient instructions, exception handling and reconciliation. Agree the test scope and spend with your supplier first.
- Compare the real operating cost. Start with face value multiplied by recipient count. Add confirmed charges and the internal cost of collecting numbers, validating networks, distributing PINs, supporting recipients and resolving exceptions. Compare like for like.
Use this worksheet in the supplier meeting
Give each option its own column. Bring the approved headcount and a few sample problems, such as a changed number or a PIN that never arrived. Leave personal details out of the sheet. Give unanswered questions an owner and a due date.
| Record | What to capture |
|---|---|
| Approved population | Number eligible, any exclusions and the owner of the list |
| Required outcome | Credit at a number or delivery of a redeemable PIN |
| Data and access | Where the confirmed number and network come from, or how the person can receive a PIN securely |
| Outcome evidence | Which report shows completed, pending, rejected or issued items, and who can access it |
| Exception decision | Who handles a changed number, unknown status, missing PIN or complaint |
| Cost and conditions | Quoted fees, invoice evidence, time to fulfil and relevant product terms |
Use the same population and outcome deadline for both trial routes. For direct recharge, count confirmed orders, pending orders and records held before submission. For vouchers, count issued PINs and separately record redemption evidence if the service and campaign allow you to see it. Judge the trial against what you promised recipients. If the campaign promised redeemed airtime, an issued PIN is still an open item until you can verify redemption.
Where to order
For a portal, batch or API workflow that recharges a known number, review SIMcloud’s business platform and its airtime API details. Confirm that the documented order flow and commercial terms match your use case before integration.
For a reward distributed as a redeemable PIN, review AllNet Airtime and its vendor terms and registration information. Confirm current voucher, delivery and redemption terms before ordering.
More in this series
- PIN airtime vs pinless airtime at the till
- Airtime or data for staff and customers?
- Bulk order or one top-up at a time?
- Prepaid value or cash reimbursement for field teams?
- Choose an airtime channel for each recipient group
- Buy fixed denominations or custom values?
- How to buy airtime when you do not know the recipient's network
- Airtime or prepaid electricity for a customer benefit?
- Write a business case for distributing prepaid value
- Wholesale airtime buying guide for South African businesses
- Plan an airtime rewards campaign from budget to reporting