Why a payment is declined with "Attempt limit exceeded"

Last updated: November 20, 2026

"Attempt limit exceeded" means we paused new attempts from the same customer for a short time, to protect your business from repeated declines. Your customer can try again in about 1 hour, ideally with a card they know has funds and is enabled for online purchases, or with another payment method.


What you see

When a payment receives this decline, you'll find it in these places:

  • In your dashboard, the decline reason reads: "Attempt limit exceeded. Ask the user to try later or use another method."

  • In the payment.created webhook, the payment arrives with status: rejected and statusDetail: max_attempts.

  • Through the API or the checkout, the response is an HTTP 429 with error.type: max_attempts.

  • Your customer receives the declined payment email.


Why a customer receives it

It's a security check that works before the payment reaches the bank. When the same customer builds up several declined attempts in a short period, we hold the next attempt for a while. This happens in three situations:

  • Several cards in a row: the customer tries different cards and the bank declines them within the same hour.

  • The same card: the card receives definitive declines, such as a card reported as blocked or invalid.

  • Waiting period: after a pause, a new attempt goes through once the waiting time is over.

The check works the same way in the checkout, the SDK and the API, for every business. It doesn't affect your account: it applies only to that customer's attempts.

In some cases, the customer's issuing bank declines the payment because the card reached its daily spending limit, and the dashboard shows this same reason. Your customer can ask their bank to raise the limit, try again the next day or use another card.


What your customer can do

  1. Wait about 1 hour and try again.

  2. Use a card they know has funds and is enabled for online purchases.

  3. Choose another payment method, if your checkout offers one.


If you charge through the API

If your integration retries payments on its own:

  • Space out the retries of the same customer instead of sending them one after another.

  • Use one card per attempt and avoid testing several cards from the same customer in a row.

  • Stop after definitive declines, such as a card reported stolen, blocked or lost. Those declines don't resolve with more attempts.

For subscription charges, each card also has its own cap of declined attempts. See How many times can I manually retry a subscription charge?


What to tell your customers

You can share this message with a customer who received the decline:

"To protect your card, the payment was paused after several attempts in a row. Please try again in about 1 hour, with a card that has funds and is enabled for online purchases, or with another payment method."


Need help?

If a customer who should be able to pay still receives this decline after waiting, contact us at support@rebill.com with the payment ID (it starts with pay_).