DPV: Confirming an Address Actually Exists

## CASS vs. DPV

A common misconception: CASS-certified address validation confirms that a specific address exists. It doesn't. CASS verifies that the **address range** exists — for example, that 100-200 Main Street is a valid block.

DPV (Delivery Point Validation) goes further: it confirms that **153 Main Street** is an actual delivery point with a mailbox.

## How DPV Works

| Check | Result |
|-------|--------|
| Address in USPS database | Y = confirmed delivery point |
| Address not found | N = not a known delivery point |
| Secondary (apt) required | S = address valid but missing unit |
| Secondary present but invalid | D = unit number doesn't exist |

## DPV Return Codes

DPV returns several flags:

- **DPV Match (Y/N/S/D)** — Primary result
- **DPV Footnotes** — Detailed reason codes (AA, A1, BB, CC, etc.)
- **CMRA (Y/N)** — Commercial Mail Receiving Agency (e.g., UPS Store mailbox)
- **Vacant (Y/N)** — Address is known to be vacant
- **No-stat (Y/N)** — Address not regularly served (seasonal, etc.)

## Why DPV Matters

Without DPV, you can send mail to addresses that:

- Were demolished or condemned
- Never existed (typo in the house number)
- Are missing apartment/suite numbers
- Are commercial mail drops (CMRA), not physical locations

## CMRA Detection

CMRAs — businesses that rent mailboxes (UPS Store, PostNet, private mailbox services) — are often used for fraud. DPV's CMRA flag identifies these addresses, which is critical for:

- **Financial compliance** — Banks must verify physical addresses
- **Identity verification** — KYC/AML regulations
- **Insurance** — Claims from CMRA addresses raise red flags

## Implementation

DPV is not a separate product — it's a component of CASS-certified software. When you run addresses through a CASS engine with DPV enabled, you get both address standardization and delivery point confirmation in a single pass.

Most modern address validation APIs include DPV by default.