How retry logic works

Rebill's retry logic activates automatically whenever a recurring payment fails for a recoverable reason — most commonly insufficient funds. We run up to 4 retries over 10 days. If all retries fail, the subscription enters Past Due.

When retries happen

Retries are triggered only by soft declines — rejections where retrying could plausibly succeed:

• Insufficient funds

• Temporary issuer errors

• Daily transaction limits

Retries do NOT run for non-recoverable rejections, such as:

• Blacklist hits

• Issuer bank declines (bank_rejected o do_not_honor)

• Issuer-side blocks (lost or stolen card, account closed, fraud rule)

• Hard declines (expired card, invalid number)

Retrying these would not change the outcome, so we stop after the first attempt.

The retry schedule

We run a total of 4 retries spread across 10 days from the original decline:

While retries are in progress, the subscription stays in Retrying state. Any successful retry moves it back to Active.

After the fourth retry

If the fourth retry still fails, Rebill stops and the subscription enters past-due. From that point:

• Automatic retries no longer run.

• The merchant must reactivate the subscription manually (Subscriptions → select subscription → update status, payment method and/or charge date).

• The customer is not charged again until the merchant takes action.

Customization

The retry schedule is not customizable at this time. All accounts run the same 4-retry, 10-day cadence.

If you need to interrupt retries before the cycle finishes, you can edit the subscription manually — for example, switch the state from Retrying to Active and set a new charge date.

Need help?

If you have questions about retry logic or a specific subscription stuck in past-due, please reach out at support@rebill.com.