Verify a user's address using proof-of-address document checking
domain: identity-general · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Accept a document image from the user that represents a proof of address such as a utility bill, bank statement, or government letter
Submit the image to an IDV vendor's proof-of-address extraction endpoint along with the applicant's stated address and name
Retrieve the extracted fields including the name on the document, the address, and the document issue date
Compare the extracted name against the user's verified identity name using fuzzy matching to allow for minor variations
Compare the extracted address against the user's stated address and apply a match policy that accepts minor formatting differences
Verify that the document issue date falls within the maximum age window required by your policy (commonly 90 days) and reject stale documents
Known gotchas
Document issue date extraction can fail for documents that do not prominently display a date; build a fallback path that routes to manual review when date extraction confidence is low
P.O. box addresses on proof-of-address documents are typically not acceptable for financial services compliance; validate that the extracted address is a physical residential address
Name matching across proof-of-address documents often encounters nicknames, middle names, or suffix differences; a pure exact match policy will generate excessive false rejects
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?