Fraud loves a mismatch. Before you authorize a card, check the issuing country against the IP, see whether the request comes from a datacenter, VPN or Tor exit, and read a composite risk score — the payments-aware signals a plain geo API cannot give you.
Why it works_
The signal a geo API cannot give you
BIN vs IP country
The killer signal: a Nigerian card from a Pakistani IP is worth a second look.
Anonymity detection
Datacenter, VPN and Tor exits surfaced and scored.
Your policy, your call
A transparent score and named signals feed your rules; you decide the threshold.
One call, these response blocks.
This page maps to these blocks of the same response every other page reads:
- Network & fraud
curl -X POST "https://api.localesense.com/v1/fraud/check" \
-H "Authorization: Bearer ls_live_..." \
-d '{"ip":"203.135.62.10","bin":"539983"}'
What your code sees, per request.
The sample on the right is the shape of the real response for a visitor in Karachi — every value attributable, nothing guessed. Point the same call at any of the 197 markets.
Try it live in the docs- Risk 12/100 · no VPN · BIN match
Keep exploring_
Related use cases
Show every buyer the right currency, format and payment methods.
Learn moreApply the correct consumption tax in every market you sell to.
Learn morePrice in local currency at a live central-bank rate.
Learn more