The procurement contact named on the official notice.

The submission route named on the official notice.

Transport for London (TfL) was created in 2000 as the integrated body responsible for London's transport system.

TfL is a functional body of the Greater London Authority.

Its primary role is to implement the Mayor of London's Transport Strategy and manage transport services to, from and within London.

TfL manages London's buses, the Tube network, Docklands Light Railway, Overground and Trams.

TfL also runs Santander Cycles, London River Services, Victoria Coach Station, the London Cable Car and London Transport Museum.

As well as controlling a 580km network of main roads and the city's 6,000 traffic lights, TfL also regulates London's taxis and private hire vehicles, the Congestion Charge scheme, the Low Emission Zone and the Ultra Low Emission Zone.

Further background on what TfL does can be found on the TfL website here: https://tfl.gov.uk/corporate/about-tfl/what-we-do Short Description Transport for London (TfL) is looking to procure a single contract with a Service Provider for the Card Not Present (CNP) Payment Gateway, a COTS (commercial off the shelf) 'application as Software as a Service (SaaS) to allow TfL to continue to provide an uninterrupted payment gateway services to customers via TfL websites and mobile Apps.

The service is primarily required for TfL's Oyster Online (OOL) platform and TfL Oyster and Contactless Mobile Application (TOCMA); however, it may be utilised by other websites or mobile Apps of TfL and/or other members or areas of the TfL group in the future (including in relation to Oyster Online and TOCMA), as and when necessary, including, but not limited to, Road User Charging.

Oyster is used as one of the means to pay for travel around London.

It is a smartcard which can hold pay as you go credit, Travelcards and Bus & Tram season tickets.

Customers can purchase and manage their Oyster cards on Oyster Online 24 hours a day, 365 days per year, including the following options: • Check their Oyster card balance • Top up their pay as you go credit and add or renew Travelcards and other season tickets • Set up Auto top-up (recurring payments based on pre-agreed arrangements) • Protect their Oyster card in case of lost or stolen • See their Oyster journey history • Apply for a refund for incomplete journeys or service disruptions TfL requires a CNP payment gateway that can be integrated into the Oyster Online platform and TOCMA in a secure way to ensure the above services are provided to customers uninterrupted.

The payment gateway should follow industry best practices for e.g. (Representational state transfer)REST/(Simple object access protocol)SOAP over (Hypertext Transfer Protocol Secure)HTTPs and must comply fully with (Payment Card Industry Data Security Standard)PCI-DSS.

The service must also offer (Primary Account Number) PAN tokenisation, including the option to bulk import (and retrieve) card numbers from (and to) a secure store.

To assure our transactions and its associated fraud risks, TfL will also require a fraud management tool to be provided through SaaS as part of the payment gateway service, which will help efficiently mitigate these risks.

The tool should enable bespoke rules to be built and applied to transactions in real time.

TfL requires a Service Provider to provide monitoring tools and capabilities to ensure that the service can be measured by TfL and any disruptions to the service can be appropriately handled.

In addition, the system should be able to facilitate chargeback processing, and output customised reports according to bespoke requirements.

Please see additional information at II.2.4