Priority markets
- United States
- United Kingdom
- Brazil
- Mexico
- India
- Indonesia
- Philippines
- Thailand
- United Arab Emirates
- Saudi Arabia
Payment needs
- Checkout for tickets, deposits, memberships, renewals, add-ons, invoices, group purchases, payment links, QR-at-door payments, and refunds.
- Cards, wallets, instant bank transfers, QR payments, cash vouchers, payment links, and bank transfer through PSP, acquirer, gateway, bank, or wallet-operator routes.
- Operational support for waitlists, cancelled events, partial refunds, transfers, chargebacks, ticket fraud, duplicate orders, and access-control reconciliation.
- Reporting by attendee ID, order ID, event ID, membership plan, location, campaign, tax document, refund, dispute, country, currency, FX, and settlement batch.
- Provider review for high-risk event categories, event cancellation exposure, age-restricted events, alcohol-adjacent activity, regulated communities, and foreign-entity onboarding.
Recommended route categories
- For general events, compare PSPs and gateways with payment links, hosted checkout, plugins, refunds, and reconciliation suited to ticketing operations.
- For paid communities and memberships, compare recurring-card, bank debit, local wallet renewal, and manual payment-link flows separately.
- For conferences and group purchases, validate invoice and bank-transfer routes alongside cards to reduce friction for business buyers.
- Use market pages to identify methods such as Pix, OXXO, SPEI, UPI, QRIS, GCash, Maya, PromptPay, mada, Tabby, Apple Pay, and Google Pay, then verify provider access for the event category.
- Without a local company, first ask whether the organizer can onboard as a foreign merchant and whether local ticketing, tax, refund, or event-permit documents are required.
Provider selection questions
- Do you support events, conferences, clubs, memberships, coworking, retreats, age-restricted events, paid communities, and ticketing deposits?
- Can our current entity onboard in each market, or do we need a local company, local bank account, local acquirer, event organizer registration, or platform route?
- Which methods support tickets, deposits, memberships, renewals, group invoices, QR-at-door flows, refunds, and event cancellations?
- How are cancelled events, partial refunds, ticket transfers, duplicate orders, chargebacks, no-shows, access revocation, and dispute evidence handled?
- Can exports include attendee ID, event ID, ticket type, membership plan, location, campaign, country, currency, FX, refund, dispute, and settlement batch?
Risk and compliance notes
- Events can carry delivery-risk and refund-risk exposure because payments may be collected before the event takes place.
- Age-restricted, alcohol-related, political, travel-bundled, investment-related, or regulated community events may require separate underwriting.
- Do not assume BNPL, wallet, QR, or cash-voucher availability for all ticketing categories; verify through provider review.
- For Russia, Venezuela, and Myanmar, publish risk warnings only and do not recommend onboarding routes.
Suggested internal links
- /en/knowledge-center/how-to-choose-psp-new-country/
- /en/knowledge-center/cash-voucher-and-convenience-store-payments-explained/
- /en/knowledge-center/chargebacks-refunds-and-disputes-in-cross-border-payments/
- /en/knowledge-center/settlement-currency-and-fx-cost-in-emerging-markets/
- /en/countries/mexico/
- /en/countries/saudi-arabia/
- /en/payment-channels/oxxo/
- /en/payment-channels/mada/