Skip to main content

Failed payment flow

Manage failed payment flow

Andrey Gadashevich avatar
Written by Andrey Gadashevich
Updated over a week ago

When a customer’s auto-charging subscription payment fails, RecurrinGO gives you full control over how to handle retries and what happens if retries are unsuccessful.

You can define the number of payment retries, the retry frequency, and the action that should occur if the retries fail.


Access these settings by navigating to RecurrinGO → Settings → Failed payment flow

Steps to set up the failed payment flow


1. Configure Maximum Payment Retries

Set the maximum number of times RecurrinGO will attempt to retry the failed payment before taking further action.

2. Set the Retry Frequency

Choose how often RecurrinGO will retry the payment (e.g., every minute, day or every 2 days) until the maximum number of retries is reached.

3. Select Post-Retry Action

Decide what happens if all retry attempts fail:

  • Pause the Subscription: The subscription will be paused until further action is taken by the customer or merchant.

  • Cancel the Subscription: The subscription will be canceled automatically.

  • Skip failed order: The failed order will be skipped, and the subscription will continue with the next scheduled order.

How this works in practice

  1. If a payment fails, RecurrinGO will retry based on your retry frequency.

  2. This will continue until the maximum retries are reached.

  3. After the limit is hit, the final action you selected (skip, pause, or cancel) will be applied.

  4. Customers will be notified depending on your Notification settings (e.g., Payment failed, Payment failed last attempt).

Example setup

Max retries: 5

Frequency: Every day

Final action: Pause subscription

👉 This setup retries for 5 days in a row. If unsuccessful, the subscription is paused until the customer resolves it.

What you can configure

1. Maximum number of payment retries

  • Choose how many times RecurrinGO should attempt to retry the payment before taking further action.

  • Range: 0–10 retries

    • 0 retries: No retry attempts will be made.

    • 1–10 retries: The app will attempt the payment the specified number of times.

2. Retrying frequency

  • Decide how often the system should attempt the payment again.

  • Options include:

    • Every minute (testing only) – for sandbox/staging tests.

    • Every day

    • Every 2–30 days
      This allows you to customize how aggressively or gently payment retries are attempted (e.g., daily vs. weekly).

3. Action after maximum retries

Once the system reaches the maximum number of retries, you can define the next step:

  • Skip failed order
    The failed order will be skipped, and the subscription continues with the next scheduled cycle.

  • Pause subscription
    The subscription is paused until the customer or merchant reactivates it.

  • Cancel subscription
    The subscription is cancelled automatically after retries are exhausted.

Best practices

  • Minimize churn: Start with daily retries for 3–5 times, then set the final action to Pause subscription. This lets customers update payment info without losing their subscription.

  • Recover revenue: If your customers often face card declines, try higher retries (7–10) with every 2–3 days frequency.

  • Strict enforcement: If inventory is limited or recurring service is resource-heavy, consider Cancel subscription after a low retry count.

Need Help?

If you have any questions or need help, please contact our support team.

📩 Contact Support: Reach out to us via live chat or send an email to [email protected]

Did this answer your question?