DEV Community

Swipe Again for Swipe Again

Posted on

Reading a Recovery Report Without Lying to Yourself

Every recovery dashboard wants to be believed, and the easiest way to be believed is to count generously: attempts described as recoveries-in-progress, self-fixed failures claimed as wins, test traffic stirred into the totals. The numbers go up. The merchant's bank account, the only auditor who cannot be fooled, disagrees quietly.

Our rule at Swipe Again is that a recovery exists only when money moved and was stamped at the single choke point where recoveries are recorded — retry, card update, or save offer, never two at once. Test merchants are excluded from business reporting by definition, not by cleanup. And the failures are printed next to the wins, with their endings named, because a report that hides its losses is training its reader to make decisions on fiction.

There is a selfish reason for the strictness: strategy runs on these numbers. Which decline family is worth a new schedule, which platform's flow is leaking, whether the trial cohort is converting — every one of those calls is only as good as the honesty of the count underneath it. The recovery flow produces the data; the discipline is refusing to decorate it. A smaller true number beats a larger decorated one every time it is time to decide something.

Top comments (0)