Credit Card Payment Failures

Most credit card payments process quickly and without issue. However when banks do decline a charge the reason given is often opaque and hard to understand. Here's a quick guide to the most common failure reasons, what they mean, and how to resolve them.

How Credit Card Failures Work

When a client submits a credit card payment, the request goes to their bank for authorization in real time. If the bank approves it, the payment goes through immediately. If the bank declines it, the payment fails on the spot and the client sees an error message. Unlike ACH payments, there's no waiting period — you know the outcome right away.

Most failures are caused by something on the client's bank side, not a Check Cherry issue. The decline codes banks return are often vague by design — banks intentionally keep the reasons generic to avoid giving fraudsters a roadmap.

Banks frequently decline legitimate charges — especially for online purchases, larger amounts, or first-time merchants. It's annoying, but it's a normal part of how card fraud prevention works. Most clients just need to call their bank or try a different card.

Common Decline Reasons

Insufficient Funds

The card doesn't have enough available balance or credit to cover the charge. The client should try a different card or contact their bank. If it's a debit card, they may need to wait until funds are available.

Generic Decline

The bank declined the charge but didn't tell us the specific reason — this is actually the most common type of decline. It often means the bank's automated fraud system flagged something about the transaction (an unusual amount, an unfamiliar merchant, a recent string of purchases), but it can also indicate an account issue the bank hasn't disclosed. The fastest fix is for the client to call the number on the back of their card and ask them to approve the charge, then retry. Once the bank clears it on their end, the payment usually goes through without issue. A different card will also work in the meantime.

Do Not Honor

One of the most common decline messages, and one of the vaguest. The bank is refusing the charge without giving a reason. It typically means their fraud filters blocked the transaction — this is especially common with online purchases, larger amounts, or charges from a merchant the client hasn't used before. It can also point to an issue with the account standing. Retrying the same card usually won't work until the client contacts their bank. They should call the number on the back of the card, confirm the charge is legitimate, and ask them to let it through. A different card is the quickest workaround while they sort it out.

Expired Card

The card is past its expiration date, or the expiration date entered doesn't match what the bank has on file. The client should check the date printed on their physical card and re-enter it, or switch to a current card.

Incorrect Card Details

One or more of the card details — card number, security code (CVC), ZIP code, or billing address — doesn't match what the bank has on file. The client should double-check each field and try again. A single wrong digit will cause the payment to fail.

Fraudulent

The bank flagged the charge as suspicious and declined it. This can happen with larger purchases or when the transaction looks out of pattern for that account. The client should contact their card issuer directly to clear the flag, or try a different card.

Transaction Limit / Card Velocity Exceeded

The client has hit a usage limit their bank places on the card — but not necessarily because they're out of money. Banks set velocity limits to protect against fraud, capping things like the number of transactions per day, the total spent in a 24-hour window, or how many times a card can be used at the same merchant. This often surprises clients because the card has plenty of available credit. Waiting a few hours and retrying often works. Calling the bank to lift the limit is another option. Using a different card is the quickest workaround.

Authentication Required

The bank needs to verify it's really the cardholder before approving the charge — often via a text message, app prompt, or PIN. The client should complete the verification step their bank requests, then retry the payment.

Processing Error

Something went wrong while processing the payment — this is usually a temporary issue on the network or processor side, not with the card itself. The client should wait a moment and try again. If it keeps happening, reach out to support via the chat bubble in the lower right.

Call Issuer

The bank wants to speak with the cardholder before approving the charge. The client should call the number on the back of their card, let the bank know they're trying to make a payment, and then retry once the bank has cleared it.

Card Not Supported

The card type, currency, or a restriction on the card prevents the transaction from going through. This can happen with certain prepaid cards, international cards, or card types that Check Cherry Payments doesn't accept. The client should try a different card.

What Happens Automatically

When a credit card payment fails, Check Cherry handles the bookkeeping for you:

The payment attempt is recorded on the event with the failure reason.
The event balance remains unchanged — no amount is applied against what's owed.
You receive an email notification with the decline reason, payment amount, and a link to the event.

If the failed payment was part of auto-pay (a scheduled payment plan), auto-pay is automatically disabled to prevent repeated failed charges. Both you and the client are notified through the automated 'Scheduled Payment Failed' message.

There is no automatic retry for failed card payments. A new payment must be initiated by the client. For auto-pay failures, only re-enable auto-pay after the client has resolved the issue with their bank — otherwise it will fail again on the next scheduled date.

What You Should Do

When you get a failure notification, here's the best way to handle it:

Check the failure reason. If you're using Check Cherry Payments you can see it at a glance by going to Sales → Payments. Otherwise you can check within your processor account or by asking the customer for details. This tells you whether the issue is likely a quick fix (wrong CVC, expired card) or something the client needs to resolve with their bank (generic decline, do not honor).
Point them to the right fix based on the decline reason. For bank-side declines (generic decline, do not honor, call issuer), they'll need to contact their bank first. For card detail issues, they can just re-enter the correct information. For velocity or spending limits, waiting a few hours or switching cards is usually enough.
For auto-pay failures, only re-enable auto-pay after the client has confirmed the issue is resolved. Otherwise it will fail again on the next scheduled date.
Keep the conversation matter-of-fact. Most card failures are simple and easy to resolve once the client knows what to do. Framing it as 'your bank flagged it — happens all the time, here's how to fix it' takes the awkwardness out of the conversation.

Was this article helpful?

Thanks for your feedback!

Sorry to hear that. Want to chat with our support team?

Chat with us

Last updated June 08, 2026 16:06