Skip to main content
PricingOffers & Rewards
Open workspace
ArticlesHow-To Guides (sign in to open)
ArticlesIDs & tickets

Travel and boarding passes on a phone: how they work

What you will take away

  • One change updates every pass
  • A four-question fit test
  • Built for trips sold by name
On this page
  1. What it is not
  2. Codes are not new here
  3. Airlines-only layout
  4. Issuing the passes
  5. What the passenger sees
  6. Scanning at boarding
  7. Delays and Reschedule
  8. A four-question test

A travel pass on a phone shows a passenger their next journey (where from, where to, when, which seat) and gives them a code that your staff scan once as they board. In native.cards you enter the journey, then issue a pass to each named passenger.

That makes it a tool for operators who know who is travelling: a tour boat, a charter coach, a resort shuttle, a small ferry with a passenger list.

What it is not

Nothing is tapped, no fare is stored and no seat is sold here. Each pass is for one journey, used once.

Settle this first, because it decides whether the rest is for you.

Nothing is tapped. A pass opens no gate or turnstile, and it holds no money and no stored fare. Each pass is for one journey and is used once, so there is no season pass and no multi-trip pass.

native.cards takes no booking and no payment. You sell the seat your own way and then issue the pass. The code on a pass is native.cards' own, read by your staff on a phone. It is not connected to any airport, terminal or airline system. And no delay or gate change reaches a passenger unless you enter it.

Codes are not new here

One KL bus terminal's own QR tickets show that boarding with a code is not new to passengers here.

In February 2026, express bus tickets bought through online travel agents for Terminal Bersepadu Selatan in Kuala Lumpur began to carry QR codes. RinggitPlus reported the Transport Minister, Loke Siew Fook, as saying that passengers holding one "can proceed directly to the departure area upon arrival at TBS", "without the need to queue at counters for ticket printing".

That is one terminal's own ticketing. It has nothing to do with a phone Wallet or with native.cards. It does show that boarding with a code is not new to passengers here.

Airlines-only layout

Apple's new boarding pass layout is for airlines and needs twelve details. Other operators lose nothing.

Apple's developer page on its newest boarding pass layout opens: "Beginning with iOS and watchOS 26, you can update airline boarding passes with live information using semantic tags." It is firm about who that is for: "Use the semantic boarding pass style only for airline boarding passes."

To get that layout, a pass must carry twelve details:

  • the airline's IATA code
  • the flight number, digits only
  • the departure airport's IATA code
  • the departure city
  • the departure time zone
  • the destination airport's IATA code
  • the destination city
  • the destination time zone
  • the originally scheduled boarding time
  • the originally scheduled departure time
  • the originally scheduled arrival time
  • the passenger's name

Leave one out and, in Apple's words, "your pass falls back to the legacy boarding pass style": the ordinary boarding pass that Wallet showed before.

Google Wallet keeps two kinds apart. Its boarding passes are for flights and can "notify users about their flight status and boarding time reminders". Its transit passes are passes "with QR codes and barcodes".

For a ferry, coach, rail or tour operator the conclusion is short. The new iPhone layout is not meant for you, and you lose nothing by that. What matters on your pass is the route, the time, the seat and a code your staff can read.

native.cards has an Airline boarding kind of program, described in the next section. We have not checked the pass it issues against Apple's twelve details on an iPhone, so we say nothing here about which of the two layouts a phone shows.

Issuing the passes

An owner or admin types every pass, for passengers who have joined by email. No booking system is linked.

Seats on the ferry
150
Passes issued together, at most
50
Batches to enter
three batches
Made-up numbers. A 44-seat charter coach is one batch. All 150 people must first have joined with an email address.

There are two kinds of card program for travel. You choose one when you create the program.

Rail, ferry, bus or cruise Airline boarding
You create A journey A flight
It needs Operator, From, To, when it departs and arrives, and a location Airline, Flight number, From (airport), To (airport), when it departs and arrives, and a location
You can add Service number, Travel instructions, Seats Terminal, Gate, Seats, and for the Wallet Card a Carrier code and Flight number, digits only
Each pass carries Passenger, Fare class, Seat, Coach or cabin, Travel restrictions Booking reference, Passenger, the given and family name as booked, Seat, Boarding group, Cabin
Issued One at a time, or up to 50 passengers together One at a time

Boarding opens is set on the journey: at departure, up to an hour before, or at a time you choose. The form says: "Boarding opens by itself at the time you set." The location is the outlet where passengers board, and "Only staff at this location can board passengers." A ferry company with two jetties sets up each jetty as an outlet.

A passenger has to join your program before a pass can be issued to them, with an email address and a 6-digit code. For a journey, someone who has not joined can be invited by email, and the pass is issued when they join with that address. Passengers cannot take a pass for themselves.

Every pass is entered by an owner or admin in the dashboard. Nothing links native.cards to a booking system. Count what that means for you, as in this example with made-up numbers:

A 44-seat charter coach is one batch of 44 passes. A 150-seat ferry is three batches of 50, and 150 people who have each joined with an email address first. Passes issued together share a fare class and a coach. A seat number is typed on each pass afterwards, one at a time.

For a dive boat with 20 booked guests, that is one batch from a list you already hold. For a commuter ferry that sells seats at the jetty to people who give no name, it does not fit.

What the passenger sees

The pass page sets out the journey, and gives a code to scan only once boarding opens.

The passenger is emailed, and their pass page sets out the next journey: the route with its two times and how long it takes, then the seat, coach, gate, terminal, boarding group and booking reference, where you gave them. A strip shows the journey in order: Boarding opens, Departs, Arrives, each with its time. Your Travel instructions appear under "Before you travel", with any restriction on that pass.

Before boarding opens there is no code. The page gives the time, for example "Your code opens today at 8:30 am", then: "That’s when boarding opens. Nothing to do until then." After that, Show my code puts a QR code on the screen.

Two buttons are worth telling passengers about. Add to calendar saves the journey. Send my arrival writes the arrival time and place as a sentence the passenger can send to whoever is meeting them.

Where you have Apple Wallet or Google Wallet turned on, the passenger can add the pass to their Wallet from the same page.

Scanning at boarding

Staff enter a PIN once in Door and scan. A pass works once, and a flat phone is found by name on the List.

Staff open Door under Counter on a phone, signed in with two-step verification. They choose the journey or flight and enter their own staff PIN once. Each scan then shows Admitted for a journey, or Boarded for a flight, with the passenger's name and seat. The pass page tells the passenger the rule: "It works once, for this journey." A second scan is refused.

A passenger whose phone is flat is found by name on the Door's List. The Door needs a connection, so test the signal where passengers board. A jetty or a lay-by is not an office. The full procedure, copied codes included, is in Event tickets on a phone: how they work.

Delays and Reschedule

No timetable feed is connected, so passes show a delay only when an owner or admin uses Reschedule.

  1. Open Reschedule from the journey
  2. Press 30 min later or 1 hour later
  3. Give a reason, such as the weather
  4. Every pass issued moves to the new time
  5. Each passenger is emailed the change
What an owner or admin does when a departure runs late. Until then every pass still shows the old time.

No timetable or flight-status feed is connected. If the boat leaves 40 minutes late and nobody touches the journey, every pass still shows the old time.

The way to tell passengers is Reschedule, which an owner or admin opens from the journey. A button moves it 30 min later or 1 hour later, and you give a reason, such as "Because of the weather", that goes into the email. The form states the effect: "Every travel pass already issued moves to the new time, and each passenger is emailed the change." The pass page then carries a note headed "The time has changed", with the old time struck through, and the code opens at the new boarding time.

Decide before the season who makes that change on a bad-weather morning, and from which phone.

Do this next

Try it against one real departure

Pick one departure next week and answer four questions about it.

  1. Do you have every passenger's name and email address before the day?
  2. Who types the passes, and how many batches is that?
  3. Who stands at the boarding point with a phone, and is there signal there?
  4. Who reschedules if it runs late?

If you can answer all four, create that journey and issue its passes. If the first answer is no, because your passengers buy at the counter and walk on, a pass on a phone is the wrong tool for that route. Keep it for the trips you sell by name: charters, tours and group bookings.

Next in IDs & ticketsInsurance and takaful cards on a phone: how they work8 min read Previous: Event tickets on a phone: how they work

Related Articles

  • Event tickets on a phone: how they workIDs & tickets · 9 min
  • Staff, student and member IDs on a phone: how they workIDs & tickets · 10 min
  • What is a Wallet Card, and how does it work?Wallet Cards · 9 min
Sources 4
  1. Apple Developer Documentation, Wallet Passes: “Creating an airline boarding pass using semantic tags” (read 10 October 2026) developer.apple.com
  2. Google Wallet developer documentation, Boarding passes (last updated 7 October 2026; read 10 October 2026) developers.google.com
  3. Google Wallet developer documentation, Transit passes with QR codes and barcodes (last updated 7 October 2026; read 10 October 2026) developers.google.com
  4. RinggitPlus, “QR Codes Introduced For Online Express Bus Tickets At TBS”, 4 February 2026 (the Transport Minister's remarks as reported) ringgitplus.com

Written by native.cards, 15 October 2026. Found a mistake? The publishing policy says how to tell us.

On this page

  1. What it is not
  2. Codes are not new here
  3. Airlines-only layout
  4. Issuing the passes
  5. What the passenger sees
  6. Scanning at boarding
  7. Delays and Reschedule
  8. A four-question test
Back to top
More in this topicIDs & tickets

On this page

  1. What it is not
  2. Codes are not new here
  3. Airlines-only layout
  4. Issuing the passes
  5. What the passenger sees
  6. Scanning at boarding
  7. Delays and Reschedule
  8. A four-question test

native.cards is the Wallet‑first customer engagement platform (CRM), powering modern brand experiences in Apple and Google Wallet.

ImmuniWeb SSL Security Test

Explore

  • Features
  • Pricing
  • Offers & Rewards
  • How it works
  • About native.cards
  • Merchant workspace

Essentials

  • Education
  • How-To Guides
  • Legal
  • Terms of Use
  • Privacy Notice
  • Privacy & storage
  • Sign in

Company

PLATEHAUS SDN. BHD.

Owner and operator of native.cards

Business Registration No. [SSM]:
1646457-T
Business address
CT-06-21 Subang Square Corporate Tower
Jalan SS15/4G, SS15
47500 Subang Jaya
Selangor Darul Ehsan, Malaysia

A reason to return.

Get started
Support
support@native.cards
Operating hours
Monday–Friday · 8:00 AM–11:00 PMSaturday–Sunday · 10:00 AM–10:00 PMMalaysia time
native.cardsnative.cards© 2026 native.cards