Alas ... there's nothing more to it, other than we both had Citi issued cards and used the same travel agency but different offices of the agency. I had no relationship with the other person although it was obvious from the credit card statement who they were since it included the name of the passenger with an usual last name, the ticket number and the airline. Citi insisted it wasn't their problem and they weren't going to credit my account until they had the proper credit card to charge it to. To this day, I don't know how this mixup occurred.

I realize that's not permitted and was shocked to get that response. So ... I could write a letter challenging their response, not pay the bill, wait until I got a person familiar with it, presume they would write off late charges and HOPE it wouldn't go on my credit report as a late payment ... or Google away. It took two minutes to find the person on LinkedIn but they wouldn't cooperate (although I presume they had expensed the trip). Finally, I found a senior exec on the other person's end who fixed it.

And while I don't think I had any obligation to do Citi's job, it was quicker than writing a letter and less risk than the credit score hit, which would then involve writing yet another letter under the FCRA (Fair Credit Reporting Act), to challenge the accuracy of the credit report.

Bottom line, the FCBA is a potential powerful tool but has limits even in obvious cases. So ... I'd leave the OP's situation to dealing with AA, rather than disputing the charge. Among other things, I think it's important that credit card issuers recognize FCBA complaints as fully legitimate rather than a challenge to the types of circumstances raised by OP which are really a customer service issue, not a legitimacy of a charge issue.