Discover Payment Decline Code

Discover Decline Code 92: Unable to Route Transaction

Category Issuer or Network AvailabilityRetry Guidance Conditional Decline (Editorial Classification)By Payment Defender Editorial TeamUpdated July 17, 2026Last reviewed July 17, 2026

What Discover Decline Code 92 Means

Discover decline code 92 (Unable to Route Transaction) indicates that the transaction could not be routed to the issuer.

Where the Response May Come From

Code 92 means the transaction could not be routed to the appropriate issuer, often due to a routing or identification problem. It reflects a routing condition, so the processor response is the reference.

Common Reasons for This Response

Common causes include routing failures that prevent the request from reaching the issuer.

Should the Merchant Retry the Payment?

Whether a retry helps depends on if the routing failure is a brief glitch or a persistent BIN or configuration problem; check with your processor before reattempting.

Recommended Merchant Action

Check routing and BIN configuration with your processor, and if the issuer cannot be reached, ask the customer to use a different card.

What to Tell the Customer

Let the customer know the payment did not reach their bank and ask them to try again in a few minutes or use another card.

How to Reduce Similar Payment Failures

Tracking code 92 by BIN helps surface routing gaps so you can correct configuration or guide customers to alternatives.

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.