# BRD-163 — Name the ISV on a toll-free verification filed for someone else

> Where a toll-free verification is submitted on behalf of an end business, the ISV or reseller name must be disclosed.

- **Rule ID:** BRD-163
- **Layer:** Brand (`BRAND`)
- **Checks:** `tfv.isv_name`
- **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:** Bandwidth
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/brand/brd-163/

## Why this rule exists

Toll-free verification asks who is filing as well as who is being verified, because the reviewer needs to know whether an unfamiliar contact in the submission is the business or its vendor. Leaving it out makes the ISV's own details look like inconsistencies in the end business's record, which is a much worse reading than the truth.

## How to fix it

Populate the ISV name field with your own company name on every toll-free verification you file for a customer. Done when the submission names both the end business and the party filing it.

## Example of a compliant value

```text
isv_name: Northstar Platform, Inc · company_name: Acme Coffee Co, LLC
```

## Provider rejection codes

| Provider | Code | Resubmission allowed |
| --- | --- | --- |
| Bandwidth | `TFV 1301` | yes |

## Notes

Applies on the toll-free verification path rather than to 10DLC brand registration; the condition lives in the check, which passes immediately for a 10DLC submission. Where the path is not declared the rule is silent rather than assuming one.