Localize checkout in one flow
Detect where a shopper is, price in their currency and show accurate delivery times — resolved before the page even paints.
How the flow works
The flow in code
{ "country": "United States", "country_code": "US", "currency": "USD", "isp": "Google LLC" }
{ "from": "USD", "to": "EUR", "rate": 0.9213, "result": 92.13 }
{ "timezone": "America/Los_Angeles", "utc_offset": "-07:00", "local_time": "2026-07-03T09:12:44-07:00" }
Piece it together, or ship one flow
A shopper from Munich lands on checkout and sees dollars, a US shipping estimate and a date in the wrong format — most of them bounce. Getting it right means detecting their country, converting to their currency at a fresh rate and rendering delivery windows in their local time. Historically that’s three vendors and three round-trips, all before the page paints.
Piece it together yourself
- Integrations: IP, FX and timezone — 3 vendors
- Speed: 3 serial round-trips
- FX rates: Stale nightly tables
- Billing: 3 dashboards, 3 invoices
One Locanium flow
- Integrations: 1 Locanium key
- Speed: One call, sub-40 ms
- FX rates: Live rates, 168 currencies
- Billing: One dashboard, one bill
Why teams build it on Locanium
One request flow
Country, currency and timezone from a single integration — no juggling three vendors.
Fast enough for first paint
Sub-40 ms median means it resolves before the checkout renders.
Global from day one
240+ countries and 168 currencies with real-time rates.
No per-endpoint fees
One key covers geolocation, currency and timezone.
- <40ms
- Median response
- 240+
- Countries
- 168
- Currencies
Step-by-step guides for this flow
Questions developers ask
How fast does it resolve?
Sub-40 ms median — geolocation, currency and timezone return before the checkout finishes its first paint, so shoppers never see a flash of the wrong locale.
Where do the exchange rates come from?
Live interbank feeds refreshed continuously across 168 currencies — never a nightly lookup table that drifts out of date.
Is an IP accurate enough to price on?
IP geolocation resolves country and region with high confidence, which is what currency and pricing need. For street-level accuracy, pair it with the GPS Geolocation endpoint.
Do I have to store the visitor’s location?
No. Call the endpoints at request time and use the result inline — nothing about the flow requires persisting the IP or location.
How is it priced?
One key, usage-based — geolocation, currency and timezone all bill off the same plan. Book a demo for volume pricing.