Resolution cascade
When you submit a transaction or a standalone lookup, the engine checks each level in order and returns the first match:Three integration paths
Path 1: ZIP code (recommended)
Send the merchant’s ZIP code. The engine resolves the full location chain automatically using a Census database of 33,791 U.S. ZIP codes — no address parsing required on your side.Path 2: State, county, and city
Send the location components directly. Use this path when your POS already has structured address data and you want explicit control over the resolution inputs.Path 3: Explicit override
Send the rounding mode and jurisdiction directly. Use this path for testing, development, and edge case handling where you need to force a specific rounding behavior regardless of the merchant’s location.Standalone ZIP lookup
You can resolve a ZIP code without processing a transaction. This is useful for pre-validating a merchant location at onboarding time or displaying compliance information in your POS UI.Coverage
The jurisdiction database currently covers:- 33,791 ZIP codes mapped to state, county, and city
- 6 enacted states with active rounding legislation
- 55+ bills tracked across 35+ states with pending or proposed legislation
- Automatic updates when new legislation is enacted
You do not need to redeploy or update your integration when new state legislation is enacted. The jurisdiction database updates automatically, and all in-flight transactions immediately reflect the new rules.