Authentication+ must now be ordered explicitly

JSONMarkdown

The requirementstatement

Under Authentication+ 2.0 the vet must be ordered explicitly after the identity check; it no longer runs automatically.

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
the Authentication+ vet order
Where it liveslayer
BrandBRAND
How Ekas settles itdetectability
DeterministicDETERMINISTIC
Settled in code from the values you submitted. No model involved, no judgement call, same answer every time.
What the fix involvesfailureClass
Wait on someone elseTERMINAL_EXTERNAL
Needs an external system or a waiting period, such as IRS propagation, a vetting result, or a carrier queue.
Who requires itauthorities
TCR
When it appliesapplicabilityText
Applies when the brand is a public company.

Why this rule existsrationale

It used to be automatic, so every runbook, integration and mental model built before the change assumes it will happen on its own. It does not: the brand verifies, nobody orders the vet, and the public-company brand sits without the Authentication+ status that gates its campaigns — with no error anywhere, because nothing failed.

How to fix itremediation

After the identity check completes, place the Authentication+ order explicitly and watch for the 2FA mail. Add the order as a step in your onboarding runbook — its absence produces no error, so nothing will remind you.

Check this yourselfattestation

Ekas flags this from what you submit, but the fact that settles it sits somewhere only you can reach.

Has the Authentication+ vet been ordered explicitly, as a step in your runbook, after the identity check completed?

  1. 1Open the brand and confirm an Authentication+ order exists. It used to run automatically and no longer does.
  2. 2Add the order to the onboarding runbook — its absence produces no error, so nothing will remind you.
  3. 3Then watch the business contact mailbox for the 2FA mail.

What wrong looks like: The brand verifies and looks healthy. No vet was ordered, every campaign is refused, and nothing anywhere reports a failure — because nothing failed.

Notesnotes

The order is an action at the registry rather than a field on the registration. What the user has to do is remember it: a public brand that verified but was never Authentication+ vetted looks healthy and cannot register campaigns.

Rules you will hit next

Other brand rules at the same severity. A registration is judged as a whole, not rule by rule.

BRD-001A legal company name is required for every entity but a sole proprietorBlockingBLOCKINGBRD-002Legal name must match the IRS record for the EINBlockingBLOCKINGBRD-003Legal name must carry its exact entity suffix as filedBlockingBLOCKINGBRD-008Legal name must not carry an appended personal name or roleBlockingBLOCKINGBRD-009The legal name field takes the legal name, not the trading nameBlockingBLOCKINGBRD-011A legal business name may back only one brand across the whole registryBlockingBLOCKING

All brand rules

BRD-225 is one of 196 brand rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.

Reading the rules is the easy part.

Ekas runs every rule that gates approval, 823 of these 915, against your registration before it reaches the carrier. It reads your site, your policy pages and your opt-in the way a reviewer would, and hands you the fix, not just the verdict.

Talk to UsHow 10DLC works