The advertised ticket fee is rarely the whole payment decision. Payout timing, refund behaviour, disputes, reserves, payment-method coverage, buyer-visible fees, and the work required to reconcile money can change the economics more than a small difference in percentage rate.
Choose an event payment platform by modelling your own orders and obligations. A provider’s price page is an input, not the answer.
Build a complete payment map
| Cost or constraint | What to verify in current primary terms |
|---|---|
| Platform charge | Fixed, percentage, subscription, usage, or a combination |
| Payment processing | Methods, card geography, wallets, bank transfer, currency conversion, and processor charges |
| Buyer-facing price | Whether fees are passed on, absorbed, included, or constrained by local rules |
| Settlement | Request, processing, receipt, weekend, reserve, and eligibility conditions |
| Refunds | What is returned, retained, or charged, and who can execute the workflow |
| Disputes | Evidence, deadlines, financial liability, account risk, and communication ownership |
| Currency and tax | Settlement currency, conversion, tax treatment, and reporting responsibility |
| Add-ons | Required plans or fees for reporting, support, integrations, payment plans, or branding |
Keep a dated link or saved copy of every source used for the decision. Terms change, and they can vary by market, account, risk assessment, payment method, and negotiated agreement.
Price a real order, not a hypothetical rate
Create a small spreadsheet with the actual mix of orders you expect: paid ticket, free ticket, discount, add-on, refund, partial refund, manual sale, international card, and payment plan if relevant. For each, calculate gross customer payment, all fees, net event revenue, settlement timing, and staff work.
For example, if you sell 300 tickets at $40, gross volume is $12,000. Do not insert a made-up provider rate. Use the provider’s live terms for the market, then add subscriptions, payment-method charges, refunds, conversion, and reconciliation time. The result is a transparent business case rather than a marketing comparison.
Cash timing belongs in the price
Imagine $6,000 in venue and contractor costs are due before the event. A low headline fee with post-event access to funds may be less valuable than a higher apparent cost with earlier, reliable settlement. The inverse can also be true if an early payout carries conditions, reserves, or risk your business cannot accept.
Ask finance to describe the exact sequence: customer pays, payment settles, funds become eligible, a payout is requested or sent, money lands in the bank, a refund is issued, and any dispute is handled. If nobody can describe it, the business cannot price the risk.
Merchant responsibility is not a detail
Clarify who appears on the customer statement, who accepts the payment, who is responsible for customer refunds, what tax or compliance responsibilities remain with the organiser, and who responds to payment disputes. The answers affect customer support, accounting, and cash flow.
This is commercial and legal territory. Get appropriate finance and legal advice for your jurisdiction and model; ticketing software does not transfer all obligations merely because it processes a card.
Reconciliation is the event-day test for finance
A finance user should be able to trace one order from gross sale to bank deposit: ticket price, tax, discount, platform charge, processor charge, refund, dispute, net settlement, currency, and bank reference. Test a partial refund and a cancelled event as well as a successful purchase.
If reconciliation requires several hand-edited exports every week, include that labour in the vendor comparison. The “cheaper” payment solution may be costing more through administration and mistakes.
What current vendor terms demonstrate
Eventbrite’s organiser help says free events can be published without ticketing fees, while paid-ticket fees are normally paid by attendees at checkout unless the organiser elects to cover them. Read the current Eventbrite guidance. Ticket Tailor describes a usage-based charge and separately notes that connected payment providers charge their own fees. Read its current explanation. These are vendor statements, not universal pricing rules.
Gomry’s published pricing says free events are available worldwide while paid events are available only in markets where Gomry settles locally. Its business terms say payout requests are generally processed within one to two business days unless a separate written arrangement applies, with actual receipt depending on payment method and banking systems. Check current Gomry pricing and business terms for your territory and account. Gomry is most relevant here when payment needs to remain connected to ticketing, bookings, memberships, and the resulting customer record, not when a business merely needs a generic card gateway. Do not promise next-day funds, a payment method, or availability without confirmation in the applicable agreement.
A payment-platform demo script
Ask the provider to show these without switching to a slide deck:
- A customer purchase with the final payable amount visible before payment.
- A discounted order with any fees and tax explained.
- A refund and partial refund, including what customer and finance see.
- A settlement or payout report matching the order records.
- The response to a disputed payment or cancelled event.
- The permissions that allow a staff member to resolve a door issue without broad financial access.
- An export that finance can import or reconcile.
The right payment platform should make every one of these activities understandable to the people responsible for it.
Frequently asked questions
What is the cheapest event payment processor?
There is no stable universal answer. Volume, market, currency, card mix, buyer-versus-organiser fee choice, refunds, settlement timing, subscriptions, and negotiated terms all alter total cost.
Should fees be passed to attendees?
That is a commercial choice constrained by applicable pricing and consumer rules. Whatever the model, show the final amount clearly and ensure your displayed pricing matches the actual checkout.
Are faster payouts always better?
They improve access to cash, but terms, reserves, refunds, disputes, and reliability matter too. Compare the complete contractual and operational model.
What should a payout report include?
Orders, gross amount, tax, discounts, fees, refunds, disputes, net amount, settlement currency, payout date, and a reference that matches the bank movement.
What is the most common procurement mistake?
Comparing one percentage without modelling refund behaviour, payment-method costs, settlement timing, finance labour, and responsibility when an event changes.