Payment Retry

A payment retry is a new attempt to complete a payment that failed or was declined, made by the merchant, biller or payment provider after the first attempt did not succeed. Retries are routine for subscriptions, loan repayments and other recurring charges, where a single failed collection does not end the customer relationship, and for one-off payments that failed for a technical reason.

Retries recover revenue that would otherwise be lost to involuntary churn, but they are tightly bounded by rules. Card networks limit how often a declined card may be reattempted and charge fees for excess attempts; the US ACH rules cap how many times a returned debit may be reinitiated; and consumer law limits repeated debits from a customer's account. A good retry strategy therefore distinguishes between failures worth retrying and those that are final, a judgement that starts with the reason for the payment decline or payment failure.

If you knock on a friend's door and nobody answers, it makes sense to come back later; they may have been out. If they open the door and tell you clearly to go away, knocking again in five minutes is pointless and annoying, and knocking fifty times will get you into trouble.

Payment retries follow the same common sense. If a payment failed because the bank's computer was busy or the customer was a little short of money that day, trying again later often works. If the bank said the card was stolen or the account is closed, trying again will not help and may break the rules. Retry systems are built to tell these situations apart and to space out the attempts sensibly.

• Technical failures. Timeouts and processor errors can be retried quickly, ideally with the same idempotency key so that, if the first attempt actually succeeded, the customer is not charged twice. Smart payment routing may send the retry through a different processor.
• Soft declines. Insufficient funds or temporary issuer limits may clear after payday or the next statement cycle, so billers often retry a few days later.
• Authentication requests. A decline asking for strong customer authentication should be retried with 3-D Secure, not resent as before.
• Hard declines. Lost or stolen cards, closed accounts and invalid numbers should not be retried; the customer must supply a new payment method.

Both major networks restrict reattempts. Visa groups decline codes into four categories. Category 1 codes, where the issuer will never approve, must not be retried, and each reattempt incurs a fee. For categories 2 to 4, Visa caps reattempts on the same card at the same merchant within a rolling 30-day window; the cap was 15 attempts from 2021 and was raised to 20 in May 2025, with a fee on each attempt beyond it. Mastercard uses Merchant Advice Codes returned with the decline, such as codes indicating "do not try again" or "try again later", and charges fees when merchants exceed its limits on repeated attempts with the same card; merchants should check the current thresholds with their acquirer. Fees per excess attempt are small, typically cents, but add up across large subscription bases.

Network tokens and account-updater services reduce the need for retries by keeping card details current after reissue, which is one of the main causes of subscription failures; see network tokenization.

For bank debits, retries are called reinitiation or re-presentment, a different idea from card chargeback representment. Under Nacha rules, an ACH debit returned for insufficient funds (R01) or uncollected funds (R09) may be reinitiated up to two times, for a total of three attempts, within 180 days of the original entry's settlement date, and the reinitiated entry must be identified as a retry. Debits returned as unauthorized or because authorization was revoked cannot be reinitiated without a new authorization. Each returned debit can also trigger an overdraft or NSF fee for the customer, which has made repeated re-presentment a consumer protection issue in the US. In the UK and euro area, direct debit schemes let billers re-present a failed collection under their scheme rules and the customer's mandate.

A sound retry schedule usually combines:

1. Classification. Map each response code or return reason to retry, retry later, change method or stop.
2. Timing. Space attempts out, often aligned with common paydays or the start of a billing cycle, rather than hammering the card.
3. Limits. Hard caps per card and per period that stay below network thresholds.
4. Customer contact. Messages asking the customer to update their card, a practice subscription businesses call dunning, sent in parallel with retries.
5. Measurement. Tracking recovery rate, fees incurred and complaints, and keeping retries out of card testing patterns that fraud systems flag.

Retries for recurring payments must also respect the customer's choices. A customer who has cancelled a subscription or stopped a payment under Regulation E must not be retried, and doing so invites a payment dispute and a chargeback. Every attempt, successful or not, needs to be traceable in the billing system and in payment reconciliation so that finance teams can tell recovered revenue from new sales.

• Nacha Operating Rules
• Visa Core Rules and Visa Product and Service Rules