Only two payment processors on Shopify can charge in the customer's currency

Showing a market’s prices in another currency and charging in that currency are two separate Shopify features. Neither belongs to the store. Both belong to the payment processor.

For charging, exactly two processors have it. Shopify’s documentation on local currencies, checked on July 13, 2026, is explicit: “To process payments in multiple currencies, your store must use Shopify Payments or Adyen as its payment processor. If you use a different provider, then customers in all markets pay in your store’s default currency.” The guidelines for selling in local currencies state the same rule from the other side: orders placed through other third-party payment providers are processed in the store’s default currency, and reports are available only in the store currency.

The same rule covers showing, which is the part this post originally got wrong. The same guidelines page, checked on August 13, 2026, says that “showing prices in local currencies and setting manual exchange rates do require that you use Shopify Payments.” The admin enforces it: on a store without a completed Shopify Payments account, the currency setting in Markets is disabled outright, behind a notice that asks you to complete the Shopify Payments setup first. What stays available on every plan is market-specific prices and percentage adjustments, in the store’s own currency.

So without Shopify Payments a customer in Bratislava never sees a euro through Markets at all: the product page, the cart and the checkout all stay in the store’s default currency. A store can still show euros through a currency app or through prices it computes itself, and that route is described below, but the checkout still charges the default currency, and the customer’s bank may add its own conversion fee on top of that charge.

You can put any number on a page. You can only charge the one your payment processor supports.

Why it surprises people

Nobody plans multi-currency as a payment feature. On a store that runs Shopify Payments you open Markets, add a market, watch the prices convert, and it reads as a storefront setting. The dependency runs the other way, and it surfaces at two different moments.

On a store that never completed Shopify Payments it surfaces at once: the currency setting is locked, and the notice in Markets says to finish the Shopify Payments setup before customizing currency. The admin at least names the dependency there.

On a store that had the feature, it surfaces on the day the payment processor changes: a new legal entity behind the store, a move to a local gateway, a Shopify Payments account that has to be verified again. Local-currency pricing leaves with it. Nothing in the admin connects the two events, so what the store sees is that the euro prices stopped working on a day when nobody touched the euro prices.

The four routes

Set up Shopify Payments. This unlocks the feature exactly, and in engineering terms it is the cheapest of the four, because there is no engineering in it. The cost is paperwork, and the paperwork has its own section below.

Adyen as the primary gateway. The only other processor Shopify documents for this, and its requirements page rules it out for most stores. Shopify’s requirements for the Adyen integration, checked on July 21, 2026, ask for an existing Adyen account, Shopify Checkout, and the Enterprise plan, the custom-priced tier above Shopify Plus that Shopify sells to its largest merchants; the same page states that access is granted by approval only. For a mid-size store this route is unavailable in practice.

A second store with the euro as its default currency. This works, with no tricks in it, and it is the honest answer when the euro market is really a different business: different assortment, different pricing, sometimes a different legal entity. What people cost is the second subscription, which is the small number. The large number is the second copy of the catalog, the theme, the apps and every integration, plus an inventory sync between the two stores that runs for as long as both exist.

Compute the prices yourself and display them. Currency apps do this, and so does storing your own converted prices in metafields. Without Shopify Payments it is the only way a localized price reaches the storefront at all. It is the route that gets proposed once the other three are unwelcome, and it needs the most care, so it gets its own section too.

What a self-computed price can reach, and what it cannot

Prices you compute yourself can reach every surface you control. The storefront, a draft order, an internal tool, a PDF quote: each of these renders numbers you supply, and each will render euros correctly.

The checkout is not a surface you control. With a third-party provider Shopify processes the order in the store’s default currency, whatever the product page said, and the reports come out in the store currency too. The euro price is therefore correct everywhere except at the point where the money is taken.

That makes this route conditional on one question about the business: does any customer ever pay you in euros through Shopify’s checkout? If a customer can put a euro price in the cart and pay by card, the price on the product page is not the price that gets charged. If the euro path instead ends in a draft order, an invoice and a bank transfer, then the checkout never handles a euro, no one is charged in the wrong currency, and computing the prices yourself is not a workaround at all. It is where the pricing has to live.

Before building any of it, check one thing. Shopify documents a currency override on draft orders once Markets is set up, with the exchange rate fixed at the moment the draft order is created. Collecting payment on such an order is restricted: Shopify’s stated limitation is that with deferred payment terms in a non-default currency you can collect only by credit card or by marking the order as paid. That may cover the quoting case without any metafields, or it may fail to survive contact with your invoicing. Test it on the actual store before writing code that assumes either answer, and not on a development store. Shopify’s page on test orders in development stores, checked on August 13, 2026, rules out draft orders and manual payment methods such as cash on delivery for checkout testing, and warns that processing an order through one of them can lock the store’s ability to process orders. The supported way to test a dev-store checkout is the test payment provider with test card numbers.

The paperwork, and why the owner cannot argue with it

The objection to Shopify Payments is rarely technical. Setting it up means identifying the people behind the company: a photo ID, a date of birth, the company’s beneficial owners, the registration number, the VAT number and a SEPA bank account. Shopify publishes the exact list per country, so it varies by a document here and there, and on the Polish page a beneficial owner is anyone holding 25 percent of the business or more. Owners resist all of this, and they resist hardest when they read it as Shopify prying into a business that is none of its concern.

Every one of those country pages gives the same reason, in the same sentence, with only the country’s name changed. Here is the page for Czechia, checked on July 13, 2026: “Shopify and its banking partners are required to collect and verify information about you and your business, in order to comply with regulations in Czechia that are designed to prevent financial crimes.”

Every card processor collects the same information, because every card processor answers to the same anti-money-laundering rules. An owner who declines to identify the company’s beneficial owners is declining to accept card payments anywhere, and the next provider asks for the same documents.

If the company is Slovak, the first route does not exist

Shopify Payments runs in a fixed list of countries. The supported-countries list, checked on July 13, 2026, includes Czechia, Germany and Poland. It does not include Slovakia.

For a Slovak entity, then, the first route is unavailable rather than merely difficult, and no amount of persuading the owner to complete the verification will change that. Adyen requires the Enterprise plan, so the choice narrows to a second store or self-computed prices. Establish this early, before somebody spends a week preparing an application that cannot be submitted.

The question that decides it

The decision turns on who pays you in euros. If customers pay in euros, the currency belongs to the payment processor, and for most stores that means Shopify Payments. If customers are quoted in euros and settle against an invoice, the checkout never handles the currency, and you are free to put the price wherever it is most useful.

Answer that first. Every option above is cheap or expensive depending only on the answer, and it is a question for the business rather than for the developer. The work that follows either answer is on our Shopify page.