Pricing_
Simple pricing. The whole commerce layer on every tier.
Every tier includes live central-bank FX and the full formatting engine. Start free — no card required — and move up only when your traffic or your fraud needs do.
Free
$0/mo
Everything you need to ship a localised checkout.
- Requests
- 10,000/mo
- Rate limit
- 30/min
- Live central-bank FX
- Full formatting engine
- IP & domain restrictions
Pro
$49/mo
For production traffic with tax and payments.
- Requests
- 500,000/mo
- Rate limit
- 300/min
- Tax rates & reduced bands
- Local payment methods
- Batch lookups (100 IPs)
Business
$249/mo
Fraud signals and the full response.
- Requests
- 5,000,000/mo
- Rate limit
- 1,000/min
- Network & threat signals
- Fraud check (BIN vs IP)
- Historical FX
Enterprise
Custom
Volume pricing, SLAs and support.
- Requests
- Custom
- Rate limit
- Custom
- Custom quotas & limits
- Priority support
- Everything in Business
197
markets, hand-verified_
5
central-bank FX sources_
6
REST endpoints, one dataset_
12
digit money precision in bcmath_
What's in each tier
This is the same table the API enforces in code — a feature is either in your tier or the response says so, never a silent downgrade.
| Feature | Free | Pro | Business | Enterprise |
|---|---|---|---|---|
| Geo, flag, currency, locale, phone | ||||
| Live central-bank FX | ||||
| IP and domain restrictions | ||||
| Tax rates and reduced bands | — | |||
| Local payment methods | — | |||
| Batch lookups (100 IPs) | — | |||
| Network and threat signals | — | — | ||
| Compliance flags | — | — | ||
| Fraud check (card BIN vs IP) | — | — | ||
| Historical FX | — | — |
Case studies_
Designed for teams who care about every checkout.
“One call at checkout and we finally show the right currency, tax and payment methods in every market. Cart abandonment on cross-border orders dropped noticeably.”
[Customer story]
[Company]
[Company]
[Headline metric — e.g. cut cross-border abandonment]_
“The BIN-versus-IP signal caught mismatched cards our old geo API was blind to. It plugged straight into our existing risk rules.”
[Customer name]
[Improved metric]
“Central-bank FX we can actually attribute to a source, and formatting that is correct down to the decimal — JPY with no decimals, India in lakh/crore. It just does the tedious part, and the response tells you where every number came from.”
[Customer story]
[Company]
Pricing questions, answered
What counts as a request?
One API call. Cached responses served from your own infrastructure cost nothing, and requests that fail authentication are never billed.
What happens when I hit my quota?
The API returns 429 with the reset time. It does not silently degrade or start charging overage — you choose whether to upgrade.
Where do the FX rates come from?
Directly from central banks — the ECB, the US Federal Reserve, the State Bank of Pakistan and others. Public data, no reseller licence, no markup. When a source is stale we say so in the response rather than serving a stale rate as fresh.
How is the country data verified?
Formatting comes from ICU/CLDR and is re-checked by an automated test on every build. Tax rates and payment methods are researched against national tax authorities and payment-provider documentation, and re-verified on each data release. Where a source is thin, the profile says so instead of guessing.
Can I use this for fraud prevention?
The Business tier includes datacenter, VPN and Tor detection plus the BIN-versus-IP country comparison. It is a signal, not a verdict — we give you the inputs and the score, and you decide your own policy.
Do you store card numbers?
No. The fraud endpoint accepts the first 6-8 digits of a card (the BIN) and rejects anything longer at validation. A full card number cannot be sent to this API even by accident.