Quick answer
The best payment gateway for event tickets is the one that lets attendees pay the way they already pay, gets money to your bank account before your event bills are due, and doesn’t stack extra platform fees on top of card processing. For most organizers selling on their own WordPress site, that means starting with a mainstream gateway such as Stripe or PayPal, checking its payout schedule against your event’s cash-flow needs, and confirming it supports your country, currency, and your attendees’ favorite payment methods. Because Tickera charges no per-ticket fees, the gateway’s processing fee is the only cost per sale you need to compare.
- Compare gateways on total cost per ticket (processing fee + fixed fee), not just the headline percentage.
- Payout speed matters more for events than for regular e-commerce — you often need the money before the event happens.
- Offering the right local payment methods (not just cards) can noticeably lift checkout conversion.
In this guide
- What a payment gateway actually does
- Understand the three layers of fees
- Payout speed and event cash flow
- Payment methods your attendees expect
- Countries, currencies, and compliance
- Popular gateways compared
- Refunds, disputes, and chargebacks
- How Tickera helps you keep gateway costs down
- Set up and test before you launch
- Checklist
- FAQ
What a payment gateway actually does
A payment gateway is the service that securely moves money from your attendee’s card or wallet to your bank account. When someone buys a ticket on your site, the gateway collects the payment details, checks them with the card networks and the buyer’s bank, and either approves or declines the transaction in a couple of seconds. A few days later, it deposits the money — minus its fee — into your account.
It’s worth separating two things that often get lumped together. A ticketing marketplace (Eventbrite and similar) sells tickets on its own platform and takes a service fee per ticket on top of payment processing. A payment gateway only processes the payment; it doesn’t care whether you’re selling tickets, t-shirts, or consulting hours. When you sell tickets on your own WordPress site with a plugin like Tickera, you connect directly to a gateway of your choice, which means the marketplace layer — and its fees — disappears entirely. We covered that math in detail in how to sell event tickets online with no per-ticket fees.
Choosing a gateway, then, is really about four questions: what it costs per transaction, how fast it pays out, which payment methods and countries it supports, and how well it handles the messy parts — refunds, disputes, and failed payments.
Understand the three layers of fees
Ticket sellers often compare gateways on the advertised percentage alone and end up surprised by the real cost. There are up to three layers to account for:
| Fee layer | What it is | Typical range | Applies when |
|---|---|---|---|
| Processing fee | The gateway’s cut per transaction, usually a percentage plus a fixed amount | 1.4%–3.5% + $0.20–$0.49 | Every paid order |
| Platform / service fee | A per-ticket fee charged by a ticketing marketplace or SaaS platform | 2%–10% + $0.50–$2.00 per ticket | Only if you sell through a marketplace — $0 on your own site with Tickera |
| Extras | Currency conversion, cross-border cards, payout fees, chargeback fees | 0.5%–2% + fixed dispute fees | International sales and disputes |
The fixed portion of the processing fee matters enormously for cheap tickets. On a $10 ticket, “2.9% + $0.30” is effectively 5.9%. On a $150 VIP ticket, the same rate works out to about 3.1%. If you sell mostly low-priced tickets, favor gateways with a lower fixed fee, or encourage group purchases so several tickets share one fixed fee — an approach that pairs nicely with group tickets and bulk discount codes.
Run the numbers on your actual price points before deciding. A gateway that looks 0.3% cheaper can be the more expensive option once fixed fees, conversion costs, and payout charges are included. Your gateway choice and your pricing belong in the same spreadsheet — see our event ticket pricing strategy guide for the pricing half of that equation.
Payout speed and event cash flow
Here’s the part of gateway selection that’s unique to events: you usually need the ticket money before the event, not after. Venues want deposits, caterers want payment schedules, and marketing spend happens weeks in advance. A gateway with a slow or reserve-heavy payout policy can leave you cash-poor at exactly the wrong moment.
Check three things in the gateway’s terms:
- Payout schedule. Daily, weekly, or monthly? Rolling 2-day payouts (common with Stripe) beat weekly batches for cash flow.
- First-payout delay. New accounts often wait 7–14 days for their first deposit. Open and verify your account well before tickets go on sale.
- Rolling reserves for events. Some processors classify future-dated events as higher risk and hold back a percentage of revenue until the event has happened. If you sell tickets months in advance, ask about this explicitly before committing.
The most expensive gateway problem isn’t a fee — it’s discovering two weeks before your event that a chunk of your ticket revenue is sitting in a rolling reserve you didn’t know existed.
If your event date is far out, it’s also worth telling the gateway’s support team what you’re selling. Sudden spikes of transactions on a new account (which is exactly what a successful ticket launch looks like) can trigger automated fraud reviews and temporary holds. A short heads-up email before your ticket sales launch prevents most of these surprises.
Payment methods your attendees expect
Cards are no longer the whole story. Depending on where your attendees live, the “normal” way to pay might be Apple Pay, Google Pay, PayPal, iDEAL (Netherlands), Bancontact (Belgium), SEPA transfers (much of the EU), or a local bank app. Every payment method you fail to offer is a small tax on your conversion rate — some buyers will dig out a card, and some will simply leave.
A practical way to think about it:
- Everywhere: credit and debit cards, plus at least one express wallet (Apple Pay / Google Pay). Wallets matter most on mobile, where typing card numbers kills momentum.
- Audience-specific: PayPal still converts well for audiences who don’t like entering cards on unfamiliar sites; local methods like iDEAL dominate in their home markets.
- Offline fallback: for corporate events and invoiced group bookings, an offline/bank-transfer option lets you take orders that would never go through a card form.
Checkout speed matters as much as method choice: a slow, clunky payment page loses buyers who were ready to pay. Google’s payment form best practices on web.dev are a good reference for what a fast, low-friction checkout should look like. And the fewer surprises at checkout, the fewer abandoned orders you’ll need to chase — a topic we covered in abandoned cart recovery for event tickets.
Countries, currencies, and compliance
Before you fall in love with a gateway, confirm the basics for your situation:
- Merchant country. Gateways support a specific list of countries where you, the seller, can be based. This is the first filter — if your country isn’t on the list, nothing else matters.
- Settlement currency. Can it pay out in your local currency to a local bank account, or will every payout eat a conversion fee?
- Buyer currencies. If you sell internationally, can attendees pay in their own currency? Unfamiliar currencies at checkout depress conversion.
- Strong Customer Authentication. In the EU/UK, PSD2 requires 3-D Secure on most card payments. Modern gateways handle this automatically; very old or exotic integrations may not.
- PCI compliance. Prefer gateways where card data is entered on the gateway’s hosted page or embedded fields, so full card numbers never touch your WordPress server. That keeps your PCI burden minimal and your risk low — a good companion to the general hardening advice in keeping your website safe and secure.
Popular gateways compared
The exact fees vary by country and change over time, so treat this as a comparison of character rather than a price list, and verify current rates on each provider’s site.
| Gateway | Strengths for ticket sellers | Watch out for | Best fit |
|---|---|---|---|
| Stripe | Fast rolling payouts, wallets and many local methods, clean checkout, wide country support | Fixed fee stings on very cheap tickets; automated risk reviews on sudden sales spikes | Most organizers selling on their own site |
| PayPal | Huge buyer trust and existing accounts; instant balance availability | Higher effective rates in some regions; holds on new accounts selling future-dated events | Audiences that prefer not to type card details |
| Square | Same system online and at the door via card readers; simple flat pricing | Fewer local payment methods; country support narrower than Stripe/PayPal | Events that also sell tickets at the door |
| Braintree | Cards + PayPal + wallets in one integration | More setup effort; approval process for some business types | Higher-volume sellers wanting cards and PayPal together |
| Authorize.Net | Long-established, works with many merchant accounts | Monthly fee on top of transaction fees; dated buyer experience | US organizations that already have a merchant account |
| Bank transfer / offline | No processing fees at all; suits invoiced corporate bookings | Manual reconciliation; tickets shouldn’t be issued until money arrives | B2B events, group bookings, small local events |
Two gateways are often better than one: a card-first gateway plus PayPal covers the vast majority of buyer preferences, and adding an offline option catches the corporate long tail. Don’t go overboard, though — every extra option adds a decision at checkout, and a confused buyer is a lost buyer.
Refunds, disputes, and chargebacks
Events get more refund requests than most businesses — plans change, dates clash, weather happens. Before choosing a gateway, understand how it handles the unhappy paths:
- Refund mechanics. Can you refund directly from the gateway dashboard, partially or fully? Does the gateway return its processing fee when you refund? (Many no longer do — factor that into your refund policy.)
- Chargeback process and fees. A disputed charge typically costs a fixed fee ($15–$25) win or lose, plus the revenue if you lose. Clear ticket descriptions, a visible refund policy, and a recognizable statement descriptor (“MYFEST TICKETS”, not a cryptic company name) prevent most “I don’t recognize this charge” disputes.
- Evidence handling. Good gateways let you submit evidence (order details, check-in records) in-dashboard. Your check-in data showing the disputed ticket was actually scanned at the door is powerful evidence — one more reason attendance records matter, as we argued in turning attendance data into your next sell-out.
How Tickera helps you keep gateway costs down
Tickera turns your own WordPress site into a full ticketing system: you sell paid tickets with QR codes, scan them at the door with the check-in apps, and keep every attendee record on your own site. Crucially for this topic, Tickera charges no per-ticket fees — the only per-sale cost you pay is your payment gateway’s processing fee, which goes straight between you and the gateway.
Tickera ships with built-in support for a wide range of payment gateways — including Stripe, PayPal, Braintree, Authorize.Net, 2Checkout, Mollie, PayUmoney, and a free offline/bank-transfer gateway — so you can pick the option that fits your country and audience rather than being locked into one processor. You can even enable more than one gateway at once and let attendees choose at checkout. If you prefer WooCommerce’s checkout, the Bridge for WooCommerce add-on lets you sell Tickera tickets through any of the hundreds of WooCommerce payment gateways, as described in selling event tickets with WooCommerce without marketplace fees.
Because you keep the marketplace layer out of the transaction, the savings scale with your success: on 1,000 tickets at $30 with a typical $1.50 + 3% marketplace service fee, you’d hand over roughly $2,400 in service fees alone — money that stays in your budget when you sell from your own site. See Tickera’s pricing for the flat license cost, then do the math for your own event size.
Set up and test before you launch
Whichever gateway you choose, wire it up properly before the on-sale date:
- Verify the account early. Complete identity and bank verification days or weeks before launch so nothing blocks your first payout.
- Use sandbox/test mode. Run test purchases end-to-end: order, payment, confirmation email, ticket delivery, and a test check-in scan.
- Do one real transaction. Buy the cheapest ticket with a real card, then refund it. This catches configuration issues test mode can’t.
- Check the statement descriptor. Make sure the charge on a buyer’s card statement clearly names your event or brand.
- Test on mobile. Most ticket buyers are on phones; confirm wallets appear and the payment form is usable with one thumb.
- Confirm refund flow. Know exactly which buttons you’ll press when the first refund request arrives, before it arrives.
These steps slot straight into the broader ticket sales launch checklist we published — payment testing is the step most often skipped and most expensive to skip.
Checklist: choosing your gateway
- Confirm the gateway supports your country as a merchant and pays out in your currency.
- Calculate total cost per ticket at your price points, including fixed fees.
- Check payout schedule, first-payout delay, and any rolling reserve for future-dated events.
- Make sure cards + at least one wallet (Apple Pay / Google Pay) are covered; add PayPal if your audience skews that way.
- Add an offline/bank-transfer option for corporate and group bookings.
- Read the chargeback fee schedule and set a clear statement descriptor.
- Verify the account and run sandbox + one live test purchase before launch.
- Enable it in Tickera (or via the WooCommerce Bridge), and test the full order-to-check-in flow.
Final thoughts
There is no universally “best” payment gateway — there’s the best one for your country, your ticket prices, and your audience’s habits. The good news is that the decision is low-risk when you sell on your own site: gateways in Tickera can be switched or combined without rebuilding your store, so you can start with the obvious mainstream choice, watch your checkout conversion and fee reports for a few events, and adjust. Spend your energy where it compounds — pricing, promotion, and a smooth event day — and let the gateway be the boring, reliable plumbing it’s supposed to be. If you get the plumbing right, everything in selling more event tickets gets easier.
FAQ
What is the cheapest way to accept payments for event tickets?
Sell on your own WordPress site so you avoid marketplace service fees, then compare gateways on total cost at your actual ticket prices. For invoiced corporate or group bookings, an offline bank-transfer option costs nothing in processing fees. With Tickera there are no per-ticket fees, so the gateway’s processing fee is your only per-sale cost.
Can I use more than one payment gateway at the same time?
Yes. Tickera lets you enable multiple gateways simultaneously, and attendees pick their preferred method at checkout. A common combination is a card gateway such as Stripe, plus PayPal, plus an offline option for bank transfers.
Do payment gateways charge extra for selling tickets to future events?
Not officially, but some processors treat future-dated events as higher risk and may apply a rolling reserve — holding back a percentage of revenue until after the event. If you sell tickets months in advance, ask the gateway about reserves before committing, and contact their support ahead of a big on-sale spike.
Is Stripe or PayPal better for selling event tickets?
Stripe generally offers faster rolling payouts, more local payment methods, and a smoother embedded checkout, while PayPal brings strong buyer trust and millions of existing accounts. Many organizers offer both and let attendees decide; the split in your own sales data will tell you which one your audience prefers.
Do I need a merchant account to sell tickets online?
Not with modern gateways. Stripe, PayPal, Square, and similar providers act as the merchant of record for processing, so you only need a standard business (or in many cases personal) bank account for payouts. Traditional gateways like Authorize.Net may still require a separate merchant account.
How do refunds work through a payment gateway?
You trigger the refund from the gateway’s dashboard (or your site), and the money returns to the buyer’s original payment method, usually within 5–10 business days. Note that many gateways keep their original processing fee even when you refund — worth factoring into your refund policy and pricing.
