Where they’re similar
Both expose airtime and data for MTN, Glo, Airtel and 9mobile, plus cable TV, electricity (with the prepaid token) and education PINs, over a REST API. Both fund from a prepaid wallet topped up by bank transfer to a dedicated account, and both offer webhooks and a way to check a transaction’s state. Neither a wallet nor a dedicated funding account is unique here — they’re table stakes, and VTU.ng has both.
Where Plustive differs
- Integer kobo everywhere. Amounts and balances are exact integers (₦1 = 100 kobo), which removes a whole class of floating-point rounding bugs in your ledger.
- Automatic reconciliation + refunds. An ambiguous call returns
Pending and settles in about a minute; a genuine failure auto-refunds your wallet to the kobo — you don’t requery and reverse by hand. - Idempotency by default. Every purchase carries your
clientReference, enforced at the database level, so a retry after a timeout returns the original result instead of charging twice. - One key across every service, documented. Data, airtime and all four bill types behind one wallet and one Bearer key, with a modern reference and live API console.
When VTU.ng may be the better call
VTU.ng publishes transparent reseller pricing and is well-known for low per-transaction cost. If your model is price-led — you’re reselling on thin margins and the headline rate is what decides it — that transparency has real value, and we’d rather you know that than oversell.
The bottom line
If you want the platform to handle correctness — exact money, safe retries, automatic refunds — Plustive is the more developer-friendly choice. Read the docs or follow the build guide to try it.
