EE Contactless Mobile Payments – Now Available on London’s Underground, DLR and Overground Networks

Share

EE, the UK’s most advanced digital communications company, today announced customers can now use their mobile phone to pay for travel on London Underground, tram, DLR, Overground and National Rail services that accept Oyster for the very first time.

The roll-out compliments the ability to make mobile payments with EE on London Buses introduced on August 4th. Customers with Cash on Tap enabled handsets can now benefit from the simplicity, convenience and security of mobile payments across the entire TfL network, without the need for an Oyster card or contactless debit card.

EE continues to work closely with TfL and MasterCard to make sure paying for the Tube is faster and more practical than ever before. Whether travelling on the tube, bus or both, customers will no longer need to queue to top-up an Oyster card, or rummage through a handbag at the barriers. Cash on Tap also removes the possibility of card clash – where gates may not open if customers have more than one contactless card in their purse or wallet
The Cash on Tap service was launched last year, and is due to be compatible with over 500,000 customers’ handsets by the end of the year. There will be no added charges for using Cash on Tap to pay for travel, and Monday to Sunday capping ensures customers will pay the best value fare for their contactless travel.

Pippa Dunn, Chief Consumer Marketing Officer, EE said: “The TfL network carries more than 30 million journeys  around the capital every day, and contactless payments can help make these journeys easier and quicker for London’s residents and businesses. This is why EE has continued to work so closely with TfL and MasterCard to bring the ease and efficiency of contactless mobile payments to London’s Tube, tram, DLR, London Overground and National Rail services that accept Oyster.

media_1410864150732.png

Leave a comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.

error: Content is protected !!