What a VTU platform actually needs
A VTU (Virtual Top-Up) platform lets users and resellers purchase airtime, data bundles, cable TV subscriptions, electricity bills, and related services digitally. Unlike a simple website, it requires wallet funding, transaction processing, provider integrations, and often tier-based account verification.
Platforms like iFlow, DataVendor, DataPlanet, PremiumSub, UzobestGSM, and Postranet — all built by ScalerDev — demonstrate the full scope: user dashboards, wallet balances, multi-service purchase flows, admin panels, and mobile apps.
Core components to plan for
Before writing code, map these modules. Each one affects architecture, timeline, and cost.
- User authentication and profile management
- Wallet system with funding, balance, and transaction history
- Service purchase engine (airtime, data, cable, electricity)
- VTU API provider integrations with fallback and retry logic
- Payment gateway integration (Paystack, Flutterwave, virtual accounts)
- Tier-based KYC for account upgrades
- Admin dashboard for users, transactions, and provider management
- Reseller/agent pricing and API access (if applicable)
- Mobile app (Flutter or React Native) for end users
- Notifications (SMS, email, push) for transaction status
VTU API integration
Your platform connects to one or more VTU API providers to fulfill airtime, data, and utility purchases. Integration work includes authentication, request/response mapping, webhook handling, and reconciliation when transactions fail or pend.
Build with idempotency in mind — the same purchase request should not debit a wallet twice if the network retries. Log every API call with request IDs so your admin team can trace issues quickly.
Wallet and payment flows
Users fund wallets through payment gateways or virtual accounts. When a purchase is initiated, the system should: validate balance, debit the wallet atomically, call the VTU provider, update transaction status, and notify the user.
Failed provider calls need clear rollback or pending states — never leave users guessing whether their money was taken.
Mobile app vs web-only
Many VTU platforms start web-first and add mobile later. DataPlanet shows the mobile-first path — an Android app on Google Play with 10K+ downloads, linked to the dataplanet.ng backend.
If your users are resellers or agents who purchase on the go, a mobile app significantly improves retention. Flutter is our typical choice for VTU apps because of UI consistency and single-codebase delivery.
Timeline and approach
A focused VTU MVP — wallet, airtime, data, one payment method, basic admin — typically takes 4–8 weeks. Adding cable, electricity, KYC tiers, reseller APIs, and mobile apps extends this in clear phases.
We recommend shipping a working core first, then expanding services based on actual user demand rather than building every category on day one.