subbySubby is a Subscription OS powered by a subscription engine. It is the operating layer for recurring businesses: plans, subscribers, mandates, renewals, recovery, communication and reporting stay connected in one system.
Subby is not a payment engine, payment gateway or payment processor. Supported payment rails collect subscription charges. Subby runs the subscription lifecycle around those charges so your team does not stitch billing, messaging and support tools together.
What is a Subscription OS?
A Subscription OS is the system a business uses to create, operate and improve subscription relationships. The subscription engine keeps the plan, subscriber, mandate, renewal schedule and recovery state in sync, then notifies your product through signed lifecycle events.
What Subby can support
- Plans, customers and subscriptions — Configure plans, manage customers and act on every subscription state.
- Failed-payment recovery — Combine retries, multi-channel nudges and escalation rules in one recovery workflow.
- Subscription checkout — Start subscriptions through embedded or hosted checkout with country-aware collection methods. Embed with @mysubbyapp/checkout, the WordPress plugin or the Shopify app.
- Subscriber self-service — Let subscribers pay, update mandates, pause or cancel through secure links.
- Money and reporting — Trace settlements to charges, monitor usage and reconcile fees.
- Developer and team operations — Manage API keys, webhooks, sandbox data, usage and team access.
- Country and rail coverage — See how automatic debit and subscriber-initiated collection work with the subscription engine.
How the subscription engine works
- Create a plan from a vertical template or a generic plan.
- Add a customer and send them through embedded or hosted checkout.
- Collect and activate the customer's payment mandate through a supported payment rail.
- Start the subscription and receive signed lifecycle webhooks.
- Let the subscription engine schedule renewals, retry failed charges and send configured nudges.
- Give the subscriber a secure self-service and pay-now path.
- Review subscription health, recovered revenue, settlements and API usage.
Product surfaces
| Surface | Purpose | Representative scope |
|---|---|---|
| Merchant dashboard | Operate subscriptions | Plans, customers, subscriptions, mandates, recovery and settlements |
| Subscription checkout | Enrol and authorise subscribers | Embedded element, hosted checkout and country-specific payment instructions |
| Subscriber portal | Reduce support work | Pay now, update a mandate, view history, pause or cancel where allowed |
| Developer platform | Integrate and observe | Keys, webhooks, logs, sandbox, API usage and documentation |
Designed for different recurring businesses
Plan templates exist for waste collection, diesel delivery, estates, gyms, laundries and meal plans, plus a generic model. A template can prefill the amount, billing cycle and service fields while leaving every field editable. Each business gets a relevant starting point without a separate billing system.
For the integration path, start with the quickstart, then review the subscription lifecycle and API reference.
Frequently asked questions
Is Subby a payment engine or payment gateway?
No. Subby is a Subscription OS. Its subscription engine coordinates recurring plans, subscriber state, billing schedules, retries, reminders and lifecycle events. Supported payment rails handle the movement of money.
What can I manage with Subby?
You can manage plans, customers, subscriptions, mandates, renewal schedules, failed-payment recovery, subscriber self-service, webhooks, settlements and subscription reporting from one operating layer.
Can Subby work inside my existing product?
Yes. Use the Subby API and webhooks to connect the subscription engine to your product, or use hosted checkout and the merchant dashboard for a lighter integration.