On Apr 17, 12:31*am, "Michael R N Dolbear" wrote:
Jack wrote

Re. your refund - this would have been purely goodwill. *Oyster has

never been able to charge in the way that you think it should.

I hope this was made clear to you when the refund was agreed.

"never been able"

Cite please.

Previous explanations of Oyster capping here and elsewhere showed this
working as would be expected, with no cases where using two PAYG Oyster
cards would give a lower cost.

* * "Oyster will work out the cheapest combination of fares for all
your
* * *journeys in one day."

--
Mike D

Cite please
:-)
Oyster PAYG has NEVER been programmed to charge for one zonal cap,
e.g. Peak Z1-4 plus a single fare for a journey outside the cap
reached, e.g. Z5.

What it does do, assuming correct usage, no max journey times
exceeded, no emergency OSI settings or OSIs causing 'circular
journeys' is charge the lowest of:

1) all single journeys fares between 04:30 and 04:29:59
2) the Peak zonal cap for all journeys made between 04:30 and 04:29:59
the next day
3) the total of single fares for journeys started between 04:30 and
09:30 and the Off-Peak zonal cap for journeys made between 09:30 and
04:29:59 the next day.
4) the Bus & Tram cap for journeys started between 04:30 and 04:29:59
the next day plus any rail fares for journeys made between 04:30 and
04:29:59 the next day

Oyster takes any discount(s) loaded into the card into account for
single fare and cap calculation.

The charging happens on the chip of the Oyster card during entry and
exit transactions and not retrospectively. In other words, assuming
no incorrect usage, no transaction errors and no OSI related issues,
it cannot charge incorrectly.

The only way to pay for one zonal cap plus a single fare for a rail
journey outside that zonal cap would be to:
1) use two Oyster cards
2) use a paper Day Travelcard and touch in and out with an Oyster card
for the one journey made outside the zones of the Day Travelcard