Halfway through, the club switched payment providers, from Wompi to AvalPay. The migration plan was simple: stop writing to the old payments table. Before deleting the write, I traced who still read that table — the admin dashboard did, building the club's revenue statistics from it. Stopping the write would not have thrown an error: it would have silently erased every AvalPay payment from the reports the club used to see its own money. The fix: keep the write only after the payment is confirmed server-side, plus an idempotency guard, because a status check can legitimately return approved more than once. The report stays whole, and it never double counts. The most dangerous bugs never throw an error.