Charity use case requires a verified 501(c)(3) non-profit brand
The requirementstatement
The CHARITY use case is restricted to a NON_PROFIT brand holding verified 501(c)(3) tax-exempt status.
- 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
- brand.entity_type + brand.tax_exempt_status + campaign.usecase
- Where it liveslayer
- Brand ↔ campaignCROSS
- 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
- Fix the fieldRETRY_FIELD
- A better value in the form fixes it. Ekas can rewrite it and re-check.
- Who requires itauthorities
- TCRTwilioInfobip
- When it appliesapplicabilityText
- Applies when the use case is CHARITY.
Why this rule existsrationale
How to fix itremediation
Register the brand as NON_PROFIT with its 501(c)(3) EIN and declare the tax-exempt status on the brand record. The EIN must appear in the IRS Tax-Exempt Organization Search. If the organisation is a 501(c)(4) or (6), choose a different use case.
A compliant exampleexample
Entity type: NON_PROFIT · Tax exempt status: 501(c)(3) · Use case: CHARITY
Rules you will hit next
Other brand ↔ campaign rules at the same severity. A registration is judged as a whole, not rule by rule.
XBC-002 is one of 13 brand ↔ campaign rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.