# Checkouts that pass the checks and still convert

> What the laws require of a subscription checkout is small — one clear line next to your own pay button that ends with the consent sentence, online cancellation and the required emails. No checkbox, no "Agree &" button.

The requirements are a short list, not a dial. Automatic-renewal laws (federal ROSCA, California, New York and the other states)
ask for four things at checkout and after it — not for banners, warning colours or a wall of checkboxes:

1. **One clear disclosure line next to the pay button**: the price, how often it is charged, that it renews
   automatically until the subscriber cancels, and how to cancel.
2. **Affirmative consent to the renewal terms**: one sentence at the end of that line, "By clicking “Subscribe”,
   you agree to these renewal terms." Your button keeps its own label ("Subscribe", "Start free trial"): no checkbox,
   no "Agree &" button.
3. **Online cancellation** for anyone who signed up online.
4. **The required emails**: the acknowledgment after sign-up, and the reminders your plan needs (Checkbox tells you which).

That's it. Checkbox's default fix for each requirement is the lowest-friction change that meets the cited text, and
it never asks for something no cited law requires ([check levels](#protection-levels)). Once those four are in place, the optional, engine-checked ways to convert and
retain better — trial buttons, a first-charge date, calmer emails, a skippable save offer — are in
[Conversion suggestions that pass the checks](https://checkbox.site/docs/guides/conversion-suggestions).

## The consent line: what the law requires, and what it does not {#consent}

**Required by law:** the subscriber's express, affirmative consent to the automatic-renewal terms before the first
charge (ROSCA, 15 U.S.C. § 8403(2): "express informed consent"; California § 17602(a)(2) and, since July 1, 2025,
§ 17602(a)(4): "express affirmative consent to the automatic renewal … offer terms"; New York § 527-a(1)(b) and the
other states: "affirmative consent to the agreement containing the renewal terms"). The renewal terms next to your own
button, ending with "By clicking “Subscribe”, you agree to these renewal terms.", meets that: the click is the
agreement, and the sentence says so. Checkbox passes it, and fails a click with no such sentence (consent only implied)
or a sentence that agrees only to your Terms of Service.

**Not checked by default.** Checkbox does not check these, and never reports them as passing:

- Vermont: bold renewal terms for plans of 1 year or longer, and a separate opt-in to the renewal for those plans
  (9 V.S.A. § 2454a);
- D.C.: separate consent for free trials that convert to paid (D.C. Code § 28A-203(c)(2)).

They are available if you want them: Checkbox Elements with `extras="vt-dc"` or the snippet-rendered disclosure with
`?extras=vt-dc` show bold terms and an opt-in checkbox only to visitors placed there by IP address (a VPN or travel can
place a visitor wrongly); on Stripe Checkout, `POST /v1/checks/region` tells your server when to add
`consent_collection`.

**Not required anywhere Checkbox checks:** an "Agree &" button label, a checkbox per term, a separate confirmation
step or a pre-purchase summary. Checkbox never asks for them.

The statute does not define "express affirmative consent", and a settlement (the CART HelloFresh judgment lists "a
checkbox, signature, express consent button or other substantially similar mechanism") is not precedent. This is
Checkbox's reading of the text, not a guarantee; see [the law pages](https://checkbox.site/laws) for the citations.

## What "clear and conspicuous" means in practice {#conspicuous}

Checkbox's conspicuousness check (`signup.disclosure.conspicuous`) passes a renewal line that is:

- **readable**: at least 12px and at least about three quarters of your body text size — not "big";
- **legible**: WCAG AA contrast (4.5:1) against its background, not faded or semi-transparent;
- **set apart from the text around it**: semibold, or a contrasting colour, or a light border — California's statute
  asks for one of these ("larger type, contrasting type, font or colour, or set off by symbols or marks");
- **next to the button**: directly above it (or directly below it, right under the button).

Vermont's bold-face rule for plans of 1 year or longer is not checked by default ([above](#consent)).

It fails classic fine print: small grey text under the button, text faded into the background, terms collapsed
behind "Details". It never asks for a banner, a red box or a bigger font.

## Example 1 — one semibold line above your own button {#line}

A short form that passes, in your page's own font and colours. Semibold is what sets it apart; the last sentence is
the consent. No checkbox, and the button keeps its label.

```html
<form action="/subscribe" method="post">
  <!-- your email / card fields -->
  <p style="margin:12px 0 6px;font-weight:600;">
    Renews automatically every month at $19.99 until you cancel. Cancel anytime in Account → Billing.
    By clicking “Subscribe”, you agree to these renewal terms.
  </p>
  <button type="submit">Subscribe</button>
</form>
```

Required by law: the line and its last sentence.

Checkbox Elements renders this by default (since 1.5.0: the one-line wording, `copy="compact"`, at your page's own
size and colours, regular weight, set off by a thin outline around the line; `appearance="line"`), with the wording
generated from your real plan and the consent recorded for you. `copy="full"` spells every term out (maximum
protection):

```html
<checkbox-disclosure publishable-key="pk_test_…" merchant-name="Acme" amount="1999" currency="usd"
  interval="month" cancel-url="https://acme.example/account/cancel"></checkbox-disclosure>
<button type="submit">Subscribe</button>
```

## Example 2 — a button that states the agreement {#button}

A button labelled "Agree & subscribe" with the renewal line right above it also passes, but it is never
Checkbox's suggestion: it changes your button's wording, which tends to cost sign-ups (conversion impact: noticeable),
and no cited law asks for it. The clickwrap sentence in Example 1 does the same job with your own label.

## Example 3 — Stripe Checkout {#stripe}

Stripe draws the page and its own Subscribe button; you supply one renewal line (`custom_text.submit`) that ends with
the consent sentence. No checkbox, no Terms of Service URL, no change to any button. Stripe styles custom text small
and grey; Checkbox shows that as "Checks pass with a note", not as a failure. Also put the same line on your own
pricing page before the redirect. Payment Links take the same custom text, edited in place (the link keeps its URL).

```json
{
  "mode": "subscription",
  "custom_text": {
    "submit": { "message": "Renews automatically every month at $19.99 until you cancel. Cancel anytime in your account. By subscribing, you agree to these renewal terms." }
  }
}
```

The default params never include `consent_collection`. If your checkout already has Stripe's checkbox, keep it.

## What Checkbox shows you {#statuses}

| Label | Meaning |
|---|---|
| **Needs a fix** | A clear gap in what the cited laws require, with the one change that fixes it. |
| **Checks pass · live check pending** | Everything Checkbox can see is right; it has not seen the live event yet (your acknowledgment sent for a real sign-up, a cancellation confirmed in Stripe, a reminder that is not due yet). Counts as passing the checks; each item says how it completes. |
| **Verified live** | Seen live: a proof run, a real BCC'd send, a Stripe-confirmed cancellation. |
| **Your call** | A real decision (for example keeping a minimum term). One question, with our recommended answer. |
| **Checks pass** | Every check that applies passes (grey areas carry a short note: "Checks pass with a note"). |
| **Not set up yet** | No sign the email or setting exists yet, with the one-click way to set it up. |
| **Not checked yet** | Checkbox has not tried it yet (for example the cancel flow), with how to let it check. |
| **Not checked by default** | Open only for a rule Checkbox does not check by default ([Vermont and D.C.](#consent)). Never a pass, never counted, nothing to do. |

A site with those four in place reads **Checks pass · 2 live checks pending** — and the live checks complete on their
own as subscribers sign up, or in a minute with a [proof run](https://checkbox.site/docs/guides/test-runs).

## Check levels {#protection-levels}

Every task is tagged **required** (what the cited laws require, as Checkbox reads them — the only thing that can keep a
site's checks from passing) or **recommended** (records and settings that support a cited requirement without touching
the checkout: consent receipts for California's three-year consent records, § 17602(a)(6); a renewal section in your
Terms; self-serve cancellation in your billing portal). Every task also says its **conversion impact** (`none`,
`small` or `noticeable`, with a one-line reason): the default fixes are `none`; a consent checkbox is `small` (one click). Choose per site in Site settings → Protection level, or with `protection_level` on
[update a site](https://checkbox.site/docs/api/sites):

- **Minimum**: required items only.
- **Balanced** (default): required items, plus recommended ones collapsed under them.
- **Maximum**: the same items, with the fuller wording and a consent checkbox everywhere (more friction; not required
  by any cited law Checkbox checks by default).

Next: [Conversion suggestions that pass the checks](https://checkbox.site/docs/guides/conversion-suggestions) — optional changes that commonly help
conversion, each checked by the same engine before you see it.

Rules written and maintained by the Checkbox team from the text of each law, each cited to its source. Automated checks, not legal advice.
