# CON-064 — A kiosk or terminal must not pre-fill the consumer's number

> A payment terminal or kiosk collecting messaging consent must require the consumer to enter their number, not present one already filled in.

- **Rule ID:** CON-064
- **Layer:** Consent flow (`CONSENT_FLOW`)
- **Checks:** `kiosk consent screen`
- **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:** Twilio
- **Applies:** Applies when consent was collected by point of sale.
- **Canonical URL:** https://ekas.io/rules/10dlc/consent-flow/con-064/

## Why this rule exists

A number the terminal already knows — from the card, the loyalty account, or the last transaction — turns the consent step into a confirmation of something the consumer never supplied for this purpose. They tap Yes to a number on screen without deciding to hand it over, and the resulting record cannot show that they did.

## How to fix it

Configure the terminal to present an empty number field at the consent step, even where the number is already on the account. Done when the screenshot shows a blank field and a keypad rather than a masked number and a Confirm button.

## Common mistakes

- Masking the pre-filled number does not fix it — the consumer still did not type it, and a reviewer reads the mask as evidence the number came from somewhere else.

## Provider rejection codes

| Provider | Code | Resubmission allowed |
| --- | --- | --- |
| Twilio (gen2) | `30925` | yes |

## Notes

Sourced from vendor guidance rather than published carrier text; the underlying obligation is that consent must be an affirmative act by the consumer, which the pre-filled field removes. Cite that if a user pushes back on the rule as stated.