All articles
Policy watch8 min read

The EU withdrawal button has been law since June 19, and your app's web checkout is the part that needs one

Since June 19, 2026, EU law requires a 'withdraw from contract here' button wherever consumers can withdraw from an online purchase. Apple and Google run it for store purchases. Your own web checkout is yours, and here's what it costs and how to build it.

A person in a European cafe checking a subscription on their phone next to a laptop checkout page, the two places an EU withdrawal button can apply

Key takeaways

  • Directive (EU) 2023/2673 adds Article 11a to the EU Consumer Rights Directive, and since June 19, 2026 online traders must offer a withdrawal function labelled "withdraw from contract here" or an unambiguous equivalent.
  • The EU withdrawal button must stay available for the whole withdrawal period, which is usually 14 days, and it only matters for contracts that carry a right of withdrawal in the first place.
  • For App Store purchases in the EU, Apple Distribution International is the merchant of record, and Apple's terms let customers cancel within 14 days through a "Withdraw Transaction" button in Purchase History.
  • Google Play asks developers to classify each EEA product as Digital Content or Service. Digital Content excludes the right of withdrawal, while Service products are eligible for a refund within 14 days of purchase.
  • An app that sells through its own web checkout is the trader for that sale, so the developer has to build the withdrawal button, the "confirm withdrawal" step and the acknowledgement of receipt.
  • A statutory withdrawal needs no reason from the consumer, so there's no evidence to send and no case to argue. The only lever is how the sale was set up at checkout.
  • Under Article 24 of the Consumer Rights Directive, coordinated cross-border enforcement must allow maximum fines of at least 4% of the trader's annual turnover, or at least EUR 2 million where turnover data isn't available.

The EU withdrawal button became mandatory on June 19, 2026, and it's easy to file it under Apple's and Google's problem. For purchases made inside the App Store or Google Play, that's mostly right. For anything you sell through your own website, it isn't. Directive (EU) 2023/2673 made every online trader that sells to EU consumers offer a labelled, always-visible way to withdraw from a contract, and when your web checkout takes the payment, you're the trader.

The rule arrived without much noise in the app world. It sits in a directive whose title is about financial services, it added a single article to the Consumer Rights Directive, and member states were supposed to write it into national law by December 19, 2025. Most of the coverage came from ecommerce and retail law firms, even though more and more app developers now sell subscriptions and currency on the web.

What the EU withdrawal button actually requires

Article 11a is short and unusually specific. It doesn't just say withdrawal must be easy. It names the label, the steps and the receipt.

RequirementWhat Article 11a says
Label"withdraw from contract here" or an unambiguous corresponding formulation, easily legible
AvailabilityContinuously available throughout the withdrawal period, prominently displayed and easily accessible
Online withdrawal statementLets the consumer provide or confirm their name, details identifying the contract, and the electronic means for the confirmation
Confirmation stepA function labelled only "confirm withdrawal" or an unambiguous equivalent
AcknowledgementSent on a durable medium without undue delay, including the content and the date and time of submission
TimelinessA statement submitted before the withdrawal period expires counts as on time

The refund deadline isn't new. Article 13(1) of the Consumer Rights Directive already requires the trader to reimburse all payments without undue delay and no later than 14 days after being told about the withdrawal.

Does the button apply when there's no right of withdrawal?

No. Recital 37 of the directive ties the obligation to distance contracts that are subject to the right of withdrawal under the Consumer Rights Directive. K&L Gates reads it the same way, saying the button applies where a statutory right of withdrawal exists for the goods or services offered. That makes the real question for an app developer whether your sale still carries a withdrawal right, and that depends on how checkout was built.

Do developers outside the EU have to comply?

Yes, if they sell to EU consumers. K&L Gates notes that the obligation doesn't turn on where the trader is established, and it names mobile applications as one of the channels in scope. A studio in Texas selling annual plans to buyers in Germany through its own site is covered.

Who builds the EU withdrawal button: Apple, Google or you

Who has to build it follows who sold the thing. Here's how the three common sales paths split.

Where the sale happensWho runs the withdrawal pathWhat the developer controls
App Store in-app purchase, EU storefrontApple. Apple Distribution International is the merchant of record, and customers use "Withdraw Transaction" in Purchase HistoryNothing in the flow itself
Google Play purchase, EEAGoogle Play, through its own withdrawal formThe Digital Content or Service classification of each product
Your own web checkout or payment linkYou, as the traderEverything: the button, the statement, the confirmation and the refund

Apple's terms for EU customers say a customer may cancel within 14 days of receiving the receipt without giving any reason. They also set two limits. A subscription can only be cancelled after the initial subscription, not at each renewal, and an order for content can't be cancelled once delivery has started at the customer's request with an acknowledgement that the right is lost.

The Google Play setting most teams set once and forgot

Google Play Console asks for a Tax and compliance classification on every paid app, in-app product and subscription that can be distributed in the EEA. Google's own help page states the consequence plainly. Products classified as Digital Content have the right of withdrawal excluded. Products classified as a Service are eligible for a refund within 14 days of purchase. Google also says that if you're in doubt, you can classify the product as a Service.

That fallback is the expensive choice for many apps. A changed classification only applies to future transactions, and Google blocks new multiline subscriptions that mix the two classifications, so it's worth checking each product now rather than after a spike in 14-day refunds.

What the EU withdrawal button costs in money

The button doesn't create new refunds on its own. It removes friction from refunds the law already allowed, so more of them get used. Whether that hurts depends on what you'd already paid for by the time the money goes back.

Take a hypothetical AI photo app selling a EUR 9.99 monthly plan on its web checkout. A new subscriber generates 300 images in the first nine days, and each one costs about EUR 0.02 in GPU time and model API calls, so EUR 6.00 of compute has already been spent. On day nine, they press the button.

How the checkout was set upWhat the trader refundsWhat the trader keeps of EUR 9.99Compute already spent
No express request to start during the withdrawal periodEUR 9.99, since Article 14(4) says the consumer bears no costEUR 0.00EUR 6.00 lost
Express request to start, service contract, Article 14(3)EUR 9.99 minus an amount in proportion to what was provided, about EUR 3.00 for 9 of 30 daysAbout EUR 3.00EUR 6.00, half covered
Digital content with express consent, acknowledgement and confirmation, Article 16(m)No statutory withdrawal right applies once supply has begunEUR 9.99EUR 6.00 covered

Multiply that across a month of EU web sales and the difference between the first row and the others is your compute bill, plus any creator payouts, licensing royalties or payment processing fees you paid on sales that came back. Check whether your payment provider returns its fee on a refunded charge.

Can you skip the button and take the risk?

You can, but the numbers aren't in your favor. Article 24 of the Consumer Rights Directive requires member states to allow maximum fines of at least 4% of the trader's annual turnover in the member states concerned when penalties come out of coordinated cross-border enforcement, or at least EUR 2 million where turnover information isn't available. National rules decide the actual amounts, and national wording can differ.

How to build the EU withdrawal button on your own checkout

The text tells you most of what to build. Treat it as a spec, not a style guide.

Put the button where the consumer already is

  • Label it "withdraw from contract here" in the consumer's language, or an equally clear phrase, and keep it visible on the account or billing page for the full 14 days.
  • Don't hide it behind a sign-in wall. K&L Gates reads Article 11a as barring a requirement to log in or authenticate before using the function.
  • Prefill the statement with the consumer's name, the order or subscription it applies to, and the email address for the confirmation, and let them edit it.
  • Finish with one button labelled "confirm withdrawal" and send an email that repeats what was submitted, with the date and time.

Fix the consent at checkout

The table above shows the money is decided at checkout, not at withdrawal. If your product starts delivering right away, collect an express request to start during the withdrawal period, and for digital content add the acknowledgement that the right is lost once supply begins, followed by a confirmation on a durable medium. Pre-ticked boxes won't do it. The consumer has to act.

Treat every withdrawal as a refund in your data

  • Revoke access and reverse any currency granted on the same event that issues the refund.
  • Record withdrawals next to store refunds, tagged by channel, so your EU refund rate includes the sales you process yourself.
  • Refund within 14 days of the statement, as Article 13(1) requires, and keep the acknowledgement email as your record.
A developer desk with a checkout flow on screen and a highlighted legal text, the setup behind an EU withdrawal button on a web checkout

Frequently asked questions

When did the EU withdrawal button become mandatory?
The EU withdrawal button became mandatory on June 19, 2026. Directive (EU) 2023/2673 required member states to adopt the rules by December 19, 2025 and apply them from June 19, 2026.
Do I need a withdrawal button for App Store or Google Play in-app purchases?
No, not inside the store flow. Apple Distribution International is the merchant of record for App Store purchases in the EU and offers a "Withdraw Transaction" button, and Google Play runs its own withdrawal form. Your job on Google Play is classifying each product as Digital Content or Service.
What does the EU withdrawal button have to say?
The EU withdrawal button has to say "withdraw from contract here" or an unambiguous equivalent, in an easily legible way. The final step must be labelled only "confirm withdrawal" or an unambiguous equivalent.
Should I classify my Google Play product as Digital Content or Service?
Classify it by what it actually is under EU law, since Google says Digital Content excludes the right of withdrawal and Service products are eligible for a refund within 14 days of purchase. Google suggests Service when in doubt, and a change only applies to future transactions.
Can I keep part of the payment when a customer withdraws from a subscription?
Yes, on your own checkout, if the customer expressly asked for the service to start during the withdrawal period. Article 14(3) of the Consumer Rights Directive then lets you keep an amount in proportion to what was provided. Without that request, Article 14(4) says the customer bears no cost.

Sources and further reading

RefundHalt

The refund autopilot for the App Store and Google Play

Keep reading

The next refund request is already on its way.

Set up RefundHalt in the time it takes to read another support email about a refund you didn't get to contest.