I bought an Anytime Day Rtn from Maidenhead to Paddington as a mobile phone eTicket. I see it states on the eTicket that break of journey is NOT allowed. Is that a new restriction brought in with the eTicket or do paper tickets also restrict BoJ?
The purported restriction is entirely ineffectual, since one is told the precise opposite before purchasing the ticket. GWR cannot simply change the terms of the contract after it has been made.I bought an Anytime Day Rtn from Maidenhead to Paddington as a mobile phone eTicket. I see it states on the eTicket that break of journey is NOT allowed. Is that a new restriction brought in with the eTicket or do paper tickets also restrict BoJ?
It is - not only does it contravene the fundamental terms of an Anytime ticket, but it is also the exact opposite of the right one has been explicitly granted just 2 minutes earlier before paying!I would say it's unenforceable
They certainly might attempt to excess you to the cheapest valid walk-up fare that permits BoJ. I wonder what that might bebut they may try to enforce it
Well, for me a bigger issue is the fact that these tickets aren't even e-tickets at all. They're m-tickets marauding as e-tickets, since they can only be displayed within the selected app, and not viewed as a PDF, printed etc.Another reason to boycott e-tickets.
Certainly not been the case with tickets bought through the FirstGroup app, at least as far back as a few months ago.Eh? GWR issue proper e-tickets. As well as having it in the app, you get the PDF on the confirmation email.
They need to change this to say "SEE RESTRICTIONS". It's been like that for months and I don't get why it isn't getting fixed.
That is not correct. An eTicket is not tied to an app if it correctly follows the RSP standards. The pkpass (the form the part that is not the pdf comes in) can be downloaded to apple wallet, shared or just displayed via email in a correct implementation.Eh? GWR issue proper e-tickets. As well as having it in the app, you get the PDF on the confirmation email.
That is not correct. An eTicket is not tied to an app if it correctly follows the RSP standards. The pkpass (the form the part that is not the pdf comes in) can be downloaded to apple wallet, shared or just displayed via email in a correct implementation.
Incorrect validities, inconsistent application, confusion between e and m tickets and whether or not it needs validation, problems with BoJ (especially overnight) - none of the above is encouraging me to use e or m tickets! I shall continue to boycott them until they have been properly and consistently implemented.
It does exist, but it's done on a per-ticket-type basis. The data assumes the break of journey restriction on a given fare will always depend on the ticket type and always be either present or absent, not variable and determined by the restriction code. FWIW, BR Fares now displays any break of journey restrictions by ticket type in the default display mode (i.e. not expert mode) and on the fare details page under the "Validity" heading.Given that the data doesn't exist in machine readable form to determine BoJ restriction on a given ticket (it's only in the text restriction)
If you buy an e-ticket from GWR's app, which I have done, you get an email with a PDF attached (and possibly also a pkpass, I forget) and you get it in the app in the same format as the PDF too.
That fare is interesting as both the ticket type and the restriction code have a break of journey restriction.
The ex-London Midland only fares have been this way for a very long time, and I think in all likelihood since their introduction. It makes perfect sense to me - customers don't see any difference in the standards-compliant ticket name, but it enables more poorly coded retail systems to display the break of journey restrictions.Oh, I see, LNR (LM) have created a new type OPR which is a Super Off Peak Return which bars it generally (in contravention of the standard "post simplification" ticket type set). Bizarre as to why they have done that and not simply used SSR like everyone else does.
The ex-London Midland only fares have been this way for a very long time, and I think in all likelihood since their introduction. It makes perfect sense to me - customers don't see any difference in the standards-compliant ticket name, but it enables more poorly coded retail systems to display the break of journey restrictions.
It is an "e-ticket" in that you don't have to activate, but it isn't one in that it is restricted to just being used in the app.
You do not get a pdf or pkpass, all you get is the "ticket" as scanable barcode in the app. Nothing else. It is an "e-ticket" in that you don't have to activate, but it isn't one in that it is restricted to just being used in the app.
Are you allowed to load it up in the app, take a screenshot, and then use the screenshot instead of the app during inspection?
Are you allowed to load it up in the app, take a screenshot, and then use the screenshot instead of the app during inspection?
When I have bought e-tickets on GWR this has categorically not been the case. I have received both an entry in the app and an email with a PDF. Are you sure you haven't been losing the email to a spam filter or similar?
OK, so I was intrigued enough to spend 150 of your earth pennies on a single from Stapleton Road to Lawrence Hill (in retrospect, should have gone for a child ticket given that I have no intention of actually using it!) and you are correct, you don't get an email with an attachment. I must indeed be thinking of a different TOC.
Bizarre.
Anyone going from Stapleton Road to Lawrence Hill today and needs a ticket?
And much as you'd have a job actually doing so given that the stations are next to each other, it too has the incorrect statement that BoJ is not permitted.