Local Currency at Checkout

Available via: hosted checkout. Nothing to integrate.

Enablement: off by default, per account. Contact Inflow to have it enabled.

What it does

Your prices stay in your settlement currency. At checkout, a customer can choose to pay in their own currency instead. They see the price converted, pay in what they know, and you are still paid in EUR, GBP or USD exactly as before.

The example below uses a Turkish customer, but any of the 134 supported currencies works the same way.

The amounts shown were captured on 1 September 2026. Rates move continuously — the proportions hold, the exact figures will not.

Your link             20.00 EUR     ← unchanged, this is what the link is worth
A Turkish customer   1,141.85 TRY    ← what they see and pay, at a locked rate
You receive           20.00 EUR     ← unchanged

Those are real figures from a €20.00 link, taken from a live checkout. Of the 1,141.85 TRY, about 1,117.64 is the €20.00 at the mid-market rate and the remaining ~24 TRY is the conversion fee — paid by the customer, not deducted from you.

There is no API to call and no code to write. Once the feature is on for your account, the hosted checkout offers the choice on its own.

What the customer sees

1. They open your checkout. We propose a currency based on where they are connecting from.
2. When a currency is applied, the rate is locked for five minutes and the price is displayed in it.
3. They pay that amount. Their bank sees a charge in their own currency, no foreign-transaction surprise on their statement.

The suggestion is never binding

Whatever we propose from their location, the customer can switch to any other supported currency at any point before paying — and switch again as many times as they like. They pick from the full list of currencies available for your account; the location-based suggestion is only a starting point.

Two consequences worth knowing:

• Each switch re-locks the rate for a fresh five minutes. The price updates to the new currency and the countdown restarts.
• Choosing your own settlement currency removes the conversion entirely. A customer we suggested lira to can decide to pay in EUR instead: the conversion is dropped, they pay your price as-is, and no conversion fee applies.

So a customer connecting from Istanbul is not locked into lira, and a customer travelling abroad is not stuck with the currency of wherever they happen to be.

If the rate expires

If the five minutes elapse before they finish, the checkout fetches a new rate and the displayed price updates. A payment already in flight when a rate expires is re-quoted automatically, within a 30-minute window and only if the rate has not moved more than 2%; beyond either bound the customer is asked to confirm the new price.

Who pays the conversion fee

The customer does. Their payment is converted at a rate that includes the conversion fee, which is why the amount they see is higher than the raw mid-market conversion of your price. That is exactly what leaves your side whole.

A customer who pays in your settlement currency triggers no conversion and pays no fee. Nothing is deducted from you in either case.

Both figures are recorded on the payment: what the customer was charged, in their currency, and what settled to you.

Be transparent with your customers. The figure shown at checkout is the amount their bank will charge, conversion fee included. There is no second fee added later. Many customers assume a converted price hides a surcharge; here the price they see is the price they pay.

Availability

Subscription creations and renewals are not converted — they are charged in your settlement currency.

If you also price in a local currency

If you use Pricing in a Local Currency to name your prices in, say, Turkish lira, the two features meet:

• You name 1,500.00 TRY. We store 26.84 EUR — the mid-market value of what you named.
• A Turkish customer at checkout sees about 1,530.48 TRY — your 26.84 EUR converted back, with the conversion fee applied.

The difference is the conversion fee. You were charged nothing when you named the price — that API uses the mid-market rate, with no fee so you receive the full value of what you set, and the customer who triggers the conversion pays for it. A customer paying in EUR sees 26.84 EUR and no conversion happens at all.

The figure you name is not a promise to the customer. It is how you express a price. Rates move, and a customer paying in that currency sees a slightly higher figure. If you need a customer to see an exact round number in their currency, price the link in your settlement currency and set that number yourself.

Related

• Pricing in a Local Currency — naming your own prices in another currency
• Checkout V2
• Understanding Your Balance