Megaton327
Senior Member
I've just been re-reading a lot of the Presto info on using the card, some of it is very ambiguous. Won't list them all right now, but this is revealing:
[For commuters looking for a faster way to get downtown from Bloor and Weston stations, the new fare structure offers prices that match GO Transit fares.]
https://www.prestocard.ca/en/about/paying-for-transit
Consider that wording very carefully. This was debated here and elsewhere almost a year ago, and yet this is currently still up at the Presto site linked prior:
"prices that match GO Transit fares". Note they don't state that the "fare" is integrated, just the price of that fare. No mention of your fare being good for 'booking through' on UPX, just that if you ride from, say, Union to Bloor, the cost of that fare is the same as if you took the GO train between the same points. No transfer from GO is recognized on UPX!
This may still be the basis of my continuing issue with the GO Presto machine on the Union UPX platform, and the advice of one GO service rep to use the GO Presto machines downstairs, or not tap off and on during the transfer from GO train at Union to UPX, and just tap off at the GO Presto machine at Bloor. That has solved the problem, but then renders getting a refund on-line for a late train void. In those instances, phoning it becomes necessary.
It shouldn't be this way! How many times does a glitch have to repeat itself being reported for it to be addressed?
And I'm getting tired of being asked to participate in their phone surveys every time I phone in. The answers obviously count for nothing.
For the record, I've done it infrequently, but on a few occasions I've transferred between other GO Train and Bus lines at Union and the UPX to Bloor, using the GO Presto reader at Union UPX, and had no issues with the transfer.
Between this and the other issues you've reported which have differed wildly from my experiences, while it shouldn't be possible and makes absolutely no sense, maybe your Presto card/account is somehow thoroughly bugged, itself?