# XBC-002 — Charity use case requires a verified 501(c)(3) non-profit brand

> The CHARITY use case is restricted to a NON_PROFIT brand holding verified 501(c)(3) tax-exempt status.

- **Rule ID:** XBC-002
- **Layer:** Brand ↔ campaign (`CROSS`)
- **Checks:** `brand.entity_type + brand.tax_exempt_status + campaign.usecase`
- **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, Twilio, Infobip
- **Applies:** Applies when the use case is CHARITY.
- **Canonical URL:** https://ekas.io/rules/10dlc/cross/xbc-002/

## Why this rule exists

Charitable messaging gets favourable treatment — better throughput and more tolerance for solicitation content — so eligibility is verified against the brand record rather than taken on trust. 501(c)(4), (5) and (6) organisations are tax-exempt but are NOT charities for this purpose, which is where most rejections come from.

## How to fix it

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.

## Example of a compliant value

```text
Entity type: NON_PROFIT · Tax exempt status: 501(c)(3) · Use case: CHARITY
```