BackToMe is the compliance infrastructure for the withdrawal right (a European obligation, Directive (EU) 2023/2673, in force since 19 June 2026; in Ireland, enforced by the CCPC under the Consumer Rights Act 2022). Installed with a single line of code, it receives the customer's request, sends them an acknowledgement of receipt by email that they keep, and archives it dated and impossible to alter afterwards for 5 years. Installing the button covers what the law requires and provides solid proof for every request.

If my app redirects to a website for payment, am I concerned?

Yes, as soon as the sale contract is concluded through the app (adding to the basket, checkout, payment in a webview). The criterion is where the contract is concluded, not the underlying technology. If the user completes the purchase on the external site, the button must appear on the site; if they complete it in the app, it must appear in the app.

Do I need two separate buttons: one on the site and one on the app?

No, a single mechanism is enough if it is accessible from both interfaces. The common practice is a shared endpoint (a web page or a native screen) that leads to the same processing procedure. Dated archiving must cover both channels without distinction.

Is the withdrawal button mandatory on mobile apps?

Q: Is the withdrawal button mandatory on mobile apps?

Yes. The button obligation applies to all contracts concluded 'through an online interface', which includes websites and mobile apps (iOS and Android): it is mandatory across the 27 EU member states (Directive (EU) 2023/2673), which requires a permanent feature across every page of the interface, so no exemption is provided for apps. Since 19 June 2026, every merchant app must include a mechanism equivalent to the button.

Do you publish a mobile app that sells to consumers in the EU? Yes, the withdrawal button is mandatory there, exactly as on a website: the obligation targets every online interface, iOS and Android included (Directive (EU) 2023/2673, across the 27 EU member states). What matters is that the contract is concluded at a distance, not the technology of the interface.

Start the free trial →Am I concerned?

0 € today · Cancel in one click · 30-day money-back guarantee

Why the mobile app is not exempt

EU Directive 2023/2673 expressly targets ‘all distance contracts concluded by electronic means’, and the Consumer Rights Directive (2011/83/EU) harmonises the underlying withdrawal right across the 27 member states. The text does not distinguish between a website and an app. A contrary reading would amount to creating a legal grey area for m-commerce, which now represents a major share of e-commerce.

The national rules transposing it require that the button be ‘visible and permanently accessible from every page that lets the user view or modify their orders’. For an app, that means: home screen, product page, basket, order history, user profile.

Three ways to integrate it

The page directly in the app: your app displays the button page hosted by BackToMe, without the customer leaving it. Nothing to change other than an address to point to. Ideal for hybrid apps (Cordova, Capacitor).
A link to the browser: the button in the app opens the hosted page in Safari or Chrome. Compatible with every app, with nothing extra to install. The customer briefly leaves the app.
A custom screen connected to BackToMe: to keep the customer inside your app, you connect your own screen to BackToMe (sending the request, returning the acknowledgement). A little more work, but the most fluid experience.

Special case: hybrid site + app sales

If the same company sells through a website and through an app, a single mechanism is enough provided it is accessible from both interfaces. The common practice is to point both interfaces to the same hosted page. Dated archiving then covers both channels in the same way, which simplifies matters in the event of an inspection by the national regulator (the CCPC in Ireland).

What about marketplace apps (Amazon, Zalando, Vinted)?

It is the marketplace operator that bears the technical obligation for the button, not each third-party seller. The third-party seller, however, remains responsible for actually processing the withdrawal (refund within 14 days). For ‘standard’ merchant apps (a single merchant), the technical and legal responsibility falls on the publisher.

Integrate the button into your app in five minutes

Page in the app, link to the browser or custom screen: BackToMe provides the hosted page and the documentation for all three integration modes. Compatible with iOS, Android and hybrids (React Native, Flutter, Cordova, Capacitor).

See the integration guides

To go further

SaaS and B2C subscriptions

Online software, immediate performance, express consent

Complete withdrawal-button guide

Full text and detailed obligations

Install the withdrawal button

No code, and when to switch to legal mode