Originally Posted by weero
Do I read that correctly: if the LH terminal does not read the card correctly,
UA did not 'program' the card properly. No leeway that the ancient LH software
in that humming box might be 'programmed' in an inadequate fashion?
(...)
You take every single option to blame LH, do you?
Let me make some comments:
1) I remember the years very well, where UA was never able to process a M&M card or a LH SEN CC card. Not that long ago.
2) I even remember the times, where all *A, but United could use BP across. Only UA required to go with the BP issued by LH in FRA for UA domestic connection flight to the gate and let it re-issue. Very annoying.
3) I also remember the times, where UA was unable to read a BP upon lounge entry issued by LH (e.g. the UA FCL in SFO). Just resolved in 2005.
3) Adding the expiration year to the number is a nice idea. But why expecting, that it immediately works with all other *A carriers. Adding 4-digits (or even just 2) may require to change the data model behind and all data exchange procedures, of course. To me this looks more like a single-decision not coordinated process by United.