Discover Payment Decline Code

Discover Decline Code 58: Transaction Not Permitted to Acquirer or Terminal

Category Transaction RestrictionsRetry Guidance Hard Decline (Editorial Classification)By Payment Defender Editorial TeamUpdated July 17, 2026Last reviewed July 17, 2026

What Discover Decline Code 58 Means

Discover decline code 58 (Transaction Not Permitted to Acquirer or Terminal) indicates that the transaction type is not permitted for this acquirer or terminal.

Where the Response May Come From

Code 58 means the transaction type is not permitted for the acquirer or the specific terminal configuration. Unlike an account restriction, it points to the acceptance setup, so your acquirer's boarding records are the reference.

Common Reasons for This Response

Common causes include terminal or acquirer configuration that does not permit this transaction type.

Should the Merchant Retry the Payment?

Reattempting on the same terminal returns code 58 again until the acquirer enables the transaction type; the customer's card is not the cause.

Recommended Merchant Action

Check with your acquirer whether the terminal or MID is configured for this transaction type and correct the setup rather than retrying the card.

What to Tell the Customer

Let the customer know the payment could not be completed for a terminal configuration reason and offer another way to pay if available.

How to Reduce Similar Payment Failures

Tracking code 58 by terminal or MID helps surface acceptance settings that block valid transaction types before they cost approvals.

Important Limitations

Decline-code meanings vary by processor, gateway, and payment environment, and issuers do not always disclose the specific reason behind a response. The retry classification on this page is Payment Defender editorial guidance, not an official network rule. Merchants should confirm handling with their processor or gateway.

Related Decline Codes

Sources and Review Information

Last reviewed July 17, 2026

Raw network-response codes are supplemental to the complete processor or gateway response. Meanings and recommended actions can vary by issuer, processor, gateway, card network, payment method, region, and merchant configuration.

Turn the Code Into Action

Know What to Do Next

Payment Defender helps merchants connect reason codes to transaction history, dispute alerts, refunds, evidence, fraud activity, VAMP exposure, and payment-performance decisions.