What should you check before selling event tickets internationally?

Someone overseas wants to come to your event. They can see the tickets, the date works, and they're ready to pay. Then checkout rejects their card, the price changes currency without explanation, or their confirmation never arrives. You had a buyer. Now you have a support conversation, and possibly a lost sale.

Before selling event tickets internationally, confirm that your actual ticketing account can accept the intended buyers, charge them clearly, pay your business, and handle refunds. Then test the complete purchase and support experience for the markets you plan to promote in. A platform accepting cards doesn't establish all of that.

You don't necessarily need prices in every buyer's currency or a separate website for every country. You need a setup that works for the people you're inviting, at a cost your event can afford. This guide explains what to check, what to ask your provider, and how to decide whether you're ready to start advertising overseas.

Decide what international selling means for your event

Start with the event itself. Are overseas visitors buying admission to an event in your home country? Are you taking your event to another country? Or are people buying online access from wherever they live? Those situations create different payment, tax and customer service questions.

An overseas cardholder attending your existing venue doesn't automatically mean you need a local company in their country. Equally, moving the event abroad doesn't become straightforward because your home checkout can accept their card. Separate the location of the buyer, the event, your business and your payout bank before asking anyone to confirm support.

Write a short description of the proposed sales arrangement. Include the legal business selling admission, where the event happens, the countries you intend to target, the currency you want to charge, and where you need the money deposited. Add whether tickets include accommodation, transport, meals or other services, because a bundle may need different checking from admission alone.

For example, a conference business might sell admission to its existing domestic conference while advertising to delegates in two additional countries. That is a narrower decision than launching conferences in those countries. Our guide to expanding an event business into a new market covers the wider business decision. Here, we're checking whether the ticket purchase will work.

Choose the initial markets deliberately. Existing enquiries, past attendance and relevant professional audiences are better starting points than a campaign targeting everywhere. A country appearing in website analytics tells you someone visited. It doesn't tell you whether they can afford the trip, attend the programme or complete payment.

Confirm support for your actual business and account

Ask the ticketing provider to confirm your proposed arrangement in writing. Give them the description you just prepared. A useful answer identifies what your account supports today and any conditions you must meet before launch.

You want to know whether your business can sell that event through the account, whether cards issued in your intended markets are supported, and which payment methods buyers will actually see. Ask separately about the event location, account country, charge currency and payout bank. Don't settle for a link to a worldwide customer list when you asked about your particular arrangement.

Also identify who is selling the ticket under the contract and who handles payment questions. Buyers need a clear business name, contact route and refund process. Your team needs to know whether it can resolve a problem itself or must escalate it to the platform or payment provider.

Check the account's verification status before campaign launch. Ask whether changes to business details, bank details, event location or expected sales require additional review. Complete any requested checks early enough to resolve mistakes. A support answer saying a country is generally available isn't confirmation that your own account is ready to receive money.

Keep the written answer with the event's payment settings and commercial terms. Record when you checked it and who confirmed it. If you later change the selling company, event country or banking arrangement, ask again. The earlier answer may describe a setup you no longer use.

Be specific about the limits too. If a provider cannot support an important market, choose a supported route before accepting bookings there. Don't advertise broad international availability while planning to handle exceptions through personal accounts or improvised payment requests. That creates a purchase process your staff cannot reliably explain or reconcile.

Separate the price buyers see from the money you receive

Currency decisions become much easier when you distinguish the advertised price, the currency charged to the buyer, and the currency deposited into your business account. They can be the same, but you should check rather than assume.

Stripe's supported currency guidance distinguishes the payment method's currency, the charge currency and the settlement currency. It explains that a buyer's bank may charge for a currency conversion or cross-border transaction. It also describes conversion when the charge currency differs from the currency your business receives. Those are separate points where costs can arise.

For your event, start with a simple question. What exact amount and currency does the buyer authorise at checkout? Write the answer using the currency code, such as USD, wherever a dollar symbol could be ambiguous. If another currency appears as an estimate, label it as an estimate and make the actual charge clear before payment.

Then ask what reaches your bank. Does the provider convert the sale? Does your bank convert the deposit? Can you receive the charge currency directly, and what account conditions apply? Ask where the exchange rate and conversion cost appear in your reports so finance can explain the difference later.

A single clear charge currency can be a sensible starting point for an event attracting occasional international visitors. Offering more currencies may help a larger overseas audience, but you need to understand pricing control, conversion costs and refunds before enabling it. More choice isn't useful if nobody can explain the amount on the receipt.

Don't promise that paying in a familiar currency removes every possible bank charge. Ask the provider what it controls and distinguish that from charges imposed by the buyer's bank. Your checkout copy should explain your own charges accurately without making guarantees about somebody else's account.

Check conversion offers before turning them on

A buyer selecting a currency and a checkout offering to convert a transaction are details worth understanding. Ask your provider exactly what the buyer is being offered, who performs the conversion, and how the cost is disclosed. Avoid using several payment terms interchangeably in your own help text.

Visa's explanation of dynamic currency conversion describes a conversion offer that includes an exchange rate and potentially additional fees. Visa says the buyer should see the relevant amounts, rate and markup, and have a choice about accepting the offer. Use that explanation to guide your questions if your setup offers this service.

Walk through the actual screens. Can a buyer understand which currency they selected? Can they return to the original choice? Does the final payment button agree with the order summary? Does the receipt show the amount they authorised? A feature name in a sales presentation doesn't answer any of those questions.

Review the wording your support team will use. "You were charged in USD" is different from "your bank converted the payment into your account currency." Support should identify which happened before trying to explain the difference between a ticket receipt and a card statement.

If the conversion offer is confusing during testing, resolve the confusion before sending more buyers through it. Ask for clearer settings or documentation, or use a supported simpler arrangement. You shouldn't need to teach each buyer how your payment setup works while they're deciding whether to purchase.

Understand the full cost of an overseas order

Ask for the cost of a representative order using your actual account terms. Include the ticketing fee, card processing, any international card surcharge, currency conversion and payout charges that apply. Check whether those charges are included in a quoted platform fee or added separately.

Then establish who pays each amount. You may cover a platform charge within the ticket price or add an allowed charge at checkout. Either way, review how the total appears to buyers and confirm the approach meets the rules that apply to the sale. A low advertised ticket price doesn't help if the final total surprises people.

Keep a clear distinction between your costs and the buyer's possible bank charges. If your provider gives a processing quote, that doesn't automatically describe the buyer's total cost. Ask for the assumptions behind any example, including account country, card issuing country, currency and payment method.

Compare international orders with the tickets you already sell. Use the amount your event keeps after relevant charges, rather than comparing gross ticket prices. Include the additional service time you expect where it is material. If a booking needs repeated manual intervention, the published processing fee won't describe the whole cost of serving it.

There may still be a good commercial reason to attract that buyer. A higher cost doesn't automatically make the sale unattractive. What matters is whether the price leaves enough money after your event's costs and whether your team can deliver what you promised. Set the budget using that answer before buying overseas traffic.

Get refund and dispute charges in the same conversation. A payment quote that covers only successful purchases leaves an important part of the event's exposure unanswered. Ask what happens to each fee when an order is refunded, disputed or cancelled, and keep those answers with the launch budget.

Test overseas payment and authentication

A familiar card logo tells buyers what kind of card they can try. It doesn't tell you why an individual payment will be approved or declined. Check supported issuing countries and methods with your provider, then test the intended purchase flow through its approved testing process.

Some transactions require the buyer to confirm the payment through their bank. Stripe's explanation of 3D Secure authentication describes prompts such as a one-time code, password or biometric check. Ask your ticketing provider how its checkout handles this step and what buyers see if authentication fails or they leave before completing it.

Test on a phone, including the return from any bank app or payment window. Confirm that a successful payment creates one order and delivers the promised tickets. Check what the buyer sees when the process is interrupted, and whether the team can distinguish an incomplete attempt from a paid booking.

Use the provider's supported test environment and instructions for declined or interrupted payments. Don't repeatedly submit genuine cards to manufacture failures. If a limited live purchase is appropriate, agree who owns it, how it will be identified and how it will be refunded. Avoid creating transactions your finance team later mistakes for customer demand.

At Loopyah, our ticket checkout supports guest purchases with card, Apple Pay and Google Pay, and the confirmation email links buyers to their QR tickets. Those capabilities address the purchase and delivery steps. Confirm your account's country, currency and overseas payment requirements with us before advertising a particular international arrangement.

Make the rest of checkout understandable

Payment can work perfectly while the event page creates doubt. A buyer travelling internationally needs to understand where they're going, when they need to arrive and exactly what their ticket includes. Check the whole purchase using the information a new visitor has, rather than the knowledge your local audience already shares.

Write the venue's full location and make the event's local time zone clear. If online admission is available, distinguish that ticket from physical entry. Explain whether recordings, accommodation, transport or meals are included only where relevant. Buyers shouldn't have to interpret a local abbreviation to establish what they're purchasing.

Review dates written only as numbers. Different readers may interpret them differently. Spell out the month where confusion is possible, and check that the confirmation agrees with the event page. A buyer booking travel around the wrong date creates a much more difficult problem than a minor wording correction before launch.

Check whether address and telephone fields accommodate your intended buyers. A required domestic postcode format can prevent an overseas visitor from completing an otherwise supported payment. Test legitimate international details through the approved flow and report validation problems to the provider. Don't tell buyers to invent domestic information to get around them.

If you offer translated pages, include the practical purchase information and important terms in the review. A polished headline followed by confusing payment or refund wording isn't a complete translation. Ask someone who understands the language and the event to check what a buyer would reasonably expect.

Make contact information easy to find before payment. State your support hours with a time zone, and explain how urgent event-day enquiries are handled. You don't need to promise constant coverage. You do need to give buyers an honest expectation about when somebody will answer.

Check tax and buyer obligations for the arrangement

Don't decide tax treatment solely from the buyer's country, the card's country or the currency charged. Your event's location and what you're selling also matter. Prepare the sales description you wrote earlier and ask your accountant to confirm the treatment for that actual arrangement.

The European Commission's place of taxation guidance illustrates why the distinction matters. It explains location rules for admission to physical events and different treatment for virtual attendance. That is a reason to check physical and online ticket types separately when they are sold together, rather than copying the tax settings across them.

Ask who calculates and collects the tax, what your business must report, and what needs to appear on receipts or invoices. If the platform handles a particular step, establish its scope. A tax field appearing in the dashboard doesn't tell you whether every obligation for your event is handled.

Also review the information and terms buyers must receive before payment. Ask a suitably qualified adviser about cancellation, postponement, refunds and applicable consumer protections in the markets you intend to target. The useful output is approved wording and operating instructions your team can follow.

If you sell admission together with travel or accommodation, flag the complete offer during that review. Don't assume advice about a standalone event ticket covers a package. Explain who supplies each part, who takes payment and what happens if one part cannot be delivered.

Collect only the buyer information you actually need for those purposes and the event. Keep your event privacy notice consistent with the purchase process, particularly if you add new service providers or information requirements. International selling shouldn't become an excuse to ask for a passport copy from everyone.

Plan refunds before the first international booking

A buyer asking for a refund should get a clear explanation of the amount you are returning and the route it will take. Write that process before launch, including cancellation of the whole event. Staff shouldn't be inventing a policy while buyers are waiting for money needed to change travel plans.

Confirm how your provider handles full and partial refunds, which fees are returned, and how you fund refunds after a payout. Ask how currency conversion works for your specific setup. Don't promise that the amount appearing on a buyer's bank statement will match an earlier converted amount unless your arrangement supports that promise.

For example, Stripe's refund documentation says refunds normally return to the original payment method and explains that the original processing fees are not returned. It also describes pending refunds when the available balance is insufficient. Check your ticketing arrangement's own terms rather than assuming a direct payment account and a platform booking work identically.

Your support message should distinguish a refund being requested, submitted, completed and visible to the buyer. Use the status your system actually provides. If a refund needs investigation, record the payment reference and route the case to the person who can trace it. Avoid telling a buyer to keep waiting without checking what happened.

Review your event refund policy against the international purchase flow. Explain your event's cancellation and postponement arrangements, and identify any questions that require individual handling. A general policy cannot establish the terms for a specific buyer's flights or hotel booking.

Finally, budget for the cash required if the event is cancelled after suppliers have been paid. Ask finance how the business would fund the refunds and what costs would remain. Growing overseas sales increases the number of people depending on that answer, even when the event itself stays in your existing venue.

Give support a safe route for payment problems

Prepare replies for the questions you expect. Why was payment declined? Was the buyer charged twice? Why does the bank show a different amount? Where are the tickets? How will a refund be returned? Each reply needs an investigation step and an escalation route, rather than a confident guess.

Ask the buyer for the order reference, contact email and a brief description of what happened. If a screenshot would help, tell them to hide sensitive information. Use the provider's secure support process when further verification is needed. Your general support inbox shouldn't become an alternative way to collect card details.

The PCI Security Standards Council explains that card verification codes cannot be retained after authorisation. Keep your support process away from collecting those codes in the first place. Never ask someone to email their full card details so a staff member can try paying on their behalf.

Don't treat an overseas name, address or language as proof that a booking is suspicious. Give staff a consistent process for referring payment concerns to the provider and checking the order status. Payment approval, refund eligibility and permission to enter are separate questions that need the appropriate evidence.

If an order genuinely needs review, use the event's agreed escalation process. Keep relevant messages and payment records together, and tell the door team only what it needs to act correctly. Our guide to evidence for ticket payment disputes explains what records to retain when a transaction is challenged.

Assign someone to monitor payment enquiries around overseas campaign launches. They need enough access to find orders and enough authority to escalate problems. A campaign can generate enquiries while the usual event team is asleep. Decide what can wait until your advertised support hours and what needs an urgent response.

Confirm when international sales become usable cash

Before you commit the expected ticket income to supplier bills, confirm how payouts work for this account. Ask when funds become eligible for payout, how the payout schedule operates, and whether the receiving bank adds processing time. Those questions concern the money your business can use, rather than the moment the buyer sees a successful order.

Stripe's payout guidance distinguishes settlement timing from payout schedules and notes that the bank can take additional time to make funds available. Your ticketing platform may have its own arrangement. Obtain the dates and conditions that apply to your account instead of copying a payment provider's general example into the event budget.

Ask what could delay a payout and how you would learn about it. If the account needs further verification, who receives the request? If a deposit fails, who investigates it? Give the responsible person access to the relevant notifications and a route to support. An unread request can become a production problem when the next supplier expects payment.

Keep enough cash available for the event's existing commitments while the first international bookings go through. Don't assume early overseas sales solve a deposit deadline until you've confirmed when those proceeds can arrive. If the timing doesn't work, adjust the payment plan or arrange dependable funding before committing the spend.

Work through one booking before approving the setup

Imagine a buyer finding your conference through an overseas campaign. You're selling physical admission to your existing venue, and the ticket is charged in USD. The buyer normally uses another currency. This is an illustrative purchase journey, not a claim about any particular account's availability or fees.

First, read the event page as that buyer. The city and country should be obvious. They should understand the date, local start time and admission type before investigating flights. If the advertisement mentions a converted price, check how that wording relates to the amount checkout will actually charge. Remove an estimate you cannot explain reliably.

Next, select the ticket and continue to payment. Check the total, currency code and fee description. If the buyer's bank asks them to approve the purchase, follow the supported test process through that step. Then check the order record and confirmation. The team should be able to establish what was purchased without relying on a screenshot of the buyer's banking app.

Now imagine the buyer contacts you because their statement shows an unfamiliar amount. Support should find the order, confirm the charge amount and currency, and identify whether the question concerns your charge or a bank conversion. It should avoid promising a correction before establishing what caused the difference. A clear receipt gives that conversation a useful starting point.

Follow the order through to payout as well. Finance needs the recorded sale, the applicable deductions and the deposit that includes it. If the provider combines several orders in one payout, establish how the report identifies this transaction. The buyer's home currency isn't necessarily the currency finance should use to reconcile the deposit.

Finally, rehearse a refund request without issuing an unnecessary real refund. Ask who decides eligibility, which system records approval and how staff verify submission. Check what the buyer would receive by email. If the event changes date, make sure your team can explain the available options using the approved policy rather than improvising a special rule for overseas customers.

This exercise is useful because it connects departments that often check their own part separately. Marketing approves the advertisement. Operations approves the event page. Finance approves the fee quote. Support writes the reply. Asking them to follow the same booking reveals whether their explanations agree before a paying customer has to point out the differences.

Run a small launch and check the complete result

Start with a controlled release to the markets you've checked. Choose a campaign budget your business can afford while you learn whether the purchase process works. Establish who can pause that campaign if genuine buyers repeatedly encounter a problem you cannot resolve promptly.

Review the steps separately. People may visit the page without selecting tickets, begin checkout without paying, pay without finding their confirmation, or receive tickets but still contact support about the charge. Those are different problems. Changing the advertisement won't fix an incorrect currency description in the order summary.

Use the reporting available in your platform and payment provider. Ask for help interpreting payment failures before drawing conclusions from a small sample. Repeated attempts by the same buyer shouldn't look like several separate lost customers. Likewise, a successful test transaction doesn't establish that every card or payment method in a market works.

Check the first payout against the orders behind it. Confirm the currency, fees and amount received, and investigate unexplained differences before increasing spend. Sales appearing in the dashboard are encouraging. You still need money arriving through the arrangement your budget relies on.

Keep a short record of problems and decisions during the launch. Note the affected step, what the provider confirmed, what you changed and whether you verified the result. This gives the next person enough information to handle a repeat without asking the buyer to explain everything again.

Agree what evidence will let you increase overseas promotion before the launch begins. You might require successful purchases through the intended methods, clear delivery of confirmations, an explained payout and no unresolved recurring checkout problem. Choose conditions that fit your event and the information you can actually observe. There is no universal number of test orders that proves a market is ready.

Keep the decision practical. If payments succeed but buyers repeatedly misunderstand the venue location, correct the page before increasing reach. If buyers understand the offer but a supported method repeatedly fails, ask the provider to investigate that method. If the first deposit cannot be explained, finance should resolve the difference. Each finding should lead to an action someone owns and a check that establishes whether it worked.

Before expanding the campaign, read the original sales description once more. Can your business accept these buyers, explain their charges, deliver their tickets and return money through a clear process when required? Increase the reach when the evidence supports those answers. If one remains uncertain, resolve that specific outstanding issue before inviting more people to pay.