The payment cleared. The ticket never arrived.
I paid via Pix in Brazil. The payment was successful. The money left my account instantly. I sent the receipt. Air France's response: "We have not received the payment. Please contact your bank."
This was repeated multiple times.
The wrong diagnosis
This wasn't a payment issue. It was a ticketing issue.
If a Pix payment is successful, there is nothing to "check" with the bank. The customer cannot investigate why a ticket was not issued. That investigation has to happen on the airline's side.
At that point, support should either verify the payment internally, or route the case to a team that can. For example: "This needs to be handled by our Brazil team during business hours."
Instead, the responsibility was pushed back to the customer.
The real failure
The issue is not a lack of knowledge about Pix. This is what happens when support cannot route issues it doesn't own.
If "Pix" had been treated as a Brazil-specific signal, this case would never have been routed to a generic queue. The system didn't know where it was. So it defaulted to a response designed for a different context.
Where localization actually begins
Localization failures don't start at translation. They start earlier — in how systems are designed to understand context.
Localization doesn't begin with words. It begins with whether the system knows where it is.