A customer told us they had been charged twice, and we could not prove them right or wrong. The payment record carried one status field, and every step in the flow overwrote the step before it, so by the time anyone asked a question the history was gone. We rebuilt that single story by hand from bank statements and log files, which is a strange way to spend a week when the system was doing exactly what it had been designed to do.
The expensive part was never the bug. It was that the shape of the data had been picked early, to ship faster, and by the time it hurt it was sitting underneath refunds, payouts and every report the finance side trusted. Changing it meant touching all of that at once, with real money moving through it the whole time.
So now, before we write anything that touches money, we ask one question: if someone disputes this six months from now, can we replay what happened, step by step? If the answer is no, the event log goes in first and the feature goes in second. It is almost free at the start and close to a rewrite later.
If you run a product that takes payments, ask whether you could tell a customer exactly what happened if they disputed a charge today.