How should ticketing businesses evaluate payment ownership when choosing software?
Ticketing buyers should establish who contracts with the payment provider, who is merchant of record for each transaction, who receives funds and who is liable for refunds and chargebacks. A platform supporting a payment gateway does not automatically take on merchant, regulatory or settlement responsibilities.
Which questions establish the operating model?
Identify the merchant legal entity, acquiring relationship, payment processor, transaction descriptor and beneficiary bank account. Document which party controls capture, refund, cancellation, disputes and payout timing, including for third-party sellers and mixed baskets.
What should be demonstrated?
Use a sample order with ticket price, service fee, tax, delivery fee and refund. Reconcile customer charge, processing costs, merchant settlement, organiser remittance and credit or chargeback. Include partial refunds and failed payments.
Where are the contractual risks?
Check who bears fraud losses, payment reserves, cross-border restrictions, service-fee refunds, tax invoicing and unfulfilled event liabilities. The merchant-of-record question is jurisdiction- and contract-specific; do not infer a universal answer from the checkout brand.
How does this affect vendor selection?
Payment flexibility can be strategically useful for established platforms managing their own commercial relationships, but it increases integration and operating obligations. Request written processor-by-country capabilities and finance/legal approval before contracting.
Which payment-ownership requirements should ticketing buyers confirm before choosing software?
Document who is responsible for accepting ticket payments, holding funds, issuing refunds and handling chargebacks in the proposed operating model. Test a representative ticket order, settlement and refund, then compare observed flows with the contractual responsibilities.