• Our new ticketing site is now live! Using either this or the original site (both powered by TrainSplit) helps support the running of the forum with every ticket purchase! Find out more and ask any questions/give us feedback in this thread!

SWR smartcard issues 19/04/2026

Status
Not open for further replies.

444007

New Member
Joined
8 Jan 2026
Messages
1
Location
London
Hi. Posting this in the disputes section however as far as I'm aware we aren't being prosecuted, this is more of a question of what went wrong/what to do next time - do say if this is incorrect.

Two of us were travelling from Farnborough Main to London today and each bought Sunday Out Travelcards on our SWR apps (on our own phones, one Android and one iPhone), which we loaded to our smartcards using the app. Upon reaching Farnborough, our tickets wouldn't work on the barriers, and when we reached Waterloo they wouldn't scan there either - saying "seek assistance" but the gateline staff let us through. However, both smartcards were checked on the train by a guard who didn't raise an issue confusingly. The National Rail smartcard manager app on my phone and the Waterloo gateline staff's device stated that the ticket loaded was an off-peak return with no further information (it didn't say which stations it was between or anything else like other tickets usually do) but had the correct price for both of our travelcards.

When we went to enter the tube, the barriers there wouldn't let us through so we went to the ticket office at Waterloo to get the issue fixed, where an agent eventually arrived at the conclusion that the tickets on our smartcards hadn't loaded correctly but didn't give much more info. We then got told the only option was to be sold a new pair of travelcards issued on credit card sized tickets with the person in the ticket office promising us we could then get a full refund of our broken smartcard tickets once customer services opens tomorrow.

Did we do anything wrong here? I've successfully had a travelcard (although a off-peak day, not a sunday out) on my smartcard once before which worked on all barriers including the tube/TfL with no issues. Would like to avoid this in the future if possible.

Thanks
 
Sponsor Post - registered members do not see these adverts; click here to register, or click here to log in
R

RailUK Forums

furlong

Established Member
Joined
28 Mar 2013
Messages
5,310
Location
Reading
Sounds as though the Sunday Out range of ticket types haven't been set up everywhere they should have been yet. Good luck getting them to fix it! Contact TfL directly in respect of their barriers. It takes much of the railway many years to roll out basic changes in their entirety. (Another example I noticed recently was that some ticket machines belonging to an operator serving the station still wouldn't sell tickets for journeys from Kenilworth which opened in 2018.)
 

saismee

Established Member
Joined
20 Oct 2023
Messages
1,710
Location
UK
I find that most non-season tickets on smartcards refuse to operate barriers at my own station, giving the same code as no ticket being loaded at all. Any smartcard reading device will happily find it though.
 

Haywain

Veteran Member
Joined
3 Feb 2013
Messages
24,608
It was mentioned in another thread that the service that uploads tickets to smartcard has been somewhat flaky of late, so that might be the problem.
 

saismee

Established Member
Joined
20 Oct 2023
Messages
1,710
Location
UK
It was mentioned in another thread that the service that uploads tickets to smartcard has been somewhat flaky of late, so that might be the problem.
"as of late" being the past year!!! Though if the tickets show up on readers then it would probably be an issue on the barrier-end.
 

Edvid

Established Member
Joined
7 Feb 2008
Messages
2,490
Two of us were travelling from Farnborough Main to London today and each bought Sunday Out Travelcards on our SWR apps (on our own phones, one Android and one iPhone), which we loaded to our smartcards using the app.
The fact SWR sold those particular tickets in ITSO smartcard format at all intrigues me.

I say this because unless there's been a recent change, ticket gates supplied to TfL and most other train operators are technically incapable of validating 'secondary' off-peak tickets (e.g. Sunday Out Travelcards) if they're stored on ITSO smartcards.

Upon reaching Farnborough, our tickets wouldn't work on the barriers, and when we reached Waterloo they wouldn't scan there either - saying "seek assistance" but the gateline staff let us through. However, both smartcards were checked on the train by a guard who didn't raise an issue confusingly. The National Rail smartcard manager app on my phone and the Waterloo gateline staff's device stated that the ticket loaded was an off-peak return with no further information (it didn't say which stations it was between or anything else like other tickets usually do) but had the correct price for both of our travelcards.
When using the app to read (not load to) my smartcard I sometimes have to scan it more than once to retrieve all the ticket information. Could be a hardware issue - same goes for the possible scanner discrepancy between the guard and gateline staff.

"Seek Assistance" errors are paired with 2/3-digit codes - next time you get one you can use this Android app to ascertain its meaning (couldn't find a free Apple equivalent):

Did we do anything wrong here? I've successfully had a travelcard (although a off-peak day, not a sunday out) on my smartcard once before which worked on all barriers including the tube/TfL with no issues. Would like to avoid this in the future if possible.
Not your fault; SWR offered the product and you bought it in good faith. Next time you need a Sunday Out / Evening Out Travelcard just stick with the credit card sized tickets; for the non-Travelcard single / return equivalents, eTickets are also a workable option.
 

saismee

Established Member
Joined
20 Oct 2023
Messages
1,710
Location
UK
"Seek Assistance" errors are paired with 2/3-digit codes - next time you get one you can use this Android app to ascertain its meaning (couldn't find a free Apple equivalent):
I'll summarise the likely ones here:
11 - ITSO ticket expired
44 - No rides (not entirely sure what this means but it sometimes appears)
57 - NLC not valid (no ticket on ITSO)

You can also find them here without an app:
 
Status
Not open for further replies.

Top