# BRD-247 — Check the token has not expired before importing it

> A Campaign Verify token must be checked for expiry before it is imported.

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

## Why this rule exists

Tokens are obtained when the paperwork is ready and imported when the campaign is, and those can be months apart — so an expired token is the normal consequence of an organised team working ahead. The import is refused, and the replacement has to come from Campaign Verify rather than from the provider.

## How to fix it

Read the expiry date off the token before importing, and request a fresh one if it has passed or is close. Done when the token in hand is current at the moment of import, not at the moment it was issued.

## Example of a compliant value

```text
token expiry: 2026-11-30, imported 2026-08-14 — current at the time of import
```

## Provider rejection codes

| Provider | Code | Resubmission allowed |
| --- | --- | --- |
| Twilio | `21722` | yes |
| Twilio | `30713` | yes |