Discover Payment Decline Code

Discover Decline Code 76: Invalid or Nonexistent To Account

Category Invalid Payment DataRetry Guidance Conditional Decline (Editorial Classification)By Payment Defender Editorial TeamUpdated July 17, 2026Last reviewed July 17, 2026

What Discover Decline Code 76 Means

Discover decline code 76 (Invalid or Nonexistent To Account) indicates that the destination ('to') account is invalid or does not exist.

Where the Response May Come From

Code 76 means the destination ('to') account specified for the transaction is invalid or does not exist, common in transfers. It concerns account data in the request, so the processor response is the reference.

Common Reasons for This Response

Common causes include an invalid or nonexistent destination account in the request.

Should the Merchant Retry the Payment?

A retry succeeds only with a valid destination account; resubmitting the same invalid 'to' account returns code 76 again.

Recommended Merchant Action

Verify the destination account details, correct them, or ask the customer to confirm the receiving account before reattempting.

What to Tell the Customer

Ask the customer to check the destination account details and try again, or use a different account.

How to Reduce Similar Payment Failures

Validating destination-account entry in transfer flows helps prevent code 76 from invalid or mistyped 'to' accounts.

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.