How to win back canceled subscribers on Mollie

When a customer cancels a Mollie subscription, the subscription is over for good: Mollie does not let you update a cancelled subscription. Winning that customer back means creating a new one. Whether they have to go through checkout again depends on one thing you can check in the API: whether they still have a valid mandate.

This guide covers what Mollie leaves behind after a cancellation, the two ways to restart a subscription, how to time and word win-back messages, and how to track whether they work. It sticks to Mollie’s documentation: Get subscription, Create subscription, Update subscription, List mandates, Revoke mandate, Create payment link and the Recurring payments guide (all accessed November 2026). Field descriptions were also checked against Mollie’s official Node.js API client.

What a cancellation leaves behind

Object	After cancellation
Subscription	status is canceled, canceledAt is set, there is no nextPaymentDate, and it cannot be updated
Mandate	A separate object with its own status. Check it rather than assume
Customer	Unchanged, with their payment history

The mandate is what decides how easy a return is. Mollie mandates have three statuses: valid, pending and invalid. Mollie’s documentation describes revoking a mandate as cancelling its subscriptions, not the other way round, but some events do revoke the mandate:

• Revoking it through the API cancels all subscriptions connected to it.
• Mollie’s help center says a mandate is revoked after a SEPA reversal.
• Mollie’s recurring payments guide says that when a subscription with a fixed mandate is cancelled for certain failure reasons, the mandate is revoked as well.

So before any win-back message, list the customer’s mandates and look at their status. That tells you which of the two paths below applies.

Two ways back

Path 1: the customer still has a valid mandate

Mollie lets you create a subscription for a customer with a pending or valid mandate, without a new checkout. Technically, a returning customer could be restarted with one API call.

That does not mean you should do it silently. The customer cancelled. Charging their account again needs their clear agreement, given at the moment they come back, for the amount and interval they are agreeing to. A practical flow:

1. The win-back email links to a page in your app that shows the plan, the price and the first charge date.
2. The customer confirms with one button.
3. Your server creates the subscription with that amount, interval and startDate, on their existing mandate (set mandateId if you want to tie it to that one), and records the confirmation.
4. Show and email a confirmation, including how to cancel again.

If the mandate is a SEPA Direct Debit mandate and the customer has not been charged for a long time, also make sure they recognise the description that will appear on their bank statement. An unrecognised debit is a common reason for a reversal.

Path 2: no valid mandate

When the mandate is revoked or invalid, the customer has to pay through checkout again. Mollie’s payment links are a good fit:

• Set sequenceType to first. Mollie’s reference says a mandate is then established right after the customer pays. With the default, oneoff, no mandate is created.
• Set customerId to the existing Mollie customer, so the mandate is attached to them.
• Set an expiresAt date if the offer is time-limited. Without one, the link does not expire.
• Leave reusable at its default (false) so the link is used once.

When the link is paid, fetch its payment to get the new mandate, then create the subscription with a startDate after the period the first payment covered. The first payment can be the first period itself, at the win-back price if you offer one.

What to offer, and when

The cancel reason is the best guide to both the message and the timing. A schedule that works for many subscription businesses:

Day after cancellation	Message
30	What changed since they left, matched to their reason. No discount yet.
60	A specific offer if their reason was price; otherwise a feature or fix that addresses the reason.
90	A last, short note with a direct way back. Then stop.

Matching the reason matters more than the discount:

• Too expensive: a lower price for a few months. On Mollie, a changed amount applies to all future charges, so either create the subscription at the offer price and update it later (tell the customer the date and the full price), or limit the offer with times and create a follow-up subscription.
• Not using it: a cheaper plan or a longer interval, such as 3 months.
• Missing feature or technical problem: only write if it is fixed or shipped. Say what changed.
• Switched to a competitor: one honest message about what you do differently, then stop.

Do not write to customers who asked you not to, and keep win-back emails apart from transactional messages in your consent records.

Before you hit send

A short check for each former customer, every time:

1. Is the mandate still valid? List the customer’s mandates just before sending, because a reversal or revocation may have happened since they cancelled. The answer decides which link goes in the email.
2. Did they leave on good terms? Skip anyone whose last payment was reversed or who is in a dispute with you until that is resolved.
3. Did they opt out? Check your consent records, not just your email tool.
4. Is the offer still true? If the email promises a price, make sure the subscription you will create, or the payment link amount, matches it exactly.
5. Does the link work for them? Open it in test mode with a test customer: payment link, mandate, new subscription, confirmation email.

Track it properly

• Store the cancellation with its date, reason and the last mandate status.
• Tag the returning subscription in its metadata, for example with the campaign and the original cancellation date. Mollie forwards subscription metadata to each payment it creates, so you can report on revenue by campaign.
• Measure months retained, not just restarts. A customer who comes back for one discounted month and leaves again was not won back.
• Watch reversals. A win-back that leads to SEPA reversals means the consent step was not clear enough.

Doing this with NoChurn

Mollie keeps the mandates, the payments and the new subscription. NoChurn adds the win-back side: emails at day 30, 60 and 90 written from the cancel reason the customer gave in the cancel flow, with a link to come back. Reasons come from NoChurn’s cancel flow, which has a one-click cancel always visible, and returns are tracked against the churn score from 0 to 100. See NoChurn + Mollie.