Why Your Payments Keep Getting Declined (And How to Fix It)

Payment declines cost you revenue and frustrate your customers. Most of them are preventable. Here is what causes them and what you can do about it.

Why do payments get declined?

Every online payment passes through multiple systems. Your payment gateway sends the transaction to the card network (Visa, Mastercard), which forwards it to the customer's issuing bank. Any of these systems can decline the transaction.

The frustrating part is that many declines are not caused by actual problems with the customer's card or account. Industry research suggests that up to 40% of declines are "false declines," where a legitimate transaction is rejected by overly cautious fraud filters or temporary processor issues.

Understanding the different types of declines is the first step to fixing them.

What are the most common decline reasons?

Insufficient funds

The simplest and most common reason. The customer does not have enough money in their account to cover the transaction. This is a hard decline and there is nothing you can do on your end except prompt the customer to use a different payment method.

Fraud flags

Issuing banks and payment processors run fraud detection on every transaction. If something looks unusual, the transaction is declined. Common triggers include purchases from a new device, transactions from a different country, unusually large amounts, or a sudden spike in transaction frequency.

The problem is that these systems are often too aggressive. A customer buying from a new phone or while travelling abroad can trigger a false decline. You lose the sale even though the customer is legitimate.

Expired or invalid cards

Cards expire. Customers forget to update them. If you store cards for recurring payments or subscriptions, expired cards will generate a steady stream of declines. Card numbers can also be entered incorrectly at checkout.

Processor errors

Sometimes the decline is not about the card at all. Payment gateways and processors experience technical issues, timeouts, and outages. During these periods, valid transactions are declined because the system cannot process them. The customer's card is fine. Your gateway simply could not reach the network.

Velocity limits

Banks and processors set limits on how many transactions a card can make in a given time period. If a customer tries multiple purchases in quick succession, or if your retry logic sends the same transaction too many times, velocity limits will trigger declines.

What is the difference between soft declines and hard declines?

Soft declines

Soft declines are temporary failures. They include processor timeouts, temporary hold on the account, and "do not honour" responses that are not related to fraud or insufficient funds. Soft declines can often succeed on a second attempt, either immediately or after a short delay.

Common soft decline codes include "issuer unavailable," "system error," and "try again later." These indicate that the infrastructure failed, not the card.

Hard declines

Hard declines are definitive rejections. The card is expired, cancelled, reported stolen, or the account has insufficient funds. Retrying a hard decline will not change the outcome and may actually trigger velocity limits or fraud flags on your merchant account.

Your payment system should distinguish between these two types and only retry soft declines. Retrying hard declines wastes processing resources and can damage your merchant reputation with the card networks.

Why does your payment gateway matter?

This surprises many businesses, but it is well documented. Two gateways can process the same card, same amount, same customer, and get different results. One approves it. The other declines it.

This happens because gateways have different acquiring bank relationships, different fraud scoring models, and different levels of integration with card networks. A gateway with strong Visa relationships might have higher approval rates for Visa cards but lower rates for Mastercard.

Geography matters too. A gateway with strong Australian acquiring relationships will typically perform better for domestic transactions than an international gateway routing through overseas acquirers.

How does retry logic work?

Basic retry logic waits a short period and tries the same gateway again. This works for processor timeouts and temporary errors. If the gateway was briefly unavailable, the retry succeeds.

Smarter retry logic sends the transaction to a different gateway entirely. If Gateway A declined because of its fraud model, Gateway B might approve it because it scores the transaction differently. This cross-gateway retry is called failover.

The key rule with retries: only retry soft declines. Never retry hard declines. And limit your retry attempts. Most payment networks allow two to three attempts before flagging your merchant account for excessive retries.

How does using multiple processors improve approval rates?

When you use a single gateway, you accept that gateway's approval rate as your ceiling. If it approves 92% of transactions, you lose 8%. Some of those 8% are legitimate customers with valid cards who would have been approved by a different processor.

By connecting to multiple gateways, you can route transactions based on card brand, currency, amount, or region. Visa transactions might go to one gateway with strong Visa acquiring. Mastercard transactions go to another. International cards go to a gateway with better cross-border approval rates.

When a gateway declines a soft decline, you retry with a different gateway automatically. The customer never knows a retry happened. They just see their payment succeed.

This approach, called payment orchestration, is how large businesses recover 2-5% of revenue that would otherwise be lost to unnecessary declines. Platforms like Zenvo make this accessible without needing to build the routing and failover logic yourself.

What practical steps can you take to reduce declines?

Send complete transaction data

Issuing banks use transaction data to make approval decisions. The more data you send, the better. Include the customer's billing address, email, phone number, and IP address. Transactions with complete data are approved more often than those with only card details.

Use address verification (AVS) and 3D Secure

AVS checks the billing address against the issuing bank's records. 3D Secure (the "Verified by Visa" or "Mastercard SecureCode" step) shifts fraud liability to the issuing bank and generally improves approval rates. Both reduce the chance of fraud-related declines.

Update stored cards proactively

If you run subscriptions or recurring billing, use account updater services. These automatically refresh expired card details before they cause a decline. Most major gateways offer this feature.

Optimise your retry strategy

Retry soft declines with a short delay. Do not retry hard declines. Limit retries to two or three attempts. If you can, retry with a different gateway rather than the same one.

Route across multiple gateways

This is the highest-impact change. Connect to two or more gateways and route transactions based on which provider is most likely to approve them. Use smart routing to match each transaction to the best provider, and failover to handle declines automatically.

You can build this yourself, but it is a significant engineering investment. Payment orchestration platforms handle the routing, failover, and gateway normalisation for you.