Payment retry: what it means and how to set it up
What a payment retry ("retry pymt") means, which declines to retry, how to time and cap attempts, Visa and Mastercard limits, and pairing retries with emails.
By Florian
A payment retry is a new attempt to charge a payment that failed the first time. The failure may come from a technical error, a temporary hold, an empty balance or a card the customer canceled. “Retry pymt” on a bank statement or in a billing dashboard means the same thing: the merchant is trying the charge again. For a subscription business, a well-planned retry schedule is one of the cheapest ways to keep revenue that would otherwise be lost to involuntary churn.
This guide explains what a retry is, which failures are worth retrying, how to time and cap your attempts, and which card network rules limit you. To see how each billing platform retries by default, read failed payment retry schedules compared.
TL;DR
- A retry is an automatic re-attempt of a failed charge. “Retry payment” and “retry pymt” are the labels you may see on statements and invoices.
- Retry soft declines (temporary problems such as insufficient funds or an issuer timeout). Do not retry hard declines, where the issuer will never approve the charge.
- Spread attempts over days, around likely paydays, not minutes, and stop after a small fixed number.
- Card networks limit reattempts and charge fees for excessive or prohibited retries.
- Pair retries with customer emails and a card update link, so the customer can fix the root cause.
What does a payment retry mean?
When a card payment is declined or errors out, the merchant can submit the same charge again later. That second, third or fourth attempt is a payment retry.
In subscription billing, retries happen on recurring invoices. The customer is not on the checkout page, so nobody can type in a new card on the spot. The billing system has to decide on its own when to try again, how often, and when to give up. That set of rules is usually called retry logic, and the process of retrying plus contacting the customer is called dunning.
What do “retry pymt” and “retry payment” mean on a statement?
If you are a customer and you see “retry pymt” or “retry payment” in your bank or card activity, a company is making another attempt at a charge that failed earlier. It is usually tied to a subscription, a bill or an installment. Two practical steps help:
- Check that the card on file is current and has enough available balance.
- Contact the merchant or update your payment method in your account settings before the next attempt, so the charge goes through once instead of failing again.
If you do not recognize the merchant name, contact your card issuer rather than ignoring it.
Why do subscription payments fail?
Not every failure is the same, and the difference decides whether a retry makes sense. Most card declines fall into a few groups.
| Type | Typical causes | Retry? |
|---|---|---|
| Soft decline | Insufficient funds, issuer temporarily unavailable, spending limit reached, a bank fraud check that clears later | Yes, on a schedule |
| Hard decline | Closed account, stolen or lost card, invalid card number, issuer instruction not to try again | No. Ask the customer for a new payment method |
| Technical failure | Network timeout, processor error, integration bug | Yes, soon, once the fault is fixed |
| Expired card | The expiration date has passed | Only if the card is updated, by the customer or an updater service |
The decline code returned with each failure tells you which group you are in; see Stripe decline codes explained and the “do not honor” decline for the most common ones. A billing system that treats every failure the same way either wastes attempts on cards that can never succeed or gives up too early on cards that would have worked a few days later. Expired and replaced cards can often be fixed before the renewal: see expiring cards and network tokens and card account updaters.
When should you retry a failed payment?
Timing matters as much as the number of attempts. A card declined for insufficient funds on the 1st is unlikely to have funds an hour later, but may well have them after payday.
These principles work for most subscription businesses:
- Retry quickly only for technical errors. A network timeout or processor glitch often clears within minutes.
- Wait days for balance-related declines. Spacing attempts across several days gives the customer’s account time to change.
- Aim at paydays. Many people are paid on the 1st, the 15th or the last business day of the month. A retry that lands on or just after those dates has a better chance than one in the middle of a pay cycle.
- Vary the day and time. Repeating the exact same hour on the same weekday gives you the same result if the cause is timing.
- Never retry a hard decline. It cannot succeed and it can cost you fees (see the network rules below).
A sample schedule
This is an illustrative starting point, not a rule. Adjust it to your own recovery data.
| Attempt | Timing after the original failure | Why |
|---|---|---|
| Original charge | Day 0 | Billing date |
| Retry 1 | Day 3 | Clears short-lived holds and timeouts |
| Retry 2 | Around the next likely payday, roughly day 7 to 10 | Balance may have recovered |
| Retry 3 | About a week after retry 2 | Final attempt before the subscription is paused or canceled |
How Stripe, Chargebee, Recurly, Paddle, Lemon Squeezy, Mollie, Braintree and the app stores schedule retries by default is in our comparison of retry schedules.
How many times should you retry, and when should you stop?
More attempts are not always better. Each retry can cost processing fees on some setups, adds noise to your approval rate, and counts against card network limits. Past a point, the customer is also more likely to be annoyed than to pay.
A small fixed number is a sensible default: three to four attempts spread over roughly two weeks, then a final notice and a pause or cancellation. A longer window is reasonable for annual plans or high-value contracts, where you can pair retries with direct outreach.
Whatever number you choose, set it by decline type:
- Hard decline: zero retries. Go straight to asking for a new payment method.
- Soft decline: scheduled retries, up to your cap.
- Unknown or generic decline: a limited number of retries, then ask the customer to update their card.
Which card network rules limit retries?
Retrying too often, or retrying the wrong declines, can trigger network fees. The networks publish rules for this and change them, so check the current program documents with your processor.
Check current rules with your processor
Visa
Visa groups declines into four categories. According to Evolve’s summary of Visa’s Processing Integrity Fee Program, Category 1 means the issuer will never approve and no reattempt is allowed, while categories 2, 3 and 4 allow up to 15 reattempts in 30 days. A later summary of Visa’s April 2026 Core Rules puts the limit for categories 2, 3 and 4 at 20 attempts in 30 days. Because the sources differ, build your schedule well below either ceiling and confirm the current figure with your processor.
Mastercard
For generic decline codes, PayPal’s guide to excessive retry penalties says Mastercard allows 10 retries in 24 hours and 35 in 30 days before a fee applies to further retries. The same source notes that merchant advice codes MAC 03 (Do not try again) and MAC 21 (Payment cancelled) mean the transaction should not be retried at all.
What this means in practice
A schedule of three to four attempts over two weeks sits far below every ceiling above. The real risk is not a well-built subscription schedule. It is a system that loops on hard declines, or several tools that retry the same invoice without knowing about each other. Make sure only one system owns retries for a given charge.
Fixed schedule or smart retries?
A fixed schedule retries on set days, for example day 3, day 5 and day 7, for every customer. It is predictable and easy to audit, but it ignores what is different about each failure.
Smart retries use payment data to choose the time of each attempt, so two customers with the same decline code can be retried on different days. Stripe’s Smart Retries, Chargebee’s Smart mode and Recurly’s Intelligent Retries all work this way; see how Stripe Smart Retries work. Typical inputs include the decline reason, the card type, past payment behavior and the time of the month.
How to choose:
- Start with a fixed schedule if your volume is low and you want to understand your own failure patterns.
- Move to smart retries when you have enough failed payments to learn from, or use a tool that already does.
- Keep the guardrails either way: no retries on hard declines, a hard cap on attempts, and a clear stop date.
Why combine retries with customer emails?
Retries fix the failures that fix themselves. The rest need the customer to act: an expired card, a replaced card, a closed account. For these, an email with a secure link to update the payment method does more than another charge attempt.
Checkout.com reports that it has rescued 20% of payments entered into its dunning mechanism, a vendor figure without a published method, but a reminder of how much revenue can sit in failed charges. A simple communication flow looks like this:
- Day 0: a short, calm notice that the payment did not go through, with a link to update the card. No blame, no alarm.
- Before each retry: a reminder that the next attempt is coming, and on which date.
- After a successful retry: a confirmation, so the customer knows the issue is resolved.
- Final notice: a clear date when access will be paused or the subscription canceled, and what the customer needs to do to keep it.
Keep the wording plain. Tell the customer what happened, what you will do next and what they can do now. Avoid decline codes and billing jargon in customer-facing messages. Ready-to-adapt examples are in our dunning email templates.
How do you set it up on your billing platform?
The controls differ by platform, but the setup questions are the same: where do retries run, how many attempts are allowed, and what happens at the end of the schedule. Platform-specific guides:
- Recovering failed payments on Stripe
- Recovering failed payments in Chargebee
- Setting up dunning in Recurly
- Reducing involuntary churn in Maxio
- Payment retries in Zuora
- Failed payments on Paddle
- How Lemon Squeezy handles failed subscription payments
- Failed recurring payments on Mollie
- Recovering failed subscription payments on Braintree
- App Store billing retry and grace period
If you run fintech subscriptions, where declines and compliance details carry extra weight, see NoChurn for fintech subscriptions.
Which metrics show that retries work?
Track a few numbers weekly so you know whether the schedule works:
- Recovery rate: the share of failed payments that eventually succeed.
- Recovery by attempt: how much comes from retry 1, 2 and 3. If the third attempt recovers almost nothing, shorten the schedule.
- Recovery by decline code: shows where retries help and where only a card update works.
- Time to recovery: how many days a typical recovered payment takes.
- Involuntary churn rate: customers lost because a payment failed, not because they chose to leave. See involuntary churn.
Retries are one part of recovery
Many teams treat retries as a setting to switch on and forget. They work best as one part of a recovery system: read the decline, choose the right timing, tell the customer what is happening and give them an easy way to fix the card. Recovery should also not cost a share of the revenue you win back, which is why a flat price known in advance beats a commission on recovered payments.
FAQ
What does “retry pymt” mean?
It is an abbreviation of “retry payment”. It tells you that a merchant or biller is making another attempt to collect a charge that failed earlier. Update your card or contact the merchant if you want the next attempt to succeed.
How long should I wait before retrying a failed payment?
It depends on the cause. For a technical error, a retry within minutes can work. For a balance-related decline, waiting a few days and aiming near a likely payday gives the account time to change. Use the decline code to decide.
How many times can a payment be retried?
There is no single number. Card networks cap reattempts and charge fees beyond their limits, and Visa Category 1 or Mastercard “do not try again” declines must never be retried. For subscriptions, three to four attempts over about two weeks is a common, conservative plan.
What is the difference between a retry and dunning?
A retry is the repeated charge attempt. Dunning is the wider process: retries plus emails, reminders and a final notice that ask the customer to update their payment details. The best results come from running both together.
How NoChurn helps
NoChurn handles the retry and the customer message together, so your team does not have to build and maintain the logic. On Stripe you can keep Smart Retries or let NoChurn time retries to likely paydays and the customer’s local time; on other platforms, retries stay where the platform runs them. On top, NoChurn sends AI-written recovery emails on days 0, 3, 7 and 14 by default, with a link to update the payment method, and shows logged-in customers an in-app banner or wall. It works with Stripe in one click, with Chargebee, Recurly, Paddle, Lemon Squeezy, Mollie, Braintree, the App Store, Google Play and others, or with any billing through the API. It is free until $300 MRR, then from $9 a month, priced by MRR only, with every feature on every plan (your own email domain from $9) and never a commission. See failed payments and pricing.