Withdrawal button from june 2026: what online portals need to implement now

What the new obligation is really about

At the beginning of 2026, the German legislator reformed consumer and insurance contract law. For operators of digital services, one change is particularly important: the electronic withdrawal function.

The idea behind it is simple: where consumers can conclude a contract online, they should, in many cases, also be able to withdraw from it online — without unnecessary obstacles.

However, it is important to note that the new obligation does not automatically apply to every online portal. It is primarily relevant for distance contracts with consumers that are concluded via an online user interface and for which a statutory right of withdrawal exists. This may include, for example:

• websites
• individual areas of websites
• online portals
• apps

The new requirements will apply from 19 June 2026.

The new withdrawal button: more than just a link in the footer

At the heart of the new rules is a digital withdrawal function — often referred to as a withdrawal button.

This does not mean just any inconspicuous link hidden deep in a help section. Consumers must be able to declare their withdrawal directly online — simply, clearly and without detours.

For the design of the function, this primarily means:

• The withdrawal function should be easy to find and clearly visible.
• It must remain available throughout the entire withdrawal period.
• It should be accessible without unnecessary steps.
• The label should be unambiguous, for example “Withdraw from contract”.

In short: withdrawing online must not become a search exercise.

How the digital withdrawal process should be structured

A button alone is not enough. What matters is a complete, functioning process through which consumers can submit their withdrawal electronically.

A typical process may look as follows:

1. Entry point via the “Withdraw from contract” button

2. Input form to identify the contract

3. Confirmation function

4. Automated confirmation of receipt

The final step is particularly important: once the withdrawal has been submitted, receipt of the withdrawal must be confirmed without undue delay on a durable medium — in practice, usually by email.

This confirmation should include, among other things:

• date and time of receipt
• allocation to the relevant contract
• confirmation that the withdrawal has been received
• where applicable, information on the next steps in the process

As much data as necessary – but as little as possible

The withdrawal process is intended to be deliberately low-threshold. The withdrawal function should therefore be limited to the information that is genuinely required to identify the contract.

Typical minimum information may include:

• name
• contract or order number
• email address
• where applicable, the date on which the contract was concluded

By contrast, the following may be problematic in particular:

• mandatory account creation
• mandatory login where the contract could also be concluded without an account
• unnecessary mandatory fields
• redirects via service or contact forms

The practical guiding principle is: withdrawal must not be more complicated than entering into the contract.

Who is affected — and what companies should review now

The new withdrawal function is not purely an IT issue. It affects legal texts, user journeys, technical processes and the subsequent handling of incoming withdrawals. Companies should therefore first clarify whether and where the new obligation applies at all.

The following checks are particularly important:

1. Clarify the scope of application

• Are there B2C distance contracts?
• Are these contracts concluded via a website, portal or app?
• Does a statutory right of withdrawal exist for the relevant type of contract?

2. Map all contract conclusion journeys

• shop checkouts
• booking processes
• subscription and tariff sign-ups
• in-app contracts
• contracts concluded via customer accounts

In practice, this is often where problems arise: companies review only the classic checkout process, while other digital contract conclusion journeys are overlooked.

3. Implement the withdrawal process technically

• placement of the function
• input form
• confirmation function
• automated confirmation of receipt

4. Update legal texts and mandatory information

• withdrawal instructions
• mandatory information
• references to the electronic withdrawal function
• consistent information in checkouts and emails

5. Test UX, technology and evidence together

• findability of the function
• mobile usability
• usability for logged-in and non-logged-in users
• accessible, low-barrier design
• reliable delivery of the confirmation email
• evidence and documentation of receipt

6. Define internal responsibilities

• Who is responsible for the legal texts?
• Who implements the function technically?
• Who tests the process?
• Who handles incoming withdrawals operationally?

Keep special cases in mind

Even under the new rules, not every contract follows the same requirements. Depending on the product or service, specific features or exceptions may apply to the right of withdrawal.

This may be particularly relevant for:

• digital content or digital services
• customised products
• quickly perishable goods
• sealed hygiene products
• services where performance begins before the end of the withdrawal period

Companies should therefore carefully assess which contracts actually come with a right of withdrawal — and which do not.

Why this topic should not be postponed

The new withdrawal function is not merely a matter of good user experience. Violations may also have regulatory consequences.

The legislative materials provide that certain infringements may be subject to administrative fines. These include, among other things:

• fines of up to EUR 50,000
• under certain conditions, turnover-based fine ranges for larger companies

For operators of digital platforms, this makes the issue clearly more than a UX detail — it is a tangible compliance matter.

Conclusion

From 19 June 2026, it will no longer be sufficient for many B2C portals to merely inform consumers about their right of withdrawal. In many cases, withdrawal must also be possible electronically and without unnecessary obstacles.

The key takeaway: this is not just about adding another button. It is about setting up a proper end-to-end process — from the visibility of the function and confirmation of receipt to consistent legal texts and clear internal workflows.

Companies that now review which contract conclusion journeys are affected, which contracts can actually be withdrawn from and how the new function can be implemented in practice will not only gain greater legal certainty, but also avoid unnecessary implementation pressure later on.