# CON-034 — The business name on the artifact must match the registered brand

> The business name visible on the consent artifact must match the registered brand legal name or DBA.

- **Rule ID:** CON-034
- **Layer:** Consent flow (`CONSENT_FLOW`)
- **Checks:** `consent artifact + brand.company_name`
- **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 vision over a consent artifact (screenshot, scan, MMS media)
- **Fix type:** Supply evidence only you hold
- **Required by:** TCR, Twilio, Bandwidth
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/consent-flow/con-034/

## Why this rule exists

An artifact showing a different business is the clearest possible evidence that the consent was collected by someone other than the registrant, which is the consent-transfer problem the framework exists to prevent. It also catches the honest version — a screenshot borrowed from a sister brand because it looked similar enough.

## How to fix it

Supply an artifact from the registered brand's own consent surface. If the site trades under a different name, register that name as the DBA so the two match.