August 1, 2026

Shopify Payments: Payout Bank Accounts by Currency

Shopify has removed the previous eight-currency limit on bank accounts for multi-currency payouts. The new rule is one bank account for each supported payout currency, according to Shopify’s Changelog.^[1]

That is useful only if a merchant treats it as a controlled finance change. It does not mean every currency is available to every merchant, remove payout fees, or make every foreign-currency balance the right operating choice. Shopify says eligibility depends on plan and region, and non-domestic payout fees still apply.^[1]

Quick answer

Before adding a payout account, confirm the supported currency, the legal account holder, the destination bank’s requirements, fee treatment, and who will reconcile the balance. Then record the setting change and verify the first payout against Shopify’s current documentation.

What actually changed

Previously, Shopify capped multi-currency payout bank accounts at eight currencies. Its July 2026 announcement says that cap has been removed: eligible merchants can now add one bank account for every payout currency Shopify supports for their region and plan.^[1] Shopify frames the benefit as receiving funds in the currency the customer used, rather than converting them back to a domestic currency first.

This is a configuration change, not a promise of savings. Currency conversion, banking fees, tax reporting, accounting policy, supplier payment needs, and country-specific availability are separate questions. Use Shopify’s Help Center as the live source of truth before acting.^[2]

Separate customer currency from operating currency

A store can sell to customers in several currencies without needing a separate operating bank account for each one. The useful question is not whether a currency appears in checkout; it is whether keeping a balance in that currency supports a documented business process. Examples include paying a supplier in the same currency, funding a local expense, or reducing routine conversions that finance has already measured.

That distinction keeps a merchant from turning a simple platform improvement into a cluttered treasury setup. If the business still converts every foreign-currency balance immediately, a separate account may add a bank feed, accounting mapping, approval path, and close checklist without materially improving the outcome. If it retains and spends a currency regularly, the account may give finance a clearer view of exposure and settlement timing.

Neither conclusion should be made from a generic rule of thumb. Merchant volume, settlement timing, banking terms, entity structure, tax obligations, and supplier contracts differ. The durable decision is the one the store can explain and reconcile later.

A practical merchant decision checklist

1. Confirm eligibility first. Check your Shopify plan, store region, supported currencies, and the payout documentation. Do not infer eligibility from a changelog headline.
2. Map a real operating use. A separate account can make sense when the business has material expenses, suppliers, tax obligations, or a formal treasury process in that currency. A small, irregular balance may create more reconciliation work than value.
3. Validate the bank account. Confirm account ownership, currency acceptance, local routing requirements, and access controls with the bank. Use an account controlled by the correct legal entity.
4. Model the fee and conversion path. Compare the expected payout, bank, supplier, and eventual conversion costs. “Paid in the customer’s currency” is not the same thing as “no cost.”
5. Assign a reconciliation owner. Decide how the new balance maps to the ledger, who investigates exceptions, and how month-end evidence is retained.
6. Change deliberately and observe the first payout. Record the before/after setting, approver, timestamp, test amount if applicable, and first settlement result.

Reconcile the first payout before normalizing the process

Most payout-setting errors are easier to fix while the first settlement is still visible. After the configuration is approved, finance or the designated operator should compare the first payout against the expected currency, amount, fee treatment, destination account, settlement date, and ledger entry. Preserve the Shopify payout reference and the bank confirmation in the appropriate controlled record.

Do not use this first-payout review to expose bank numbers, credentials, or sensitive customer data in a broad project channel. The change record should contain enough context to trace the decision while pointing sensitive evidence to the correct access-controlled system.

Why a change record matters

Payout settings can affect cash forecasting, accounting, vendor payments, and support questions. When a finance outcome changes, the team should be able to answer: which payout setting changed, when, by whom, for which currency, and what was expected?

A lightweight record should include the Shopify store, currency, destination account’s approved internal reference, effective date, approver, reason, fee assumption, reconciliation owner, and a link to the current Shopify documentation. Do not place full bank account numbers in a general changelog.

This is the operational problem StoreChangelog is designed to make easier: retaining context around important store changes. StoreChangelog is not represented here as publicly available in the Shopify App Store; see the product page for current product context.

A lightweight approval and rollback pattern

For a small team, this can be a short ticket with an owner and a finance approver. For a larger business, it may be part of an established payment-controls process. The shape is the same: state the requested currency and bank, link the applicable Shopify documentation, identify the reason, obtain approval, make the setting change, and record the first-payout result.

Write down what “rollback” means before changing anything. It may mean removing a bank account from payout settings, pausing a vendor-payment workflow, correcting an accounting mapping, or escalating to Shopify and the bank. It does not mean guessing at payout instructions or making a second unreviewed change during an incident. A clear owner and evidence trail prevent a bad setting from becoming a long reconciliation problem.

Teams that review platform changes every week can add this item to the same operating log they use for price, inventory, app-permission, tax, theme, and market changes. The goal is not paperwork for its own sake; it is to make consequential changes recoverable and understandable.

Common mistakes to avoid

• Adding accounts before confirming regional and plan eligibility.
• Assuming the new rule removes non-domestic payout fees or all conversions.
• Using an account that does not match the business entity or currency requirements.
• Changing payout settings without finance approval or an audit record.
• Publishing sensitive banking details in tickets, chat, or exported change logs.
• Forgetting to reconcile the first payout and investigate a variance promptly.

When doing nothing is the better choice

A merchant does not have to use every new Shopify Payments option. Keeping the existing payout setup can be sensible when foreign-currency volume is low, the business lacks a bank account that meets the relevant requirements, finance has no tested reconciliation path, or conversion timing is already handled through a different approved process.

In that case, record a conscious decision rather than leaving the change unexplored forever: note the date, the currency or currencies considered, the reason for deferring, the owner, and the review threshold. A useful reopening trigger might be sustained sales volume in the currency, a new supplier payment obligation, a documented reduction in conversion costs, or a change to Shopify eligibility. This makes “not now” an operating decision instead of an accidental gap.

Make the weekly platform-change review useful

Platform changes often arrive as short announcements, while their downstream impact crosses payments, tax, support, and finance. A weekly review should therefore classify each item before anyone changes a setting: informational, evaluate, configure, or escalate. For an item in the configure bucket, designate a named owner, list the source of truth, capture the expected business effect, and create a post-change verification step.

For this payout-account change, the practical evidence is modest but important: the eligibility check, approval record, destination-account validation, before/after setting evidence, and first-payout reconciliation. That is enough to prevent confusion without inventing compliance claims or treating an ordinary configuration change as a product launch.

Questions finance and operations should answer together

Payments are not owned by one screen in Shopify. A merchant should bring the people who understand settlement, bookkeeping, supplier payments, and customer operations into the decision before the configuration changes. The result need not be a committee meeting; a short, written answer to the important questions is often enough.

• Which business entity owns the destination account and the underlying store activity?
• Which currency exposures are natural because the business pays suppliers or expenses in that currency?
• What exchange-rate source and accounting policy apply when balances are later converted or revalued?
• Who checks deposits, fee deductions, failed payouts, and unexpected balance movements?
• What is the response if the wrong account, currency, or accounting mapping is selected?

These questions also help distinguish a sound operational use from a purely cosmetic one. A merchant that cannot name the reconciliation owner should not rush to add accounts just because the option exists. Conversely, a business already tracking multiple currency balances may find that a separate destination account reduces manual work and makes the audit trail cleaner.

Keep customer support informed without overstating the change

Customer-facing teams generally do not need to announce a payout-bank-account configuration. It does not alter a customer’s order, refund entitlement, or checkout promise by itself. Support should, however, know where to route a merchant-side payment question and avoid telling customers that a particular payout currency is available unless the merchant has confirmed eligibility in Shopify’s current documentation.

That same restraint matters in internal documentation. Say what was verified: that Shopify removed the eight-currency limit and permits one account per supported payout currency for eligible plans and regions. Do not turn that into a blanket claim that every store can receive every currency, that fees disappeared, or that a new configuration guarantees a financial result.

FAQ

Can a merchant add unlimited payout accounts?

No. Shopify’s stated rule is one bank account per supported payout currency, and availability still depends on the merchant’s plan and region.^[1]

Does this eliminate conversion risk?

No. It can change where and when conversion happens, but it does not eliminate exchange-rate exposure, fees, or accounting obligations.

Should this be treated as a security-sensitive change?

Yes. Payout destinations affect cash movement. Use least-privilege access, a documented approver, and a post-change reconciliation check.

What should I use as the definitive instruction?

Use Shopify’s current Help Center guidance, not this article, for your exact eligibility, supported currencies, fees, and setup steps.^[2]

Disclaimer

This article is general operational information, not banking, tax, accounting, legal, or financial advice. Verify your own Shopify eligibility, bank requirements, fees, accounting treatment, and jurisdictional obligations before changing payout settings.