Every IP range, with its country's currency.
Every IPv4 and IPv6 range matched to its country's official currency — the ISO 4217 code, the name and the symbol — for pricing and checkout pages that adapt to where a request comes from.
Schema at a glance.
See documentation →The database's schema and metadata are documented carefully. It is published as CSVGZ and MMDB.
| start_ip | end_ip | country | currency_code | currency_name | currency_symbol |
|---|---|---|---|---|---|
| 2a01:7a7:2:1630:: | 2a01:7a7:2:1630:ffff:ffff:ffff:ffff | FR | EUR | Euro | € |
| 2001:470:1f13:93:: | 2001:470:1f13:93:ffff:ffff:ffff:ffff | IN | INR | Rupee | ₹ |
| 2a0e:ec01:7c00:: | 2a0e:ec01:7fff:ffff:ffff:ffff:ffff:ffff | NZ | NZD | Dollar | NZ$ |
| 1.0.0.0 | 1.0.0.255 | AU | AUD | Dollar | A$ |
| 23.230.24.0 | 23.230.25.255 | US | USD | Dollar | $ |
Downloading it from code.
Database API reference →One call gets you the current IP Country Currency build. Every official client wraps it three ways: straight to disk, a time-limited link you hand to your own runner, or bytes in memory. A file written to disk lands only once the whole transfer has arrived, and checksums() returns the published digests to verify it against.
download()downloadUrl()downloadBytes()metadata()checksums()import osfrom internetdata import InternetDataclient = InternetData(os.environ["INTERNETDATA_API_KEY"])# what is in today's build, without moving the filemeta = client.database.metadata("ip_country_currency_v1")client.database.download("ip_country_currency_v1", "mmdb", "./ip_country_currency_v1.mmdb")sums = client.database.checksums("ip_country_currency_v1", "mmdb")print(meta.updated, meta.entries, sums["sha256"])
Getting your hands on it.
The file is the product. Teams join IP Country Currency against traffic they already log, inside their own infrastructure, and never send an address anywhere to get an answer.
Pricing and checkout
Default a price or a checkout to the visitor's own currency before they have to tell you.
Reporting
Label revenue and invoices with the currency a country actually uses.
An official client for every major language.
All SDKs on GitHub →Twelve official clients for the languages you ship in, each wrapping the database endpoints — list what you are licensed for, poll a build, follow the download redirect, verify what landed. Install commands are in the docs.
No loose ends.
How often does this database rebuild?
Daily. The metadata call answers when the current build landed and how many rows it holds, before you fetch it.
Where does the country come from?
It's the country IP Geolocation gives the same range, so the two files agree.
Why is the currency sometimes empty?
A few territories have no currency of their own, Antarctica among them. Their ranges still carry the country, with the currency left blank.
Which formats does a build ship in?
Gzipped CSV and MMDB, both cut from the same build. The schema section above names them.
Test the real build first.
An evaluation license puts a full current build in your hands — every row, every column, no sampling — so you can measure it against your own traffic before anyone talks about terms.