The QR landing page must display the registered brand name
The requirementstatement
The page a QR code opens must display the brand name as registered, so the consumer can see whose programme they are joining.
- 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
- QR landing page branding
- Where it liveslayer
- WebsiteWEBSITE
- How Ekas settles itdetectability
- AI · crawlCRAWL
- Needs your live site or policy page fetched and read. Ekas crawls it the way a reviewer would.
- 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
- Aerialink
- When it appliesapplicabilityText
- Applies when consent was collected by QR code.
Why this rule existsrationale
A QR code is opaque by design: the consumer has no idea where it goes until the page loads, so the page is the first and only chance to say who is asking for their number. An unbranded hosted form — the platform's template with the merchant name left at its default — gives them nothing to recognise, and gives the reviewer nothing to tie the surface to the brand.
How to fix itremediation
Put the registered brand name or DBA in the heading of the landing page, not only in the page title or the platform footer. Done when someone who has just scanned the code can see whose programme it is without scrolling.
Provider rejection codescodes
The code you get back when this rule is what failed, and whether that provider lets you resubmit.
| Provider | Code | Resubmit |
|---|---|---|
| Aerialink | 806 | Yes |
Notesnotes
Distinct from WEB-102, which asks whether the landing page carries the full disclosure set. A page can carry every required sentence and still never say who is sending.
Rules you will hit next
Other website rules at the same severity. A registration is judged as a whole, not rule by rule.
WEB-001A brand website URL is requiredBlockingBLOCKINGWEB-009The website must resolve and return contentBlockingBLOCKINGWEB-012A parked or for-sale domain is not a websiteBlockingBLOCKINGWEB-013A pre-launch placeholder is not a websiteBlockingBLOCKINGWEB-014Staging, admin and internal hosts must not be the brand websiteBlockingBLOCKINGWEB-016The website must be machine-crawlableBlockingBLOCKING
WEB-101 is one of 93 website rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.