# WEB-101 — The QR landing page must display the registered brand name

> The page a QR code opens must display the brand name as registered, so the consumer can see whose programme they are joining.

- **Rule ID:** WEB-101
- **Layer:** Website (`WEBSITE`)
- **Checks:** `QR landing page branding`
- **Severity:** BLOCKING — Breaking this rule gets the submission rejected outright.
- **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
- **Fix type:** Fix the website — no form edit clears it
- **Required by:** Aerialink
- **Applies:** Applies when consent was collected by QR code.
- **Canonical URL:** https://ekas.io/rules/10dlc/website/web-101/

## Why this rule exists

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 it

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 codes

| Provider | Code | Resubmission allowed |
| --- | --- | --- |
| Aerialink | `806` | yes |

## Notes

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.