One stop ticketing solution for bus and coach operators

Open Loop vs Account Based Ticketing: 5 Key Questions for Bus Operators

account-based-ticketing-pilot-programme-boarding-gate

Open loop vs account based ticketing is a question more bus operators are asking as riders expect to pay with the card already in their wallet. The two terms are often mixed up, even though they describe different things.

This guide explains the difference in plain language, so you can talk to vendors without guessing. We keep to concepts and buying questions. We do not quote adoption numbers, savings or compliance claims, because none of them help you decide.

What Open Loop Means for a Bus Operator

open-loop-vs-account-based-ticketing-boarding-gate

In an open loop system, the passenger pays with a bank-issued payment card or phone wallet. The card belongs to the bank, not to you. The same card works on many other services, which is why people call the loop “open”.

A closed loop system works the other way round. The operator issues its own ticket, pass or card, and it only works inside that operator’s network. Paper tickets and stored-value cards are the familiar examples.

So when you compare open loop vs account based ticketing, remember that open loop describes who owns the payment medium. It says nothing about where the fare is calculated or how the passenger record is kept.

For a longer look at the card side, read our comparison of account based and card based ticketing before you continue.

What Account Based Ticketing Means

Account based ticketing moves the intelligence from the ticket to the back office. The passenger has an account. A card, phone or code is only a key that points to that account.

Your system then records the journey against the account, applies the fare rules and takes payment. The medium in the passenger’s hand does not store the balance or the ticket.

That is the main point to hold on to in the open loop vs account based ticketing debate: one idea is about the payment medium, the other is about where the record lives. If you want the mechanics step by step, our guide on how account based ticketing works walks through it.

Open Loop vs Account Based Ticketing: Where They Overlap

The two ideas are not rivals. An open loop payment can be tied to an account in the back office. The bank card then acts as the key, and your system builds the rider history behind it.

This is why many public transit projects combine them. The card is open loop, the processing is account based. The passenger taps a familiar card and the system does the rest later.

open-loop-vs-account-based-ticketing-planning-desk

It also works the other way. An account based system can use your own closed loop media, such as a QR code in an app or a pass you issue. Nothing forces you to accept bank cards just because you choose accounts.

When a vendor says “we do open loop vs account based ticketing”, ask which half they mean. They may offer one, the other or a combination, and each answer changes your project.

Five Questions to Ask Before You Choose

A fair comparison starts with your own operation. Here are five questions an owner can answer before any sales call.

  • Who are my riders: commuters who travel daily, or leisure travellers who book once or twice a year?
  • Do my vehicles have gates, or does a driver check each person at the door?
  • How many sales channels do I run: counter, website, partner sites, phone?
  • Do I need to know who a passenger is across several trips?
  • What does my current validation process cost me in minutes at the door?

Open loop suits fixed-price, tap-and-go travel, where speed at the reader matters most. Account based thinking suits operators who want one passenger record across channels.

Most intercity operators sell reserved seats on fixed departures. That makes the account question usually more relevant than the tap question. You can still answer both, but start from the account.

What Changes at the Door

Boarding is where the difference becomes visible. With an open loop approach, the reader must recognise the bank card, check the fare and decide quickly. That asks more of the reader hardware and of the connection behind it.

With a seat-based ticket, the check is simpler. The driver or agent confirms that the passenger holds a valid booking for this departure. A QR code, a printed ticket or a name on a manifest can all do that.

UBT’s site describes this part of its offer as flexible ticketing validation options to meet your needs. That wording tells you the validation method is a choice, not a fixed rule. It does not tell you that bank card readers are included, so do not assume they are.

If boarding speed is your real problem, start with our notes on bus ticket validation options. They cover the methods an operator can compare.

What Changes in the Back Office

Behind the door, an account based record helps you answer questions that paper tickets cannot. Who travelled twice this month? Which channel did that passenger use? Which fares were refunded?

Open loop on its own does not give you that. A bank card payment tells you an amount was charged, but not who the passenger is in your terms. You still need an account or booking record to attach it to.

For a deeper look at what a joined-up record gives an operator, see our piece on the benefits of account based ticketing.

Here is a simple way to remember the split. Open loop answers how the passenger pays. Account based ticketing answers what you know about the passenger afterwards.

Risks and Limits to Plan For

Any option has costs that brochures leave out. We cannot give figures, because they depend on your routes, your processor and your contract. We can name the areas to check.

  • Reader hardware: which devices are needed, who supplies them and who repairs them.
  • Connectivity: what happens at the door when the signal drops on a rural stop.
  • Fare rules: whether your fares can be calculated from a tap or need a booking first.
  • Refunds: how a refund reaches a bank card, a stored balance or an account.
  • Support: who answers when a passenger says their card did not work.

Write these down and ask every vendor the same list. The comparison becomes honest when the questions are identical.

Do not accept a general promise on any of these. Ask to see the step on screen, with your own example fare.

A Practical Way to Decide

Start small and keep the decision reversible. Pick one route or one station, define what you want to learn, and run it for a fixed period.

Measure things you can count yourself: minutes spent at the door, number of manual checks, number of disputes about tickets. Compare them with your current baseline, not with a number from a brochure.

If your riders are mostly booking in advance, strengthen the account and booking record first. If you later see demand for tap-and-go travel, an open loop layer can be added on top of a clean account record.

That order protects you. A clean record is useful with or without bank card payments, while a tap reader without a record leaves you blind.

Final Thoughts on Open Loop vs Account Based Ticketing

Open loop vs account based ticketing is not an either-or choice. One describes the payment medium and the other describes where the passenger record lives, and many systems combine them.

Decide which problem you have first: speed at the door, knowledge of your passengers, or both. Then ask vendors to show you, on screen, how they solve exactly that.

UBT offers its technology as a service, and its site says that if you do not like it, there is no cost and no obligation. If you want to see how a single passenger record could work across your counters and channels, request a UBT demo and bring your own questions.