# CON-DISC-RATES — Consent disclosure must carry the message and data rates notice

> "Message and data rates may apply" (or a clear equivalent) must appear at the point of consent.

- **Rule ID:** CON-DISC-RATES
- **Layer:** Consent flow (`CONSENT_FLOW`)
- **Checks:** `consent disclosure text`
- **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 judgement over the crawled website or policy page; AI vision over a consent artifact (screenshot, scan, MMS media)
- **Fix type:** Fix the website — no form edit clears it
- **Required by:** CTIA, TCR, Twilio, Bandwidth, AWS
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/consent-flow/con-disc-rates/

## Why this rule exists

The consumer may be paying their carrier per message, and the disclosure exists so nobody is billed for something they did not knowingly accept. It is one of the oldest and most mechanically-checked elements in the industry, which makes its absence a cheap and very common rejection.

## How to fix it

Add "Message and data rates may apply." to the consent disclosure, adjacent to the checkbox. A rates notice that lives only in your Terms page does not count.

## Example of a compliant value

```text
Message frequency varies. Message and data rates may apply. Reply STOP to unsubscribe, HELP for help.
```