Regions and currencies

Sell in several currencies at once (US dollars, euros, shekels, pounds) by grouping countries into regions, each with its own currency, payment providers and, if you need it, its own choice of whether prices include tax.

Yes, you can sell in more than one currency at the same time: US dollars (USD) to American buyers, euros (EUR) to European ones, shekels (ILS) at home. Regions are how you do it.

A region binds a set of countries to a currency and a list of payment providers, and can set whether prices there include tax. When a buyer arrives, Brainerce matches their country to a region and serves them that region's setup, so an American sees dollars and a German sees euros without you maintaining two stores.

If you sell in one country and one currency, you can ignore this page. If a payment method isn't showing at checkout, this page is almost always the reason.

How a region decides what a buyer sees

Three things follow from the buyer's region:

Currency is the currency their prices are shown and charged in.
Tax in this region decides whether the price a buyer sees already includes tax or has tax added at checkout. By default it follows your store setting.
Payment providers decides which of your installed providers they can pay with.

A country belongs to one region only. Buyers whose country maps to no region fall back to your default region.

Everyone still sees my home currency

Setting up regions here is only half the job. Your website has to ask Brainerce which region the visitor is in, and pass that along with every price it looks up. A site that never asks is served your default region every single time, so a German customer sees shekels or dollars at your home prices.

This is the one setting on this page that fails without telling you. The page is not broken, no error appears, the layout is fine, and the prices are simply the wrong ones. Shops have run like this for months.

Check it now. If you have more than one region set up, look at your shop from a customer's point of view. If every visitor sees your home currency wherever they are, the wiring is missing. Your regions are configured correctly and the shop is ignoring them.

A one-region shop is not affected today, and is still worth wiring. The moment you add a second region, an unwired shop quietly serves it the wrong currency on the same afternoon you thought you had opened a new market.

Ask your developer, or your AI builder, for this:

"Detect the visitor's country, look up the matching Brainerce region, and pass the region on every product lookup and when creating the checkout. Add a currency switcher too."

The switcher matters. Guessing a country from someone's internet connection is wrong for travellers, expats and anyone on a VPN, so let people choose.

Pass the region to the checkout as well as the product pages. A shop that passes it to product pages only shows one price and charges a different one, which is worse than not having regions at all.

See a feature you turned on is not showing on your website.

Create a region

Go to Settings → Regions. The page opens with the View settings permission; changing regions needs Manage settings.
Click Add Region.
Give it a Name you'll recognise, such as "European Union", "Israel", or "Rest of world". Required, up to 100 characters.
Pick the Currency. Required. The dropdown offers USD, EUR, GBP, ILS, JPY, CAD and AUD.
Add the countries that belong to it. Required: at least one.
Under Tax in this region, leave Same as the store unless this market needs something different (see Prices with or without tax in one region).
Optionally switch on Default region (the region used for buyers whose country maps to no region).
Click Save. Save stays greyed out until the name, currency and at least one country are filled in.
Payment providers come after the first save. The Payment Providers list only appears when you edit a region, because the list of compatible providers depends on the countries you saved. Open the new region again (pencil icon) and switch on the providers that should serve it.
In the edit window you also get an Enabled switch ("Inactive regions are hidden from storefronts").

The regions list shows a Configured Regions (N) table with Name (with a Default badge and a Tax included or Tax added badge when set), Currency, Countries (a count, for example "3 countries"), Status (Active or Disabled) and three icon buttons per row: the star (Set as default, greyed out on the default region), the pencil (edit) and the trash can (delete). A disabled region is dimmed. A store with no regions shows "No regions. Create your first region to sell in multiple currencies".

A small two-arrows icon beside Add Region opens the file Export and Import menu (plus Continue or Recent imports when one applies), the same one other screens have. See Edit your data in a file.

Why a provider isn't in the list

The Payment Providers section only offers providers compatible with the countries you selected. If it says "No installed payment providers are compatible with these countries", either you haven't installed a provider that covers them, or the countries in this region aren't served by the ones you have.

This is the thing people get wrong: a gateway being installed doesn't put it at checkout. It has to be enabled for the region the buyer is in.

Setting a price per region

By default, a buyer in another region sees your price converted at the current exchange rate. That is usually fine, but it produces prices like €91.37, and it means a currency swing moves your price without you deciding to. To get tidy prices such as €91.99 without typing a price for every product, use price rounding (see "Rounding converted prices" below).

If no exchange rate has been fetched yet for that currency pair, the buyer sees your store-currency price unchanged rather than a converted one, so a German buyer would see shekels, not euros. Nothing warns you when this happens. When you add a region in another currency, or change a region's currency, Brainerce asks for a fresh exchange rate straight away, so the rate normally appears within a few minutes instead of at the next daily update (about 02:00 UTC). If a newly added region is still showing your home currency after that, no rate was fetched for that currency, and setting a manual price for the region (below) sidesteps it entirely.

To set the price yourself, open a product and find Prices per Region in the editor. Pick a region and enter a Base price and, optionally, a Sale price for it. That region now charges exactly what you typed: €89.00, not €91.37.

Your default region always uses the main Base / Sale prices at the top of the product. You only override the others.
The products table shows Manual or Auto per region, so you can see at a glance which prices you set and which are still being converted.
The Region filter on the products list narrows the table to one region while you work through a price list.
A sale price must be lower than the base price for that region, and you cannot set a sale price without a base price.
A product with variants gets one regional price for all its variants in the product editor. A different price for each variant can only be set through the API or the MCP tools. On a product with variants your default region uses each variant's own price.

A manual price only takes effect if the region actually charges in its own currency. Today that happens only with Stripe (see Which currency the customer is charged in). With any other provider, or with none enabled for the region, the buyer is charged in your store currency and sees a converted price, and your manual figure is ignored rather than applied. Check the region's Payment Providers list if a price you set isn't showing.

Manual prices replace the whole pair. A region with a manual base price will never show a converted sale price alongside it. You set both, or neither.

Which currency the customer is charged in

Showing a price in euros and charging in euros are two different things, and today only one provider does both.

With Stripe, the customer is charged in the region's currency. The payment is taken in euros (or whatever the region's currency is) at an exchange rate fixed the moment the checkout opens, so the total the customer saw is the total they pay. That rate includes a margin on top of the market rate, 2% unless you set your own. The margin goes to you and covers the conversion fee Stripe charges when it pays you out in your store currency. To change it, open the region, find FX margin (it only appears for a region in a currency other than your store's) and type a percent from 0 to 100, with up to 2 decimals. Leave it blank for the platform default of 2%; type 0 for no margin. A higher margin raises every converted price in that region, and a checkout that is already open keeps the margin it was opened with. The margin has no effect on a region where the customer is charged in your store currency.
When the region's provider is not Stripe, the customer is charged in your store currency. That covers Cardcom, Morning, Grow, Takbull, Rivhit (iCredit), Sola and a region that only has PayPal. The customer still sees prices converted into the region's currency while browsing, but the payment itself is taken in your store currency. A manual price for the region is not used for the charge in that case.
A one-currency gateway needs a store currency that matches it. Grow, Morning and Takbull take shekels only and Sola takes US dollars only. Because the charge is made in your store currency, a store in another currency cannot take payments through them: the checkout is refused before the customer is charged, with a message naming the currency. See Which gateways take one currency only.
Which provider counts. The provider that settles the checkout is the default card processor among those you enabled for the region. If you enabled none for the region, your store's default card processor is used. PayPal is only the settling provider when no card processor is available for the region.
No exchange rate yet means no foreign charge. If no rate is available when the checkout opens, the customer is charged in your store currency instead of an unconverted foreign amount. A new region gets its rate within a few minutes of being created, so this mainly affects the first minutes of a new region or a currency the exchange-rate feed does not publish.
Refunds follow the charge. A refund is made in the currency the customer was charged in, so the customer gets back the same euros they paid. What it costs you can differ slightly from what you received: Stripe converts your payout to your store currency, and takes a refund back from your balance at the exchange rate of the day of the refund. If the euro moved against your store currency since the sale, you get back a little less or more than the refund took. The 2% margin covers Stripe's conversion fee, not a rate movement, and Brainerce cannot protect you from one.
The order is recorded in your store currency, with the foreign amount saved beside it.

Rounding converted prices (.99, .95, whole numbers)

A converted price like €18.32 looks odd next to a price tag of €17.99. Price rounding turns it into a tidy price, and you choose the step per currency, in Settings > Regions: click the gear icon in the header of the regions list and open Currencies and price rounding:

None (the default): the price stays as converted, €18.32.
Whole: rounded up to the next whole unit, €19.00.
.99: rounded up to the next price ending in .99, €18.99.
.95: rounded up to the next price ending in .95, €18.95.
Half: rounded up to the next half unit, €18.50.

Pick a step and press Save rounding. The window shows a live example with three sample prices before you save. A currency with no decimals, such as the yen, offers only None and Whole.

How it works:

Prices only go up, never down. A price already on the step stays as it is. With .99, .95 and half, a converted price below one whole unit (for example €0.60) is left as converted, because rounding it up would be a large jump; Whole rounds it up to €1.00.
The rounded price is the price the customer pays. For an ordinary product line, the product page, the checkout line, the amount charged and the amount on the order are all the same number (a line with its own discount or option add-ons is the exception, below).
It only applies where the customer is charged in the region's own currency. Today that is a region paid through Stripe. A row in that window is greyed out, with the reason, when no region in that currency is charged in it. A region that only shows converted prices (any other provider) is never rounded, because the customer pays in your store currency there.
Rounding applies to product prices only. It does not change shipping, tax, discounts, gift cards, or a price you typed yourself for the region (see "Setting a price per region" above). A discount code comes off the rounded total as the converted amount of the code, not as a percent of the rounded price, and tax is not charged on the rounding step.
A cart line with a discount applied to that line, or with option add-ons, is not rounded. It is charged at its converted price, so that line can differ from the rounded price shown on the product page. A product kit is converted without rounding, on the product page too.
It is one choice per currency, not per region. Two regions in euros use the same step, so the same product costs the same in France and in Germany.
A change reaches the shop within about a minute. A checkout that was already open keeps the price it was opened with; new checkouts use the new step.
Refunding by items returns each line in proportion to what the customer was charged for the order, so a refunded line can differ by a few cents from its shelf price.
Rounding does not protect you from exchange-rate movement. The price a customer sees is converted at the day's rate and the checkout fixes the rate when it opens, so a large swing in between can still make the two differ slightly.

The default region

One region is marked Default. It catches every buyer whose country you haven't explicitly placed.

Set it deliberately. If your default is "European Union" and someone orders from Australia, they'll be charged in euros, which may or may not be what you want.

To change it, click the star (Set as default) on another region's row, or open that region and switch on Default region. The rules, so you are not surprised by an error:

You cannot delete the default region, or switch it off. Make another region the default first, then delete or disable the old one.
You cannot untick "Default region" on the default itself. There must always be one, so you move the default by setting a different region as default.
An inactive (disabled) region cannot be the default.
A country can only be in one active region. Adding a country that another active region already holds is refused, and the message names that region and the countries. A disabled region does not hold its countries, so you can reuse them elsewhere.
You cannot change a region's currency while checkouts are open in it. Wait until the pending checkouts have finished or expired, then change it.
Only providers compatible with the region's countries can be enabled. Saving a provider that is not installed for the store, or that serves none of those countries, is refused. A provider counts as compatible when it serves at least one country in the region.

Prices with or without tax in one region

Your store has one Prices include tax switch under Settings → Tax. Each region can follow it or set its own. Open the region and pick one of three options under Tax in this region:

Same as the store (the default for every new region). The region follows the store switch, and the option shows what that is today. If you change the store switch later, this region changes with it.
Prices include tax. Buyers in this region pay exactly the price shown. The VAT is already inside it and is worked out of the price for your records. This is usual in Israel, the EU and the UK.
Tax added at checkout. Buyers in this region see the price before tax, and the tax is added on top at checkout, so they pay more than the price shown. This is usual in the US and Canada.

This changes what buyers in that region pay. On a 100 dollar product with a 20% rate, "Prices include tax" charges 100 (of which 16.67 is tax), while "Tax added at checkout" charges 120. Change it before you launch a region, or tell your customers, because the next checkout in that region uses the new setting. Orders already placed keep the tax they were charged.

A region with its own setting shows a Tax included or Tax added badge in the regions list. A region with no badge follows the store.

The region only decides how the tax is applied. The tax rates themselves (for example 18% VAT for Israel) still come from Settings → Tax, and a country with no rate pays no tax whatever this option says.

Your website should show the same thing. If your shop prints "incl. VAT" or "+ tax" next to prices, it should read it from the buyer's region, not assume the store setting. Ask your developer or AI builder to use the region's effective tax setting for that label.

Turning a region off

Switch Enabled off in the region's window and the region shows Disabled in the list: "Inactive regions are hidden from storefronts". Use this to prepare a region before you launch it, or to stop selling somewhere without deleting the configuration. The default region cannot be disabled.

Deleting a region (Delete Region?) is permanent, and the default region cannot be deleted.

What's next?

Set up taxes covers the rates that apply within a region.
Connect payment methods covers installing the providers you then enable here.

On this page