Address Cleansing vs Verification vs Standardization
Four terms that often overlap, defined from published sources, with live API output for each step and a table of when you need which.
Address cleansing is the umbrella term: Smarty defines it as the collective process of standardizing, correcting and then validating a postal address. Parsing splits an address into fields. Standardization rewrites it with postal abbreviations. Verification checks it against authoritative address data for accuracy, completeness and deliverability. An address cleansing API typically runs these steps together.
The four terms, defined
Each definition below is quoted from a published source. The last column shows what an API that does that step returns, using sthan.io field names from live calls on October 4, 2026, rechecked on October 6, 2026.
| Term | Definition | Source | What an API returns |
|---|---|---|---|
| Parsing | "a method of breaking down a postal address into individual components so that each can be analyzed, standardized, and validated." | Loqate glossary | Separate fields: addressNumber, streetName, streetPostType, unitType, city, stateCode, zipCode |
| Standardization | "A standardized address is one that includes all required address elements and that uses the Postal Service standard abbreviations" | USPS Publication 28, section 211 | One address in postal format, for example 233 S Wacker Dr STE 3300, Chicago, IL 60606-6387 |
| Verification | "the crucial process of checking the accuracy, completeness, and deliverability of a physical address against an authoritative, official source of truth." | Loqate glossary | A deliverability result, for example dpvConfirmation Y and deliverableStatus Confirmed |
| Cleansing | "the collective process of standardizing, correcting, and then validating a postal address." | Smarty | The results of all three steps together |
Loqate defines cleansing in similar words: "the process of reviewing and reformatting postal addresses to make them accurate, complete, and updated." Loqate also notes that verification is "often referred to as Address Validation", while saying the two are slightly different.
One building, two calls, live
The same input, 233 south wacker drive suite3300 chicago illinois, sent to the sthan.io parser and to sthan.io verification on October 6, 2026.
| Parser call | Verification call | |
|---|---|---|
| Address returned | 233 S Wacker Dr, Chicago, IL 60606-7147 | 233 S Wacker Dr, Chicago, IL 60606-7147 |
| Unit | Not returned; unit marked Unmatched | Not returned; unit marked Unmatched |
| Deliverability | Not part of a parse | dpvConfirmation D, deliverableStatus ConfirmedPrimaryOnly: the building is confirmed, the suite is missing |
| Match signal | Near, confidence 0.9 | Near, confidence 0.9 |
Both calls standardized the returned address the same way, and both said they could not match the suite glued to its number. Only verification added a deliverability status: D means the primary number was DPV-confirmed and the secondary (unit) information was missing. Here the building was confirmed and the suite was missing, so a form should ask for the suite. With the suite typed as "Suite 3300" and the ZIP included, both calls returned 233 S Wacker Dr STE 3300, Chicago, IL 60606-6387, and verification returned dpvConfirmation Y (Confirmed). Parsing tells you what the parts are. Verification adds a postal deliverability status.
When you need which
| Your goal | Step you need | Why |
|---|---|---|
| Split one address field into street, city, state and ZIP columns | Parsing | You need the parts, not a postal check |
| Store or print addresses in one consistent postal format | Standardization | Publication 28 abbreviations and formatting; adding a missing ZIP+4 needs a lookup in postal data |
| Check that an address is deliverable before you ship | Verification | A verification call returns a postal deliverability status |
| Fix an old customer list in one pass | Cleansing | Standardize, correct and validate every row |
In practice the steps stack. Loqate describes the order: once the data is parsed, "the next step is to standardize it and convert it to a consistent format." Smarty adds that before an address can be validated it must first be in the official postal format. The sthan.io verification API, for example, returns the standardized address and the deliverability result in one call.
Where sthan.io fits. sthan.io offers two of these steps as APIs. The US Address Parser returns separate fields with a match tier and confidence: 100 free a month, then $8 a month for 10,000. US Address Verification returns the standardized address, ZIP+4 and a deliverability status: 100 free a month, then $12 a month for 10,000. Neither free tier needs a credit card. sthan.io is not CASS-certified.
Frequently Asked Questions
Sources
Read October 4, 2026, and rechecked October 6, 2026: smarty.com/articles/address-cleansing; loqate.com/en-us/glossary pages for address parsing, address verification and address cleansing; USPS Publication 28 section 211 on pe.usps.com; live sthan.io v2 address parser and v2 address verification responses (the same input to both, October 6, 2026); sthan.io/pricing/united-states. Prices change; check the vendor page before you buy.
Try parsing and verification free
100 parses and 100 verifications a month, no credit card.