Code 58: Transaction Not Permitted to Terminal

Decline Code 58: What 'Transaction Not Permitted to Terminal' Means

Decline code 58 means the merchant's terminal or merchant account is not configured to accept this type of transaction. Unlike most decline codes that originate with the cardholder's bank, code 58 is a merchant-side configuration issue. The card may be perfectly valid. The customer's account may have plenty of available funds. The problem is on your end, not theirs.

What Does Decline Code 58 Mean?

Merchant accounts and terminals aren't configured to accept every possible transaction type by default. Cash advances, certain card networks, manual key-entry transactions, and specific payment methods all require explicit enablement. When a transaction type is attempted that the terminal or merchant account hasn't been set up to handle, the network returns code 58.

The card being presented isn't the problem. The cardholder didn't do anything wrong. The terminal received a request it isn't authorized to fulfill, and code 58 is the network's way of communicating that.

Code 58 vs. Code 57: Key Difference

These two codes look similar and are easy to confuse, but they point to different sides of the transaction.

Code 57 means the cardholder's card or account doesn't permit this transaction type. The restriction is set by the cardholder's issuing bank at the account level. The fix requires the cardholder to contact their bank.

Code 58 means the merchant's terminal or account doesn't permit this transaction type. The restriction is a configuration issue on the merchant's end. The fix requires the merchant to contact their processor.

Same outcome at the terminal, completely different problem and completely different resolution path. Sending a customer to call their bank when the actual issue is your terminal configuration wastes their time and doesn't fix anything.

Common Causes of Decline Code 58

• Merchant account not configured for the card network being used. Accepting Amex, Discover, or certain international networks requires separate enrollment. Attempting to process a card from a network you're not enrolled in returns a 58.
• Cash advance or quasi-cash transactions not enabled. These transaction types require explicit configuration on the merchant account and are not enabled by default.
• Manual key-entry transactions disabled on the terminal. Some terminals are configured to accept chip or swipe only. Attempting to manually key in a card number on a terminal where that's disabled will return a 58.
• Incorrect MCC or SIC code assigned to the merchant account. If the merchant category code on file doesn't align with the transaction type being processed, certain transaction types may be blocked at the network level.
• Terminal software not updated. Outdated terminal software may not support newer transaction types or updated network requirements, producing a 58 on transactions that should otherwise be permitted.
• Specific transaction type not enabled on the account. Recurring billing, installment payments, and certain card-not-present transaction types may require separate configuration.

How to Fix Decline Code 58

1. Identify which transaction type triggered the code 58. Was it a specific card network, a manual entry attempt, a cash advance? The transaction type tells you what needs to be enabled.
2. Contact your payment processor to enable the required transaction type. Most configuration changes are handled by your processor rather than at the terminal level. A call to your processor's support line with the transaction type and terminal details is the starting point.
3. Update your terminal software if it's outdated. If the issue is tied to a terminal software version, your processor can walk you through the update process or push an update remotely depending on your terminal model.
4. Verify your merchant account supports the card network being used. If you're not enrolled to accept a specific network and customers regularly present those cards, enrollment is worth pursuing rather than repeatedly asking customers for a different card.
5. Ask the customer for an alternate card while the configuration is being resolved. Code 58 affects the transaction type or card network, not necessarily all cards. A card on a supported network will typically process without issue while the configuration issue is addressed.

Frequently Asked Questions About Decline Code 58

Is decline code 58 the customer's fault or the merchant's fault? It's the merchant's. Code 58 means the terminal or merchant account isn't configured to handle the transaction that was attempted. The cardholder's card and account are not the problem. Treating it as a customer-side issue, asking them to call their bank or try a different card without first checking your own configuration, is the wrong response and won't resolve the underlying issue.

How do I enable a transaction type that's triggering code 58? Contact your payment processor directly. Configuration changes to merchant accounts, enabling new card networks, turning on manual key-entry, or adding support for new transaction types are handled at the processor level. Have the specific transaction type and your merchant account details ready when you call. Most processors can make standard configuration changes quickly, though some may require additional documentation depending on what's being enabled.

How is code 58 different from code 57? Code 57 is a cardholder restriction: the issuing bank has blocked this transaction type for this specific card or account. The fix is the cardholder calling their bank. Code 58 is a merchant restriction: the terminal or merchant account isn't configured to process this transaction type. The fix is the merchant contacting their processor. One is a bank-side configuration, the other is a merchant-side configuration. The codes look identical at the terminal, which is why knowing the distinction matters.

Will all customers' cards decline if I have a code 58 issue? Not necessarily. A code 58 is specific to the transaction type or card network involved. If the issue is that your merchant account isn't enrolled to accept Amex, only Amex cards will return a 58. Visa and Mastercard transactions will process normally. If the issue is that manual key-entry is disabled, only manually keyed transactions will fail while chip and swipe transactions continue to work. The scope of the impact depends on what's misconfigured.

Related Decline Codes

Code 58 sits in the merchant configuration category. These related codes cover adjacent terminal and account-level issues:

• Code 57 — Transaction Not Permitted to Cardholder. The cardholder-side version of a permissions error. Looks identical at the terminal but requires a completely different fix.
• Code 12 — Invalid Transaction. A transaction validity error that can also stem from merchant account configuration issues.
• Code 62 — Restricted Card. Card-level restrictions on an otherwise valid card, a cardholder-side issue.
• Code 05 — Do Not Honor. The bank's catch-all decline. Originates with the issuing bank rather than terminal configuration.
• Code 06 — General Error. A broader processing error that can sometimes overlap with configuration issues.
• Code 30 — Format Error. A data formatting error in the transaction request, a different kind of technical issue from a configuration restriction.
• Code 51 — Insufficient Funds. A balance issue on a valid, permitted transaction.
• Code 01 — Refer to Issuer. The bank wants cardholder verification before approving, unrelated to terminal configuration.