Originally Posted by
Horatio
So this is weird. Made a BA flight booking this morning and when clicking the dropdown to pick a passenger for the seat choice, one of the names offered was of some Spanish guy I have never heard of, with his BAEC number attached.
I spoke to a very helpful lady at BA and as far as we could see it was nothing fraudulent (fingers crossed) but more likely a bug, although if anything that's probably more concerning.
The only link between him and me that she could see is that he is flying to a destination today (on BA) that I flew to a few weeks ago (on a different OW airline). The very weird thing was that when she logged into my account it said that I was flying to that destination today, which I am certainly not. When she logged out of my account, into his (where the booking was showing as normal) and then out of his and back into mine, the erroneous booking had disappeared.
I can proceed all the way to the payment screen with his name and Exec number on the booking. Obviously I've not gone any further. The person does not however appear in my travel companion list.
I've not asked BA to lock my account as I can see being shut out for weeks whilst they fail to sort the problem but I have changed my password. Of course, being BA IT I couldn't do that the normal way but had to follow the forgotten PIN/password instructions...
I have made a dummy booking on a different date to a different destination and his name and BAEC number are still on the list.
Anyone else lucky enough to have this new enhancement? I wonder how interested the Information Commissioner would be.
Well this is another fault which will get BA into trouble over GDPR breaches. I've had a similar fault trying to book seats for people on my household account. The drop down box only included 4 people and then a 'someone else' option instead of all the people on my list. I had to enter the names of two of my children and their exec card numbers into the system manually. At least there weren't unrelated parties on my list but I suspect a bug. Do BA not do any testing; looks to me like they are using 'b team' development engineers and their test engineers need to expand the test suite and have some sessions about what GDPR means.