SEC Violation on Credit Card Machine: What Decline Code 63 Means and How to Fix It

An SEC violation on a credit card machine is decline code 63, a security violation. It means a security check blocked the transaction, and the terminal won't tell you which one.

Here is what the code means, which causes sit on the card side and which sit on yours, and how to clear each one.

What an SEC Violation on a Credit Card Machine Means

Code 63 tells you that a security check refused the payment. The card was not declined for insufficient funds, and the account behind it is not necessarily frozen. A rule somewhere between your terminal and the issuing bank stopped this one transaction.

One point of confusion worth settling first: on a card machine, SEC stands for security. It has nothing to do with the Securities and Exchange Commission. If your terminal shows this message, you are dealing with a payments error, not a regulator.

What Causes Decline Code 63

The causes fall into two groups, and knowing which group you are in determines the fix.

Card-Side Causes

A common trigger is a CVV or CVC mismatch — the security code on the back of the card was entered incorrectly or misread. Any card data that does not match the issuer's records can return the same code. And the issuing bank's own fraud or security system can flag a specific transaction even when every digit is correct.

Merchant-Side Causes

An invalid merchant ID (MID) or terminal ID can also return code 63. This is a configuration problem, not a card problem, and it often surfaces after a change in processing setup — the terminal is still carrying credentials that no longer match the account behind it.

How to Fix an SEC Violation at the Terminal

Work through these steps in order:

• Run the card again. If it was dipped or tapped, have the customer insert it instead, since chip reads are the most reliable. If the card was keyed in, re-enter the card number, expiration date and CVV carefully. A single mistyped digit can trigger this decline.
• Stop after one retry. If the first attempt was a misread, a clean second attempt often goes through. If it doesn't, move to the next step.
• Have the cardholder call their issuing bank. If the decline persists on one card, the issuer's security system is blocking it. The number is on the back of the card, and only the issuer can clear the flag.
• Accept another payment method in the meantime. Do not keep retrying the same card. Repeated attempts will not override a security block.

When the Problem Is Your Account, Not the Card

Here is the test. If one card declines with code 63, suspect the card. If every card declines with code 63, suspect your terminal configuration.

A terminal that declines everything with a security violation is usually carrying an invalid MID or terminal ID. Contact your processor, give them the terminal ID and the exact decline code, and ask for a corrected configuration on a specific timeline — within one or two business days, not an open-ended promise.

If you recently switched processors and your terminal was never reprogrammed for the new account, this is almost certainly where the problem lives.

How to Prevent Code 63 Declines

• Require the CVV on card-not-present transactions. It is the single check most often behind this code.
• Confirm terminal and gateway configuration after any account change. New MID, new terminal ID, new credentials — verify all of them before you take your first payment.
• Watch decline patterns, not single declines. One code 63 is a bad keystroke. A cluster of them is a signal worth a call to your processor.

Repeated Security Declines and High-Risk Processing

If banks treat your industry as high-risk, security declines are rarely an isolated annoyance. They sit alongside tighter fraud controls and chargeback exposure, and they deserve a processor that reads the whole picture rather than answering each error on its own. Decline monitoring and chargeback management work best together, because the same transaction patterns drive both.

High-risk processing is all we do. If you need a high-risk merchant account with terminals configured correctly from the start, we can tell you where you stand before you commit. Every fee is disclosed in your merchant service agreement before you sign, so there are no surprises after approval. Apply today and we will take it from there.