One festival pass. More good days.

A festival pass needs to do more than show a QR code. Valid days, camping, zones and re-entry need clear rules. This guide explains how the pass and the system at the gate can work together.

Talk to us

We use your details to respond to your enquiry, and this site is protected by reCAPTCHA. Privacy

Read the guide
After Hours festival pass

Plan the whole festival experience

Dates in one place

Make it clear whether a pass covers one day or the whole festival. Dates and category should be easy to read in the queue.

Zones without confusion

Separate festival admission, camping and additional zones. Security staff need the same rules guests see on the pass.

An agreed fallback

Batteries run out, networks fail and wristbands go missing. Plan how staff can find and verify the correct ticket.

Multi-day passes need an access model

A festival pass can be presented as an event ticket in Wallet. The key decision is how the ticketing system describes entitlement: valid dates, access zones and add-ons. One pass can show the whole picture, but validation at each gate must know the specific rules.

Avoid a single used status for every visit if guests need access on several days. Instead, describe what each scan means: first admission, wristband collection, exit or re-entry. A day ticket must not acquire weekend access through an incidental update to the pass.

Wallet and wristbands can have different jobs

If you use wristbands, the Wallet ticket can be the basis for collecting one on first arrival. The ticketing system should record that the wristband has been issued and link it to the right ticket. Later admission can then use the wristband under the festival’s rules.

A Wallet pass does not automatically become a contactless wristband or payment account. NFC needs compatible equipment and a separate integration. If the festival offers a food and drink balance, funds and admission rights should remain separate in the system even when customers see them in the same experience.

Test queues, re-entry and network failures together

Prepare concrete tests before opening the gates: the same code at two entrances, a guest arriving on the wrong day, a camping add-on without festival admission and a refunded ticket being presented. The validation system needs to give clear answers staff can act on.

Offline reading needs a plan for downloaded data, update timing and simultaneous scans when devices synchronise. A guest’s Wallet pass can be accessible while gate systems have stale data. Decide which risks are acceptable and provide staffed support for exceptions.

How to get started

  1. Define dates and admission

    Describe day tickets, weekend passes, camping and add-ons, with clear re-entry rules.

  2. Connect passes to gate validation

    Use an individual reference the gate can validate, and agree how wristbands are issued if applicable.

  3. Rehearse admission

    Test concurrent readers, incorrect dates, transfers, refunds and network failures with staff.

From ticket purchase to festival weekend.

Let the ticketing system handle orders and validity. Wallet makes the ticket easy to find when your guest arrives.

  1. Confirm the booking

    Connect the ticket to the right event, date and admission type.

  2. Deliver the ticket

    Send a link that lets the guest save their ticket to Wallet.

  3. Check at the entrance

    Scan the code against the ticketing system. It decides whether the ticket is valid and already used.

Questions before you start

Can one Wallet pass cover several festival days?

A pass can display several valid dates. The ticketing system must define and validate admission for each day, including re-entry and zones.

Can Wallet replace a festival wristband?

That depends on admission rules, readers and gate operations. Wallet may provide first admission or subsequent scanning, but wristbands and contactless access need separate planning.

Is this the same as paying with Wallet?

No. Admission and payment are different entitlements. A festival balance needs payment and settlement services; it does not exist just because a ticket is saved in Wallet.

A useful pass needs a considered flow

Tell us what issues the ticket, who will use it and how it will be validated. We can discuss the integration before you build.

Talk to us

We use your details to respond to your enquiry, and this site is protected by reCAPTCHA. Privacy