Dunning settings reference
This page describes the settings on the Recurring billing & dunning configuration page (Recurring billing & dunning (at /admin/billing/payment-processor/dunning)). These settings are your org’s policy for how MapleGather handles failed recurring-billing charges.
Nothing retries a failed charge on its own today. Every setting below is stored against your org and governs the retries it will run; retry execution is planned, not running. Until it runs, a failed renewal stays unpaid until the member pays it, or replaces their card and then pays.
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 retry attempts your org allows before the dunning cycle ends. Higher values give members more time to update their card but extend the period of friction. | 3 | 1–4 |
| Retry schedule (Retry 1–4) | The day each retry runs, counted from the failed charge. Fill the boxes in order; leave later ones blank to use fewer. Each retry attempt runs on one of these days. | Days 1, 3, 7 | 1–4 days, each 1–30 |
| Days before lapse after the final retry | How many days after the last failed retry the member’s membership lapses. | 30 days | 0–90 |
| Use adaptive retry timing | Selects the timing mode your retries use once they run. When on (default), MapleGather adjusts when each retry runs around its scheduled day, which generally recovers more than fixed spacing. When off, each retry runs exactly on its scheduled day. Turn it off only if your org requires fixed retry spacing for accounting or policy reasons. Takes effect once automatic retries are running — until then, switching it on or off changes the stored policy only. | On | On / Off |
The maximum for Max retry attempts is 4 — one attempt per scheduled retry day. The list offers only 1 to 4, and you can’t save more attempts than the retry days you’ve filled in.
Per-attempt member copy
Section titled “Per-attempt member copy”For each retry attempt up to your Max retry attempts, you can customize a message for that attempt. The copy is stored with your policy; no failed-payment (dunning) email is sent yet, so members don’t receive it by email today. There are up to four template fields (one per possible attempt). The fields are labeled Attempt 1 of [max] through Attempt [max] of [max]. This copy is not used in the member’s portal banner.
Email delivery target
Section titled “Email delivery target”No failed-payment (dunning) email is sent yet. A member whose renewal payment failed sees the dunning banner in their billing portal instead. (The policy also stores a dunning email template choice, which nothing uses yet.)