# CON-109 — The disclosure must sit next to the button the consumer presses

> The consent language must appear directly beneath the phone field or immediately above the submit control.

- **Rule ID:** CON-109
- **Layer:** Consent flow (`CONSENT_FLOW`)
- **Checks:** `disclosure position relative to the submit control`
- **Severity:** HIGH — Rejected by at least one carrier or provider, and a common cause of failure at the rest.
- **When it bites:** Gates approval — get this wrong and registration is refused
- **How it is detected:** AI vision over a consent artifact (screenshot, scan, MMS media)
- **Fix type:** Fix the website — no form edit clears it
- **Required by:** Klaviyo, Infobip, Salesmsg, Quo
- **Applies:** Applies when consent was collected by web form, checkout, account settings, third party and point of sale.
- **Canonical URL:** https://ekas.io/rules/10dlc/consent-flow/con-109/

## Why this rule exists

Consent is given at the instant of submitting, so the words that count are the ones in view at that instant. A disclosure at the top of a long form has scrolled away by the time the consumer acts, which is why the placement is specified as a position relative to the button rather than as presence on the page.

## How to fix it

Move the disclosure into the gap between the last input and the submit button. Done when a screenshot cropped to the submit button still contains the whole disclosure.

## Common mistakes

- Long forms pass on desktop and fail on mobile, where the same block falls a full screen above the button — check the narrow viewport before capturing evidence.