Discover Payment Decline Code

Discover Decline Code 68: Response Received Too Late

Category Technical or Processing ErrorRetry Guidance Soft Decline (Editorial Classification)By Payment Defender Editorial TeamUpdated July 17, 2026Last reviewed July 17, 2026

What Discover Decline Code 68 Means

Discover decline code 68 (Response Received Too Late) indicates that the response was received too late to complete the transaction.

Where the Response May Come From

Code 68 means the authorization response arrived after the network's timing window, so the transaction was not completed cleanly. It reflects a timing or connectivity condition, making the processor response the reference.

Common Reasons for This Response

Common causes include timeouts or delays that caused the response to arrive after the processing window.

Should the Merchant Retry the Payment?

A single retry often succeeds once timing normalizes; persistent code 68 points to latency or connectivity issues worth investigating with your processor.

Recommended Merchant Action

Retry once after a brief pause, and if code 68 recurs, review network latency and timeout settings with your processor or gateway.

What to Tell the Customer

Let the customer know a temporary timing issue occurred and ask them to try the payment again.

How to Reduce Similar Payment Failures

Monitoring code 68 rates helps detect latency and timeout problems in your processing path before they suppress 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.