Passenger Technology Group Ltd

eCommerce & Transport Information Website

High quality custom branded websites for transport operators and local authorities.


  • Travel information, for multiple transport modes, including bus and tram
  • Secure mobile ticket purchase and delivery
  • Ticket gifting to family and friends
  • Journey planning
  • Travel departure and timetable information
  • Personalised travel disruption alerts
  • Promotion of local attractions and events
  • Fare information
  • Customer support contact information
  • Company Information and Job Opportunities


  • Increasing customer satisfaction levels through an easy to use interface
  • Customers can plan journeys and purchase tickets at their convenience
  • Quick and easy communication of travel disruptions on your network
  • Providing your customers with information about your business
  • Staff recruitment
  • Providing customer support information to your customers
  • Providing information to customer on fares and ticket products
  • Communicating the latest company news to your customers
  • Increased revenue through digital ticket sales


£37120 per instance

Service documents


G-Cloud 11

Service ID

3 9 2 0 3 6 3 5 1 8 1 9 7 0 2


Passenger Technology Group Ltd

Tom Quay


Service scope

Software add-on or extension
Yes, but can also be used as a standalone service
What software services is the service an extension to
Passenger Digital Services Platform
Cloud deployment model
Private cloud
Service constraints
Not Applicable
System requirements
  • Web browser: Chrome, Safari, Firefox, Edge or IE11
  • JavaScript, cookies and TLS v1.2 must be enabled
  • Broadband internet connection

User support

Email or online ticketing support
Email or online ticketing
Support response times
Our standard contractual response time for support requests, during standard office hours, is 4 hours. However, we aim to provide an initial response to support requests within 1 hour during standard office hours.
User can manage status and priority of support tickets
Phone support
Phone support availability
9 to 5 (UK time), Monday to Friday
Web chat support
Onsite support
Yes, at extra cost
Support levels
Our standard support package provides Help Desk cover from 9am - midnight, 7 days a week. Our Help Desk Manager reports weekly analysis to the business management team, including support requests received and response times to ensure optimum performance by our Help Desk agents. Our first line support agents have varying levels of technical expertise and are backed by a team of second line support agents.
Support available to third parties

Onboarding and offboarding

Getting started
We have a defined 'onboarding' process that we follow with all users to capture all the information we need to deliver the service. This includes: 1) Key staff roles and contact details to identify responsibilities for sign off and training needs for users. 2) Collation of material to enable design and artwork to be completed. 3) Review of relevant company policies and procedures so relevant links can be provided. 4) Agreement on copy to make sure we have the right information to promote the service. 5) Assessment of the datasets and feeds we will need to set up the service. 6) Review of GDPR requirements for the service. 7) Provision of relevant contact information to be provided as part of the service. For example, email addresses for, in app, user feedback to be sent to.
Service documentation
Documentation formats
End-of-contract data extraction
Typically when a contract is terminated, the service will no longer be accessible to users. Exports of sales and revenue data will be provided. However, if required, at the end of the contract data may be held within the system and made accessible for 3 calendar months following the termination date of the contract.
End-of-contract process
The contract price includes: 1) Exporting historic sales and revenue data. 2) The termination of relevant services. For example, SIRI-SM and SIRI-VM services. 3) The transfer of domain(s) to either the customer or a nominated 3rd party. 4) Deletion of customer data from our supporting cloud based hosting infrastructure.

Sales data needs to be retained, following contract termination, for accounting purposes. The length of time sales data will be retained for will be agreed as part of the end of contract process.

Using the service

Web browser interface
Supported browsers
  • Internet Explorer 11
  • Microsoft Edge
  • Firefox
  • Chrome
  • Safari 9+
Application to install
Designed for use on mobile devices
Differences between the mobile and desktop service
Differences between mobile and desktop services are dependant upon the features that are implemented for each individual customer. Where possible we design all our implementations to deliver feature parity between mobile and desktop services.
Service interface
Customisation available
Description of customisation
The following items can be customised: 1) Website branding can be customised to provide a bespoke look and feel. This customisation can only be completed by Passenger. 2) Website content can be managed the customer. 3) Bus users can tag their favourite bus stops, journey plans and timetables to get quick and easy access to the information they care about the most.


Independence of resources
We use a range of industry leading suppliers that provide reliable and scalable cloud computing services. We have designed and scaled our infrastructure to deal with current and forecasted demand based on historic data. We have automated monitoring of our infrastructure that enables us to forecast future demand and scale our infrastructure, if required within minutes, to manage peaks in demand.


Service usage metrics
Metrics types
There are numerous metrics provided by industry recognised services. The metrics include but are not limited to: 1) Number of active users per day. 2) Number of new users each day. 3) Break down by website content. 5) Break down by user segment 6) Daily revenue.
Reporting types
Real-time dashboards


Supplier type
Not a reseller

Staff security

Staff security clearance
Staff screening not performed
Government security clearance

Asset protection

Knowledge of data storage and processing locations
Data storage and processing locations
United Kingdom
User control over data storage and processing locations
Datacentre security standards
Managed by a third party
Penetration testing frequency
Less than once a year
Penetration testing approach
Protecting data at rest
Scale, obfuscating techniques, or data storage sharding
Data sanitisation process
Data sanitisation type
  • Explicit overwriting of storage before reallocation
  • Deleted data can’t be directly accessed
Equipment disposal approach
In-house destruction process

Data importing and exporting

Data export approach
In terms of users of the website, there is no data that users can export. Data is held on the supporting Digital Services Platform. Sales and revenue data for digital tickets sold can be exported by the Customer via the Digital Services Platform.
Data export formats
  • CSV
  • Other
Other data export formats
  • TransXChange
  • GTFS
Data import formats
Other data import formats

Data-in-transit protection

Data protection between buyer and supplier networks
  • Private network or public sector network
  • TLS (version 1.2 or above)
Data protection within supplier network
TLS (version 1.2 or above)

Availability and resilience

Guaranteed availability
The website and Passenger Digital Service Platform that provides underlying data to the website(s) has a service level agreement of 99% and a service level objective of 99.99%. There is no refund mechanism for guaranteed levels of availability.
Approach to resilience
We use a range of industry leading suppliers that provide reliable and scalable cloud computing services. With guaranteed levels of service and support. We have designed and scaled our infrastructure to deal with current and forecasted demand based on historic data. We have automated monitoring of our infrastructure that enables us to forecast future demand and scale our infrastructure, if required within minutes, to manage peaks in demand.
Outage reporting
There are a number of ways that outages could be reported. For example: 1) Automated outage reporting - We monitor our key infrastructure and automatic error reports are provided. For example, if the demand on our infrastructure that is used to process mobile ticket purchases exceeds a fixed threshold an alert is generated and provided on to the relevant member(s) of our team. 2) Customer outage reporting - Customer(s) may report an outage, in which case, this will be dealt with by our Help Desk Team.

Identity and authentication

User authentication needed
Access restrictions in management interfaces and support channels
Access is granted via web portal and email. Web portal access is restricted to authorised users (user name and password). Strong passwords are enforced. Email requests are authorised by receiving an email at a pre-agreed domain or via a pre-agreed out-of-band mechanism such as SMS or phone.
Access restriction testing frequency
At least once a year
Management access authentication
  • Public key authentication (including by TLS client certificate)
  • Username or password

Audit information for users

Access to user activity audit information
Users have access to real-time audit information
How long user audit data is stored for
At least 12 months
Access to supplier activity audit information
Users have access to real-time audit information
How long supplier audit data is stored for
At least 12 months
How long system logs are stored for
At least 12 months

Standards and certifications

ISO/IEC 27001 certification
ISO 28000:2007 certification
CSA STAR certification
PCI certification
Other security certifications

Security governance

Named board-level person responsible for service security
Security governance certified
Security governance approach
1) Communication Security - Valid TLS connections are used for communication and are tested against SSL Labs SSL Server Test. Communication with external systems is via TLS wherever possible. 2) System Configuration - Server software is kept up to date at least quarterly, with security patches typically being applied within 48 hours. All server software is configured and provisioned automatically with asset management tools. Test and development systems and applications are kept separate from production. Test systems are restricted to authorised users. 3) Database security - Parameterised queries are always used. Applications access databases with the lowest required credentials.
Information security policies and processes
Ultimate responsibility for information security rests with the Chief Executive Officer of PTG, but on a day-to-day basis the Operations Director shall be responsible for managing and implementing the policy and related procedures. Line Managers are responsible for ensuring that their permanent and temporary staff and contractors are aware of: information security policies applicable in their work areas, personal responsibilities for information security and how to access advice on information security matters.

Operational security

Configuration and change management standard
Supplier-defined controls
Configuration and change management approach
All infrastructure is managed as code in git source control management. Changes require peer review from a senior developer and output from runs are added to an append-only log.
Vulnerability management type
Supplier-defined controls
Vulnerability management approach
Software components in configuration management are automatically tested against security lists at frequent intervals. Threat information comes from Canonical's Ubuntu Security Notices, AWS security bulletins and Symfony Security Monitoring. Patches are deployed within 48 hours, with a target of 24 hours for any CVE with a base score over 5. Service provider security responsiveness is reviewed annually.
Protective monitoring type
Supplier-defined controls
Protective monitoring approach
Compromises are identified from network ingress/egress alerts and extensive application event monitoring alerts. Response process includes review from a senior developer with a target response time of 1 hour.
Incident management type
Supplier-defined controls
Incident management approach
Users report incidents email (optionally with PGP), documented via the well-known security.txt standard. Reports are provided to impacted users via email within 1 week of incident. Processes are in place for incidents such as DDoS, personal or confidential data exposure.

Secure development

Approach to secure software development best practice
Conforms to a recognised standard, but self-assessed

Public sector networks

Connection to public sector networks


£37120 per instance
Discount for educational organisations
Free trial available

Service documents

Return to top ↑