How to Build a Subscription App in Nigeria
What counts as a subscription app, and which model are you building?
A subscription app is one where the customer pays a recurring fee, usually monthly or yearly, for continued access to something: content, a service, a tool, or a physical delivery managed through the app. The business logic is different from a one-off purchase because the app must repeatedly answer one question: is this user entitled to access right now? The model you pick determines what you have to build. Five common models in Nigeria:
| Model | What the subscriber gets | Examples | Engineering weight |
|---|---|---|---|
| Content access | Videos, audio, articles, past questions, devotionals | Exam prep, faith content, courses | Content management, offline caching, piracy control |
| Membership and community | Access to a group, events, discounts | Professional bodies, alumni groups, gyms | Member verification, event tools, chat |
| Software tool | Features that do work for the user | Invoicing, bookkeeping, inventory for SMEs | Feature gating, data export, team plans |
| Service plan | Ongoing human service booked via the app | Telemedicine plans, tutoring, cleaning | Scheduling, provider management, usage limits |
| Product replenishment | Physical goods delivered on a schedule | Water, groceries, diapers, farm produce | Delivery logistics, address handling, pause and skip |
Decision framework. Write down three things before any design work: what the subscriber gets on day one, what they get on day thirty-one that they did not have before, and what happens to their data or access when they stop paying. If the second answer is "nothing new", you are selling a one-off product with instalments, and a subscription model will churn badly.
How recurring billing actually works in Nigeria
Recurring billing in Nigeria works in one of three ways: a tokenised card that your payment gateway charges automatically each cycle, a manual renewal where the app prompts the user to pay again by transfer, USSD or card, or an app store subscription managed by Apple or Google. Most Nigerian subscription apps combine the first two, because automatic card charges fail more often than founders expect and a transfer fallback rescues many of those subscribers.
Automatic card charges through a Nigerian gateway
Gateways such as Paystack and Flutterwave support charging a card again after the first successful payment, using a token (often called an authorisation code) returned by the first transaction. The mechanics that matter for your build:
- The first payment must succeed inside the gateway's checkout so the token is created. You then store the token against the user on your backend, never in the app.
- On each renewal date, your backend calls the gateway with the token and amount. The gateway returns success or a failure reason.
- Not every card is reusable. Some bank cards decline recurring charges, some have low online limits, and some are blocked by the issuing bank after fraud alerts. Your system must treat every renewal as something that might fail.
- The gateway will send a webhook for every charge. Your backend must verify the webhook signature and update the subscription state from the webhook, not from what the app reports.
Check each gateway's current developer documentation for how recurring charges are enabled on your account, because the exact steps and account requirements change.
Manual renewals by transfer, USSD or card
For many Nigerian customers, especially outside Lagos and Abuja, the reliable path is a renewal prompt a few days before expiry that opens the gateway checkout, where they pay by bank transfer to a virtual account, USSD or card. It is less elegant than automatic charging but it converts. Design it as a first-class flow, not a fallback.
Prepaid wallets and longer plans
A third pattern that fits Nigerian purchasing habits: quarterly or yearly plans at a discount, or a wallet the subscription draws from. Longer plans mean fewer renewal events and fewer chances for a charge to fail, and they match how many people budget, paying when salary or trading income arrives.
App store in-app purchases vs your own billing
The difference between app store in-app purchases and your own billing is who processes the payment and who controls the relationship. Apple's App Store and Google Play require that digital content and features consumed inside the app be sold through their in-app purchase systems, which take a commission and handle renewals, receipts and refunds. Physical goods and services consumed outside the app are generally exempt and can use a gateway like Paystack directly.
| Factor | App store in-app subscription | Own billing via Nigerian gateway |
|---|---|---|
| Typically required for | Digital content, premium app features | Physical deliveries, real-world services, business tools in some cases |
| Commission | A percentage of each payment to Apple or Google (verify current rates and small-business programmes) | Gateway transaction fees, usually far lower |
| Payment methods | Cards and carrier or wallet options the store supports in Nigeria | Cards, bank transfer, USSD, mobile money via gateway |
| Renewal handling | Managed by the store, including retries and grace periods | You build it |
| Receipt verification | Your backend must verify store receipts or server notifications | Gateway webhooks |
| Customer relationship | Store owns billing; you see limited data | You own the payment history |
Two practical notes as of 2026. First, the rules on which categories must use in-app purchase, and the exceptions for "reader" apps and external links, have been changing; read the current App Store Review Guidelines and Google Play payments policy before committing to an architecture. Second, many Nigerian content apps take payment on the web through a Nigerian gateway and let users log into the app afterwards. Whether that passes review depends on how the app presents it and on current policy. Verify rather than assume; a rejection can cost weeks. If your app must use store subscriptions, budget for the Apple Developer Program yearly fee (US$99 historically) and the one-time Google Play registration fee (US$25 historically), both in US dollars; verify current fees.
The entitlement system: the part most first-time founders skip
An entitlement system is the backend logic that answers "what is this user allowed to access right now?" It sits between billing events and the app's features. Without it, teams end up hard-coding "if paid, show content" in the app, which breaks the moment a payment fails, a refund happens, a plan changes or the user switches phones. A sound entitlement design has:
- A subscription record per user: plan, status (trial, active, past due, cancelled, expired), current period start and end, billing route (card token, manual, Apple, Google).
- A state machine that only changes status from verified events: gateway webhook, store server notification, admin action, or scheduled expiry check.
- A grace period rule: how many days of access continue after a failed renewal before the status becomes expired.
- An access check API the app calls on launch and before opening gated content, with a short cache so the app works during brief network drops.
- An admin view where support staff can see the history and manually extend, pause or refund, with an audit trail.
The app should hold as little billing logic as possible: show plans, open the checkout, ask the backend what the user can access. Everything else lives on the server.
How to build a subscription app: step by step
- Define the offer in one sentence. "₦2,500 per month for unlimited past questions with explanations, downloadable for offline use." If the sentence takes a paragraph, narrow it.
- Pick the billing route per platform. Decide whether each platform will use in-app purchase, a Nigerian gateway, or both, based on the store rules for your category. This decision shapes the backend.
- Design the entitlement model and plan catalogue. Plans, prices, trial length, grace period, what happens on expiry. Put prices in a server-side configuration so you can change them without an app release.
- Build the backend first. User accounts, subscription records, gateway integration with webhook handling, store receipt verification if needed, scheduled jobs for renewals and expiries, and an admin dashboard.
- Build the app around the access check. Onboarding, plan selection, checkout, a clear subscription status screen, and gated content that asks the backend before opening.
- Add the retention flows. Pre-expiry reminders through push notifications, WhatsApp or SMS, failed-payment recovery, easy cancellation, and win-back messages for lapsed users.
- Test the money paths end to end. Successful first charge, successful renewal, failed renewal, renewal after grace, refund, plan upgrade mid-cycle, and reinstalling the app on a new phone. Use the gateway and store sandboxes.
- Run a closed pilot. Fifty to two hundred real users for one full billing cycle. Watch renewal success rate, support questions and where users drop off.
- Launch, then instrument. Track trial-to-paid conversion, renewal success by payment method, and churn by cohort from day one.
Step seven separates sustainable apps from abandoned ones. If you have not tested a failed renewal and a phone change before launch, your first real subscribers will test them for you.
Retention mechanics: reminders, dunning and cancellation
Dunning is the process of recovering a subscription after a failed payment. In Nigeria it deserves more attention than almost anywhere else, because card failures are common and many customers simply need a nudge to pay by transfer. A practical dunning sequence:
- Day minus three: renewal reminder with a one-tap "pay now" option for manual renewers.
- Day zero: attempt the card charge if tokenised; on failure, notify immediately in plain language with a transfer option.
- Day one to three: retry the card once or twice at different times of day.
- Day three to seven: grace period, access continues, WhatsApp or SMS reminder for high-value plans.
- Day seven: access ends, data preserved for a stated period, win-back offer scheduled.
Cancellation should be easy and inside the app. Hidden cancellation generates chargebacks, bank complaints and bad reviews, and the app stores require accessible cancellation for in-app subscriptions. A short exit survey at cancellation tells you more than most analytics dashboards. Reminders work best on channels Nigerians actually read: push is cheap but easily disabled, WhatsApp Business Platform messages cost per conversation but get read, and SMS still reaches everyone. Choose by plan value.
What changes for subscription apps in Nigeria
Subscription apps in Nigeria operate under constraints that international playbooks do not mention:
- Card reliability. Automatic renewals fail more often than in markets with mature card ecosystems. Plan for manual renewal as a primary path, not an exception.
- Bank transfer expectations. Many customers trust transfer over card entry, and virtual accounts through gateways make transfer renewals traceable.
- Price sensitivity and salary cycles. Renewals timed to month-end salary dates convert better for salaried segments; weekly micro-plans can work for traders and students. Test plan lengths rather than copying foreign pricing pages.
- Naira and USD costs. Revenue is in naira; store fees, cloud hosting and messaging services are in US dollars. Model unit economics with an exchange-rate buffer.
- Data and device constraints. Subscribers on mid-range Android phones with limited data judge the app on download size and offline access. Offline caching of paid content, with expiry tied to entitlement, matters for content apps.
- Trust and refunds. Publish clear terms: what the plan includes, when it renews, how to cancel, how refunds work. A registered business name and visible support contact reduce the hesitation that stalls first payments.
- Data protection. The Nigeria Data Protection Act 2023 applies to the payment history and personal data you hold. Collect only what you need and confirm your obligations with the NDPC's current guidance or a qualified adviser.
- VAT and tax. Digital services can attract VAT obligations and the rules have been evolving. Ask a qualified tax adviser; do not rely on a developer for this.
Example (hypothetical): a JAMB and WAEC prep app in Ibadan
Example (hypothetical): a tutoring centre in Ibadan wants to turn its past-question bank and video explanations into a subscription app for secondary school students across the South-West. The offer is ₦2,000 per month or ₦15,000 per year for unlimited access, with a seven-day free trial. Because the content is digital and consumed in the app, the founders plan for in-app subscriptions on iOS and Google Play, and a web sign-up with Paystack for students who prefer transfer or whose parents pay from a bank app. All three routes feed the same entitlement system on the backend, so a student who paid on the web can log into the Android app and access everything. The retention design leans on parents: renewal reminders go to the parent's WhatsApp number captured at sign-up, with a transfer link. Content downloads for offline use are encrypted and expire when the subscription lapses, so the app works in a hostel with no data and still respects the paywall. The first pilot runs with one school for a full term to measure renewal rates before marketing spend. The figures are illustrative and not client results.
How much does it cost to build a subscription app in Nigeria?
Indicative 2026 ranges are shown below; actual quotes vary with scope, vendor and exchange rate. The biggest cost drivers are the number of billing routes you support, whether content needs offline protection, and how much admin tooling you need at launch.
| Cost item | Indicative 2026 range | Notes |
|---|---|---|
| Product definition, plan design and UX | ₦400,000–₦1,500,000 | Includes entitlement and state design |
| Backend: accounts, subscriptions, webhooks, admin | ₦1,500,000–₦5,000,000 | The core of the product |
| Mobile app (cross-platform, both stores) | ₦1,500,000–₦5,000,000 | Native in-app purchase modules add effort |
| Gateway plus app store billing integration | ₦400,000–₦1,500,000 | Each additional route adds cost |
| Notifications, dunning and messaging flows | ₦200,000–₦800,000 | Push, WhatsApp and SMS wiring |
| Testing, store submission and pilot support | ₦300,000–₦1,000,000 | Sandbox testing of every money path |
| Typical total, focused first release | ₦3,000,000–₦12,000,000 | One model, two billing routes |
| Typical total, content-heavy or multi-plan product | ₦8,000,000–₦20,000,000+ | Offline content protection, team plans, agent tools |
Recurring costs, separate from the build: gateway fees on every payment and store commission where in-app purchase applies; cloud hosting and storage at ₦150,000–₦800,000+ per year for most early-stage apps, more for video; usage-based WhatsApp and SMS messaging; developer programme fees in US dollars; and maintenance at typically 15–25 percent of build cost per year. When comparing quotations, ask each vendor to price the same written list of billing routes and money-path test cases, confirm whether the admin dashboard and dunning flows are included, and state who owns the code. Two or three written quotes on identical scope will show who has built recurring billing before.
Mistakes to avoid
- Trusting the app to enforce the paywall. Anything checked only on the phone can be bypassed. Entitlement lives on the server.
- Updating subscription status from the app instead of the webhook. Apps crash, networks drop, and the payment still went through. The webhook is the source of truth.
- Launching with card-only renewals. In Nigeria that guarantees churn from failed charges. Offer transfer renewal from day one.
- Ignoring store billing rules. Selling digital content through your own gateway inside the app can lead to rejection or removal. Verify the current policy for your category.
- No grace period. Cutting access the minute a charge fails punishes loyal users for their bank's problems.
- Forgetting the phone change. Users replace phones often. Login and restore-purchase flows must bring the subscription back without a support ticket.
Conclusion
A subscription app in Nigeria succeeds or fails on renewals. Define the offer in one sentence, choose billing routes that match how your customers actually pay, put entitlement logic on the server, and treat failed payments as a normal event with a designed recovery path. Respect the app store rules for your category, price in naira while budgeting for dollar costs, and pilot for a full billing cycle before spending on growth. The screens are the easy part; the state machine behind them is the product. If you are planning a subscription app and want help deciding between app store billing and a Nigerian gateway, or designing the entitlement and dunning logic, Linestech builds subscription and recurring-billing apps for Nigerian businesses and can scope a focused first release with you.
Frequently asked questions
Can Paystack or Flutterwave charge my subscribers automatically every month?
Yes, both support recurring charges using a token created after the first successful card payment, subject to account setup and the customer's card and bank permitting recurring transactions. Not every card will work, so pair automatic charging with a manual renewal option by transfer or USSD. Check each provider's current developer documentation for setup requirements.
Do I have to use Apple or Google in-app purchases for my subscription?
If the subscription gives access to digital content or features used inside the app, the stores generally require their in-app purchase systems. Physical goods and services consumed outside the app are usually exempt. Policies and exceptions change, so read the current App Store Review Guidelines and Google Play payments policy before deciding.
How do I stop people from sharing one account?
Limit the number of active devices per account on the backend, require re-authentication on new devices, and watch for logins from many locations in a short period. For content apps, tie offline downloads to the device and expire them with the subscription. Perfect prevention is impossible; aim to make sharing inconvenient.
Should I offer a free trial in Nigeria?
A short trial helps when users need to see the value before paying, but trials that require a card up front convert poorly in Nigeria. Consider a limited free tier or a trial that ends with a manual payment prompt. Measure trial-to-paid conversion and adjust length rather than guessing.
What happens to a subscriber's data when they stop paying?
Decide and publish it. A common approach keeps the account and data for a stated period, such as ninety days, so returning users pick up where they left off, then deletes or anonymises it. Whatever you choose must be consistent with your privacy notice and the Nigeria Data Protection Act.
How long does it take to build a subscription app?
A focused first release usually takes three to five months, with billing integration and money-path testing consuming more of that than the screens. Add time for app store review, especially when in-app subscriptions are involved, and for a pilot billing cycle before public launch.
Sources and further reading
Figures, platform rules and regulations change. These are the primary references behind this article and the places to check before you act on it.
