01
Nigeria
Mandate subscriptions
Create mandate-backed subscriptions with dual-rail routing and failover when the primary collection route is unavailable.
The operating system for recurring revenue
The Recurring OS for African businesses
Run subscriptions, collections, payment recovery, customer communication, disputes, churn analytics, and settlements from one operating layer built for Nigeria and Ghana.
More than recurring payments
Recurring payments move money on a schedule. A Recurring OS handles everything around that movement: how customers authorise payments, how failed collections recover, how teams communicate, and how money is reconciled and settled.
Subby connects the complete recurring-revenue workflow. Customers get clear payment routes and timely follow-up; businesses get collections, retries, nudges, disputes, churn analytics, settlements, refunds, and reporting in one place.
One operating layer
What the Subby Recurring OS can do
Start with the payment rails your market supports, then manage every customer and operational event around the collection from the same system.
Collections Reminders Disputes Churn analytics Settlements Customer management
02
Recovery
Retries and Sweep
Schedule retries around rail behaviour, then use Sweep for multi-account recovery when a payment needs another route.
03
Messaging
Multi-channel nudges
Follow up through the existing messaging stack after reminders, collection attempts, retries, and an overdue notice.
04
Reconciliation
Split settlement
Split each transaction between the right parties and add month-end reporting for finance and operations teams.
05
Merchant sites
Embedded checkout
Let customers start and pay for subscriptions from a checkout embedded in a merchant website.
06
Payment operations
Refunds
Return eligible payments from the same operating environment used to manage customers and collections.
A layer on top of payment rails
What happens when a charge fails
Payment rails move the money. Subby decides what happens around every charge: which rail it runs on, what to do when it fails, when to try again, and when to hand the decision back to the business.
Rails in Nigeria
- Direct debit mandates across two rails
- Embedded checkout on merchant sites
How Subby decides the recovery path
Every failed charge comes back from the rail with a reason. Subby reads that reason and picks the path that fits it.
Rail returns
Insufficient funds
Retry on schedule
The customer’s account is reachable but short. Subby keeps the charge on the same rail, follows the retry schedule, and nudges the customer before each attempt. Sweep can recover the payment from another account the customer has linked.
Rail returns
Rail unavailable
Fail over to the second rail
The problem is the rail, not the customer. Subby routes the charge through the secondary rail instead of waiting for the primary rail to come back.
Rail returns
Mandate revoked
Stop debiting and offer another route
The customer has withdrawn authorisation, so Subby stops attempting the mandate. The customer is asked to re-authorise, and Subby sends a payment link or charges a saved card to complete the payment.
The retry schedule
Retries follow a fixed schedule from the due date, so customers and businesses always know when the next attempt is coming.
Amaka · Weekly laundry plan
Swank Laundry · ₦15,000 due on the 1st
Scheduled attempt Failed Paid Paused Grace period, up to day 60
When automatic retries run out, the business can
Due date · 24 hours later · Day 3 · Day 7
Activity
Press play to follow Amaka’s payment.
Verticals already collecting on Subby
All use cases →Laundry
Swank Laundry
With Subby, Swank transformed everyday laundry into simple prepaid subscriptions, making payments easier for customers and revenue more predictable for the business.
Meal Plans
Hey Kara
Three services, three different workflows, one recurring payment infrastructure. Hey Kara bills meal plans, laundry, and cleaning from a single platform in Uyo.
E-commerce
CeedMart
Laptops, gadgets, solar generators, and security cameras: CeedMart sells on structured instalment plans, with Subby handling the collections across Lagos, Uyo, and Port Harcourt.
Waste Management
Spring Cleaners
Households, estates, and businesses pay for waste collection on a schedule. Subby ties every pickup route to a payment rate and keeps collections on track.
Energy & Fuel
Fonzville
Recurring diesel deliveries to estates, offices, and businesses in Abuja. Subby tracks what was collected, what failed, what is outstanding, and what has settled.
Estate Management
SPDC
SPDC uses Subby to collect service charges consistently, send timely reminders, and track payments across its residential properties in Abuja.
Guides on recurring payments
Guides
Recurring Payments vs Subscriptions: What Nigerian Businesses Actually Need
Recurring payments and subscriptions are related but not the same. Learn when a meal plan, laundry service, or estate dues needs a subscription — and how Subby handles both.
Guides
How to Set Up Recurring Billing in Nigeria
A practical guide to launching recurring billing in Nigeria — local payment realities, failed cards, WhatsApp reminders, payouts, and how providers go live on Subby in about five minutes.
Revenue
Failed Payment Recovery for Subscription Businesses
Involuntary churn kills recurring revenue. Learn how failed payment recovery — retries, reminders, and dashboards — helps subscription businesses keep customers who still want to pay.
Verticals
Subscription Billing for Meal Plans
How meal businesses use subscription billing to cut waste, lock in seats, and collect on time — with lessons from Lunch Park and Green Mile Meals on Subby.
Verticals
How Laundry Businesses Run Prepaid Subscriptions
Prepaid laundry subscriptions turn weekly pickups into predictable revenue. See how Swank Laundry moved customers onto plans with Subby — and what to copy.
Verticals
Recurring Service-Charge Collections for Estates
Estate managers lose weeks chasing service charges. Learn how recurring collections, reminders, and one billing system — as used by SPDC on Subby — raise on-time payments.
Recurring OS FAQ
What is the Subby Recurring OS?
The Subby Recurring OS is the operating layer for recurring revenue. It brings subscription setup, collections, reminders, nudges, payment recovery, disputes, churn analytics, settlements, refunds, and reporting into one product.
How fast can I launch subscription billing on Subby?
Most providers create an account, set pricing and billing cycles, and publish plans in about five minutes. Subby then handles renewals, collections, reminders, and failed payment recovery.
Does Subby work for Nigerian payment realities?
Yes. In Nigeria, Subby supports mandate subscriptions with dual-rail routing and failover, rail-aware retries, Sweep multi-account recovery, payment link and card fallback, multi-channel nudges, split settlements, embedded checkout, and refunds.
What happens when a recurring payment fails?
Subby reads the failure reason from the payment rail and picks a recovery path. Insufficient funds are retried on the due date, 24 hours later, on day 3, and on day 7, with nudges and Sweep recovery. If the rail is unavailable, Subby fails over to the second rail. If the mandate is revoked, Subby stops debiting and offers the customer a payment link or a card payment. After the final retry, the business can pause the subscription or extend the grace period for up to 60 days.
Who uses Subby for recurring revenue?
Estates, gyms, meal plans, insurance and healthcare plans, waste collection, diesel supply, laundry, e-commerce instalment plans, logistics retainers, and community hives. See the use cases library for customer stories.
Launch a subscription plan in five minutes
Put recurring billing, collections, recovery, customer communication, settlements, and reporting on Subby — then grow predictable revenue.