What is the best bill-payment API in Nigeria?

For developers who need correctness by default — verify-then-pay for electricity and cable TV, the prepaid token returned in the API response, idempotent calls on clientReference, and automatic reconciliation with refunds — Plustive is our pick. VTpass is a strong, long-established choice with a broad biller catalog; Flutterwave suits teams that want a single vendor for collections, payouts and bills across multiple African countries.

What bills can a Nigerian bill-payment API cover?

The main categories are electricity (prepaid token delivery), cable TV subscription renewal (DSTV, GOtv, StarTimes), and education result-checker PINs (WAEC, NECO, JAMB). A good API verifies the meter or smartcard number before charging and returns the prepaid token or confirmation code directly in the response — no separate lookup step for your customer.

What does "verify-then-pay" mean for electricity and cable?

Before debiting your wallet, the API calls the biller to confirm the meter number (or smartcard/IUC number) is valid and retrieve the customer's name. If the lookup fails, the purchase is rejected before any money moves. This prevents charges against invalid accounts and gives your UI a confirmation step for the customer.

Why does idempotency matter for bill payments?

Electricity and cable TV payments are time-sensitive: a customer waiting for a token after a network timeout may retry. Without idempotency enforced at the API level, a retry creates a second charge. Plustive enforces clientReference at the database level so any retry returns the original outcome — the customer never pays twice for the same bill.

What happens if a bill-payment delivery fails?

With Plustive, a delivery that can't be confirmed immediately returns Pending. A background reconciler settles it — usually within a minute. If it ultimately fails, the wallet refunds automatically to the exact kobo. Education PIN calls are the exception: there's no verify step (the PIN is returned in the success response), but idempotency still applies.

How are education PINs different from electricity and cable TV?

Electricity and cable TV have a verify step: the API confirms the meter or smartcard number before charging. Education PINs (WAEC, NECO, JAMB) don't have a pre-purchase verification — the PIN is issued and returned in the API response. Idempotency on clientReference is therefore especially important here: the PIN is only generated once per reference, even if you retry.

Best Bill Payment API in Nigeria (2026)

What to look for in a bill-payment API

Verify-then-pay — electricity and cable TV should confirm the meter/smartcard number is valid before any money moves, and return the customer name for confirmation.

Token in the response — the prepaid electricity token or cable renewal confirmation should be in the purchase response, not in a second lookup.

Idempotency — a reference that makes retries safe; customers waiting on a token will retry, and the API must not charge twice.

Auto-reconcile + refunds — failed deliveries should refund your wallet automatically, not require a support ticket.

Education PINs handled correctly — no verify step exists for WAEC/NECO/JAMB; the PIN is issued on purchase, so idempotency is especially critical here.

Electricity tokens — correctness matters most

A customer who has just paid for a prepaid electricity token needs it within seconds. The verify-then-pay flow protects against charges on invalid meters; the prepaid token should be in the purchase response so your app can display it immediately without a second API call. Plustive returns the token in the token field of the purchase response and confirms the meter number with the disco before charging your wallet.

Cable TV — verify the IUC number first

Renewing a wrong smartcard is an immediate support request. A good cable TV API confirms the IUC number (and returns the subscriber name) in a verify call before the actual payment, so your UI can show the customer their name for confirmation. Plustive's cable TV endpoint follows this pattern for DSTV, GOtv and StarTimes.

Education PINs — idempotency is the guard

WAEC, NECO and JAMB PINs have no pre-purchase verify step — the PIN is issued when the purchase succeeds. That makes idempotency especially critical: if a network drop causes a retry, the second request must return the original PIN, not generate a second charge. Plustive's clientReference enforcement at the database level ensures exactly this.

How we compared them

We weighted correctness primitives — verify-then-pay, idempotent retries, automatic reconciliation and refunds — over raw biller counts. We describe each provider from its own public documentation and don't claim gaps we can't verify; where a competitor's strength is real, we say so.

The bottom line

For Nigerian developers building electricity, cable TV or education PIN products who want correctness handled by the platform, Plustive is the strongest fit. If you need a specific biller we don't list yet, we'd rather tell you honestly than oversell. Read the docs or follow the bill-payment guide.

Best Bill Payment API in Nigeria