How to pause subscriptions in Recurly
How pausing works in Recurly Subscriptions: pause cycles, resume, webhooks, what cannot be paused, annual plans, coupons and offering a pause in a cancel flow.
A pause is often the right offer for a customer who wants to cancel because they will not use the product for a while: they keep their account and you keep the customer. Recurly supports pausing natively, but it has a set of rules that are easy to miss, especially on annual plans and with coupons. This guide explains how pausing works in Recurly Subscriptions and how to offer it well.
It sticks to Recurly’s own documentation: pause subscription, pause subscriptions: things to consider, the subscription management guide, subscription notifications, the subscription lifecycle webhook guide and the webhooks overview (all accessed November 2026). Recurly Commerce, a separate product, has its own pause settings; this guide is about Recurly Subscriptions.
How a pause works
You pause through the Pause Subscription endpoint with remaining_pause_cycles, the number of billing cycles to skip (pause subscription). Recurly’s examples use 10, which freezes billing for ten cycles. The mechanics:
- It starts at the next billing date. Recurly does not support mid-cycle pauses. The customer keeps the period they already paid for.
- Each skipped renewal counts down. At every billing date during the pause,
remaining_pause_cyclesdrops by one and Recurly sends a renewal-skipped notification. - It ends on its own. When the count reaches zero, the subscription resumes: Recurly starts a new billing cycle and generates an invoice immediately, charged to the stored payment method if collection is automatic.
- You can end it early. Admins can resume from the subscription or account page, and the API has a resume endpoint. Resuming early also starts a new billing cycle with an immediate invoice.
There is no separate “pause indefinitely” setting. Recurly’s own pause notes mention that some merchants set a very high cycle count instead. The docs we found do not state a maximum.
What cannot be paused
Recurly’s considerations page lists the limits:
| Situation | What Recurly says |
|---|---|
| Trial, canceled, expired or failed subscriptions | Cannot be paused; only active subscriptions can |
| Customer in dunning or with past-due invoices | Resolve that first |
| A pause already scheduled or running | Concurrent pauses are not supported; one must end first |
| Immediate subscription change during a pause | Cancels the pause |
| Usage-based add-ons | Usage logged before the pause is invoiced on the pause date; no usage can be logged during the pause |
The last two matter in practice. If a support agent upgrades a paused customer, or your app makes an immediate change, the pause disappears. And if you bill usage, check that nothing in your product logs usage for paused accounts.
Annual plans: postpone instead
A pause skips whole billing cycles. On an annual plan, one cycle is a year. Recurly’s example: a customer six months into an annual plan asks for a one-month break; pausing one cycle schedules a full one-year pause starting at the next annual renewal.
For short breaks on annual plans, Recurly recommends postponing the next bill date instead, using the Modify (update) Subscription endpoint. That extends the current period rather than skipping a year.
Coupons keep running
Recurly says coupons are not paused with the subscription: their duration keeps running during the pause. If you saved a customer with “50% off for three months” and they then pause for three months, the discount may be used up before they are billed again. Either offer the discount after the pause, or choose one offer, not both.
Other side effects
- Term dates. Recurly notes that term renewal dates do not update during a pause.
- Reporting. Paused subscriptions count as active in Recurly analytics but add no MRR, since no invoices are generated. Track them separately when you look at retention.
- SCA regions. Recurly’s pages advise resuming through the API with proper customer authentication in SCA regions rather than from the Admin Console. The two pages that mention it do not describe the issue identically, so test resume in your region before you rely on it.
Who can pause
Recurly’s docs say customers cannot pause or resume their own subscription from Hosted Account Management. That page shows the paused status, but the pause itself has to come from:
- your support team, in the Admin Console;
- your own app or account page, through the pause and resume endpoints, which is the only self-serve option in Recurly Subscriptions;
- Recurly Commerce, whose Customer Portal has a pause toggle, if you sell through that product.
If you want pause to be part of a cancel flow, you need to build that step or use a tool that does.
Webhooks
Recurly sends notifications for each stage of a pause (subscription notifications): a pause scheduled, a pause modified, a pause canceled (the pause fields go back to null), the subscription paused, each skipped renewal, and the subscription resumed, sent when it goes from paused back to active with a new billing cycle.
Recurly’s pages name these events in different ways. The notifications reference uses titles such as “Scheduled subscription pause” and “Subscription pause canceled”, the lifecycle guide uses identifiers such as pause.scheduled and renewal.skipped, and another page uses subscription.paused and subscription.resumed. Check the names in the payloads your account actually receives. Recurly also says webhooks are configured in the Admin Console, not by API, that you should confirm state through the API before updating your systems, and that your endpoint must accept duplicates and out-of-order events.
Offering a pause well
- Offer it for the right reason. “I won’t use it for a while”, “seasonal business”, “budget freeze until next quarter”. It is a poor answer to “the product doesn’t do what I need”.
- Check eligibility first. Only show the offer for active, non-trial subscriptions that are not in dunning and have no pause scheduled.
- Choose the right tool for the plan. Pause cycles for monthly plans; postpone the next bill date for short breaks on annual plans.
- Say exactly what happens. “Your subscription is paused from 12 December for 2 months. You will be billed again on 12 February.” Read the dates from Recurly’s response.
- Remind them before billing resumes. Resuming creates an invoice right away. Send a reminder a few days before, with a link to cancel if they no longer need the product.
- Keep cancel visible. A pause offer sits next to “Cancel now”, never in its place.
- Track what happens after. Look at how many paused customers resume and keep paying, and how many cancel at the end.
Doing this with NoChurn
NoChurn’s cancel flow can offer a pause, alongside a coupon or a plan change, and applies the accepted offer to the Recurly subscription; a one-click cancel stays visible at every step, hosted or headless through the API. It follows Recurly’s webhooks, so customers who cancel later get win-back emails at day 30, 60 and 90 based on their reason, and the 0–100 churn score takes their history into account. Billing, invoicing and the resume charge stay in Recurly. NoChurn is free under $300 MRR. See NoChurn + Recurly.