Discover Payment Decline Code

Discover Decline Code 67: Hard Capture

Category Card or Account StatusRetry Guidance Conditional Decline (Editorial Classification)By Payment Defender Editorial TeamUpdated July 17, 2026Last reviewed July 17, 2026

What Discover Decline Code 67 Means

Discover decline code 67 (Hard Capture) indicates that the issuer has instructed a hard capture of the card.

Where the Response May Come From

Code 67 carries an issuer instruction to capture the card in an attended setting, tied to an account condition. Because handling depends on environment and issuer rules, the processor response and acquirer procedures are the reference.

Common Reasons for This Response

Common causes include issuer instructions to capture the card outright.

Should the Merchant Retry the Payment?

A retry generally will not clear the underlying condition; whether any future attempt succeeds depends on the cardholder resolving it with their bank, so confirm handling first.

Recommended Merchant Action

Follow your acquirer's card-handling procedure in attended settings, and otherwise ask the customer to use a different payment method.

What to Tell the Customer

Suggest the customer contact their issuing bank about their card and offer an alternate way to complete the purchase.

How to Reduce Similar Payment Failures

Recognizing capture instructions like code 67 helps you route customers to alternate methods rather than reattempting a flagged card.

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.