QR opt-in must resolve to a compliant surface
The requirementstatement
A QR code used for opt-in must land on a page carrying the full consent disclosure, or the disclosure must be printed beside the code.
- Severityseverity
- BlockingBLOCKINGBreaking this rule gets the submission rejected. There is no partial credit.
- When it bitesphase
- Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
- What is checkedobject
- consent surface
- Where it liveslayer
- Consent flowCONSENT_FLOW
- How Ekas settles itdetectability
- AI · formAI_FORM
- A semantic question about what you wrote: whether a description matches a use case, whether a name looks like a filed entity. Judged by a model against written criteria.
- What the fix involvesfailureClass
- Produce a documentTERMINAL_ARTIFACT
- Needs a document that does not exist yet, such as a verbal script, a paper consent form, or QR landing copy. Ekas drafts it.
- Who requires itauthorities
- CTIATCR
- When it appliesapplicabilityText
- Applies when consent was collected by QR code.
Why this rule existsrationale
A QR code carries no information a consumer can evaluate — it is an opaque instruction to trust wherever it goes. The disclosure therefore has to exist either next to the code or on the page it opens, and a QR that fires a pre-filled SMS bypasses both.
How to fix itremediation
Point the QR at a hosted opt-in page carrying the full disclosure and a real checkbox, and supply that URL or a capture of it. If the code appears on print where you also control the surrounding space, print the disclosure beside it as well.
Common mistakespitfalls
- A QR that opens a pre-filled "text JOIN to 55512" message collects no disclosed consent at all — the consumer never saw terms.
Rules you will hit next
6 other rules read consent surface. Fixing one field to satisfy a single rule is how a resubmission trades one rejection for another, so read these before you change anything.
CON-043A mandatory phone field needs its own separate, optional SMS opt-inBlockingBLOCKINGCON-108The disclosure must be on the same page as the phone-number fieldBlockingBLOCKINGCON-AGE-GATEAge-gated programs require real age verification at opt-inBlockingBLOCKINGCON-BOX-BUNDLEDMessaging consent must be separate from terms acceptanceBlockingBLOCKINGCON-BOX-PRESENTAn explicit affirmative opt-in control must existBlockingBLOCKINGCON-BOX-UNCHECKEDThe consent control must be unchecked by defaultBlockingBLOCKING
CON-QR-DEST is one of 101 consent flow rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.