Apple Wallet & Google Wallet Passes

The link in your confirmation email carries only the ticket references; everything printed on the pass — event, date, venue, attendee, ticket type, seat — is looked up when you tap it, which keeps the link short and the details current. If the order holds one ticket, the pass file comes back directly and Wallet opens on it. If it holds several, you get a small page with one download button per ticket, so you can add them individually or hand each one to the person it belongs to. No sign-in is needed, since the link arrived in your own inbox.

What is stored is a signed file rather than a link to one. The Apple pass is generated and signed with a certificate at the moment you add it, and the QR is written inside the file as a barcode, so opening it involves no request at all. Google's version is a pass object signed as a token and saved into the wallet the same way. The code itself is the same value that appears in your confirmation email and that the venue's scanner expects, so all three routes present an identical code.

The layout is fixed. The event title sits as the headline, with the date and venue beneath it, then a row of smaller fields for ticket type and, on events with reserved seating, section, row and seat as three separate values. Where the seating detail arrives as one combined string, BrightStar splits it so the seat field shows only the seat rather than repeating the section and row alongside it. The attendee's name is attached to the barcode itself as its alternative text.

The scan runs a short sequence of checks in order: that the code resolves to a real ticket, that the ticket belongs to this event rather than another, that its status is still active rather than refunded or cancelled, and that it has not already been checked in. If any of those fails, the scanner shows the specific reason instead of a bare refusal, including the time an already-used ticket was scanned. On success the check-in time is written to that individual ticket.

Because check-in is recorded against each ticket separately, a group does not have to arrive together or in any particular order — four codes from one order are four independent admissions. If you would rather hand the tickets over properly than forward the email, sending them through BrightStar groups them by recipient, so each person receives a single message holding all the codes meant for them rather than one email per ticket.

The link itself carries only the ticket references. Everything shown on the pass, including the event, date, venue, your name, ticket type and seat, is looked up by BrightStar at the moment you tap it, which keeps the link short and the details current. If the order holds one ticket you get the pass file straight away; if it holds several you get a page with one download button per ticket, so each person can take their own.

On iPhone, BrightStar builds and signs a pkpass file and hands it to Wallet, with the barcode embedded as part of the file itself. Google's model is a pass object signed as a token and saved through a link, stored the same way once saved. In both cases the only step that requires a connection is adding the pass in the first place, which is why it is worth doing before you set off rather than in the queue.

Check-in is recorded against each ticket individually, so four codes from one order are four independent admissions and the group does not have to arrive together or in any order. Each card on that page shows the event, date, venue, attendee name, ticket type and, where the event has reserved seating, the section, row and seat, so it is clear which pass belongs to whom before you send it along.

The code is built from the event and the individual ticket, which is why it is per ticket rather than per order. Because the door scanner records a check-in against that single ticket, presenting the wallet pass and then presenting the PDF for the same ticket would not get two people in. The second attempt comes back as already checked in, along with the time of the first scan.

The other common cause is the device rather than the site. A pkpass file only opens in Wallet on an iPhone or iPad, so tapping the Apple link on an Android phone or a desktop browser downloads a file that nothing will open. Use the Google Wallet link on Android, and on a laptop use the PDF instead. If you are on iPhone and nothing happens, open the confirmation email in Apple Mail or Safari rather than inside a third-party app that may block the download.

With a free BrightStar account, every ticket you have bought sits in one list, each with its own wallet link, so you can re-add a pass months later without hunting for the original email. The same signed-in surface is where transfers, refund requests and messages to the organizer are handled. Without an account, the confirmation email and the lookup page it links to give you the same pass.