# BRD-157 — Say whether you are the business or a reseller registering for it

> The business-identity and reseller flags must say correctly whether the registering party is the brand itself or an ISV, reseller or partner.

- **Rule ID:** BRD-157
- **Layer:** Brand (`BRAND`)
- **Checks:** `brand.business_identity + brand.is_reseller`
- **Severity:** MEDIUM — Usually survives review, but lowers your trust score or invites manual review.
- **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:** Twilio, Telnyx
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/brand/brd-157/

## Why this rule exists

This flag is how the platform knows whether to expect the brand's own details or a third party's, and it changes what is treated as a contradiction: an agency address on a direct-customer registration is a finding, while the same address on a declared reseller registration is not. Setting it wrong turns correct data into suspicious data.

## How to fix it

Set the flag to direct_customer when the business is registering itself, and to isv_reseller_or_partner when you are registering on someone else's behalf. Declaring the reseller relationship does not weaken the registration — concealing it does. Done when the flag matches who filled the form in.

## Example of a compliant value

```text
is_reseller: false · business_identity: direct_customer — for a business registering itself
```

## Provider rejection codes

| Provider | Code | Resubmission allowed |
| --- | --- | --- |
| Twilio | `30894` | yes |

## Notes

Only the internal consistency of the two fields is checkable here. Whether the declared answer is TRUE is BRD-160 and BRD-121, which read it against the campaign and the contact details.