How to win back canceled subscribers on Braintree

A cancelled subscriber on Braintree is still in your vault: customer record, payment methods, transaction history. That makes win-back easier than finding a new customer. But Braintree does not run win-back campaigns, and it has one rule that shapes everything: a cancelled subscription cannot be reactivated. Every returning customer starts a new subscription.

This guide covers how to track cancellations on Braintree, how to restart a subscriber cleanly, and a campaign structure you can run. It sticks to Braintree’s own documentation: Subscription: Cancel, Subscription: Create, Plans, Statuses, Subscription webhooks, Recurring billing advanced settings and Account Updater (all accessed November 2026).

Step 1: capture every cancellation

Win-back timing depends on the date a customer left and why. Braintree gives you the event but not a stored date:

• The subscription_canceled webhook fires when a subscription is cancelled.
• Braintree notes that the cancellation date is not included in subscription search results, and suggests storing it from that webhook.

So the first job is a webhook handler that writes the subscription ID, customer ID, plan, price and cancellation date to your own database. Without it, you cannot tell a customer who left last week from one who left last year, and you cannot build cohorts later.

Also listen to subscription_expired, which fires when a subscription reaches its set number of billing cycles. Depending on how you handle end-of-term cancellations, some of your churn may arrive as expirations rather than cancellations.

Step 2: separate voluntary from failed-payment churn

Braintree cancels subscriptions for two very different reasons:

• The customer asked, through your cancel flow or support.
• Payments failed and your retry settings end with “cancel the subscription” after the last retry.

The webhook looks the same. Mark the source when you cancel (your cancel flow knows), and for system cancellations, check whether the subscription was Past Due just before. The two groups get different messages: a voluntary churner needs a reason to return, a failed-payment churner just needs an easy way to restart with a working card.

Step 3: know the reason

Braintree does not record why a customer cancelled. Capture the reason in your cancel flow and store it with the subscription ID (see how to add a cancel flow to Braintree subscriptions). The reason decides the content and the offer of each win-back email.

Step 4: restarting a subscriber on Braintree

Braintree’s cancel reference is explicit: a cancelled subscription cannot be edited or reactivated, so you create a new one. In practice:

1. Find the customer in the vault by your stored customer ID.
2. Check the payment method. If the old card is still valid, the customer may only need to confirm. If it has expired, ask for a new one first. Account Updater, where enabled, may already have refreshed it.
3. Create the subscription with Subscription: Create, from a plan and the payment method token. Subscriptions always start from a plan.
4. Apply the return offer, if any, as a discount on the new subscription. Discount details are managed in the Control Panel, so create your win-back discount there in advance and apply it by ID.
5. Confirm by email, with the price, any discount and when it ends.

Note from Braintree’s plan docs: changes to a plan apply to new subscriptions only. If you raised prices since the customer left, their new subscription gets the new price unless you set the price or a discount explicitly. Decide whether returning customers get their old price.

Always ask for explicit consent before charging a stored card for a new subscription. The “come back” link should open a page that shows the plan and price and asks the customer to confirm, not start billing on a click in an email.

What the return page should show

The page behind the “come back” link does most of the work, so keep it short and specific to the customer:

• the plan they had, and the plan you suggest if their reason was price;
• the price they will pay, with any discount and the date it ends;
• the card on file (brand and last four digits only) with a clear option to use a different one;
• one confirmation button, and a plain sentence on when the first charge happens.

If the customer picks a new card, save it first, then create the subscription on that new payment method. A customer who has to log in, find billing settings and start again from a pricing page is far less likely to finish.

Step 5: choose the offer by reason

Reason given	Message	Offer
Too expensive	A lower plan, or a limited discount	Discount for the first months, or downgrade
Not using it enough	What others use it for, what changed	Usually none
Missing feature	It shipped (only if true)	None needed
Switched to another tool	What improved since they left	Optional discount
Payment failed	Restart in one click with a new card	None
Closed business, no need	Nothing	Do not email

Keep win-back discounts time-limited and separate from your sales discounts, so you can measure them.

Step 6: timing

A reason-based sequence spaced over three months works for most subscription businesses:

1. Day 30: a short, personal note tied to the reason.
2. Day 60: what changed since they left.
3. Day 90: the offer, if any, with a clear end date.

Failed-payment churners are the exception: contact them within days, while they still expect the service. Stop the sequence as soon as a new subscription is created for the customer, and suppress it for anyone who opted out. Copy ideas in win-back email examples.

Step 7: measure

For each cancel reason and each email:

• the share of churned customers who started a new subscription within 120 days;
• the revenue of those subscriptions, net of discounts;
• how many are still active three months later.

Because Braintree gives returning customers a new subscription ID, link old and new subscriptions through the customer ID in your own data. Otherwise a returning customer looks like a new one, and your win-back results disappear into new sales.

Common mistakes

• Not storing the cancellation date. It is not in search results; without the webhook, it is gone.
• Emailing failed-payment churners as if they chose to leave.
• Charging a stored card without confirmation.
• Ignoring price changes, so a returning customer is surprised by the new price.
• Mixing win-back revenue into new customer revenue.

Doing this with NoChurn

Braintree keeps the vault, the new subscription and the charge. NoChurn follows Braintree webhooks, stores each cancellation with the reason from its cancel flow, and sends win-back emails at day 30, 60 and 90 written from that reason, with a link to come back. Failed-payment churn is handled separately with AI-written recovery emails you review and a hosted page to update the payment method, and each customer has a churn score from 0 to 100. See NoChurn + Braintree.