Event Ticketing & On-Site Validation: One-Time QR Codes, Split Payments & Reconciliation Integration

Selling tickets for an event seems like a simple 'collect money, issue tickets' process. But once you're on-site, it becomes a multi-front operation: online sales, instant on-site purchases, rapid entry validation, clear refunds, partner revenue sharing, and ultimately, accurate reconciliation. If you've ever, right before an event opens, discovered 'someone entered with a screenshot,' 'there's a massive queue,' or 'you were reconciling in Excel until late after closing,' you'll understand that a ticketing system isn't just a tool. It's a complete workflow, from payment to validation, and from settlement to reporting.

The Wonder platform applies its fintech capabilities – typically used by merchants for payments, deposits, payouts, expense management, and data analysis – to event ticketing. This ensures the ticketing process meets enterprise-grade operational requirements.

What are your biggest worries when selling tickets?

The biggest fear isn't not selling tickets, but rather 'selling tickets that can't be used for entry, entry that doesn't reconcile, or reconciliation that can't be split.'

Ticket revenue involves multiple stakeholders

Ticket revenue involves multiple stakeholders: organizers, venues, performers, ticketing agents, and sponsors. Sometimes, there are also charity donations or distribution commissions. Beyond the ticket price, each ticket might have handling fees, discount codes, add-ons (drink vouchers, merchandise), and refund policies. The more detailed you want to be, the more you need a traceable, auditable, and automated process.

The challenges of entry validation

Entry validation is even more direct: if one step is slow, the entire operation slows down. If there's a loophole, it leads to disputes and complaints.

How to ensure fast and stable online ticketing?

Online ticketing needs to be 'easy to buy' and 'hard to make mistakes with.' In practice, the most common method is using a Payment Link to complete transactions: buyers click the link, choose to pay with credit card, debit card, e-wallet, or QR code, and the organizer receives instant transaction results.

Multi-channel payment capability

Wonder offers up to 34 payment methods, including Visa, Mastercard, JCB, Octopus, UnionPay, UnionPay QR, WeChat Pay, Alipay, PayMe, FPS, and more. This is incredibly practical for event organizers, as you don't need to predict which payment method your audience will use, nor do you need to set up separate processes for each one.

Quick account setup, instant ticket sales

Another key point for organizers is 'fast account setup to start selling tickets.' Wonder emphasizes 7-minute rapid account opening, which is especially useful for tight schedules, impromptu additional shows, or pop-up events. You don't want your promotion out there while your payment system isn't ready.

Fast entry validation: How do one-time QR codes prevent screenshots?

Traditional static QR codes have an inherent problem: if someone screenshots or forwards it, the same 'image' can be used by others to attempt entry. Even if you have a 'first scan, first entry' rule, disputes at the gate will arise: who arrived first, who used it first, and how do you prove it?

The design of one-time (dynamic) QR codes

The design philosophy behind one-time (or dynamic) QR codes is that the QR code is not permanently valid. Instead, it's tied to a 'time window' and 'usage status.' The most common approach is to embed the ticket ID, timestamp, and encrypted signature into the QR payload, or use timed refreshing dynamic codes so screenshots quickly become invalid. When scanned, the system instantly verifies authenticity and usage status with the backend. If valid, it's immediately marked as 'validated.'

Enhancing the on-site experience

The on-site experience will be significantly different: staff won't need to visually differentiate between emails, PDFs, or album screenshots. They just scan and see a clear status to grant entry.

In summary, the ideal entry experience is: fast and dispute-free.

Three perspectives for reviewing validation design

You can evaluate the robustness of your current validation design from the following perspectives:

• Can screenshots be reused?
• Does repeated scanning trigger an immediate warning?
• How are offline situations handled?

Need to sell tickets on-site? How to do it with a mobile phone and terminal

Many events can't rely solely on pre-sales. Walk-ins, upgrades, paying the difference for seat changes, and buying drink vouchers are all 'instant on-site sales' opportunities.

Two ways to handle on-site payments

Wonder can process on-site payments in two ways:

Turn your phone into a payment terminal

Use the Wonder App or Virtual Terminal to process card or QR code payments. This is suitable for mobile staff, temporary booths, or upselling during venue rounds.

Retail-grade card machines

Use the Wonder Terminal. It supports tap, insert, scan, or display QR code payments, and can be integrated with the Wonder Dashboard for real-time transaction management. For large venues with multiple gates, booths, and shifts of staff, the greatest value of hardware terminals lies in their stability, ease of management, and lower training costs.

The importance of on-site equipment division of labor

If you need both 'payment' and 'validation,' pay attention to the division of labor for on-site equipment: which points are for selling tickets, and which are for scanning entry, to avoid crowd congestion and confusion.

Don't want to rely on Excel for revenue sharing: How to automate income splitting

Event revenue usually isn't a 'one-time deposit and done.' You need to pay venue fees, share revenue with performers, deduct ticketing platform fees, and potentially set aside a refund pool. Relying on manual calculation for revenue sharing isn't just troublesome; it's prone to errors and difficult to trace, especially when there are many ticket types, discounts, and refunds, which can lead to reconciliation discrepancies.

Automated revenue sharing rules

A more mature approach is to pre-set revenue sharing rules that automatically calculate each party's receivables for every transaction, while maintaining auditable records. Rules can be percentages, fixed amounts, tiered commissions, or varied by ticket type.

Common revenue sharing and reconciliation design comparison table

Practical advice for automated revenue sharing

Practically, you don't necessarily need to achieve 'instant fund distribution to multiple accounts' from the start. Many organizers begin with 'automated revenue calculation + transparent reporting,' which already solves 90% of disputes: after each ticket sale, the system immediately records the revenue sharing result, and settlement is done later according to rules.

Clear reconciliation: How to streamline sales, refunds, and validation

The biggest fear in ticketing is 'fragmented data': one set of numbers from the payment platform, another from the ticketing system, and yet another from gate scans. If you want to answer a simple question like 'How many people actually entered today? What's the revenue? How many refunds?', you have to open three systems and manually piece together the information.

Centralized Management and Transparent Reporting

Wonder Dashboard provides real-time transaction monitoring and detailed reports. All transactions completed via Payment Link or terminal can be centrally managed. Daily reports, transaction details, and breakdowns by payment method are all available in one backend, which is extremely useful for both finance and operations.

Ideal data flow visualization

If you also write validation results back to the same backend or your own event backend, the ideal scenario is:

• Sales: Instant viewing of transaction deposits
• Validation: Instant increase in attendance numbers
• Refunds/Cancellations: Instant decrease in revenue, with simultaneous update of ticket status

This 'single timeline' data is incredibly helpful for handling complaints, investigating fraud, and reconciling with venues.

How to integrate technology and processes? A practical blueprint

When it comes to integration, many teams assume they need to 'replace all systems.' In reality, the more common approach is to gradually connect systems using APIs and webhooks/callbacks: payments are handled by Wonder, ticketing logic by your event system, entry scanning devices act as the execution end, and data is then aggregated for reporting.

Practical API integration process

Taking Wonder's Payment Link API as an example: your event website or app can call `Create Order` to generate a payment link corresponding to ticket types (line items); upon successful payment, a `callback_url` notifies your server of the payment result, and then a one-time QR ticket is generated and sent to the audience. On-site, a scanning device reads the QR code and sends it to your verification endpoint. If verification passes, it's immediately marked as 'used,' and repeated scans are rejected.

Deconstruct demand modules, implement incrementally

To balance operations and technology effectively, the best approach is to break down requirements into clear modules and implement them one by one:

• Ticket Sales & Collection: Payment Link (online) + Terminal / Virtual Terminal (on-site)
• Ticket Issuance: Automatic ticket generation after successful order, QR payload bound to ticket status
• Entry Validation: Scanners instantly verify authenticity, time window, and usage status, and write back validation records
• Revenue Sharing & Reporting: Calculate revenue sharing based on transaction details, integrate with settlement processes, and provide exportable reports

Two key points for security

On the security front, two points need attention: First, payment data must be processed through compliant channels, avoiding your own systems from handling sensitive card data. Second, ticket validation needs a signature or encryption design; otherwise, if someone guesses the rules, they could forge QR codes. Wonder emphasizes data encryption and transaction security, while your ticket logic needs to ensure it's 'unforgeable, non-reusable, and traceable.'

Questions to ask yourself before starting

The most common problem with event systems isn't that APIs can't be called, but that requirements aren't clarified at the beginning, leading to last-minute fixes.

Five quick questions for team assessment

You can quickly assess with your team using the following questions:

• Are you selling only one type of ticket, or multiple ticket types, sessions, and prices?
• Is entry through one gate, or multiple entrances, time slots, and zones?
• Will refunds occur? If so, do tickets need to be simultaneously invalidated?
• Is partner revenue sharing by session, ticket type, or channel?
• Does finance need daily reconciliation, or would they prefer to view cash flow hourly?

Integrate payment, validation, and reconciliation with one platform

Once these answers are clear, you can integrate 'payment, validation, and reconciliation' into one streamlined rhythm using a single platform. Wonder's approach is to provide a complete toolchain from the Wonder App and Wonder Terminal to the Wonder Dashboard, coupled with transparent fees, no contracts, no monthly fees, no rental fees, and the T+0 instant settlement capability common in F&B. This allows event organizers to let the system handle the most labor-intensive parts, freeing up their energy for the program, on-site experience, and customer satisfaction.

‍