What currencies can net payment terms actually be issued in? Does this work the same for international B2B buyers?
Net payment terms carry no currency restriction of their own, because a term is a day count attached to an order. The currency comes from the market tied to the buyer's shipping address, and B2B multicurrency requires Shopify Payments (Shopify Help Center, September 2026). The real limit is settlement: ACH Direct Debit is United States and USD only.
Separate the term from the currency from the settlement
Three things get collapsed into this question and they behave differently.
- The term is
net,fixed,fulfillmentorreceiptwith a day count (perPaymentTermsType, Shopify developer docs, September 2026). It has no currency field. Net 60 is Net 60 in every market you sell into. - The currency is a property of the order, set by the market. "The local currency and pricing are determined by the market associated with the customer's order," and that market is "determined by the shipping address of the customer" (per Shopify Help Center, September 2026). To sell multicurrency in B2B you must be on Shopify Payments.
- The settlement method is where the actual restrictions live, and they are tighter than either of the above.
What restricts what
| Capability | Currency or country constraint |
|---|---|
| Payment terms (all types) | None |
| Multicurrency B2B pricing | Shopify Payments required |
| Catalog currency | Set on the price list; does not set the storefront currency, which follows the market |
| Vaulted credit card | Shopify Payments required |
| Vaulted bank account / ACH Direct Debit | United States merchants, USD, US bank accounts, more than 100 fulfilled orders |
| Store credit on a company location | Multiple currencies per location; only the balance matching the checkout currency is shown |
| Manual payment method (wire, check) | None from Shopify; your bank's, and your reconciliation |
So the honest shape of the answer: an international B2B buyer can absolutely be issued Net 60. What they cannot do is settle it by ACH, and what you cannot do is auto-charge a vaulted bank account in their currency. Outside the United States, a net-terms invoice on a non-USD order is most often settled by wire against a manual payment method, which means no platform fee, no automatic matching and a manual reconciliation on your side.
The two traps in cross-border B2B terms
Catalog currency is not storefront currency. "The catalog currency doesn't determine the currency that your customers are presented with in your online store. The online store currency is based on the customer's market" (per Shopify Help Center, September 2026). A price list built in EUR does not make a buyer check out in EUR unless the market is configured to. Teams discover this after the price list is loaded.
Changing a draft order's market does not re-derive taxes from the market. Shopify's international B2B guidance warns that changing a draft order's market while keeping the original shipping address leaves the original taxes and duties in place. On a terms order that sits open for 60 days, a mis-taxed draft is a credit note later. Also note that price-rounding rules under Shopify's international tools do not apply to B2B customers, so a converted wholesale price will not be tidied for you.
Who carries the FX risk on a 60-day term
Nothing in Shopify answers this, and it is the most consequential currency question on a terms book. An order priced in EUR and paid 60 days later settles at a rate nobody knew on order day. Three defensible positions, and you should pick one explicitly:
- Price in your home currency and let the buyer carry the FX. Simplest, and some buyers will refuse.
- Price in the buyer's currency on a fixed price list and review the list on a stated cadence. You carry the drift between reviews, and the list is a commercial document you can show.
- Price in the buyer's currency and shorten the term. Net 30 halves the exposure window against Net 60 at no cost to anyone but the buyer's working capital.
When NOT to offer cross-border terms
- When you have no collections route in that jurisdiction. A due date you cannot enforce is a price concession.
- When the term is long enough that FX movement exceeds the margin. Do the arithmetic against your own volatility, not a benchmark.
- When the account expects ACH and is not in the United States. The feature does not exist for them, and discovering it at checkout is a bad first order.
This page describes platform behaviour and commercial modelling, not tax, customs or foreign-exchange advice. Duties, tax treatment and cross-border collections obligations are jurisdiction-specific.
The Deploi point of view
Our own position, from building on Shopify. Separate from the facts above.
- Our take: The currency question is nearly always a settlement question wearing a currency costume. Terms travel everywhere; the automated ways of getting paid do not. Scope cross-border B2B terms against the settlement method first, and the currency configuration second.
- What we’ve seen: The catalog-currency and storefront-currency distinction is the single most common configuration surprise we encounter in B2B markets work. It is documented, it is easy to miss, and it surfaces after somebody has already loaded a price list.
- Where we disagree: The standard advice is to align catalog currency with market currency and move on. That is fine as far as it goes and it skips the question that actually costs money, which is who holds the FX exposure for the length of the term. We would rather a client shorten the term than quietly absorb 60 days of drift on a large account.
- What this page adds: that terms carry no currency field at all, that the binding constraints are on settlement rather than on terms, that catalog currency does not set storefront currency, and the three defensible ways to allocate FX risk across a 60-day term.
Reviewed by Martin Dejnicki, Director of SEO & AI Search. Facts verified 2026-09-14.
Where we worked this out
Our decision records