A kiosk or terminal must not pre-fill the consumer's number
The requirementstatement
A payment terminal or kiosk collecting messaging consent must require the consumer to enter their number, not present one already filled in.
- Severityseverity
- HighHIGHRejected by at least one carrier or provider, and a common cause of failure at the rest.
- When it bitesphase
- Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
- What is checkedobject
- kiosk consent screen
- Where it liveslayer
- Consent flowCONSENT_FLOW
- How Ekas settles itdetectability
- AI · visionVISION
- Needs the pixels: a screenshot of the opt-in surface, a scanned paper form, an MMS attachment.
- What the fix involvesfailureClass
- Fix the websiteTERMINAL_WEBSITE
- The fix lives on your site. No amount of rewording the form clears it.
- Who requires itauthorities
- Twilio
- When it appliesapplicabilityText
- Applies when consent was collected by point of sale.
Why this rule existsrationale
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 itremediation
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 mistakespitfalls
- 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 codescodes
The code you get back when this rule is what failed, and whether that provider lets you resubmit.
| Provider | Code | Resubmit |
|---|---|---|
| Twiliogen2 | 30925 | Yes |
Notesnotes
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.
Rules you will hit next
Other consent flow rules at the same severity. A registration is judged as a whole, not rule by rule.
CON-017An offline opt-in still needs a findable business behind itHighHIGHCON-033Opt-in evidence must be the live surface, not a mockup of itHighHIGHCON-038Verbally-collected informational campaigns need the mockup and the messagesHighHIGHCON-042The phone field must be optional on a general-purpose formHighHIGHCON-044A required phone field must carry an SMS disclaimer beside itHighHIGHCON-071The decline path must be as usable as the accept pathHighHIGH
CON-064 is one of 101 consent flow rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.