Skip to main content
Smart Retries determine when Airdun re-attempts a charge, rather than retrying on a fixed interval. Three inputs shape the schedule.

Three inputs to the retry schedule

Airdun estimates likely payday dates from the customer’s country and billing history, and holds the retry for the window when the account is most likely to have sufficient funds — typically just after a payday — rather than firing on a fixed day-3 schedule.
Salary cadences, bank processing times, and account replenishment patterns differ by market. Airdun applies country-specific retry windows and frequency limits rather than a single global default.
The retry approach depends on the failure reason:
  • Expired card — retrying immediately cannot succeed; Airdun prioritizes outreach to prompt a card update before attempting again.
  • Insufficient funds — retries are held and timed around likely payday dates.
  • Bank block or do-not-honor — customer action is usually required; Airdun routes to outreach first and retries only after engagement signals.
  • 3DS / authentication required — Airdun surfaces the authentication request through outreach rather than re-attempting without customer involvement.

Coordination with outreach

Smart Retries are not standalone. The retry schedule and the outreach sequence are timed together, so a customer receiving a payment reminder is also being retried at the moment that reminder is most likely to have had an effect.

Enabling and disabling

Smart Retries are toggled from the Channels page in your dashboard, below the channel toggles. Disabling them reverts to Stripe’s default retry schedule. See Channels Setup.