Brand registration failed: EIN and legal name mismatch (Twilio 30795)
Short answer
Most brand failures come from a legal name or address that doesn't exactly match the IRS records for the EIN. Copy the legal name exactly as printed on your IRS CP 575 or 147C letter. Put a trade name in the DBA field, and use an email on your business domain.
What you'll see
| Where | Code | Wording |
|---|---|---|
| Twilio | 30795 | “Brand Registration: Tax ID data mismatch” |
| Twilio | 30799 / 30796 | “Brand Registration: Unable to verify registration details” / “Entity type or stock information mismatch” |
| The Campaign Registry | UNVERIFIED / TAX_ID | “Brands with an UNVERIFIED identity status cannot create new campaigns.” Feedback: “Data mismatch related to tax id and its associated properties” |
| Twilio (10DLC) | 30894 / 30918 | “Campaign vetting rejection - Invalid Brand Information” / “DBA name does not match the legal business name on file” |
| Twilio (10DLC) | 30898 / 30971 | “Campaign vetting rejection - Excessive EIN” / “Business contact email cannot be verified” |
| Telnyx, Bandwidth | 603, 710, 711, 713 | Brand, website and samples inconsistent; agency registered instead of the brand; one EIN reused for several brands; large company using a non-official email domain |
Text in curly quotes is the provider's wording; the rest is our summary.
Why it happens
- The legal name has a typo, a missing “LLC” or comma, or uses the trade name instead of the legal name.
- The address doesn't match what the IRS has on file (an old address, or a branch).
- The EIN is brand new and not yet in the databases the verifiers check.
- An agency or software platform registered itself instead of the client (Twilio 30894, DCA 710).
- The same EIN was used to create several brands (30898, DCA 711).
- A Gmail or Yahoo contact email, or a contact who isn't an authorized representative (30971, 30972).
- Wrong entity type: a private company marked public, or a for-profit marked nonprofit (30796, 30798).
How to fix it
- Find your IRS CP 575 (or request a 147C letter) and copy the legal name exactly. Twilio:
An exact match between the Legal Company Name and the EIN as displayed on CP 575 is required for the Brand to be successfully registered.
- Use the address the IRS has for the EIN. Don't use names from a W-2 or W-9.
- Put a trade name in the DBA or brand name field, and use it consistently on your website and in samples.
- Use an email on your business's domain for the brand contact and support email.
- Register each real business once. Agencies register each client under the client's EIN.
- For a new EIN, wait or appeal. Twilio says new EINs take
around 30- 90 days
to propagate, and an identity appeal with the CP 575usually takes 5-7 business days
.
Legal names that span several lines
The Campaign Registry's guide says to enter only the first line of the legal name as printed on the CP 575. HighLevel says to enter all lines above the address. If one fails, an identity appeal with the full letter attached is more reliable than guessing again.
Appeals and retries
Identity appeals are allowed within 45 calendar days of brand creation and cost $11 (TCR's guide text still says $10). Twilio covers two extra brand registration attempts for the same brand, and its API allows up to three brand updates at no extra charge (error 21724 after that).
Authentication+ in 2027
Authentication+ (Auth+) emails a PIN to the brand's business contact, who has to complete the check before new campaigns can be created. Free addresses (Gmail, Outlook) and role addresses such as sales@ or support@ are rejected. Each attempt costs $12.50. Today only public for-profit brands need it. The Campaign Registry's Auth+ 2.0 overview (updated October 1, 2026) extends it in two steps:
| Brand entity type | From January 21, 2027 | From April 29, 2027 |
|---|---|---|
| Public for-profit | Required (already today) | Required |
| Government | Required | Required |
| Non-profit | Optional | Required |
| Private for-profit | Optional | Required |
| Sole proprietor | Not covered | Not covered |
These dates are for brands with an email address on their own domain. TCR says brands with free email addresses will get a separate validation path, to be announced later; some providers describe it as a government ID check. Telgorithm, Bandwidth and Intermedia describe the January 21 change as covering every entity type except sole proprietors, but TCR's own document keeps it optional for non-profits and private companies until April 29, 2027.
Check before you resubmit. Every rejection costs days, and often another $15 vetting fee. Paste your description, message flow, samples and policy text into the free preflight check, or generate a consistent set with the campaign builder.
Frequently asked questions
Can I use a DUNS number instead of an EIN?
No. Twilio says a DUNS number is not acceptable for US companies creating Standard brand registrations. Without an EIN, use a Sole Proprietor brand if your provider supports it.
My EIN is a few weeks old. Will it fail?
It might. Twilio says new EINs take around 30-90 days to show up in the validation databases. You can register and appeal with your CP 575 if it comes back unverified.
Can I register my clients under my agency's EIN?
No. Each brand must be the business that sends the messages, under its own EIN. Agency-as-brand gets rejected (DCA 710, Twilio 30894), and reusing one EIN for many brands triggers 30898 and DCA 711.
Does my private company need Authentication+?
Not yet. The Campaign Registry makes it optional for private for-profit and non-profit brands from January 21, 2027 and required from April 29, 2027. Government brands need it from January 21, 2027, and public companies need it now. Sole proprietors are not covered.
Sources
- Twilio: A2P 10DLC Brand Approval Best Practices (updated 2026-09-15)
- Twilio error 30795 (accessed 2026-10-03)
- Twilio error 30894 (accessed 2026-10-03)
- Twilio error 30898 (accessed 2026-10-03)
- Twilio error 30971 (accessed 2026-10-03)
- The Campaign Registry: CSP User Guide (July 2026)
- The Campaign Registry: CSP API OpenAPI spec (accessed 2026-10-03)
- The Campaign Registry: Fees and Pricing (updated 2026-08-13)
- The Campaign Registry: Authentication+ 2.0 Feature Overview (updated 2026-10-01, accessed 2026-10-04)
- Bandwidth: DCA2 vetting rejection reasons (2026-03-17)
- Telnyx: 10DLC carrier error codes explained (accessed 2026-10-03)
- Twilio: Edit or Delete an A2P Brand or Campaign Use Case (updated 2026-05-21)
- HighLevel: A2P campaign rejections, required fixes and vetting errors (modified 2026-09-09)
- Bandwidth: 10DLC fees (updated 2026-09-16)
- Telgorithm: Authentication+ 2.0 is expanding in January 2027 (published 2026-08-28, accessed 2026-10-04)
Rules change often and providers sometimes disagree; where they do, this page says so. This is general information, not legal advice, and no one can guarantee approval. See the disclaimer.
Related problems
- Twilio 30891, 30907, 30919-30922, 30473, 30489, 30526 · DCA 804, 807 · Proxy 1003 · TF 1201-1205Website rejected for A2P or toll-free: what reviewers need to see
- Twilio 30903, 30914, 30915, 30752, 21732 · DCA 801, 802 · Bandwidth 6100Sole Proprietor A2P registration: limits, OTP and rejection codes
- Twilio 30527, 30530, 30472 · TF 1103, 1111, 1112Toll-free Business Registration Number required (since Feb 17, 2026): fix Twilio 30527
- TCR fees · DCA $15 vetting · carrier surchargesA2P 10DLC fees in 2026: registration, vetting, resubmission and surcharges
The Approval Kit adds industry template packs, opt-in and policy page templates, and an agency checklist.