{"id":16650,"date":"2016-09-15T11:30:00","date_gmt":"2016-09-15T10:30:00","guid":{"rendered":"https:\/\/masabidev.wpengine.com\/news\/what-is-account-based-ticketing\/"},"modified":"2016-09-15T11:30:00","modified_gmt":"2016-09-15T10:30:00","slug":"what-is-account-based-ticketing","status":"publish","type":"post","link":"https:\/\/www.masabi.com\/it\/news\/what-is-account-based-ticketing\/","title":{"rendered":"What is Account Based Ticketing?"},"content":{"rendered":"
\n

Most traditional transport ticketing systems are \u2018Card Centric.\u2019 This means the travel information and the right to travel on public transport is stored on or in the ticket. This is the same for magstripe paper or smartcard ticketing systems.<\/p>\n

\u00a0<\/p>\n

These \u2018Closed-Loop\u2019 systems, where the fare media is supplied by the transport provider, have been around for years and provide a robust solution in which transactions are primarily stored on the card and only secondarily in the readers and then in the local and\/or central back-offices.<\/p>\n<\/p>\n

\u00a0<\/p>\n

In recent years, thanks to advances in communications technologies, innovative transport providers have launched new transport ticketing systems that allow passengers to use contactless bank cards, mobile phones, wearables, or other IDs to travel.<\/p>\n

\u00a0<\/p>\n

These new technologies allow for \u2018Open-Loop<\/a>\u2019 and \u2018Account-Based\u2019 systems. They provide a greater degree of convenience for passengers than \u2018Card Centric\u2019 and cash based ticketing systems, while saving transport providers money.<\/p>\n

\u00a0<\/p>\n

Account-Based Ticketing is defined by the Smartcard Alliance as: <\/strong>\u201cThe transit fare collection system architecture that uses the back office system to apply relevant business rules, determine the fare, and settle the transaction.\u201d<\/em><\/p>\n

\u00a0<\/p>\n

Essentially right to travel is managed by the central back office and the \u2018ticket\u2019 the passenger has acts as a ‘token’ or proof of the right to travel and identifier of a customer\u2019s account – hence, Account-Based. The back office stores the tokens usage patterns and also settles the transaction (based on usage). As such, the back office is the primary source of truth, unlike in a Card Centric system where, as described above, it is the card.<\/p>\n

\u00a0<\/p>\n

Because of this, passengers are able to use what they have in their pocket to travel, be it an cEMV contactless bank card, smartcard, phone or a smart wearable and the payment will link with their \u2018account\u2019 residing in the back office. This means passengers no longer need to buy a ticket or understand fares to travel, safe in the knowledge they will be charged ‘best fare’; for their journey.<\/p>\n

\u00a0<\/p>\n

Account Based Ticketing systems are also better placed to take advantage of the advances in technology to run and scale more efficiently, with the back-offices often being managed from the \u2018Cloud\u2019.<\/p>\n

\u00a0<\/p>\n

For the transport provider the benefits are significant. With legacy Card Centric systems, transport providers have to act as a local currency, exchanging cash or card payment for a ticket to travel. These paper or smartcard systems are expensive to install and expensive to operate and update.<\/p>\n

\u00a0<\/p>\n

Account Based Ticketing allows transport providers to move to an \u2018open loop\u2019 system (open tokens such as contactless bank cards) and away from the cost of issuing physical ticket media and the cost of handling cash. (However, we would recommend using ‘Open Loop’ tokens and stored value accounts as detailed in this post, <\/a>to ensure equity.)\u00a0<\/p>\n

\u00a0<\/p>\n

Account-Based Ticketing is revolutionising the passenger experience because it is effectively a ticketless way of allowing people to travel. Instead of needing to select a fare and buy a ticket before traveling the rider simply taps their secure token. The amount of taps and location of these taps calculates the fare, which is charged to the passenger after they travel.<\/p>\n

\u00a0<\/p>\n

It’s important to remember that having an account does not make a system ‘account-based’ and if passengers need to purchase a ticket before traveling (you can be pretty sure) it’s not account-based.\u00a0<\/p>\n

\u00a0<\/p>\n

Mobile ticketing can operate both as a traditional proof of payment style ticket (data on the ticket – suitable for last minute tickets) and also enable Account Based ticketing (static token & data primarily in the back office), allowing you to feed in and experiment with account based products as you move to full Account Based Ticketing.<\/p>\n

\u00a0<\/p>\n

Further reading:<\/strong><\/p>\n