Availability
Tollgate is launching with a narrow geography by design. We prefer to be fully-compliant in fewer places than half-compliant everywhere. Requests from non-supported regions receive 451 GEO_BLOCKED.
Test mode
Operators running TOLLGATE_MODE=testnet (see test-mode docs) do NOT enforce the US-state whitelist above. The country-level OFAC sanctions block (IR, KP, RU, CU, SY, BY, and occupied Ukraine regions) applies in all modes — federal sanctions law is not a product launch gate.
Supported US states (at launch)
- WY — Wyoming
- TX — Texas
- FL — Florida
- DE — Delaware
- MT — Montana
- NH — New Hampshire
The authoritative allowlist is enforced at the edge by the facilitator (ALLOWED_STATES env). This list is the summary; the env var is the source of truth.
Supported countries
- United States (select states, see above)
- Canada
- United Kingdom (payment-facilitator mode)
Not yet supported
- EU (all member states) — Pending GDPR counsel engagement and second-opinion on coordination-as-transmission.
- New York, California, Washington (US) — Money-transmitter licensing is expensive; prioritised for phase 2.
- OFAC-sanctioned jurisdictions — Permanently blocked. No exceptions.
Developer perspective
As a developer, your own geography is unaffected by this list — you can operate from anywhere (subject to your local laws). The restrictions apply to agents making paid requests, which the facilitator detects by source IP.
I'm blocked but think I shouldn't be
Reach out at support@tollgatepay.com. Geo- blocks are rule-based, not account-based — there's usually an easy answer (VPN misdetection, etc.).