---
title: "What a ferry e-ticket must carry · Supaferry"
description: "An electronic ferry ticket has four readers: the passenger, the boarding officer, the accountant and the auditor. What it must print, how it travels, how it is checked, and what a refund does to it."
url: https://supaferry.com/resources/journal/what-a-ferry-e-ticket-must-carry
language: en
published: 2026-05-12
---
[Journal](https://supaferry.com/resources/journal)

# What a ferry e-ticket must carry

2026-05-12 · 12 min read

An electronic ferry ticket has four readers: the passenger, the boarding officer, the accountant and the auditor. What it must print, how it travels, how it is checked, and what a refund does to it.

![An illustration of a ferry ticket with a blue header band, a perforated stub on the right carrying a QR code and the code FSM-7K2PQ9-1, and a line reading PAID · FIN-PNI-11902.](https://supaferry.com/blog/e-tickets.webp)

*One ticket per passenger. The code in letters beside the QR is what the officer types when the scanner fails, and the receipt number is what the accountant matches against the cashier's register that evening.*

## Key takeaways

- A booking is the transaction, a ticket is one passenger's right to travel, and on a free-seating ferry the scanned ticket is the boarding pass; a second document adds nothing.
- Derive ticket codes from the booking reference, in an alphabet without 0, O, 1, I and L, so they survive being read over a radio and typed with gloves on.
- Print for four readers: passenger, boarding officer, accountant and auditor. The payment reference, a Finance receipt or a gateway id, is the line the auditor tests.
- Deliver by PDF, SMS, agency print and radio; the officer must be able to find the booking from the reference alone, and a name search is an exception path that gets logged.
- The paper never changes when the booking does. Scan on every sailing, and treat the second use of a code as a visible refusal rather than something to prevent.
- Keep the record, not the file: a ticket PDF can be regenerated at any time, the manifest with its boarding scans cannot.

An electronic ticket is the one document a ferry service produces that leaves the building. The manifest stays with the master, the cash sheet stays with the agency, the sailing schedule stays on the ministry's wall. The ticket goes home with the passenger, is photographed, forwarded to a cousin, printed at a shop, read aloud over a VHF radio, and finally shown to an officer at the gangway who has forty seconds to decide whether the person in front of him may board. It is also the only document the passenger keeps when something goes wrong: a cancelled sailing, a refund dispute, an insurance claim after an incident.

This article sets out what an e-ticket is and what it is not, what it must carry for each of the four people who will read it, how it reaches a passenger who has neither a smartphone nor an email address, and what happens to it when the booking is cancelled or refunded. It is written for operators, agencies and the ministries and donors that procure ticketing systems. It applies as much to a Greek island line, a Canary Islands crossing or a Caribbean water taxi as to a government ship in the Pacific.

## Ticket, booking and boarding pass are three things

The three words are used interchangeably in tender documents, and the confusion costs money later. They are three different objects with three different lifetimes.

- A **booking** is the commercial transaction: one buyer, one voyage, one origin call, one destination call, one or more passengers, one price, one payment status. It has a reference the buyer quotes when phoning the agency. It can be held, confirmed, cancelled or refunded. It is what the accountant reconciles.
- A **ticket** is the right of one named passenger to travel on that booking. A booking with four passengers has four tickets. Each has its own code, its own fare line, its own row on the manifest and its own used-or-not flag at boarding. It is what the boarding officer checks.
- A **boarding pass** is the proof that the check was done. On an airline it is a separate document because the airline sells the ticket months before it assigns a seat and a gate. On a ferry with free seating there is no reason for a second document: the ticket, once scanned and marked as used, is the boarding pass. Systems that print a second card at the gangway are copying aviation without aviation's reason.

The practical consequence is that the ticket must stand alone. A passenger who has lost the confirmation email but still has the ticket must be able to board, and an officer who holds only the ticket must be able to find the booking from it.

## One booking reference, one ticket per passenger

A ticket code should be derived from the booking reference, not generated independently, so that either can be found from the other. The pattern that has worked for us is a short reference such as FSM-7K2PQ9 for the booking and FSM-7K2PQ9-1, FSM-7K2PQ9-2 and so on for the tickets, where the suffix is the passenger's position in the booking. An officer reading FSM-7K2PQ9-3 knows, before any lookup, that this is the third passenger on booking 7K2PQ9, and a passenger phoning the agency can give the reference without reading the suffix.

The alphabet matters more than it looks. A code that will be read aloud over a radio, written on a receipt by hand and typed into a boarding tablet by someone wearing gloves must not contain characters that are confused with each other. Drop 0 and O, drop 1, I and L, and thirty-one symbols remain. Six of them give nearly 900 million combinations, enough for any operator for decades, and a six-character group fits in one breath. The system should accept the code typed in any case, with or without the hyphens, with spaces where the passenger paused.

> A ticket code that cannot be read over a VHF radio at an outer-island anchorage is not finished.

Why one ticket per passenger and not one per booking? Because people do not travel in bookings. A father books four places and boards with three; the fourth person takes the next sailing or does not travel at all. The manifest, which is a safety document, must say who was actually on board, and it can only do that if each person has a code that was or was not scanned. One code for the whole family would make the manifest say four when the ship carries three.

## What must be printed, and for whom

The ticket has four readers, and each one looks for different lines. A good layout serves all four on a single page.

**The passenger** needs to know what they bought: the full name as it will be matched at boarding, the voyage code and the vessel, the origin call with its date and departure time, the destination call with its estimated arrival, the islands in between on a multi-call voyage, the class (deck, cabin, a berth number where the operator assigns them), what luggage is included, and the conditions that matter in practice: how early to be at the wharf, whether the ticket can be changed, what happens if the sailing is cancelled. The passenger also needs a phone number that someone answers.

**The boarding officer** needs the code, as a QR for the scanner and in letters for the fallback, large enough to read in poor light; the passenger's name and category (adult, child, infant) to match against an identity document where the operator requires one; the origin and destination calls, because on a multi-call voyage a ticket from Nukuoro to Pohnpei is not valid for boarding at Sapwuahfik; and a plain statement of validity: valid for boarding, or not valid, with the reason. A hold that was never paid must say so on the paper, not only in the database.

**The operator's accountant** needs the fare lines (two adults at the cabin rate, one child at half, one infant at zero), the total, the currency, the payment method and the external reference of that payment: the card gateway's transaction id, the voucher number, or the receipt number from the Finance office where the cash was taken. The receipt number is the link between the ticket and the public accounts, and on a government service it is the line the auditor will test.

**The auditor**, internal, from the national audit office or from a donor, needs to reproduce the fare. That means the tariff version and the distance it was computed from, the date and time the booking was made and confirmed, the user or agent who confirmed it, and a way to find the booking in the system a year later. None of this takes much space. A footer line reading “Tariff 2003 rev. 2, 319 statute miles, confirmed 12 May 2026 14:02 by agent PNI-03” answers most audit queries before they are asked.

Then the operator's own identity: name, short name, logo, colour, and the legal text that the operator's lawyer or ministry requires. On a white-label platform all of this is data the operator sets once, which we return to below.

> **Note:** A one-page checklist for the ticket: passenger name and category; booking reference and ticket code, as QR and in letters; vessel and voyage code; origin call with date and time; destination call with estimated arrival; class and berth; fare lines, total and currency; payment method and its external reference (gateway id, voucher number, Finance receipt); validity statement; operator name, logo and contact; conditions of carriage in two or three sentences; tariff version and distance; ticket n of m. If any of these is missing, one of the four readers will phone someone.

## How the ticket reaches the passenger

The common assumption in a procurement document is that the passenger has a smartphone and an email address. On most island services a good share of passengers have one, some have the other, and a meaningful number, often older passengers and those boarding at outer islands, have neither. The ticket has to work for all of them, and a system that only emails a PDF is not a ticketing system for that population.

1. **PDF by email.** The default where an address exists. One A4 page per passenger, attached to the confirmation, with the logo referenced from the operator's server rather than embedded, because several mail clients strip embedded images. The PDF should also be downloadable from a page reached with the reference and the buyer's contact, so a passenger who deleted the email can get it again without phoning anyone.
2. **SMS with the code.** Where there is a mobile number but no email, a text message carrying the booking reference, the ticket codes, the voyage and the departure time is a complete ticket. The code in letters is what the officer types. On a line where SMS delivery is unreliable, the message should be re-sendable from the agency screen in one click.
3. **Printed at the agency.** The counter prints the same PDF the web buyer receives, on plain paper. A passenger who booked by phone collects it when paying. The print carries the receipt number because the agent entered it before printing. This is also the fallback for every passenger who has a phone but no credit for data.
4. **A code read over the radio.** Outer islands reached by a field trip often have a VHF or HF radio at the dispensary or the municipal office and nothing else. A relative in the state centre books and pays at the agency; the agency reads the reference over the radio; the passenger writes it on a piece of paper and presents it at the anchorage. The officer types it, the system shows the name, and the passenger boards. This is why the alphabet above matters, and why the ticket must be findable by reference alone.

A fifth channel is worth naming: the passenger who has nothing at all. The officer at boarding can search the manifest by name and origin call, and the system can issue the ticket code on the spot. This is an exception path and should be logged as one, with the officer's identity, so that the audit trail shows that a person boarded on a name match rather than a scan.

## Verification at boarding

A scan is a query, not a lookup. When the officer scans FSM-7K2PQ9-3 the system answers three questions in order: does this ticket exist on a confirmed, paid booking; is this ticket valid for this call of this voyage; and has it already been used. A yes to the first two and a no to the third turns the row green and records the time, the device and the officer. Anything else is refused with a reason the officer can read aloud: not paid, wrong voyage, wrong call, already boarded at 07:41 on device DESK-2, cancelled on 10 May.

The third question is the duplicate control. A PDF can be printed twice, forwarded, photographed. Two people with the same code arrive at the gangway. The first scan is accepted, the second is refused with the time of the first, and the officer decides on the spot, usually by asking for a name and an identity document. The system does not need to prevent copying, which is impossible with a document that must be forwardable; it needs to make the second use visible in under a second.

Offline matters here. An outer-island anchorage has no signal. The boarding device therefore downloads the manifest for the voyage before sailing, with every ticket code and its status, and verifies scans against that local copy. Duplicates within one device are caught immediately; duplicates across two devices on the same ship are caught when the devices sync with each other or on return to port. A scan recorded offline carries the device clock and the officer, and is reconciled to the server when the ship is back in range. The structure of the code, reference plus passenger index, is what makes that reconciliation unambiguous. Supaferry's boarding desk works this way: the manifest is cached on the device, and a voyage can be boarded end to end with no connection.

Fraud on a small ferry line is rarely sophisticated. It is a photocopied ticket, a date altered by hand, a ticket from the previous voyage. All three are defeated by the same measure: the officer trusts the scan, not the paper. The printed ticket is a convenience for the passenger and a fallback for the officer; the record of truth is the booking in the system, and the paper only has to carry enough to find it.

> The paper ticket is a pointer. The record is the ticket.

## Cancellations, refunds and the ticket that remains

The ticket in the passenger's hand does not change when the booking changes, which is why its validity statement must be verified rather than read. Four events need a defined effect.

- **The passenger cancels.** The booking moves to cancelled, every ticket on it becomes invalid, and the seats return to inventory for the legs the booking occupied. The refund, where the conditions allow one, is a separate accounting event with its own reference, because the money goes out through a different channel from the one it came in on: a card refund through the gateway, a cash refund at the Finance office against a payment voucher number. The cancelled ticket keeps its code; a scan of it at boarding is refused with the cancellation date.
- **The operator cancels the sailing.** Every booking on the voyage is released with one action and a reason, every passenger with a contact is notified, and the ticket codes are kept so that rebooking onto the next voyage can either carry them over or issue new ones with a link to the old. The audit trail records which tickets were rebooked, refunded, or neither.
- **A hold expires.** A booking held at the agency with no receipt entered by the deadline, typically a fixed number of hours before departure, lapses automatically. The tickets, which were already printed with “not valid for boarding, hold”, stay that way. The passenger who turns up with one is sent to the counter. The log says when the hold expired and why.
- **A change of date or passenger.** The cleanest rule is that a changed booking is a new booking with a link to the old one: new reference, new tickets, old ones cancelled. The alternative, editing in place, produces a ticket whose paper says one thing and whose record says another, and a boarding officer who has to work out which is true.

In all four cases the passenger's document does not know what happened. The system does. This is the single strongest argument for scanning at boarding on every sailing, including the ones where everyone knows everyone.

## The receipt as proof of payment

On many public ferry services the operator does not take money. The ministry's Finance office or a treasury cashier does, against an official receipt with a serial number, and the ticketing system never sees a card transaction. The ticket then has to carry two numbers: its own code, and the receipt number that proves the fare was paid into the public account.

The procedure that works: the agent creates the booking as a hold, prints a quotation with the reference and the amount, the passenger walks to the cashier, pays, and returns with the receipt. The agent enters the receipt number against the booking, the system confirms it, and the ticket prints with “PAID · FIN-PNI-11902” in the validity line. The receipt number is unique within the Finance office's own series, so the daily reconciliation can match the ticketing system's list of confirmations against the cashier's list of receipts, line by line, and any receipt entered twice or any confirmation without a receipt shows up that evening rather than at the year-end audit.

The same logic applies where a voucher stands in for money: a government travel warrant, a school's authorisation for a group, a medical referral. The voucher number is the payment reference, the ticket carries it, and the accountant reconciles the vouchers to the issuing office's register.

## Accessibility, retention and the plain-text ticket

A ticket that is a picture of a ticket fails blind and low-vision passengers, fails the officer whose scanner is broken, and fails the auditor who wants to search a year of tickets for a receipt number. The PDF should be real text: selectable, searchable, read correctly by a screen reader in the order a person would read it. The QR is the only image on the page, and the code beside it in letters is its text alternative.

The same content should be available as plain text in the body of the confirmation email and on the booking page, so that a passenger using a screen reader never has to open the attachment. Large print is cheap: the passenger name, the departure time and the code are set at a size that reads at arm's length, and the operator's colour is used for the header band and nothing else, so that the body stays black on white. A passenger with a colour vision deficiency should never need the colour to tell valid from not valid; the word does that.

Retention is a question for the operator's lawyer, but the shape of the answer is stable. The booking record, with its tickets, payment references and boarding scans, is part of the manifest, and the manifest is a safety record with a retention period set by the maritime administration, often several years. Personal data beyond what the manifest needs, a phone number or an email address, can be deleted or anonymised sooner, after the refund window and the accounting year have closed. The ticket PDF itself does not need to be stored: it can be regenerated from the record at any time, and regenerating it on request is simpler and safer than keeping a file store of documents that may carry stale validity statements.

## Branding: whose ticket is it?

The ticket is the operator's document. The passenger should see the operator's name, logo, colour and phone number, in the operator's language, with the operator's conditions. The platform that produced it should appear once, small, in the footer, as a “powered by” credit, the way a printing house's mark appears on a paper ticket. This is a white-label arrangement and it should be data, not a custom build: the operator uploads a logo and picks a colour in settings, and the same tokens drive the booking site, the emails and the PDF. In Supaferry this is one settings page, and the PDF, the confirmation email and the public booking site change together when the operator changes the colour.

Two cautions. First, the operator's colour must have enough contrast against white for the header text, and the system should refuse a colour that does not rather than print an unreadable ticket. Second, the legal footer belongs to the operator and should be editable without a developer: conditions of carriage change when a ministry issues a new regulation, and the ticket has to say what the regulation says on the day it is issued.

## A worked example: four people, one phone call

A family in Pohnpei wants to travel to Kosrae on the next sailing of the government ship: two adults, a child of nine and an infant of fourteen months. The grandmother phones the agency on a Tuesday. She has a mobile phone that receives text messages and no email.

> **Note:** The agent finds the voyage, Pohnpei to Kosrae, departing Friday 07:00, and creates a booking in cabin class: reference FSM-7K2PQ9, held, with the grandmother's name and number as the buyer's contact. The published distance is 319 statute miles. The tariff gives $0.20 per mile in cabin from 100 miles, so the adult fare is $63.80; the child pays half, $31.90; the infant pays nothing and takes no berth. Total $159.50. The system sends an SMS with the reference, the amount and the deadline: the hold lapses 48 hours before departure, Wednesday 07:00. On Wednesday morning a son-in-law pays $159.50 in cash at the Finance office and receives receipt FIN-PNI-11902. He walks to the agency, the agent enters the receipt number, the booking confirms, and four tickets print: FSM-7K2PQ9-1 to -4, each with “PAID · FIN-PNI-11902”, the family name, the class and the voyage. The agent also resends the SMS, now carrying the four ticket codes. On Friday the family arrives at the wharf with the printed tickets. The officer scans -1, -2 and -3; the infant's ticket -4 is scanned too, so the manifest shows four persons on board, three of them in berths. That evening the reconciliation matches FIN-PNI-11902 to the confirmation of FSM-7K2PQ9, and the voyage closes with every receipt accounted for.

Nothing in this example needed an email address, a card or a smartphone, and everything in it left a record that the accountant, the master and the auditor can read. That is the test of an e-ticket. Not whether it looks modern, but whether it works for the grandmother, for the officer at the gangway and for the person who reconciles the cash, and whether it still says the right thing a year later.

## Questions people ask

**Is a PDF ticket a valid ticket in law?**
In most jurisdictions the contract of carriage is formed when the booking is confirmed and paid, and the ticket is evidence of it rather than the contract itself. A PDF, an SMS or a printed sheet are all acceptable evidence as long as the operator's conditions say so and the record behind them can be produced. Check the national maritime or consumer regulation; some administrations require specific wording on the document.

**What does a passenger with no phone and no email receive?**
A printed ticket from the agency, or a booking reference read to them over the radio or by a relative. The officer at boarding finds the booking by reference, or by name and origin call as a logged exception. The ticket must be designed so that the reference alone is enough to board.

**Can a ticket be transferred to another person?**
That is a policy decision for the operator, and it should be written in the conditions printed on the ticket. Where names are matched to identity documents at boarding, a transfer means cancelling the ticket and issuing a new one with the new name, so that the manifest is correct. Where boarding is anonymous, the ticket is effectively a bearer document and the operator should say so.

**What should the boarding officer do when the same code is scanned twice?**
Accept the first scan and refuse the second, showing the time and device of the first. The officer then asks the second person for a name and, where required, an identity document, and decides. The refusal and the decision are both logged. The system's job is to make the duplicate visible, not to stop a PDF from being copied.

**How long must ticket records be kept?**
The booking with its boarding scans is part of the manifest, which the maritime administration treats as a safety record; retention periods of three to ten years are common. Contact details beyond what the manifest needs can be removed sooner, after the refund window and the accounting year close. The PDF itself need not be kept, since it can be regenerated from the record.

**Does the ticket have to show the fare?**
Yes, for two of its four readers. The accountant needs the fare lines and the payment reference to reconcile, and the auditor needs the tariff version and the distance to reproduce the figure. Operators that prefer not to show the price to the passenger can print it on the stub only, but it must be on the document.

**Why print the tariff version and the distance?**
Because a regulated fare must be reproducible. If a passenger disputes the price or an auditor samples the voyage a year later, the ticket itself states which tariff was applied and over how many miles, and the figure can be recomputed without searching for the operator's settings as they were on that day.
