Strengthen onboarding, risk scoring, and compliance with a fast geo and network signal on every request.
In financial services, where a request comes from is a first-class signal. IP geolocation adds country, network, and basic risk context to onboarding, payments, and compliance — one input in your stack, resolved in under 50ms.
From everyday onboarding to risk and compliance controls. Treat security fields as signals, never a sole verdict.
Resolve country and region at onboarding so the right currency, language, and regional product rules apply from the first screen — before any manual input.
Signup → 194.60.x.x
country: United Kingdom → GBP accounts, FCA-region onboarding flow
Feed country, ASN, and connection type into your existing risk model. A payment from an unexpected country or a hosting network raises the score without blocking good customers outright.
Payment → 45.9.x.x · ASN: hosting
datacentre origin + high-risk geo → +risk score, step-up to verification
Compare the IP-derived country with the billing address at checkout. Large mismatches are a well-established card-fraud indicator worth surfacing before you capture funds.
Billing: Japan · IP country: Brazil
country mismatch → route to manual review, request 3-DS
Use country and EU-status to apply geo-restrictions, licensing boundaries, and sanctioned-region checks as a first-line compliance filter in regulated markets.
Access attempt → 5.62.x.x
country: sanctioned region → block + compliance log entry
The security object surfaces basic VPN, Tor, and threat-level signals. Treat them as one input into account-takeover and bonus-abuse detection — not a sole verdict.
Login → security.isVpn: true
VPN + new device → challenge with step-up auth
Every one of these ships in the standard response — no add-ons, no tiers.
country / countryCode Jurisdiction, sanctions, and risk geography connection (ASN / type) Hosting / datacentre origin as a risk signal security (isVpn / isThreat) Basic VPN, Tor, and threat-level inputs is_in_eu EU regulatory and data-handling rules region / city Finer-grained location for mismatch checks No — and it shouldn't be used that way. IP geolocation is one high-signal input (country, ASN, VPN/threat flags) that strengthens a broader risk model. Use it to raise or lower a score and trigger step-up verification, not to auto-approve or auto-decline in isolation.
A basic security object with VPN, Tor, and a threat-level indicator, plus connection/ASN data that reveals hosting and datacentre origins. These are solid risk inputs for most consumer flows; they are deliberately scoped as signals rather than a full enterprise fraud score.
Country and EU-status fields give you a reliable first-line geo filter for licensing boundaries and sanctioned-region restrictions. Pair it with your authoritative KYC/identity checks for the full compliance picture.
Free tier: 2,000 lookups/day, no card. Paid plans from $2.50/month. One call per event, under 50ms median response.