Earlier quoted context omitted.
"You just can't put a band-aid type solution on a problem created by a weird race condition" Oh yes you can, and do, often, in payment processing code. I've done it (with a simple sleep for x seconds I think), and I can assure you the higher ups couldn't have been happier.
You absolutely shouldn't need to do that often in payment processing code. Did you go back and fix it properly later?
The race condition resulted in an error syncing between two datacenters, so when it happens it can be dealt with manually.
Also, to be clear, it did not affect customer waiting time as the delay was in a webhook which we used as a backup to the main payment process.