Why Auto-Pay Gets Disabled

If your Runpod auto-pay keeps turning off, it is usually caused by repeated payment failures from your bank.

When does auto-pay get disabled?

Auto-pay is automatically disabled after multiple consecutive declined payment attempts.

This happens when Runpod tries to charge your saved payment method and the bank keeps rejecting the request. After the 10th failed attempt, our system turns off auto-pay and sends a notification so you can take action.

Please check your inbox for the notifications from Runpod always.

Email example - 

Why does Runpod do this?

This is expected product behavior and cannot be changed.

We intentionally limit the number of retry attempts because repeated charge requests can cause your bank to flag Runpod as a fraudulent vendor. To avoid that, we stop retrying after limited failed attempts and disable auto-pay.

How to avoid service interruptions

To reduce the risk of downtime or production shutdowns, we recommend the following:

• Monitor payment attempts closely and resolve any failed transactions before auto-pay is disabled.
• Set a higher balance threshold so your services can continue running for several more days even if auto-pay turns off.
• Increase your auto-pay top-up amount to maintain a larger balance cushion.

A higher threshold and top-up amount can help keep your services running for an additional 5–7 days while you resolve the payment issue.

Can this behavior be changed?

No. If your bank continues rejecting auto-pay requests, auto-pay will be disabled after 10 failed attempts. Runpod informs you about your setup changes, always pay attention to the email notifications.

Need help finding the exact reason?

If this keeps happening, contact Runpod support and include your Runpod account email address. We can help investigate the likely reason your bank is rejecting the payment attempts.