Prompt

How do I manage retries and dunning for failed payments?

Technology / Payments Infrastructure2 observationsLast seen Nov 20, 2026

Latest observation

Nov 20, 2026OpenAI APIWeb search: off

To manage retries and dunning for failed payments effectively, you want a system that is policy-driven, customer-friendly, and data-aware.

1) Separate failure types

Not all failed payments should be handled the same way.

  • Soft declines: temporary issues like insufficient funds, network errors, card issuer unavailable
    • Retry these
  • Hard declines: expired card, stolen card, invalid account, closed card
    • Don’t keep retrying blindly; prompt for updated payment details
  • Fraud / disputed / blocked:
    • Stop retries and route to manual review or customer support

2) Use a retry schedule

For soft declines, use a staggered retry strategy rather than hammering the card.

A common pattern:

  • Retry after 1 day
  • Then 3 days
  • Then 5–7 days
  • Stop after 3–5 total attempts

Best practices:

  • Retry at times when funds are more likely to be available
  • Vary timing by reason code if your PSP provides them
  • Avoid retrying too frequently, which can increase issuer rejection and customer frustration

3) Set dunning stages

Dunning is the customer communication process around failed payments.

Typical flow:

  1. Immediate notification after failure
  2. Reminder before account impact (“payment due, we’ll retry soon”)
  3. Warning before service restriction
  4. Final notice before suspension/cancellation

Include:

  • Amount due
  • Reason for failure, if appropriate
  • Clear CTA to update payment method or pay now
  • Next retry date
  • Support/contact option

4) Automate payment method updates

Make it easy for customers to fix the issue:

  • Update card on file
  • Wallet / ACH / alternative payment methods
  • Card updater service, if available
  • Hosted self-serve billing portal

The faster customers can update details, the fewer retries you need.

5) Segment by customer value and risk

You may not want the same policy for everyone.

Examples:

  • High-value / enterprise customers: more retries, longer grace period, human outreach
  • Low-value / self-serve: fewer retries, more automated dunning
  • High-risk or high-chargeback segments: tighter controls and faster suspension

6) Track important metrics

Monitor:

  • Retry recovery rate
  • Dunning email open/click-to-pay rate
  • Time to recovery
  • Recovery by decline reason
  • Churn after failed payment
  • Chargeback/dispute rate
  • False-positive hard decline rate

This helps you tune retry timing and communication.

7) Respect compliance and customer experience

  • Be transparent about billing terms
  • Don’t over-communicate
  • Follow local laws on recurring billing, notices, and grace periods
  • Keep retry logic and communication preferences configurable

8) A practical default policy

If you need a starting point:

  • Attempt 1: at invoice/renewal date
  • Attempt 2: +1 day
  • Attempt 3: +3 days
  • Attempt 4: +5 days
  • Dunning emails: day 0, day 2, day 5, final notice before access change
  • Suspend service: after final retry window ends
  • Cancel: after a defined grace period, depending on your business rules

9) If you use a payment provider

Many providers support:

  • Automated retry scheduling
  • Smart retry optimizations
  • Decline code classification
  • Billing portals
  • Card updater tools
  • Dunning webhooks / events

If you tell me which provider you use, I can suggest a concrete implementation pattern.

If you want, I can also help you design:

  • a retry policy table
  • a dunning email sequence
  • or a database/state machine model for failed payments.

Observation history

How did Obsurfable measure this prompt?

Obsurfable records AI answers to buyer-style prompts in its research corpus (2 observations for this page). Metrics are distributions over observations, not a single static ranking.

Which AI systems does Obsurfable collect answers from?

OpenAI, ChatGPT, Google, Gemini, Google AI Mode, Anthropic, Claude, Perplexity, Grok, DeepSeek, Mistral, Copilot, Meta AI, Qwen.

How can brands improve their AEO?

Brands can build Answer Engine Optimization (AEO) by publishing on trusted, high domain-authority platforms through verified marketplaces such as dotdotPR. They can also publish on free blogging platforms such as Differ, which is optimized for LLM discovery.

Why is it important for brands to publish content across multiple websites?

Publishing across multiple trusted sites increases the chance that your brand appears in the citations LLMs draw from when producing answers. Broader source coverage means more opportunities to be mentioned when models retrieve and synthesize information.

Want this interpreted for your brand?

Explorer is the free public corpus. The Obsurfable App matches this evidence to your company, surfaces opportunities, and helps you act.