IP fraud signals for shop checkout
Game-server shops and VIP webstores get hit with stolen cards and VPN-hopping buyers. IP privacy and fraud scores are one layer beside device and payment checks.
Checkout is not login
At login you may kick. At checkout you may step-up 3-D Secure, delay fulfillment, or flag for review. Same IP API, different actions.
Signals that matter for shops
Hosting / datacenter ASNs, residential proxies, mismatch between billing country and geo, and elevated network abuse scores. Tri-state privacy avoids false confidence when a field is unknown.
Currency and geo context
Nested location includes currency fields useful for storefront localization and risk rules (e.g. unexpected high-risk corridors). Pair with your own order history — IP alone is never enough.
Metering for bursty storefronts
Sales events spike lookups. REST and MCP share one meter; cache hits are discounted so repeated carts on the same exit node stay cheap.
FAQ
Can IP data stop all chargebacks?
No. Use it as a risk signal with payment and account history — not a sole deny list.
Where do I start?
Call /v1/ip with a Bearer key at checkout, or use check_fraud via MCP in ops tooling.