Exceeds Withdrawal Amount Limit
Category: Velocity/Limit Exceeded Retryable: yes
Variability
Meaning varies by network
Take the card brand and processor into account before treating this as diagnostic.
Retryable
yes
Retry after the daily/weekly limit reset window, or at a lower amount / split across transactions if the merchant relationship and use case allow it.
Namespace: Legacy/conventional ISO 8583 field-39 code as implemented by card networks and processors — not the current ISO 8583:2023 Annex D table.
What this code typically means
The transaction amount, alone or combined with other activity in the period, exceeds a limit configured on the card — daily spend cap, per-transaction cap, or a cardholder-set control. Stripe's withdrawal_count_limit_exceeded decline code covers the same underlying concept, though what counts toward the limit (single transaction vs. cumulative) is issuer- and card-program-specific and not standardized.
What to do about it
Merchant action
If the amount is large, consider whether splitting the charge or waiting for the reset window fits your business model; don't retry the identical amount immediately.
Customer-facing guidance
Ask the customer to check their card's spending limit, or use an alternative payment method for this amount.
What's happening on the issuer's side
Enforcing a configured limit, not a risk decision about the transaction's legitimacy.
Cross-processor equivalents
stripe: withdrawal_count_limit_exceeded
commonly treated as equivalent
Cross-processor mappings are commonly treated as equivalent, not identical — every processor's own documentation notes lossy or partial mapping between raw network codes and its own vocabulary.
Sources
- Stripe — Card decline codes — fetched 2026-08-20
- Worldpay ISO 8583 Reference Guide V2.58 — Debit/Credit Response Code Mappings — fetched 2026-08-20
- ISO 8583:2023 Annex D — Action codes (current standard, 4-digit) — fetched 2026-08-20
Concept + retry philosophy
Decline Codes: why they're opaque and how to retry them