The EU Withdrawal Button: A New, Separate Cancellation Requirement Since June 2026

If your cancellation flow already handles the moment someone decides to leave, you might assume you're covered here. You're probably not. Since June 19, 2026, EU law has required a second, separate mechanism — a dedicated withdrawal button — that has nothing to do with your regular cancel flow and everything to do with the first 14 days after someone signs up.

The rule comes from Directive (EU) 2023/2673, which technically started life as an update to the EU's distance-marketing-of-financial-services rules but ended up amending the general Consumer Rights Directive (2011/83/EU) as well — the same directive that already gives EU consumers a 14-day cooling-off period on most things they buy online. Member states had to transpose it into national law by December 19, 2025, and the obligation itself applies as of June 19, 2026. Germany has already implemented it as the "Widerrufsbutton." France transposed it under its own consumer code. Ireland missed the December deadline and has since received a formal letter of notice from the European Commission — a reminder that enforcement readiness isn't uniform across the bloc even though the underlying obligation is.

What Article 11a actually requires

The core requirement is narrow and specific: a clearly labeled electronic button or link — wording like "Cancel my contract" or "Withdraw from contract" is what regulators expect, not something vaguer — placed on the same online interface where the consumer entered into the contract, and reachable throughout the entire withdrawal period. You can't bury it three menus deep, and you can't require a support ticket, a phone call, or a login to a portal the consumer doesn't already have credentials for.

Clicking it triggers a two-step confirmation, not an instant cancellation. First, the consumer confirms they want to withdraw and supplies enough detail to identify which contract or order they mean — name, and something that ties back to the specific subscription or purchase. Second, you're required to send an acknowledgment of that withdrawal request on a durable medium, which in practice means an email the consumer can keep, not just an on-screen confirmation that disappears when they close the tab.

We covered the FTC and California columns in detail in our FTC click-to-cancel guide — worth reading alongside this one if you sell into both the US and the EU, because you'll need both mechanisms live at once, and they answer different questions. The US rules are about not obstructing an existing customer who wants out. The EU withdrawal button is about giving a brand-new customer an unambiguous, low-friction way to undo a decision they made in the last two weeks.

Why this isn't the same thing as your cancel flow

A subscriber who withdraws under Article 11a isn't going through your normal churn funnel. They're not seeing your retention offer, they're not answering a cancellation survey, and legally, they shouldn't have to click through either one before the withdrawal takes effect — the whole point of the cooling-off period is that it's unconditional. If your only cancel path routes every request through a save-flow with an offer screen and an optional reason field, that flow satisfies neither the "clearly labeled" nor the "not more burdensome than sign-up" language regulators are reading into this rule when the request lands inside the first 14 days.

The practical fix isn't building a second full flow. It's making sure the withdrawal button, wherever it lives, resolves the contract without forcing the consumer through retention logic first — you can still show them an offer afterward by email if you want, just not as a gate in front of the button itself.

That 379-day figure isn't a rounding error or a scare number — it's the existing Consumer Rights Directive mechanism for any trader who fails to properly inform a consumer of their withdrawal right, now extended in guidance to cover a missing or broken withdrawal button. Get it wrong, and every EU consumer who signed up during the non-compliant period effectively keeps the right to walk away and get their money back for over a year, not two weeks. That's a very different liability calculation than a single fine.

Where this hits Stripe billing specifically

Stripe's customer portal and default emails don't ship a purpose-built Article 11a withdrawal button out of the box — the portal's cancel link is built around ongoing subscription management, the same one we described in our Stripe cancellation flow guide, not the two-step, durable-medium-acknowledgment flow the directive spells out. Stripe has published country-specific guidance for merchants on this (Germany and France so far), which tells you two things: enough of their customer base asked about it that it was worth writing, and the fix on their end isn't a toggle you flip in the dashboard.

In practice, that means building the acknowledgment step yourself — capturing the withdrawal request, firing a transactional email through whatever you already use for receipts, and logging enough detail (timestamp, contract identifier, consumer name) to prove compliance if a regulator ever asks. None of this has to touch your existing subscription-management code. It's closer to an audit trail bolted onto the signup flow than a rebuild of your billing logic.

What to check this week if you have EU consumers

• Confirm it's B2C-relevant first. If every signup on your product runs through a verified company account, this doesn't apply to you. If individuals can self-serve with a personal card, it does.
• Find or build the withdrawal button. It needs to sit on the same interface used to sign up — your app, your billing page, wherever that is — and stay reachable for the full 14 days, not just on a confirmation email that gets archived.
• Wire up the two-step confirmation. A single click that immediately cancels doesn't satisfy the requirement any more than a hidden button does — you need the confirm-then-acknowledge sequence, with the acknowledgment sent on a durable medium.
• Separate it from your save flow. Don't route withdrawal requests through the same offer-and-reason gate you use for later-stage cancellations — that pattern is exactly what regulators are watching for.
• Check your actual transposition jurisdiction. Enforcement details — exact penalty caps, which authority handles complaints — vary by member state, since this is a directive each country implements on its own timeline, not a regulation that applies identically everywhere.

If you're already running a purpose-built cancellation flow for the US side of your business, the honest framing is that this is additive work, not a replacement for it. The two rules solve different problems for different windows of the customer relationship, and a subscriber who withdraws in week one was never going to show up in your churn numbers the same way a subscriber who cancels in month eight does — worth keeping that distinction in mind if you're using a churn calculator to track cancellation trends, since lumping cooling-off withdrawals in with real churn will understate how well your product is actually retaining people past the point where anyone's still deciding whether to keep it.

Frequently asked questions

Stop losing subscribers today

One script tag. One function call. A live cancellation flow in under 10 minutes.