# How Sender ID Verification works

Sender IDs identify the sender of application-to-person (A2P) SMS messages.
Before A2P SMS can be sent through DIDWW using these Sender IDs, the
business and messaging traffic must be approved through a Sender ID
Verification.

## What is a Sender ID?

A Sender ID is the name or phone number shown as the sender of an
application-to-person (A2P) SMS message. It helps recipients identify the
sender. If the Sender ID supports incoming SMS messages, recipients can also
reply.

DIDWW supports four Sender ID options:

- **Alphanumeric** displays a business or brand name instead of a phone number. It is not linked to a DID number and does not support replies.
- **Long-code** uses an eligible DID number assigned to the DIDWW account.
- **Toll-Free** uses an eligible US Toll-Free DID number assigned to the DIDWW account.
- **Carrier** uses a dynamic Sender ID assigned by the destination carrier. It is not linked to a DID number in the DIDWW account.

The Sender ID type determines what recipients see, whether replies are
possible, and which country requirements apply. For a detailed comparison, see
[Sender ID types](sender-id-verification-types/index.html).

## Why do Sender IDs require verification?

Regulations and downstream carriers can require businesses and Sender IDs to be
registered before A2P messages are delivered. Verification establishes who is
sending the messages, where the traffic will be sent, and whether the intended
messaging use is supported.

Depending on the Sender ID type and country, a verification can associate the
following information:

- The business identity and address.
- The Sender ID or eligible DID numbers.
- The countries where the Sender ID will be used.
- The messaging use case and campaign description.
- The recipient consent and opt-out process.
- Sample messages and supporting documents.

The submitted information must describe the same business and traffic that
will use the Sender ID. For messaging and consent requirements, see
[A2P SMS compliance requirements](compliance-content-requirements.html). For type-specific fields, see
[Sender ID Verification reference](sender-id-verification-reference.html).

## How does Sender ID verification work?

A Sender ID Verification contains the business and messaging details required
to approve a Sender ID for use in specific countries. For Carrier
verifications, approval applies to the messaging traffic rather than a specific
Sender ID because the destination carrier assigns the Sender ID dynamically.

The submitted information is reviewed by DIDWW. Once approved, the Sender IDs
covered by the verification can be used for the approved business, countries,
and messaging purpose. To send messages, associate the verification with an
[outbound SMS trunk](../sms-trunks/index.html).

The estimated review time is shown in the DIDWW User Panel before submission.
Actual approval time can vary depending on the Sender ID type, country
requirements, and whether additional information is requested.

## Verification lifecycle

```
        ---
config:
  layout: dagre
---
flowchart LR
   classDef decision stroke:#fb923c,fill:#fef3c7,stroke-width:2px
   classDef action stroke:#22c55e,fill:#dcfce7,stroke-width:2px
   classDef outcome stroke:#ef4444,fill:#fee2e2,stroke-width:2px
   classDef input stroke:#38bdf8,fill:#e0f2fe,stroke-width:2px

   new["New"]:::input
   review["In Process"]:::decision
   active["Active"]:::action
   changes["Changes Required"]:::outcome
   closure["Pending Closure"]:::decision
   closed["Closed"]:::outcome

   new -->|Review started| review
   review -->|Approved| active
   review -->|Changes requested| changes
   changes -->|Review resumed| review
   active -->|Closure requested| closure
   closure -->|Closure completed| closed
```

A newly created verification has the **New** status. Its status changes to
**In Process** when the review starts and to **Active** after approval.

If the submitted information needs corrections or additions, the verification
moves to **Changes Required**. After you update and resubmit it, it returns to
**In Process** when the review resumes.

When you request closure of an active verification, its status changes to
**Pending Closure**. After the closure is completed, the status changes to
**Closed**.

When you request closure of an active verification, it moves to **Pending
Closure**. After the closure is completed, it becomes **Closed**.

For complete status definitions, see [Status
values](sender-id-verification-reference.html#sender-id-verification-statuses).

## Pricing and billing

Verification pricing depends on the Sender ID type and destination country.
Charges can include:

- A **non-recurring charge (NRC)** for the one-time setup fee.
- A **monthly recurring charge (MRC)** for maintaining the verification.

The applicable NRC and initial MRC are charged after the verification is
approved and its status becomes **Active**. Subsequent MRCs are charged on the
renewal date shown in the verification details.

Before submission, the DIDWW User Panel shows the applicable setup fee,
recurring price, per-message pricing, and the amount due upon approval. Message
usage charges are separate from verification setup and recurring charges.

Always review the pricing shown in the DIDWW User Panel before submitting a
verification. For billing field descriptions, see
[Sender ID Verification fields](sender-id-verification-reference.html#sender-id-verification-fields).

## Managing Sender ID Verifications

Verifications can be updated, resubmitted when changes are required, or closed
when their Sender IDs should no longer be used. For task instructions, see
[How-to guides](how-to-guides/index.html).

## Related resources

- [Sender ID types](sender-id-verification-types/index.html)
- [Compliance content requirements](compliance-content-requirements.html)
- [Sender ID how-to guides](how-to-guides/index.html)
- [Sender ID Verification reference](sender-id-verification-reference.html)
- [SMS trunks](../sms-trunks/index.html)

On this page