Rail and bus operators can issue tickets as passes in Apple Wallet and Google Wallet. Passengers add a single, return or season ticket to the wallet and show its barcode to the inspector or at the gate. The ticket updates when the platform or departure time changes. It’s a barcode ticket, not tap-to-ride NFC transit.

In Pushwoosh, tickets and messages share 1 passenger profile, so you can run wallet passes for rail and transit operators right next to your delay alerts.

Why tickets belong in the wallet

Passengers already carry their tickets on their phones. Operators such as GWR and ScotRail let passengers add tickets to Apple Wallet or Google Wallet (market examples). The wallet is where passengers look on the platform.

The bigger opportunity is information. Only 37% of rail passengers were satisfied with how their operator handled a delay (Transport Focus, National Rail Passenger Survey, 2018). Real-time information changes behavior: 3 years after live transit status appeared in Google Maps, per-capita ridership rose 14% (UW-Madison study of 128 US transit systems, 2026).

Ticket types

TicketApple typeGoogle typeShows
Single or returnBoarding Pass, transit type train, bus or boatTransitOrigin, destination, date, departure, coach and seat
Season ticketGeneric or Boarding PassTransit or GenericRoute, valid dates, holder
Multi-leg journeyBoarding Pass per legTransitEach leg with its own details
Ticket
1 / 3
Single or return
Apple type
Boarding Pass, transit type train, bus or boat
Google type
Transit
Shows
Origin, destination, date, departure, coach and seat
Ticket
2 / 3
Season ticket
Apple type
Generic or Boarding Pass
Google type
Transit or Generic
Shows
Route, valid dates, holder
Ticket
3 / 3
Multi-leg journey
Apple type
Boarding Pass per leg
Google type
Transit
Shows
Each leg with its own details

Plan alerts per platform. On Apple, fields with a change message can show a lock-screen alert. On Google, only loyalty, event ticket and flight passes get Google’s automatic update notification. For a Transit ticket, add your own notification text to the API update, or send the delay alert by push or SMS.

Platform and delay updates

When your operations system changes a platform or departure time, it sends the new values through the API and the ticket redraws on the passenger’s phone. On Apple, a message like “Now departing from platform %@” appears on the lock screen.

Pair every significant change with a message. The ticket shows the new details. A push explains the delay, the alternatives, and what the passenger is entitled to. Pass notifications stay about the ticket itself: Apple and Google don’t allow promotions through the pass.

See Pushwoosh in action
Request a demo

Delays and passenger rights

In some markets, delay messages carry legal weight. In the EU, passengers delayed by more than 60 minutes have a right to information about what’s happening, and under Article 20 of Regulation (EU) 2021/782 a right to assistance such as meals and accommodation where needed.

Compensation is another moment to get right. A YouGov survey for Trainline found that 29% of UK passengers didn’t claim the delay compensation they were owed in 2025, leaving more than £80 million unclaimed each year (vendor-commissioned survey). A message telling passengers they’re eligible, with a link to claim, is a service people remember.

A typical delay journey:

  1. Delay detected

    The ticket updates the departure time. A time-sensitive push explains the delay.

  2. Platform change

    The ticket updates, with a change message on Apple. Push to everyone.

  3. Delay passes 60 minutes

    Push and email with assistance and compensation information.

  4. Cancellation

    The ticket is updated or voided. Rebooking options go by push, email and SMS.

Barcode formats

Match the barcode to your gates and inspectors’ devices. Apple supports QR, PDF417, Aztec and Code128. Google supports the same plus EAN-13. Aztec and QR are common in rail ticketing. Test with real phones at real gates before launch.

QR tickets vs Express Transit and NFC

Tap-to-ride is a different product. In systems like OMNY in New York, where 68% of transactions run through digital wallets on phones and wearables (MTA, 2023), passengers tap a contactless payment card stored in the wallet. That’s contactless payment, not an operator’s wallet ticket. Express Transit and other tap-to-ride cards are NFC products as well.

Pushwoosh issues barcode and QR tickets, not NFC transit cards. If your network runs on tap-to-ride, standard passes still fit around it: season ticket cards for barcode gates, event or excursion tickets, and loyalty cards.

Keep passengers informed with Pushwoosh

Pushwoosh issues native Apple and Google Wallet tickets by User ID, updates platforms and times through the API, and runs delay, assistance and compensation journeys by push, email and SMS from the same platform.

Keeping passengers informed isn’t about faster trains. It’s about a ticket and a message that tell the same story the moment something changes.

Explore wallet passes for rail and transit
Explore wallet passes

FAQ


Pushwoosh Team
Content Team at Pushwoosh
Share

Related articles

View all