# BRD-223 — Website and contact email must be in place before an identity-plus vet

> The brand website and business contact email must be populated before an Authentication+ or RBM vet is ordered.

- **Rule ID:** BRD-223
- **Layer:** Brand (`BRAND`)
- **Checks:** `brand.website + brand.business_contact_email`
- **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:** Deterministic (settled in code from the submitted values)
- **Fix type:** Fix the field — a better value in the form clears it
- **Required by:** TCR
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/brand/brd-223/

## Why this rule exists

These vets verify the brand through its own domain and mailbox, so ordering one before either exists submits an examination with nothing to examine — it is refused on a missing field after the fee is taken. The two fields are optional on an ordinary brand, which is exactly why they are empty at the moment somebody decides to order the vet.

## How to fix it

Populate the brand website and the business contact email, and let the update settle on the brand record, before placing the vet order. Done when both fields read back from the brand and the mailbox has been tested (BRD-119).

## Example of a compliant value

```text
website: https://acmecoffee.com · business_contact_email: jane.doe@acmecoffee.com — both present before the order
```

## Provider rejection codes

| Provider | Code | Resubmission allowed |
| --- | --- | --- |
| TCR | `501` | yes |