Glossary

Stripe Multi-Currency Price

A Stripe multi-currency Price is a single Price object that carries a fixed amount for each of several currencies in its currency_options field, so a customer can be charged, say, 45 EUR or 39 GBP instead of the default 49 USD without you creating a separate Price for each currency.

Also called: currency_options, manual currency prices, price by currency, multi-currency pricing

14-day free trial · card required · cancel anytime

Definition

Most Stripe Prices have one currency and one amount. A multi-currency Price keeps its default currency and amount, and adds a map called currency_options with an amount for each extra currency you choose. You set those amounts yourself, which is the whole point: 45 EUR is 45 EUR whatever the exchange rate does next month.

Stripe calls this approach manual currency prices, and it is not what Stripe recommends first. Its Checkout guide says: “Stripe recommends using Adaptive Pricing instead of manual currency prices to reduce currency exchange rate fluctuation risk and to automatically enable support for over 100 local currencies.” Manual prices remain the right tool when you want round local prices, when Adaptive Pricing isn’t available for your setup, or when you are comfortable carrying the exchange rate risk in a given market.

The accounting difference between the two is bigger than the pricing difference. A charge made through a currency option is a charge in that currency. A charge made through Adaptive Pricing is recorded in your own price currency. That decides what currency the sale has when it reaches QuickBooks.

Key points

  • +currency_options is a map on the Price object: one entry per extra currency, each with its own unit amount.
  • +The default currency is the first one on the Price, and Stripe requires all your Prices to share it.
  • +The API doesn’t return currency_options unless you expand it.
  • +Checkout picks the currency from the customer’s IP address. Subscriptions created through the API use the default currency unless you pass a currency.
  • +A currency option overrides Adaptive Pricing for that currency.
  • +A charge through a currency option is in that currency, so QuickBooks needs to record a foreign-currency sale.

How a multi-currency Price is built

In the Dashboard you add a Price in your main currency, then use “Add a price by currency” to add others. Stripe’s guide sets the first rule: “The default currency is the first currency on your Price. All your Prices must have the same default currency.”

For each extra currency you enter the amount, and Stripe offers a starting point: “Stripe suggests an exchange rate based on currency values at 12:00 pm EST, but you can pick your own. For currencies that are subject to larger fluctuations, we recommend adding more of a buffer.” After that the amount is fixed. It doesn’t move with the market, which is what makes it a price rather than a conversion.

In the API, the amounts live in currency_options, keyed by currency code, each with its own unit_amount. The field is easy to miss when you inspect a Price, because “The API response won’t include currency_options by default.” You have to expand it to see what a customer in another country is actually being offered.

The same idea extends past Prices. Stripe notes that “Coupons, promotion codes, and shipping rates also support multi-currency in a similar way to prices.”

Which currency a customer is charged in

A multi-currency Price offers several currencies. Each purchase still uses exactly one, and how Stripe chooses depends on where the Price is used.

Checkout chooses for you. Stripe: “Checkout automatically determines the customer’s local currency from their IP address, as long as the price supports that currency. If the customer’s local currency isn’t supported, Checkout uses the default currency for the price.” Every item in the session has to agree. If any Price, coupon, promotion code or shipping rate lacks the customer’s currency, the whole session falls back to the default. If you use Stripe Tax, each currency also needs its own tax_behavior. When localization succeeds, Stripe says “Fields like currency, payment_method_types, and amount_total reflect the local currency and price.”

Subscriptions created through the API don’t choose at all. Stripe: “If you create subscriptions directly, the multi-currency prices don’t take effect until you pass the currency parameter. If you don’t pass the currency parameter, the subscription always uses the default currency for the price.” Adding a EUR option to a Price your backend already uses changes nothing for API-created subscriptions until your code passes currency=eur.

Invoice items and charges you create with explicit amounts are a third case. Stripe: “If you create invoice items or charges with the API, Stripe processes the amount and currency you explicitly provide.”

Multi-currency Price vs Adaptive Pricing

Both show a French customer a price in euros. They do it in opposite ways, and they leave different records.

With a currency option, you chose the euro amount in advance and the customer pays it. The charge, the invoice and the balance transaction are in EUR.

With Adaptive Pricing, Stripe converts your price in real time, using “an exchange rate guaranteed for 24 hours.” The customer pays in euros, but Stripe records the sale in your price currency: “The Checkout Session and the underlying PaymentIntent objects reflect what your customer paid in your integration currency and amount.” The euro figure appears only in a presentment_details hash on the events.

When both exist, yours wins for that currency. Stripe: “Manually defined multi-currency prices override Adaptive Pricing for those currencies, even if it’s enabled.” The Adaptive Pricing guide makes the same point from the other side: if a Price has currency_options for EUR and GBP, Adaptive Pricing won’t convert to those currencies but can still convert to others. So a business with a handful of hand-set currency options and Adaptive Pricing on can end up with sales in two shapes: EUR sales recorded in EUR, and CAD sales recorded in USD.

A worked example, and what the balance sees

Take a Price of 49 USD with currency options of 45 EUR and 39 GBP, on a US Stripe account with no extra settlement currencies. A customer in France buys through Checkout and is charged 45 EUR.

The charge is a EUR charge. Your Stripe balance is in USD, and Stripe’s settlement guide explains what happens next: “Before incoming currencies settle in your account, Stripe automatically converts them into the default currency of your home country.” The USD amount that lands depends on that day’s conversion, and Stripe’s manual currency prices page lists a currency conversion fee among the fees on converted transactions.

So one sale produces two figures that both matter: 45 EUR, the amount the customer agreed to and the amount on the invoice, and a USD amount that varies by day, the amount that funds your payout. If you enable settlement in EUR instead, the 45 EUR stays in a EUR balance and Stripe charges its processing fees in EUR.

The GBP customer and a US customer paying 49 USD follow the same pattern. The point for the books is that a multi-currency Price makes some of your revenue foreign-currency revenue, on purpose, at amounts you set.

What QuickBooks needs before currency_options sales sync

A sale through a currency option is a sale in that currency, so syncing it means syncing a foreign-currency transaction, and that needs setting up on both sides before the first one arrives.

QuickBooks first. QuickBooks Online must have its own Multicurrency setting turned on to record any transaction outside its home currency, and once it is on it cannot be turned off. Acodei’s Invoice Sync lists it as a prerequisite whenever any invoice currency differs from the QuickBooks home currency.

Then Acodei. Its multicurrency handling has two levels, and neither is a self-serve toggle: both are enabled by the Acodei team on request. Multicurrency Support matches the Stripe transaction currency to the QuickBooks customer. QuickBooks fixes one currency per customer, so when a customer already set up in USD makes a EUR purchase, Acodei creates a second customer record named in the format Acme - EUR. That is designed behavior required by QuickBooks, not a duplicate to clean up. Invoice Multicurrency goes further for Invoice Sync users: the QuickBooks invoice is created in the Stripe invoice’s currency, and the payment is recorded in that currency with an exchange rate, taken from Stripe when available and otherwise from QuickBooks. Without it, invoices post in the QuickBooks home currency, with exchange rates applied on payment. Invoice Multicurrency isn’t available when the holding account is Undeposited Funds.

Fees follow the balance, not the price. Acodei typically records Stripe fees in the currency of the actual balance transaction, so on a USD balance the fee for the 45 EUR sale is a USD expense.

One hard limit for anyone choosing currencies. Acodei doesn’t support zero-decimal currencies such as JPY. A currency option in yen is a valid Stripe price, but Acodei can’t sync those sales correctly, so check before adding one.

Want to see this on your own Stripe data?

Start a free trial

14-day free trial · card required · cancel anytime

Frequently asked questions

What is currency_options on a Stripe Price?

It is a map on the Price object holding a fixed amount for each extra currency the Price supports, alongside the default currency and amount. Stripe uses the matching entry when a purchase is made in that currency. The API leaves it out of responses unless you expand it.

Why is my Stripe subscription still billing in the default currency?

Probably because it was created through the API without a currency parameter. Stripe says that for subscriptions created directly, multi-currency prices don’t take effect until you pass currency, and without it the subscription always uses the Price’s default currency. Checkout is different: it picks the currency from the customer’s IP address.

What is the difference between a multi-currency Price and Adaptive Pricing?

With a multi-currency Price you set each local amount in advance, and the charge is made in that currency. With Adaptive Pricing, Stripe converts your price at checkout and records the sale in your own price currency, with the local amount kept only as presentment details. Where a Price defines a currency in currency_options, that option overrides Adaptive Pricing for that currency.

Do I need QuickBooks Multicurrency for Stripe multi-currency Prices?

Yes, if any customer pays in a currency other than your QuickBooks home currency. Those are foreign-currency sales, and QuickBooks can only record them with Multicurrency turned on. The setting cannot be turned off once enabled, so decide before you switch it on.

Can I add a JPY price to a Stripe multi-currency Price?

Stripe allows it, but JPY is a zero-decimal currency, and Acodei does not support zero-decimal currencies. Sales in yen won’t sync correctly to QuickBooks through Acodei, so keep currency options to decimal currencies such as EUR, GBP or CAD if you sync with Acodei.

What customers say about running Stripe through Acodei

Stripe Verified Partner BadgeIntuit QuickBooks
★★★★★
“If you're testing out all the different Stripe/QuickBooks integration apps right now, let me save you some time. This one is the best one by far.”
RyanOwner at Indie Music Academy
★★★★★
“Works well and is really helpful for massive transactions. The support is really fast and helpful. 100% recommended.”
AndresCo-founder and CEO at Kanguro Collections and Reinsurance

Related reading

More glossary terms

See the full glossary

Ready to try Acodei?

Connect Stripe to QuickBooks Online in minutes and let the fees, refunds, and payouts land where your accountant expects them.

14-day free trial · card required · cancel anytime