Turn a failed renewal into a considered next step.

Set a recovery policy for recurring payments

Decline Manager controls scheduled attempts after recurring payments decline. Profiles match connected funnels and define attempts before hold, scheduling and optional gateway or discount settings. The account default applies when no active profile matches.

Zero attempts means immediate hold with no retries. It does not mean an immediate retry. Review this distinction when creating a new policy or investigating a subscription that stopped attempting payment.

Choose the timing and limits deliberately

Available scheduling controls include daily, weekly, monthly and custom timing. The earliest processing hour is expressed in Eastern Time. Review these settings against your operating needs rather than assume they use your browser’s timezone.

A recovery gateway can override the gateway used for profile attempts. Its preservation setting may affect subsequent rebills. Leave it unselected when you do not intend that override.

Understand what verification tells you

A verified profile confirms that saved configuration was read back. It does not guarantee a successful payment. The decline response, gateway availability, payment credentials and subscription state still matter.

If a settings refresh is unavailable, the last verified configuration remains visible. An unavailable read does not mean recovery has been disabled. Review the status and contact support before making repeated changes.

Review recovery in the customer workflow

Connect the failed payment with its customer and subscription history. Define who reviews unresolved cases and how your team handles customer requests. In a demo, we can walk through the policy and reporting relevant to your recurring model without promising a recovery percentage.