One stop ticketing solution for bus and coach operators

Account Based Ticketing Contactless Bank Cards and Mobile Wallets: 5 Key Questions for Operators

bus-ticket-validation-options-boarding-gate

Account based ticketing contactless bank cards and mobile wallets is a question that reaches operators as soon as they understand that a ticket can live in an account instead of on paper.

The card or the phone is only the key a rider presents. The fare, the trip history and the rules stay in the back office.

That difference matters for an owner who is deciding what to ask a vendor. A contactless card is not a ticket, and a wallet on a phone is not a ticket either. They are ways to recognise the same account every time, and your system decides what that account is allowed to ride.

This guide is written for the owner or operations manager of a bus company. It explains how account based ticketing contactless bank cards and mobile wallets fit together, which five questions to settle first, and what to check in a walkthrough.

It claims no particular card network and no particular wallet.

account-based-ticketing-contactless-bank-cards-and-mobile-wallets-boarding-gate

How Account Based Ticketing Contactless Bank Cards and Mobile Wallets Fit Together

In a card-based design the value or the pass is stored on the card itself. In an account design the card only points to a record on a server. Our overview of how account based ticketing works goes through that record in detail, so here we stay on the credential.

A bank card, a physical transit card and a phone wallet can all serve as that credential. The rider taps, the reader reads an identifier, and the back office looks up the account and decides whether the tap is valid for this departure.

The reader does not need to know the price, because the account does.

This is why the choice of credential is separate from the choice of fare rules. You can change which credentials you accept later without rebuilding your timetable or your products. You cannot easily change your fare rules if they are scattered across card readers.

Operators sometimes read this as a technology topic only. It is also a business topic, because every credential you accept changes who can ride without visiting a counter and what you must support when something goes wrong. The questions below keep both sides in view.

Account Based Ticketing Contactless Bank Cards and Mobile Wallets: Five Questions to Settle First

The five questions are about decisions, not about hardware. Answer them on paper before you speak to any vendor, and the walkthrough becomes much shorter. Each question has a plain answer that your counter agent and your driver can repeat.

Question 1: What Identifies the Rider?

A physical bank card usually carries a number that the issuer controls. A phone wallet normally presents a different token tied to the device, so the same person can have a card in a purse and a token on a phone without the two looking alike.

Your account design has to decide whether those two credentials belong to one rider or to two. If the rider replaces a lost card or buys a new phone, the account should survive. If it does not, you lose the history and any pass attached to it.

Write down the rule for linking and unlinking credentials. Decide who can do it, whether it needs a confirmation step and what happens to a trip already paid for. Staff at the counter need a one-line answer for this.

Question 2: Where Is the Fare Decided?

In an account design the fare is decided in the back office after the tap, not on the reader. That keeps the reader simple, but it raises a practical question for a coach on a rural stretch: what happens when the reader has no connection at the moment of the tap?

Ask each vendor how their validation behaves online and offline, and ask for the answer in writing. Our guide to bus ticket validation options lists the choices an operator can compare, including what the driver sees on the device.

Do not accept a general promise. A good answer states what is checked on the device, what is checked later, and how a tap that could not be verified at the door is settled afterwards.

Question 3: How Does the Rider Prove What They Paid For?

Paper gives the rider a stub. A tap gives them nothing visible, so the proof moves into the account and into the receipt that your system sends. If a rider says they paid and the reader refused them, your agent needs to see the same account the system saw.

This also touches disputes with card issuers. A payment made with a bank card can be challenged later, and your records of the trip are your side of the story. Our article on bus ticket chargebacks explains what evidence to keep.

Make sure the back office can show, for each tap, the account, the departure, the time and the result. If a platform cannot show that history to your staff, treat it as a gap and ask how it is planned.

Question 4: What About Riders Without a Card or a Phone Wallet?

Not every passenger has a contactless bank card, and not every phone has a wallet set up. A system that accepts only taps will turn some riders away at the door. Decide in advance what those riders do.

Most operators keep a second path: a ticket at the counter, a printed or mobile code, or a pass issued at a point of sale. The key point is that the second path should land in the same inventory and the same reports, so you do not run two separate businesses.

That is the reason inventory and reporting belong in the same conversation as the credential. Point-of-sale, ticket validation, inventory control and real-time reporting should all see the same rider, whatever they used to board.

Question 5: What Data Do You Keep and For How Long?

An account holds names, contact details and a trip history, and the credential adds an identifier. The more credentials you accept, the more careful you must be with what you store. Collect only what you need to run the service.

Decide who in your company can see the account, who can export it and when it is deleted. This is a policy decision first and a system setting second. Ask your own legal adviser what applies in your market, because the answer differs by state and by country.

Tell riders what you keep in plain words, at the moment they link a card or a wallet. A short notice builds more trust than a long page that nobody reads.

account-based-ticketing-contactless-bank-cards-and-mobile-wallets-scanning-device

What to Ask in a Vendor Walkthrough

Which cards and wallets a platform accepts depends on the vendor and on the payment provider you use. We do not list specific card networks or wallets in this article, and you should not assume that any system supports a given one. Ask for it by name and get the answer in writing.

Then ask what happens after the tap. A short list is enough: how the account is found, where the fare is calculated, how a refused tap is explained to the driver, how the trip appears in the report and how a rider is helped when the tap failed.

United Bus Tech describes flexible ticketing validation options and a platform that combines point-of-sale, ticket validation, inventory control and real-time reporting.

Use those same four headings as a checklist for any platform, and ask each one to show how a card or a wallet would pass through every stage.

Also ask about the difference between a first release and the full design. For example, a platform may accept a rider account first and add more credential types later. Your plan should say which ones you need on day one and which can wait.

If you want the wider comparison of card-style and account-style designs, read our article on open loop vs account based ticketing. It covers the differences at a higher level, while this guide stays with the credential.

A Simple Way to Test Cards and Wallets With a Small Group

A small trial teaches more than a long specification. Pick one route, a limited group of riders and a fixed period, and write down what success means before you start. For example, you may decide that every refused tap must be explained within a day.

Run the second path in parallel, so that nobody is stranded while the new credential is tested. Compare the two paths in your reports and note where staff needed help. Those notes become your training material.

At the end, answer three questions: did riders understand how to link a credential, did the driver trust the result on the device, and did the back office show a complete record? If any answer is no, fix that before adding routes.

Keep a log of every case that did not fit your rules. It is a low-cost way to improve the rules, and it gives your vendor concrete examples instead of vague complaints.

Putting It Into Practice

Account based ticketing contactless bank cards and mobile wallets is mostly a set of decisions: what identifies the rider, where the fare is decided, how proof is kept, what happens to riders without a credential and how data is handled. Settle those on paper, then test them with a small group.

To see POS, ticket validation, inventory control and real-time reporting working together, request a walkthrough from United Bus Tech and bring your own list of credential questions. We provide Technology as a Service, with no cost and no obligations if you do not like it.