Is decline code 61 a soft or hard decline?

Soft. The card is valid — the charge just exceeds a withdrawal or spending limit the bank enforces over a window. A retry timed after that window resets often succeeds, so it's a retryable decline rather than one that needs the card replaced.

What is the Stripe equivalent of decline code 61?

Stripe surfaces it as the withdrawal_count_limit_exceeded decline_code on a card_declined error. The underlying issuer decision is the same as ISO 8583 code 61 — the charge would breach a limit the bank applies to the card.

Can a subscription be retried after an Exceeds Withdrawal Amount Limit decline?

Yes. Because code 61 is a soft, limit-based decline, retrying after the cardholder's limit window resets — the next day for a daily cap, or the next cycle for a cycle cap — frequently clears it. Back-to-back retries keep hitting the same ceiling. Revatto handles that timing plus human outreach for you, and only takes a cut if the payment comes back.

How do I prevent Exceeds Withdrawal Amount Limit declines?

You can't control a cardholder's bank limits, but timing renewals away from a customer's known limit windows, splitting or flagging high-ticket charges, and prompting customers on prepaid or debit cards to confirm available limits before a large renewal all reduce them.

Decline code 61: Exceeds Withdrawal Amount Limit

By Calum Ewing · Head of FulfillmentReviewed by Jay StevensUpdated June 19, 20263 min read

Summarize with AI

Quick answer

Decline code 61 — “Exceeds Withdrawal Amount Limit” — is an ISO 8583 response code returned when a charge would push the cardholder past a withdrawal or spending cap their bank enforces over a set window (per-day, per-cycle, or per-transaction). It’s a soft, retryable decline: the card is valid, the limit just hasn’t reset. Stripe surfaces the equivalent as withdrawal_count_limit_exceeded; Braintree returns it as code 2002, “Limit Exceeded.” Recovery is a timed retry plus a nudge to the customer.

What code 61 means

Soft declineRetryable

A soft decline tied to a limit window — a blind immediate retry usually fails for the same reason, so retry once the cardholder's daily/cycle limit resets (typically the next day), or after they confirm a higher limit with their bank.

Cross-processor equivalents

The same issuer decision surfaces under a different code on every processor. Here is how code 61 maps across the stacks Revatto recovers on.

ProcessorCodeWhat it’s called

ISO 8583

Code61

CalledExceeds Withdrawal Amount Limit

Codewithdrawal_count_limit_exceeded

CalledWithdrawal count limit exceeded

Code2002

CalledLimit Exceeded

Code49

CalledAmount exceeds maximumresponseReasonCode 49

Code203

CalledOver limitalso 300 (exceeds maximum ticket)

Codetransaction_limit_exceeded

CalledTransaction limit exceeded

Codetoo_many_attempts

CalledToo many attempts

Code2004

CalledLimit exceededadapterCode 61/65 also map here

Codelimit_exceeded

CalledLimit exceedednormalized — no processor-specific code (free-text categorized)

Codelimit_exceeded

CalledLimit exceedednormalized — matched by substring rule, no processor-specific code

Why it happens

The transaction would push the cardholder past a daily or per-cycle spending limit their issuer enforces.
A per-transaction ceiling on the card (common on debit, prepaid, and corporate cards) is lower than the charge amount.
The cumulative total of recent charges has already consumed most of the available limit for the window.
A temporary issuer-set cap — newly issued cards, prepaid balances, or risk-based throttling — is tighter than the cardholder expects.
A high-ticket or annual renewal lands above a limit that comfortably cleared smaller monthly charges.

How to recover it

1Don't re-run the same charge immediately — the limit window hasn't reset, so an instant retry hits the same ceiling and inflates your decline ratio.
2Time the retry to land after the limit resets — typically the next day for a daily cap, or early in the next billing cycle for a cycle cap.
3Reach the customer on email and SMS: explain the bank capped the charge and ask them to raise the limit, use a different card, or expect the retry once the window resets.
4
When it persists, a real person works the card update or alternate-payment conversation directly. That AI-timed-retry-plus-human handoff is exactly what Revatto does for you, fully done-for-you — and you only pay if it works (20% of the first recovered payment, $0 setup, $0 monthly, cancel anytime).See how Revatto recovers 61declines →

See what Revatto would recover for you

Failed payments recovered automatically — no engineering, no manual chasing. We do the work; you keep the revenue.

See Your Recovery Potential