Dunning settings reference
This page describes the settings on the Recurring billing & dunning configuration page (Billing & payments > Recurring > Dunning). These settings control how MapleGather handles failed recurring-billing charges.
To change these settings, see Configure recurring billing and dunning settings.
Retry settings
Section titled “Retry settings”| Setting | What it does | Default | Allowed values |
|---|---|---|---|
| Max retry attempts | How many times Stripe retries a failed charge before the dunning cycle ends. Higher values give members more time to update their card but extend the period of friction. | 4 | 1–4 |
| Dunning window (days) | The total number of days the dunning window runs from the first failed charge. Retries are spread across this window according to the selected timing mode. | 21 days | Any positive integer |
| Use Stripe Smart Retries adaptive timing | When on (default), Stripe uses machine learning to pick the best time to retry each charge — this typically recovers approximately 25% more payments than fixed intervals. When off, retries use fixed 5-day spacing. Disable only for accounting or policy reasons. | On | On / Off |
The maximum for Max retry attempts is 4. Setting it higher is blocked by a validation error.
Per-attempt member copy
Section titled “Per-attempt member copy”For each retry attempt up to your Max retry attempts, you can customize the message that appears in the dunning notification email and in the member’s portal banner. There are up to four template fields (one per possible attempt). The fields are labeled Attempt 1 of [max] through Attempt [max] of [max].
Email delivery target
Section titled “Email delivery target”Dunning notification emails are sent to the member’s billing contact email role. If no billing email is set for a member, the notice falls back to their primary email. Email roles are configured per member in the member’s profile settings.