subscriptions that actually renew.
Recurring built for African markets, on the rails your customers actually hold. Self-healing when a charge misses.
Book a technical walkthroughnetwork-native mandates, per market.
Card-on-file where cards work. Mandate-based collection where they don't. Every rail behind one integration.
own the schedule, or keep yours.
Settld's billing engine can drive the schedule, or your existing engine keeps it and calls Settld to execute each charge. Never rip out what already works.
retries and updates over channels customers read.
Smart retries and payment-method updates over channels people actually open, including WhatsApp. Fewer silent failures.
consent, notice, one-click cancel.
Consent captured before the first charge. Renewal notice before every charge. Cancellation that takes one click.
three models of recurring, and which one you are actually getting
Cards renew themselves. Mobile money does not, unless the network provides a way to ask once and charge many times. Across our markets that comes in three shapes. Customer-side standing orders, like M-Pesa's, where the amount is fixed at creation. Merchant-initiated collection against a pre-approved mandate, like MTN MoMo's, the closest thing to card-on-file. And markets where neither exists yet, where anything sold as recurring is really a fresh payment prompt every cycle. We tell you which model applies per market before you build revenue forecasts on it, because a renewal that depends on a monthly tap is not a renewal.
recovery built for wallets, not just cards
Card dunning logic assumes a card to retry. Wallets fail differently: the mandate is alive but the balance is short. So recovery here is about timing and channel. Retries aligned to when people are actually paid. Payment-method updates and reminders over channels customers really open, including WhatsApp. A failed charge becomes a paused subscription with a clear path back, not a silent cancellation.
frequently asked questions
Yes. Your engine keeps the schedule and calls Settld to execute each charge under mandate. Or our billing engine drives the schedule end to end. Never rip out subscription logic that already works.
Not where real mandates exist. Consent is captured once, before the first charge, and renewals run against it with notice before each charge. Where a market only supports payment prompts, we say so upfront rather than dressing it up as recurring.
Recovery starts, tuned to the rail. Card failures get tokenised refresh and disciplined retries. Wallet failures get payday-aware timing and a reminder over a channel the customer reads. Cancellation stays one click throughout, which protects your dispute ratio.
ready to sell into africa without the drag?
Book a technical walkthrough