How to Sell Tickets in Multiple Currencies for International Events

How to sell tickets in multiple currencies: the short version

If you want to sell tickets in multiple currencies for an international event, you need a ticketing setup that shows each buyer a price in their own money, takes the payment cleanly, and still lands the funds in your bank without a mystery haircut on the way. That is the entire job. The problem is that most platforms treat currency as a single dropdown you pick once and regret forever. Multi currency event ticketing is not hard in theory, but the platform you choose decides whether it is a five-minute settings change or a weekend spent cloning events and refunding people in the wrong pounds.

Here is how the money actually moves, the three ways organisers usually handle overseas buyers, and the fees hiding inside the exchange rate, so you can price like a grown-up instead of quietly donating 4% to the void.

Currency conversion: the one bit of event maths that happens after you think the sums are done. Credit: Roman Mager / Unsplash

Presentment versus settlement: the two currencies that matter

There are only two currencies in this story, and confusing them is where organisers lose money. The presentment currency is what the customer sees and is charged at checkout. The settlement currency is what actually lands in your bank account. When those two differ, a foreign exchange conversion happens somewhere, and someone pays for it (Stripe explains the distinction here).

Show a London buyer a price in US dollars and one of two things happens. Either they do mental arithmetic at the checkout, which is never the moment you want someone to pause and think, or their bank converts it for them and adds a foreign transaction fee they will absolutely blame on you. A price that reads clean in the buyer's own currency removes the friction and the finger-pointing. That is the whole reason multi-currency exists, and it is a conversion lever, not a vanity feature.

The three ways organisers handle multiple currencies

1. Pick one global currency and hope for the best

The simplest option: choose one currency, usually USD or EUR, and let every overseas buyer sort themselves out. It works, in the sense that a raft with one paddle works. You lose nothing in setup time and a little in conversion at the checkout, because a chunk of your audience is now paying a price their brain has to translate. Fine for a small event where 90% of your crowd is local. Increasingly costly the more international your list becomes.

2. Build a separate event for every region

This is the workaround people reach for on platforms that only allow one currency per event. Eventbrite, for example, locks currency at the event level: every ticket in an event must use the same currency, and once you have sold tickets you cannot switch without refunding orders or resetting the event entirely (Eventbrite's own help centre confirms this). So organisers clone the event once per currency: a GBP version, a EUR version, a USD version. Now you are maintaining three listings, three capacity counts, three sets of promo codes and three reporting exports for one event. If that sounds like a recipe for overselling, it is, and we wrote a whole separate piece on how double-booking happens.

3. Run true multi-currency through your own processor

The grown-up option: one event, one capacity count, and a checkout that presents the right currency to each buyer while you settle to your own account. Modern payment processors such as Stripe handle this natively. Stripe can present localised prices to buyers and either settle everything to your home currency or hold balances in several currencies at once, provided you give it a bank account for each (Stripe's multi-currency settlement docs). The catch is that your ticketing platform has to actually let you plug your own Stripe account in, rather than acting as the merchant of record and pocketing the currency spread itself.

Multi-currency is not about looking global. It is about not making a paying customer do arithmetic at the exact moment they are deciding whether to buy.

The fees hiding inside the exchange rate

Currency conversion is never free, but it is often invisible, which is worse. Here is where the money leaks when a payment crosses a currency line. All figures are Stripe's published rates as a worked reference; your processor's numbers may differ, so check your own contract.

Two things to notice. First, Stripe's Adaptive Pricing feature bakes a conversion margin into the price the buyer sees, and that margin scales inversely with order size: roughly 4% on orders under 500 USD, 3% between 500 and 1,500 USD, and 2% above that (per Stripe's Adaptive Pricing documentation). The customer covers it, so it costs you nothing directly, but it does inflate their price, so it is a conversion trade-off worth understanding rather than switching on blindly.

Second, and this is the one that stings: if your ticketing platform is a percentage-fee reseller, its per-ticket cut sits on top of every line in that table. You are paying a currency conversion fee and a platform fee that also happens to be levied on the converted amount. Two meters running at once. On a flat-fee platform where you bring your own Stripe account, the platform fee simply is not part of the equation, so the only currency cost you carry is the processor's, which you can see and plan for.

What good multi-currency ticketing looks like

Judge any platform against these criteria before you trust it with an international on-sale. None of them are exotic; they are just the difference between a checkout that converts and one that leaks.

• One event, many currencies. You should be able to run a single listing with a single capacity count and still present the right currency per buyer. If the only route is cloning the event per region, you are signing up for the overselling risk that comes with split inventory.

• Your own payment account. When you settle through your own Stripe rather than the platform's, the funds are yours from the moment of purchase and the currency spread is transparent, not a number the platform quietly keeps.

• Clear prices, no surprise fees at the buyer's bank. A price shown in the buyer's currency should be the price they pay. Hidden foreign transaction fees added downstream are how you end up with angry emails after a sold-out show.

• Reporting in one place. If you sold in five currencies, you want one dashboard that reconciles them, not five CSV exports and a spreadsheet formula you will get wrong at 11pm.

• Settlement you can predict. Decide up front whether you want everything converted to your home currency (simpler, one 1% conversion) or held in native currencies (more admin, less conversion). Both are valid; the platform should let you choose.

Where eventcloud fits

eventcloud is a flat-fee platform where organisers connect their own Stripe account, so international payments settle directly to you and the currency handling is Stripe's own, presented transparently rather than marked up by a middleman. Because the pricing is a flat monthly fee per user with zero per-ticket charge, there is no percentage cut stacking on top of your conversion costs, which matters most precisely when you are selling across currencies. It is a good fit for organisers running genuinely international conferences, summits and trade shows who want predictable costs. It is not the right tool if you are running a tiny free local meetup with no payments at all, in which case any of this is overkill and you should keep your life simple.

If you are pricing an international on-sale and want to see how bringing your own processor changes the currency maths, take a look at how eventcloud handles ticketing and payments or run the numbers on the pricing page before your next event goes live.