What § 312k BGB requires in detail
The provision applies when consumers can conclude a contract through a website that creates an ongoing obligation and commits the business to a service in return for payment (§ 312k(1) BGB). Typical examples are subscriptions, memberships, software plans and maintenance or supply agreements. Whether the individual contract was concluded online does not matter: according to the legislative explanatory memorandum, what counts is whether the business enables online conclusion of the contract at the time of cancellation (Bundestag printed paper 19/30840). The obligation therefore also covers contracts concluded before July 1, 2022 (vzbv).
The statute describes a two-stage process, and each stage comes with its own requirements:
- Cancellation button: labeled in an easily legible way with nothing other than “Verträge hier kündigen” (cancel contracts here) or an equally unambiguous wording (§ 312k(2) BGB).
- Confirmation page: The button leads directly to it, and the page asks for the cancellation details, from the type of cancellation to the address for the electronic cancellation confirmation (§ 312k(2) BGB).
- Confirmation button: labeled “jetzt kündigen” (cancel now) or with an equally unambiguous wording; only this button submits the notice of cancellation (§ 312k(2) BGB).
- Availability: Both buttons and the confirmation page must be permanently available and directly and easily accessible (§ 312k(2) BGB).
- Storage: The notice must be storable with date and time on a durable medium (§ 312k(3) BGB).
- Confirmation: The business confirms the cancellation immediately and electronically in text form (§ 312k(4) BGB).
This blog has already covered two related mandatory buttons: the label of the order button under § 312j BGB and the click path of the withdrawal button under § 356a BGB. § 312k differs from both in the one point this post is about: the law attaches a legal consequence to availability itself, and that consequence hits the existing contract base.
The obligations do not apply to contracts for which the law prescribes exclusively a stricter form than text form for cancellation, nor to websites relating to financial services or to contracts for financial services (§ 312k(1) BGB). According to the explanatory memorandum, the model is the corresponding rule in § 312j BGB (Bundestag printed paper 19/30840). For mixed offerings, the distinction is a matter for legal advice.
Subsection 6: what a gap in the cancellation path costs
If the buttons and the confirmation page are not provided in accordance with subsections 1 and 2, a consumer may terminate the affected contract at any time without observing a notice period (§ 312k(6) BGB). The explanatory memorandum explicitly calls this a sanction rule (Bundestag printed paper 19/30840). The reason is given right next to it: with the order button, the business has its own incentive to get things right, because without a correct button no contract is formed. With cancellation, that incentive is missing (Bundestag printed paper 19/30840), so the law creates it through the right to cancel without notice.
For annual plans and minimum terms, this is the real core of the provision: anyone who cancels while the cancellation path is missing or not working as required may, under subsection 6, cancel without observing the agreed notice period. How long the gap lasted is therefore not a technical footnote but a question revenue depends on.
The burden initially lies with the customer. According to the explanatory memorandum, the consumer has to present and prove that the conditions of subsection 6 are met (Bundestag printed paper 19/30840). If the customer presents a screenshot or an error message, the provider can hardly put it into context without its own series of measurements: was the confirmation page unreachable that evening, or was it the customer’s device? A dated sequence of check runs usually answers that faster than any reconstruction from log files.
Not every interruption counts. According to the explanatory memorandum, merely temporary, technically caused unavailability due to maintenance work is harmless (Bundestag printed paper 19/30840), and on subsection 6 it likewise states that short interruptions for maintenance are harmless (Bundestag printed paper 19/30840). A theme update that redirects the confirmation page to a login screen for three days, by contrast, is unlikely to count as maintenance, and you have to be able to show the difference.
Whether a specific gap triggers the consequence of subsection 6, and how to handle cancellations from that period, remains a legal question. A browser check answers the factual question that comes first: what the test browser saw at which point in time. This post is not legal advice.
How often the cancellation path fails in practice
Several surveys by the German federal consumer association vzbv show that implementation does not take care of itself. Consumer advice centers and associations checked 840 websites between July 18 and October 14, 2022 (vzbv 2022). On 349 of them, the cancellation button was missing entirely (vzbv 2022), and only 273 websites had it installed as required (vzbv 2022). For this post, another figure from the same campaign is more telling: 339 further violations concerned the confirmation page and the final confirmation button, such as missing mandatory details or impermissible labels (vzbv 2022). So the defect often sits not at the first button but one page further on.
The vzbv’s automated analyses show progress, but not a finished job. In the November 2022 survey, the cancellation button was implemented in a legally compliant way on 28 percent of the websites examined (vzbv 2023), with almost 3,000 provider websites checked (vzbv 2023). In the repeat check in June 2023, the figure was 42 percent of 2,946 websites (vzbv 2023). In February 2024, the vzbv found a cancellation button at 80 percent of 1,200 providers examined (vzbv 2024); in telecommunications, 40 percent of the providers examined had not yet implemented the rules (vzbv 2024).
The 354 consumer reports that were evaluated (vzbv 2023) also covered defects behind the first button: no cancellation confirmation, or a cancellation that could not be sent at all because of a technical error (vzbv 2023). All surveys are snapshots, whereas the law requires permanent availability.
Permanently available means reachable without logging in
For subscriptions with a customer account, the cancellation path often sits in the customer area. According to the explanatory memorandum, that is not enough for the statutory button. It states that consumers must be able to access both buttons and the confirmation page at any time and without first having to log in on the website (Bundestag printed paper 19/30840). Identification instead takes place on the confirmation page, through the details on unambiguous identification (§ 312k(2) BGB). Name and address will typically be required for this, and to designate the contract the business may ask for customer, order or contract numbers (Bundestag printed paper 19/30840).
Several courts have followed this line. In 2023, the Regional Court of Munich I ruled that cancellation via the cancellation button must also be possible without logging in on the website (vzbv). In 2025, the Berlin Court of Appeal upheld claims in two cases against cancellation paths that asked for login credentials (BGH). Both cases are pending before the Federal Court of Justice (BGH) under case numbers I ZR 272/25 and I ZR 275/25, with the oral hearing scheduled for November 5, 2026 (BGH). At the editorial deadline at the end of October 2026, no judgment had been issued. For monitoring, the outcome changes little, because the button must in any case lead directly to the confirmation page (§ 312k(2) BGB).
This is exactly the point that breaks quietly in practice. A new central sign-in, a middleware that protects every path below /account, or a relaunch that moves the cancellation form into the customer area: anyone testing internally is usually logged in and sees no difference. A customer who has not logged in for months, on the other hand, ends up on a login screen. For SaaS providers with a self-service portal this is the typical case. How to check the logged-in path separately is covered in the post on monitoring the login flow; for § 312k, the logged-out path is what counts.
The button does not just have to be somewhere. For its 2024 analysis, the vzbv followed case law of the Regional Court of Munich I under which the cancellation button must, among other things, be findable on the same page on which the contract can be concluded (vzbv 2024). A sensible check therefore covers the page where the subscription is purchased, such as the pricing page, and in addition the home page or the footer.
The confirmation page: the required details and nothing else
The second stage is the confirmation page. It asks for and allows five details (§ 312k(2) BGB): the type of cancellation, including the reason for an extraordinary cancellation, unambiguous identification, unambiguous designation of the contract, the end date and a channel for fast electronic delivery of the cancellation confirmation, usually the email address. According to the explanatory memorandum, the business may not make the end date a mandatory field without which the cancellation cannot be declared via the website (Bundestag printed paper 19/30840). If it is left out, the cancellation takes effect, in case of doubt, at the earliest possible date (§ 312k(5) BGB).
Since summer 2026, the highest civil court has also settled what must not appear on this page. On July 16, 2026, the Federal Court of Justice ruled that the design of the confirmation page is conclusively regulated in § 312k(2) sentence 3 BGB (BGH). It may not contain any further offers or information; the case concerned a notice offering to pause the contract free of charge instead of canceling it (BGH). The confirmation page serves solely to capture the details required for the cancellation and to submit the notice of cancellation (BGH).
A browser check verifies fields and labels directly. A text comparison cannot prove that nothing has been added, because it establishes that a text is present, not that it is absent. This is where the screenshot at the end of each run helps: if a retention offer shows up, it is visible in the image even though the check stays green.
| Requirement | Legal basis | Checkable in the live check | Step in the browser check |
|---|---|---|---|
| Cancellation button visible and correctly labeled | § 312k(2) sentence 2 BGB | yes | assert_visible, assert_text |
| Leads directly to the confirmation page | § 312k(2) sentence 3 BGB | yes | click, wait_for, assert_url |
| Reachable without prior login | § 312k(2) sentence 4 BGB; Bundestag printed paper 19/30840 | yes | fresh browser instance |
| Details a to e possible | § 312k(2) sentence 3, item 1 (a) to (e) BGB | yes, as fields present | assert_visible per field |
| Confirmation button “jetzt kündigen” | § 312k(2) sentence 3, item 2 BGB | yes | assert_text with equals |
| No additional offers | BGH, I ZR 200/25 | only in the image | screenshot with full_page |
| Notice can be saved with date and time | § 312k(3) BGB | only in a test environment | second monitor after the click |
| Confirmation in text form | § 312k(4) BGB | no | mailbox, outside the browser |
The check from a logged-out state
In XICTRAQ® browser monitoring, multi-step flows run in a real Chromium browser (XICTRAQ® documentation). Every run opens a fresh browser instance without traces of real users (XICTRAQ®). For § 312k, that is exactly the right starting point: without a stored session, the test browser sees the website the way a customer does who has not logged in for a long time. A scenario consists of up to 40 steps (XICTRAQ® documentation) drawn from eleven step types, including goto, click, wait_for, assert_text, assert_url, assert_visible and screenshot (XICTRAQ®).
The flow checks the cancellation button on the page where the subscription is purchased, clicks it and checks the address, the fields and the label of “jetzt kündigen” on the confirmation page. The assert_visible step requires a selector to be present on the page and visible (XICTRAQ® documentation); assert_text with equals compares the exact text (XICTRAQ® documentation).
{
"name": "Cancellation path § 312k, logged out, stop before the click",
"viewport": { "width": 1280, "height": 800 },
"timeout_ms": 20000,
"step_retry": 1,
"steps": [
{ "type": "goto", "url": "https://abo.example.invalid/preise" },
{ "type": "assert_visible", "selector": "#cancel-contracts" },
{ "type": "assert_text", "selector": "#cancel-contracts", "equals": "Verträge hier kündigen" },
{ "type": "click", "selector": "#cancel-contracts" },
{ "type": "wait_for", "selector": "form#cancellation" },
{ "type": "assert_url", "contains": "/vertrag-beenden" },
{ "type": "assert_visible", "selector": "#cancellation-type" },
{ "type": "assert_visible", "selector": "#customer-name" },
{ "type": "assert_visible", "selector": "#customer-address" },
{ "type": "assert_visible", "selector": "#contract-number" },
{ "type": "assert_visible", "selector": "#termination-date" },
{ "type": "assert_visible", "selector": "#confirmation-email" },
{ "type": "assert_text", "selector": "#confirm-cancellation", "equals": "jetzt kündigen" },
{ "type": "screenshot", "full_page": true }
]
}Addresses and selectors are placeholders. A second goto to the home page checks the button in the footer. The fields are only checked for presence, not filled in: in live operation, a filled-in form is one wrong click away from a real cancellation. The last step captures the whole page as an image that is shown in the run detail (XICTRAQ® documentation).
A run that presses the confirmation button submits a notice of cancellation. With real customer data, it ends a real contract; with a test contract in the live system, it creates a cancellation with confirmation and work for customer support on every run. The live check therefore stops before this click.
The runner blocks the XICTRAQ® tracker so that synthetic runs do not distort your own statistics with test page views (XICTRAQ® documentation). And because the text actually found is logged, depending on the step type (XICTRAQ® documentation), you know after the first run what the browser really read. How to create a scenario by recording it is shown in the post on recording browser flows; all step types are listed in the browser monitoring documentation.
Subsections 3 and 4: what gets checked after the click
Two further subsections govern what happens after “jetzt kündigen”. The consumer must be able to save the notice of cancellation, with the date and time it was submitted, on a durable medium in a way that shows it was submitted via the confirmation button (§ 312k(3) BGB). A durable medium is any medium that keeps a statement personally addressed to the recipient accessible for an appropriate period and can reproduce it unchanged (§ 126b BGB). As an example, the explanatory memorandum mentions a downloadable summary of the content that documents in particular the date and time the button was pressed (Bundestag printed paper 19/30840).
Subsection 4 then requires an immediate electronic confirmation in text form, stating the content, the date and time of receipt and the date on which the contract is to end (§ 312k(4) BGB). A notice submitted via the confirmation button is presumed to have reached the business immediately after it was submitted (§ 312k(4) BGB).
Neither can be checked in live operation without triggering a cancellation. That is what a second monitor against a test environment with the same theme and a test contract is for: it clicks “jetzt kündigen” and checks date, time and the link to the summary on the completion page. It does not check the file itself, because downloads cannot currently be tested in the builder (XICTRAQ®); a person checks its content after every release. Every goto address has to be a publicly reachable http or https address (XICTRAQ® documentation), so a test environment that only exists on the internal network is ruled out.
Whether the confirmation under subsection 4 arrives in the mailbox is a separate measurement path outside the browser; the posts on monitoring the double opt-in flow and on the receipt confirmation of the withdrawal button show what it looks like. If the summary is a link to a file, you can count how often it is downloaded; what a cookie-free tracker recognizes there is explained in the post on tracking downloads and outbound links without cookies.
Turning runs into evidence of availability
For subsection 6, the period is what matters, and only the sequence of runs answers that. The overview shows the last 50 runs per monitor (XICTRAQ® documentation); each run records start and end time, the index of the failed step and an error message (XICTRAQ® documentation). On failure, a screenshot is taken automatically at the moment of the failure (XICTRAQ® documentation) and an alert with critical severity is created (XICTRAQ® documentation); once the flow passes again, XICTRAQ® closes the alert automatically (XICTRAQ® documentation).
This is how the runs turn into a gap with a beginning and an end:
- Last passing run before the failure: At this point the path was still there. The gap began afterward, at the latest with the next run.
- First failed run: The alert, screenshot and error message show what went wrong, such as a login screen instead of the form.
- First passing run after the fix: The alert closes, and the image from this run shows the restored state.
- Filing: Export the alert and add the screenshots and the cause. That completes the record for this gap.
How precisely the gap can be pinned down depends on the schedule. The interval ranges from 5 minutes to 24 hours (XICTRAQ® documentation); with a daily run, the start remains uncertain by up to a day, with 15 minutes by a quarter of an hour. After every deploy, “Run now” helps: the next cron tick, every minute, then runs the monitor without waiting for the interval (XICTRAQ® documentation). Why deploys in particular break click paths is covered in the post on deploy errors as a cause of outages.
Beyond individual runs, a dashboard card shows a browser monitor’s success rate over a selectable period. In the alert overview, individual alerts can be acknowledged, resolved and exported as a postmortem (XICTRAQ®). Together, this makes up the evidence folder: a monthly look at the success rate and a postmortem with screenshots and cause for each gap. How to file measurement records so that they hold up later is shown in the post on website acceptance with a test report.
During a maintenance window, XICTRAQ® does not trigger alerts (XICTRAQ®), but monitoring data is still collected (XICTRAQ®). A window entered in advance shows that a short interruption was planned, and the runs show how long it lasted. Anything that was not planned beforehand remains an outage. More on this in the post on maintenance windows in monitoring.
From alert to fix
The alert arrives through the configured channels; XICTRAQ® offers seven, including email, common team messengers, a webhook and browser push (XICTRAQ®). After that, two things matter: restoring the path quickly and recording the period accurately.
- Read the failed step: If assert_visible fails, the button is missing or hidden; if only the click fails, a consent or chat layer may be covering it.
- Reproduce it logged out: If the screenshot shows a login screen instead of the form, start the search with login logic, middleware and redirects, reproduced in a private browser window.
- Fix and verify: Roll out the fix, trigger “Run now” and wait for the first passing run.
- Match cancellations from the gap: Customer support checks what arrived between the last passing run before the failure and the first passing run after it; how to handle it is a matter for legal advice.
Agencies with many client websites first need to establish which of them sell subscriptions at all. The same inventory that the post on finding affected websites by inventory builds for a security vulnerability does the job, with an extra column for subscription offers.
Treat the cancellation path like a core feature
For a subscription business, the cancellation path is not a mandatory page on the sidelines but a feature with legal consequences. If you monitor it as carefully as login and payment, you learn about a gap from an alert rather than from a cancellation without notice.
- Clarify the scope, including the exception for financial services.
- Check without logging in, on the page where the subscription is purchased and in the footer.
- Check all five details and both labels, with a full-page image per run.
- Stop before “jetzt kündigen” and check the rest in a test environment.
- Enter maintenance in advance and file every gap with a postmortem.
At EU level, the topic keeps moving. In connection with the planned Digital Fairness Act, there are calls for simple, easily accessible, EU-wide cancellation options for online subscriptions (European Consumer Center Germany). A Commission proposal only opens the legislative procedure; until that procedure is completed, § 312k BGB continues to apply unchanged in Germany. Browser monitoring is included from the Business plan upward (XICTRAQ® documentation); scope and terms are on the pricing page.
This post is based on: the statutory text of § 312k and § 126b BGB (gesetze-im-internet.de); the recommendation and report of the Bundestag Committee on Legal Affairs on the Act on Fair Consumer Contracts, Bundestag printed paper 19/30840 of June 18, 2021, with the explanatory memorandum on § 312k BGB; press releases of the Federal Court of Justice no. 128/2026 of July 16, 2026 (judgment I ZR 200/25) and no. 133/2026 of July 27, 2026 (hearing date I ZR 272/25 and I ZR 275/25); five publications of the German federal consumer association vzbv of November 14, 2022, January 16, 2023, July 5, 2023, December 19, 2023 and March 18, 2024 on the review campaign, website analyses and case law on the cancellation button; the statement by the European Consumer Center Germany on the Digital Fairness Act of October 2, 2026; XICTRAQ® documentation and feature pages. The sources were accessed in October 2026. This post is not legal advice.