Changing an identity field re-runs verification, and costs the fee again

The requirementstatement

Any change to entity type, EIN, EIN issuing country or legal name re-runs brand verification and resets the identity status.

Severityseverity
HighHIGHRejected by at least one carrier or provider, and a common cause of failure at the rest.
When it bitesphase
Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
What is checkedobject
brand.entity_type + brand.ein + brand.ein_issuing_country + brand.company_name
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
VonageTCRTwilio
When it appliesapplicabilityText
Applies to every 10DLC registration.

Why this rule existsrationale

These four fields are the identity itself, so editing one is not a correction to a verified brand — it is a new claim about who the business is, and the registry treats it that way: the status drops back, the fee is charged again, and any completed vet expires with it. Teams fixing a typo in a legal name are routinely surprised to find a working brand back in UNVERIFIED and their campaigns blocked behind it.

How to fix itremediation

Batch every identity correction into one edit rather than making them one at a time — each round trip charges the verification fee again. Expect the brand to return to UNVERIFIED and campaign registration to be blocked until it clears, and do not schedule the change on the day of a send.

Check this yourselfattestation

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

Are all of your identity corrections — entity type, EIN, EIN country, legal name — batched into a single edit, made on a day you are not sending?

  1. 1List every identity field you intend to change and make them in one operation. Each separate round trip charges the verification fee again.
  2. 2Expect the brand to drop to UNVERIFIED and campaign registration to be blocked until it clears, and expect any completed external vet to expire with it.

What wrong looks like: A typo in the legal name is fixed on a Friday. A working brand is back in UNVERIFIED, its vet has expired, its campaigns are blocked, and the fee has been charged twice.

Notesnotes

Absorbs OPS-343, which states the same trigger together with its two consequences: the identity reset, and the vet expiry that BRD-222 covers. The re-verification itself happens at the registry and takes as long as it takes — what the user has to do is time the change deliberately and be ready to re-order any external vet that expires with it.

Rules you will hit next

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

All brand rules

BRD-044 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.