Retry logic can trip the card network's own decline-rate monitor

A merchant account was flagged for an excessive decline rate despite every individual transaction eventually succeeding. The client was puzzled by this situation. Their retry logic resubmitted a declined authorization up to four times with short backoff, using the same card and amount, hoping a soft decline would clear. To the client's application, this appeared to be a success story. However, from the network's perspective, it counted as four authorization attempts, with three of them being declined.

Visa and Mastercard both utilize decline-rate monitoring at the merchant level. They count declines alongside total authorization attempts in a rolling window, rather than unique transactions. The retries inflated both the denominator and the decline count together. When the decline rate crosses a certain threshold—around 15% triggers a warning tier on some programs—the merchant account is subject to review, and in some cases, rate-limiting by the acquirer, irrespective of the overall approval outcome after retries.

To resolve the issue, the merchant capped retries to one for hard declines and routed only specific soft-decline codes (51, 65) into a delayed retry queue. Anything else was treated as terminal on the first attempt. The merchant advises that anyone tracking their decline ratio should account for the difference between "attempts vs. unique transactions" or else the issue could remain invisible until the acquirer brings it to attention.