---
title: "Paying at the agency: a booking system for a cash economy · Supaferry"
description: "Two banks, ten ATMs, no card acceptance beyond the hotels. Online booking has to work when the money is cash handed over a counter and the law requires a government receipt before boarding."
url: https://supaferry.com/resources/journal/paying-at-the-agency
language: en
published: 2025-12-09
---
[Journal](https://supaferry.com/resources/journal)

# Paying at the agency: a booking system for a cash economy

2025-12-09 · 11 min read

Two banks, ten ATMs, no card acceptance beyond the hotels. Online booking has to work when the money is cash handed over a counter and the law requires a government receipt before boarding.

![Hands stamping a paper receipt at a shipping agency counter beside a handwritten passenger ledger, with a shipping manifests board on the wall](https://supaferry.com/blog/agency-counter.webp)

*The receipt is the ticket. In the FSM regulation nobody boards without the Finance Office's receipt, and the agency's ledger is the manifest until the ship sails.*

## Key takeaways

- In a cash economy the first payment method is a reservation: hold the seats, give the passenger a reference and a deadline, and let the agency record the receipt.
- Every unpaid booking carries two deadlines, a thirty-minute checkout hold and an operator-set agency hold measured in hours before departure, and both release seats automatically with an audit entry.
- Cash at the counter, card and government travel authorisation share one booking record, which is what makes revenue and daily reconciliation reports a filter rather than a reconstruction.
- Card acceptance in a small market is a procurement question, so the gateway lives behind an adapter and is connected once the contract names the bank.
- The passenger-facing site puts the receipt, the deadline and a phone number first, and never lets a reservation look like a paid ticket.

The first thing a booking site usually asks for, after the dates, is a card. For most of the people who travel on the inter-island ships of the Pacific, that is where the site stops being useful. This article is about why Supaferry treats cash at a counter as the primary way to pay, how it keeps that path honest with holds that expire and receipts that are recorded, and why the real card gateway is the last thing we connect rather than the first.

## The money, as it actually moves

The Federated States of Micronesia has two banks, Bank of FSM and Bank of Guam, with eight branches and ten ATMs for the whole country, all on the four main islands. The currency is the US dollar. Card terminals exist in hotels, the larger stores and a few restaurants in the state capitals. On the outer islands there is no bank, no ATM, and in many places no mobile data. Cash is how wages are paid, how goods are bought and how passage is paid for.

The government's own rules reflect that. The Ship Tariff Regulations state that bookings of passengers and cargo are made with the ship's agent or the Marine Division before departure, that the passenger pays the fare at the FSM Finance Office, and that the Finance Office's receipt is the documentary evidence that allows boarding. The 2022 request for proposals for a booking service adds the operational detail: one shipping agency per state, agency staff collecting boarding passes at departure, and all money collected deposited at Finance every day. This is not an old practice waiting to be replaced by a card form. It is the legal flow of public money, and a booking system has to serve it.

The same is true, in different degrees, across the region. The Yap State agency that opens bookings for the Hapilmohol announces a one-week booking window, cargo delivery days and a departure time on the state website and on Facebook, and takes bookings at its office. Vanuatu's Big Sista sells tickets at its offices in Port Vila and Luganville. Fiji's outer-island routes are booked at the ticket office before departure. These operators are not behind; they are serving passengers who have cash and no card.

## Reservation first, payment second

So the first payment method in Supaferry is not a payment. It is a **reservation**. The passenger, or someone booking on their behalf from a town with a connection, enters the voyage, the origin and destination calls, the passengers and their details, and chooses “**pay at the agency**”. The system creates the booking, issues a **booking reference** such as FSM-7K2PQ9, holds the seats, and tells the passenger exactly how long they have and where to go. The confirmation page and the ticket both carry the reference, the amount due and the instruction that boarding requires the Finance receipt.

At the agency, the clerk searches the reference or the passenger's name, sees the amount, takes the cash, and types the **Finance receipt number** into the booking. That one action does three things:

1. it turns the reservation into a confirmed booking;
2. it prints the receipt number on every ticket of that booking;
3. it writes an audit entry with the agent's identity, the time and the receipt number.

The passenger walks away with a ticket that says “paid, receipt FIN-PNI-20533”, which is what the boarding officer needs to see.

The **counter sale** for a walk-in passenger is the same screen in a different order: the clerk enters the passengers, types the receipt number straight away, and prints. There is no separate “manual booking” mode with fewer checks; the same seat availability, the same tariff, the same manifest.

> The first payment method is not a payment. It is a reservation with a deadline.

## Holds that expire, for two reasons

A reservation that is never paid blocks a seat that somebody else needed, and on a ship that visits an island twice a year that is not a minor inconvenience. Every unpaid booking in Supaferry therefore carries a deadline, and there are two of them.

The first is the **checkout hold**, and it is short. While a passenger is still at the checkout, deciding whether to pay by card now or walk to the agency later, the seats are held for thirty minutes. If the browser is closed, the connection drops, or the person simply changes their mind, the hold lapses and the seats go back on sale. This protects the inventory from abandoned checkouts without asking anyone to do anything.

The second is the **agency hold**; it is long and is set by the operator. When the passenger chooses to pay at the agency, the hold is extended to a fixed number of hours before departure, forty-eight in the FSM configuration. The passenger has until then to pay. The deadline is shown on the confirmation page in the operator's time zone and in relative terms (“in six days”), and it is printed on the ticket. When it passes, a background sweep marks the booking as expired, releases the seats, and records in the audit log that it did so and why. The passenger can still travel; they make a new booking if seats remain, or buy at the counter on the day.

The operator can change the number of hours in the settings. A service with a long booking window and a short agency opening schedule may want seventy-two hours; a daily line may want six. Two refinements are on the roadmap: a reminder by SMS before the hold ends, and a waiting list so that an expired hold on a full leg goes to the next passenger automatically.

- A hold is visible in the back office as “unpaid hold” with its deadline, and the dashboard counts them and their total value so the agency knows what cash to expect.
- A hold still counts as a taken seat in every availability calculation, so the web and the counter can never sell the same place twice while someone is walking to Finance.
- A booking can be cancelled by the passenger from the manage page, with the reference and the phone number, which frees the seats before the deadline.

> **Note:** Worked example. A departure on Saturday at 08:00 with a 48-hour agency hold expires on Thursday at 08:00. If the Finance Office is open Monday to Friday from 08:00 to 16:00, the passenger's last real chance to pay is Wednesday afternoon, not Thursday. Set the hold with the counter's opening hours in mind, and print the deadline as a date and a time, never only as a number of hours.

## Three methods, one record

Cash at the agency is the first method; two more share the same booking record. **Card payment**, through whichever gateway the operator's bank can acquire for, confirms the booking immediately and attaches the gateway's reference. **Government travel authorisation**, the TA or purchase order number that a department issues for official travel, confirms the booking immediately with the status “invoiced” and the authorisation number on the ticket, so the department is billed rather than the traveller.

The **booking record** is the same in all three cases: voyage, legs, passengers, the itemised fare, and a payment block with the method, the status and the reference. That uniformity is what makes the reporting work. The dashboard splits confirmed revenue into cash and card on one side and invoiced authorisations on the other. A daily report per agent, which is what the Finance Office reconciles against the deposit slip, is a filter on the same data: bookings marked paid by this agent today, with their receipt numbers and amounts. It is on the roadmap as a printed slip, and it is already possible as a CSV.

## Why the gateway comes last

Card acceptance in a small market is a procurement question before it is a product question.

- Which bank will acquire for a government department?
- Will it be a local bank's merchant service, a regional gateway, or an international processor through a foreign entity?
- What are the fees, and who pays them?
- Does UnionPay need to be accepted because that is what the ATMs take?

None of this is decided by the software vendor, and a vendor who ships a system wired to one gateway has made the decision for the customer.

> A vendor who ships a system wired to one gateway has made the procurement decision for the customer.

Supaferry therefore has a **payment adapter** boundary, not a payment provider. The demonstration runs a simulated gateway so that the whole flow, including a declined card and a retry, can be seen end to end: a valid test number pays, a specific number is declined, an expired date is rejected, and nothing is charged. The adapter for the real bank is written once the contract names it, and it slots in behind the same “pay by card” button without touching the booking, the tickets or the reporting. Card data never reaches Supaferry's servers in either case; a real gateway uses its own hosted or tokenised fields.

## What the passenger sees

A booking site that respects a cash economy looks slightly different from one that does not, and the differences are deliberate.

The payment step is a choice between methods with their instructions written out, not a card form with a small “other options” link. The agency option says where to pay, that the booking reference must be quoted, that the Finance receipt is required for boarding, and when the hold ends. The confirmation page repeats all of it in a banner, with the amount and the deadline, and offers a card payment as a second chance for someone who finds a connection later. The ticket says “Hold · unpaid” until the agency records the receipt, and “Paid, receipt number” afterwards, so a passenger cannot mistake a reservation for a ticket.

The contact details are a phone number first and an email second, because the phone is what the agency has and what the passenger can be reached on. Finding a booking later asks for the reference and the phone number, not an account and a password; nobody on an outer island is going to maintain an account. The confirmation can be printed, and it is readable as plain text if the QR image does not load over a slow link.

> The receipt is not an afterthought printed below the ticket. It is the thing that makes the ticket valid, and the system is built around recording it.

## What the operator gains

For the shipping agency, the ledger becomes a screen that already knows the fare, already knows how many seats are left on each leg, and already prints the ticket. The daily deposit becomes a report instead of an evening of adding up carbon copies. The boarding officer gets a list that is complete before the ship sails and a scan that refuses the unpaid.

For the operator's head office, revenue is visible per voyage and per state as it is collected, and holds that never turn into cash are visible too, which is the first step to understanding no-shows on routes where a seat lost is a seat lost for six months.

For the Finance Office, every confirmed booking carries a receipt number it issued, and the audit log says who typed it and when. That is a reconciliation trail that paper never gave them.

## A worked example: one school group

Consider the case that happens every June and every August in Yap and Chuuk: a school sends its boarding students home for the holidays, and brings them back. A teacher at the Department of Education sits at a computer in the state capital on a Tuesday and books fourteen students and two chaperones from Weno to Satawan on the Mortlocks Run. She chooses “pay at the agency” because the department pays by cheque at the Finance Office, and the system holds sixteen deck seats on the legs from Weno down to Satawan until forty-eight hours before departure. The operator's dashboard shows one unpaid hold worth a little over four hundred dollars, and the agency in Weno can see it in the bookings list. On Thursday the department's clerk walks the cheque to Finance, receives receipt FIN-TKK-11902, and the agency records it against the reference. Sixteen tickets print on one sheet each, with the receipt number, the students' names and the guardian's name on every one. On sailing day the boarding officer scans sixteen codes; two students who switched to a relative's canoe at the last minute simply do not scan, and the manifest for that call shows fourteen embarking rather than sixteen, which is what the master signs. Nobody re-typed anything, nobody reconciled a carbon copy, and the department has a receipt number on an audit line it can show its own auditor. That is the whole design in one booking.

## In short

A booking system for island shipping has to be built around how money actually moves on the islands: cash, counters, receipts and public accounts. Supaferry puts reservation and counter payment first, protects the inventory with holds that expire on their own, records the receipt as the thing that confirms a booking, and keeps card payment as a configurable option behind an adapter. The result is a site most passengers can actually finish, and an operator who can finally see where the money is.

## Questions people ask

**How does paying at the agency work in an online booking?**
The passenger books online, chooses to pay at the agency and receives a reference, the amount due and a deadline. The seats are held until that deadline. At the counter the clerk finds the booking, takes the cash and types the receipt number, which confirms the booking, prints the receipt number on every ticket and writes an audit entry.

**What happens if a reservation is never paid?**
A background sweep marks it as expired when the agency hold runs out, releases the seats and records why in the audit log. The passenger can still travel by making a new booking if seats remain or by buying at the counter on the day. Until the deadline, the hold counts as a taken seat everywhere.

**How long should the agency hold be?**
Long enough for a passenger to reach a counter during its opening hours, and short enough to release seats that will not be paid before the ship sails. Forty-eight hours before departure is a common starting point for a weekly service; a daily line may want six hours, and a service with a long booking window and a counter open twice a week may want seventy-two. The operator changes it in the settings.

**Why not connect a card gateway from the start?**
Because which bank acquires for a public operator, what the fees are and which card schemes must be accepted are decisions the operator and its bank make, not the software vendor. Supaferry keeps a payment adapter boundary and demonstrates the full card flow with a simulated gateway. The real adapter is written once the contract names the bank, and card data never passes through the booking server.

**How does a counter sale differ from a web booking?**
It is the same screen in a different order: the clerk enters the passengers, types the receipt number straight away and prints. There is no separate manual mode with fewer checks, so the counter sale goes through the same availability per leg, the same tariff and the same manifest as a booking made online.
