Skip to content
Guides

Digital transit passes in the wallet

, Founding Engineer, RevisitUpdated 3 min read

Cover for Digital transit passes in the wallet

Key takeaways

  • A transit pass in the wallet replaces a paper ticket for a bus, rail, tram or ferry trip.
  • Revisit's design holds the operator, route, time, coach and fare name, and staff scan it to record the ride.
  • It is a pass design, not a fare system. It does not connect to any metro, railway or card network.

What is a transit pass?

Google Wallet has a transit pass type that supports bus, rail, tram and ferry journeys, and Apple Wallet carries similar tickets through its pass styles. In both, the pass is a card in the wallet with the route and a barcode. See Google's wallet developer guide and Apple's wallet pages.

Single trips and recurring riders

There are two common cases:

  • A single trip ticket: Dhaka to Sylhet at 7:30 AM, coach B, seat 12.
  • A regular rider: an office staff shuttle or school bus where the same person rides every day.

Revisit's transit design covers the trip details. For a rider who needs many rides, the operator issues passes as needed. If you want a counted number of uses, a subscription card fits better.

What the pass can show

  • Operator name and branding.
  • Transport kind: bus, rail, tram, ferry or other.
  • Origin and destination, with short station codes if you use them.
  • Usual departure and arrival time.
  • Carriage or coach, and a fare name such as "Economy".

At the counter, staff scan the pass and "Ride validated" is recorded in the activity list.

What it does not do

  • It does not sell tickets or collect fares.
  • It does not connect to any government or private fare system, and it does not use contactless readers. It works with a barcode scan.
  • It does not hold a stored taka balance.

Be careful about the difference between what a wallet can do in theory and what a local operator supports. A pass here is a clear, scannable proof for your own service.

A bus operator's day (hypothetical)

  1. 01

    Create the route design

    Name the operator, set bus as the kind, add the route and usual times.

  2. 02

    Issue passes

    After a customer books through your usual channel, staff issue their pass and send the link.

  3. 03

    Scan on boarding

    The conductor scans each pass. The ride is recorded.

What should happen when the boarding scan fails?

Write down the valid route, trip date and passenger reference where staff can check them quickly. At a busy stop, a route code staff understand may be unfamiliar to the rider, so display the destination or stop name alongside it. In the boarding list, keep the trip identifier specific enough to distinguish two buses leaving for the same destination.

Rehearse a valid pass, a pass for the later departure and a rider whose phone has gone flat. A supervisor can check the last case against the roster and record boarding through the operator's fallback process. If two people show the same reference, check the booking before admitting either on that reference again. For managing similar exceptions at a fixed entrance, see the wallet ticket entry-day checklist.

Does it work with Dhaka Metro Rail or Bangladesh Railway?

No. Revisit has no integration with any operator. The pass is for operators who issue their own.

Do riders need an app?

No. They add the pass to Apple Wallet or Google Wallet from a link.

Can it work offline?

Passes are saved on the phone and open without a signal. The staff scan needs the usual internet connection.

Does Revisit sell the tickets?

No. Operators who book through their own channels can issue the pass after booking.

Related: transit pass card page, boarding passes and what is a wallet pass.

Turn first visits into regulars.

Live in 2 minutes. Pay with bKash, Nagad or card. 7-day money-back.

We use cookies and analytics tools (Google Tag Manager, PostHog) to see which pages bring shops to Revisit. Privacy policy