Skip to content
Decline code 57 Meaning varies by network

Transaction Not Permitted to Cardholder

Category: Restricted/Blocked Card Retryable: conditional

Variability

Meaning varies by network

Take the card brand and processor into account before treating this as diagnostic.

Retryable

conditional

Retry once, 24 hours after the initial decline, only if you have reason to believe a control setting may have changed. Otherwise treat as requiring customer action first.

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 card exists and has funds, but the issuer or a cardholder-configured control blocks this specific transaction type — commonly a card not enabled for card-not-present/e-commerce use, a merchant-category restriction, or a self-service spending control the cardholder set in their banking app. Adyen's published refusal-reason list has no exact equivalent; its closest entry, 'Not supported,' describes a related but distinct condition (the issuer doesn't support the transaction type at all, rather than permitting it selectively).

What to do about it

Merchant action

Ask the customer to check card controls (many banking apps let cardholders toggle online/CNP purchases) or contact their issuer, rather than retrying blind.

Customer-facing guidance

Direct the customer to check their card's settings in their banking app, or contact their issuer to enable this transaction type.

What's happening on the issuer's side

Enforcing either a network-level restriction on the card product or a cardholder self-service control.

Cross-processor equivalents

stripe: not_permitted

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.

Confidence: medium. Status: convention. This code is widely used across card networks and processors but is not traceable to a single fetchable authoritative standard document — the current ISO 8583:2023 standard uses a different (4-digit) code scheme entirely. This entry is cross-verified against Stripe, Adyen, and/or a dated processor implementation; see sources below.

Sources

Concept + retry philosophy

Decline Codes: why they're opaque and how to retry them

Other Restricted/Blocked Card codes