Verify customer age with the AvaTax age verification API
domain: avalara.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Review the 'Understanding the age verification APIs' guide to see how age verification fits into the overall BevAlc transaction workflow before integrating.
Call the Verify Age endpoint with the purchaser's identifying details to check age compliance for a beverage alcohol transaction.
Use Store Verification to persist a successful age-verification result against a customer record.
Use Find an Age Verification Record to look up whether a given customer already has a stored, valid verification before re-verifying.
Use Store if Verified to combine the verify-and-store steps for a streamlined checkout flow.
Tie the verification result into the shipping verification workflow, since purchaser/recipient date-of-birth are also evaluated as part of BevAlc shipment compliance.
Known gotchas
Age verification and shipment compliance verification are separate API surfaces that both feed into whether an order is ultimately compliant — passing one does not guarantee the other passes.
Storing a verification result (Store Verification / Store if Verified) avoids re-verifying the same customer on every order, but stale records should be periodically re-checked depending on state rules.
These endpoints are part of the certified BevAlc integration path and are expected to be exercised as part of Avalara's functional review before production use.
Give your agent this knowledge — and 15,500+ 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?