Discover Payment Decline Code
Discover Decline Code 60: Card Acceptor Contact Acquirer
Category Merchant or ConfigurationRetry Guidance Conditional Decline (Editorial Classification)By Payment Defender Editorial TeamUpdated July 17, 2026Last reviewed July 17, 2026
What Discover Decline Code 60 Means
Discover decline code 60 (Card Acceptor Contact Acquirer) indicates that the card acceptor is instructed to contact the acquirer.
Where the Response May Come From
Code 60 instructs the merchant (card acceptor) to contact the acquirer, indicating an acceptance-side condition that needs attention. It points to the merchant-acquirer relationship, so the acquirer is the reference for resolution.
Common Reasons for This Response
Common causes include acquirer-side conditions requiring merchant follow-up.
Should the Merchant Retry the Payment?
A retry may or may not help until the acquirer condition is understood; reattempting blindly is discouraged, so confirm the situation with your acquirer first.
Recommended Merchant Action
Contact your acquirer to determine what prompted code 60 before reprocessing, and offer the customer an alternate method if resolution takes time.
What to Tell the Customer
Let the customer know the payment could not be completed and offer another way to pay while the issue is reviewed.
How to Reduce Similar Payment Failures
Logging code 60 occurrences and following up with your acquirer helps resolve recurring acceptance-side conditions that quietly block transactions.
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.