subbySubby's subscription engine keeps plans, renewal dates and subscriber state consistent across markets. The available payment rail determines how each charge is completed. Design checkout, renewal messaging and recovery around the collection mode available to the subscriber.
Contact Subby support to confirm which countries and rails are enabled on your account.
Collection models
| Collection model | Automatic renewal | Subscriber experience |
|---|---|---|
| Authorised debit mandate | Yes | Authorise once; Subby can debit scheduled renewals within the mandate rules |
| Subscriber-initiated collection | No | The subscriber completes each cycle after a reminder |
Nigeria uses authorised debit mandates. Other markets may use subscriber-initiated collection through virtual-account or mobile-money instructions.
Automatic debit
Checkout collects an authorisation mandate. Once active, Subby can attempt renewal charges on schedule, apply retry rules after a failure and ask the subscriber to re-authorise if the mandate expires or reaches its ceiling.
Your integration should still handle mandate_pending, mandate.active, failed charges and mandate exhaustion. Read Subscription lifecycle and Webhooks for the corresponding states and events.
Subscriber-initiated collection
Subscriber-initiated collection means the subscriber must take action for every payment. Checkout can present virtual-account or mobile-money instructions and wait for confirmation. Reminders should say plainly that the payment is not automatic.
This changes product behavior:
- A renewal becomes due before it becomes paid.
- Nudge volume is likely to be higher than in an automatic-debit market.
- Access and service-grace rules should allow time for subscriber action.
- The merchant should monitor reminder delivery and payment conversion by country.
Build for rail differences
Do not infer available actions from the country alone. Read the collection mode and capabilities returned by Subby, show unavailable actions with an explanation, and keep retry schedules within the active rail's rules.
Use Subscription checkout for the integration options and Failed-payment recovery for country-aware recovery planning.
Frequently asked questions
Is Subby a multi-country payment platform?
No. Subby is a Subscription OS. Collection models differ by rail, but the subscription object, lifecycle events and recovery policy stay in Subby.
How should I design for a market without automatic debit?
Treat a renewal as due until the subscriber pays. Allow time before restricting service, and expect higher nudge volume than in an automatic-debit market.