VTpass has been part of the Nigerian VTU landscape for years, and for many teams it works well. If you're exploring alternatives, the honest question isn't "is VTpass bad?" — it isn't — but rather "does a more developer-focused API fit your stack better?"
What most developers want from a VTU API
When you're building a product where real money moves on every API call, the things that bite hardest at volume aren't feature counts — they're the correctness primitives:
- Safe retries. Can you retry a timed-out request without double-charging the customer?
- Exact money. Are amounts integer values with no floating-point drift over thousands of transactions?
- Automatic recovery. When a delivery fails, does your wallet refund automatically, or do you have to chase it?
- Predictable funding. Can you top up your wallet by bank transfer without logging into a portal?
- Transparent pricing. Can you query the price of a plan before you buy?
How Plustive approaches these
Idempotency on clientReference
Every Plustive purchase carries a clientReference you supply. It's enforced at the database level: a second request with the same reference returns the original outcome rather than creating a new transaction. You can retry after any timeout or dropped connection without writing defensive de-duplication logic on your side.
Integer kobo throughout
Amounts, balances and refunds are all whole-number kobo (₦1 = 100 kobo). There are no decimals in the API response and no floating-point arithmetic in the platform. Across thousands of daily transactions, that precision compounds into clean reconciliation ledgers.
Automatic reconciliation and refunds
Calls that can't be confirmed immediately return Pending. A background reconciler settles them — typically in under a minute — against the upstream confirmation. If a delivery fails, the wallet refunds automatically without a manual reversal request. Electricity and cable TV purchases use a verify-then-pay approach to reduce the incidence of failures in the first place.
Dedicated-account wallet funding
Every Plustive account gets a dedicated NUBAN. Transfer any amount from any Nigerian bank and the wallet credits in seconds — no portal login, no minimum top-up. For resellers with variable daily volumes, this makes cash-flow management predictable.
One wallet across all services
Airtime, data, electricity, cable TV and education PINs all draw from the same prepaid balance. No need to maintain separate wallets or sub-accounts per service.
Where VTpass still makes sense
VTpass is long-established and has a very broad biller catalog. If you depend on a specific biller Plustive doesn't list yet, or you're already deeply integrated and stable, that incumbency has real value. We'd rather tell you honestly if a biller you need isn't live with us than oversell. You can check the live catalog in the docs or reach out before integrating.
Making the switch
Both APIs follow the same wallet-funded REST pattern, so migration is largely a matter of mapping plan and biller identifiers. You keep your existing clientReference scheme (Plustive uses the same field name) and point your calls at the new base URL. The integration guide walks through the full flow in under thirty minutes.
For a side-by-side feature table, see the Plustive vs VTpass comparison.