Cancel Flow and Failed Payment Setup on Recharge and Skio

A subscriber leaves in one of two ways. They click cancel, or their card fails and nobody gets it back. Most Recharge and Skio stores I open run both on install-day settings: a cancel flow that leads with a discount, and one failed payment email.

RetainUP sets up both for $1M to $10M subscription brands. We have built 80+ subscription programs on Recharge, Skio, Stay AI and Loop. This page covers what we set up on Recharge and Skio for cancels and failed payments, and the two numbers we report every month: save rate and recovery rate.

What a cancel flow and failed payment setup covers

Five pieces: the cancel flow, the retry schedule, the card update emails and SMS, what happens after the last retry, and a monthly report on save rate and recovery rate. A cancel is active churn. A failed card is passive churn. Each needs its own fix.

Cancel flow on Recharge

Recharge calls its cancel flow Cancellation Prevention. Stores set up after 23 October 2023 get this builder. What we set:

• Reasons in the brand's words, with custom answers. The top three reasons from 12 months of cancels decide the flow.
• One offer per reason. Too much product gets skip, or delay and change frequency. Too expensive gets a swap to a smaller size, or swap and discount. Product didn't work gets contact support or a swap.
• A fallback offer for anyone who turns the first one down, and a one-time discount code, so nobody learns to cancel for money off.
• Conditional branches and A/B paths, so we test one change at a time.
• Response pages that confirm the save in plain words.

One limit to plan around. Survey answers in Recharge stay optional, so you can't force a written answer on "Other". We read the custom answers that do come in each month and turn the common ones into reasons. Skip and reschedule also belong one click from the upcoming charge email, so a subscriber who only wants to delay a box never reaches the cancel screen. The order we use is in pause and skip.

Cancel flow on Skio

Skio's builder gives more room. What we set:

• A splash screen before the reasons, with a skip or pause action. It catches "too much product" before the subscriber picks a reason.
• Sub-reasons under the broad ones. "I no longer use it" splits into never started, found something else, told to stop by a doctor, and life changed. Each gets its own treatment.
• Treatments per reason: skip, pause, swap or a discount.
• Separate flows by order number or total value, so a first-order subscriber and a twelfth-order one see different screens. Multiple flows are in early release, so you ask Skio to turn them on.

The logic for which offer goes to which reason is in cancel flow routing. The full Skio build is in Skio retention setup.

Failed payments on Recharge

Recharge's Failed Payment Recovery sets retry timing with smart retries, and hard declines skip the strategy. What we add:

• The Card Declined email for hard declines, which stays off until you turn it on.
• Klaviyo flows on the Charge processing failed metric, split by decline reason. Expired, invalid or revoked cards get a card update link the same day. Insufficient funds gets quiet retries first.
• For Shop Pay subscribers, Shopify's update link (customer profile, Manage payment methods, Request an update via email) and the five shop.app steps in the email.
• A card expiring email at 30 and 7 days before expiry.

When every retry fails, Recharge cancels the subscription automatically, with the reason “Failed Payment flow max retries”. There is no pause option at that point. So the card update ask has to land before the last retry, and anyone cancelled by a failed card goes into a winback flow of their own. The rest of the Recharge build is in Recharge retention setup.

Failed payments on Skio

Skio's Payment Recovery splits retries into phases, each with its own number of attempts and interval. What we set:

• Three phases, tight in the first week. Skio suggests 7 attempts, 3 days apart, as a first phase.
• Smart Retries on. It moves the timing and keeps your total retry count.
• A one-use discount code on the last phase, as Skio's own guide recommends.
• Klaviyo flows on the Billing attempt failed metric, which carries the error code. An expired card gets an update link. Insufficient funds gets "we'll try again Friday".

Skio says about 15% of failed payments recover with no action from the customer. The rest need the customer to act. When the final attempt fails, Skio counts the subscription as passively cancelled. Older accounts were moved to one phase of 14 daily retries, so check yours.

The retry schedule we run

For bank declines, six attempts: day 1, 3, 5, 7, 10 and 14. For dead cards, no retries. The update link goes out the same day by email and SMS. In our audit data, attempts past nine brought back almost nothing. The table by decline reason is in failed subscription payments.

Results: one save rate, one recovery rate

Save rate: 14.8% to 29.6% on Skio

One client on Skio had a cancel flow saving 14.8% of people who clicked cancel. After six versions, it saves 29.6%, almost 1 in 3. That is about $30K a month in retained revenue, with no new discount. What changed: a benefits splash screen first, the skip prompt ahead of the reasons, two answers for "too expensive", and copy that takes the shame out before the offer. The build is in the cancel flow case study.

Recovery rate: 44% to 70%

One brand's failed payment recovery went from 44% to 70% after we rebuilt its dunning flow: seven touches, with 10% off at the last one.

We count both by orders. A save counts once the subscriber pays the next order. Recovery is failed orders that later paid, over failed orders, each month.

What we track every month

• Save rate by reason and by offer.
• Orders paid after a save, by offer.
• Recovery rate by decline bucket: bank declines, dead cards and setup faults.
• Card updates from the email and SMS, by click.
• Passive cancels as a share of all cancels, set against when subscribers cancel.

If you want your own numbers read first, the free subscription audit scores the cancel flow and dunning among its 48 checkpoints.

Moving apps? Cancel flows and retry rules stay behind. Rebuild them with our subscription app migration checklist, remap the payment emails with the Klaviyo event map, and compare cancel flow and dunning control across apps in our best Shopify subscription app comparison.

FAQ

What is a good cancel flow save rate on Recharge or Skio?

The average cancel flow saves about 1 in 6 people who click cancel, and a strong one saves 1 in 3. Judge it by orders paid after the save, not the save alone.

Can Recharge's cancel flow require a written reason?

It asks for a reason, but answers stay optional by design. Read the custom answers each month and turn the common ones into new reasons.

How many times should Recharge or Skio retry a failed payment?

For bank declines, about six times over 14 days, tight in the first week. For expired, invalid or revoked cards, skip the retries and send the update link the same day.

What happens when the last retry fails?

Recharge cancels the subscription automatically, with no pause option. Skio marks it passively cancelled. Get the card update in front of the subscriber before then, and send the rest to a winback flow.

Do I need Churn Buster or another dunning tool?

Start with the app's own settings, the decline split and the card update emails. Most gaps we find are settings and broken emails. A separate tool is worth testing once you have a few thousand active subscribers.

How long does the setup take?

The cancel flow and dunning go live in week two of our 30-day build, the Subscription LTV Maximizer.

About the author

Rahi Jain

Rahi Jain is a subscription LTV specialist who helps $1M to $10M DTC brands reduce subscription churn and maximize LTV on Recharge, Skio, Stay AI and Loop.

More about Rahi