What would you do to grow your revenue by even just 1%? Would you spend extra money on marketing? Sales?
What if we told you that you can add 5-10% to your revenue without spending an additional dime on your existing operation?
Every year, businesses worldwide lose $800 billion to declined card payments. In this article, we will show you how to recover that revenue and never suffer from incorrectly declined transactions again. It’s going to be like picking up money from the floor!
Let’s dive into the world of declined payments to understand what they are, why they happen, and how you can rescue them.
To learn how to fix the problem, we need to first understand it. Hence, this is a quick yet insightful run-down of everything you must know about declined card payments.
Hard declines are payments declined by the card’s issuer. The most common hard declines are card lost or stolen errors, and invalid card.
Soft declines happen for various reasons, from technical problems to acquirer/gateway rejection due to fraud suspicion. Soft declines are often dependent on the payment method used for processing and might not be final.
With the right technology, most soft declines can be retried seamlessly within the payment session because they don’t require customers to re-enter their details. Saving soft declines in real-time will rescue both revenue and customers, as they’ll never see the initial rejection.
After a transaction is declined, the acquirer/gateway notifies you of the reason why the rejection happened: these are the declined card codes. These codes can be quite cryptic and, to add to the problem, Profitwell discovered that about 25% of the declined card codes issued are incorrect. Some processors don’t have the latest technologies and giving too much information about declines might aid fraudsters; these two facts combined make decline codes hard to decipher. Nonetheless, these error messages are a place to start when we want to understand how to minimize payment rejection.
Every payment gateway has different codes and error messages, but they often look quite similar, so we put together a list for you with an explanation of what each error means. If you don’t find your specific error message, look for a similar one.
Below you’ll find a breakdown of the most common declined card codes:
|Invalid credit card number||The card number is incorrect|
|Invalid address||The address entered does not match the one in the issuer’s database|
|Do not honor||The issuer fraud filter has been triggered|
|Suspected fraud||A fraud filter has been triggered|
|Transaction declined (suspecting manipulation)||A fraud filter has been triggered|
|Processor declined||The acquirer/gateway has declined the payment|
|Transaction not allowed||The acquirer/gateway has declined the payment|
|Declined by payment system||The acquirer/gateway has declined the payment|
|Expired card||The expiration date on the card has passed|
|Card reported lost/stolen||The card was flagged as stolen or lost|
|Insufficient funds||The cardholder doesn’t have sufficient funds in their account|
|Risk management transaction timeout||The provider’s risk management system did not respond on time to the request|
|Session expired||The user took too long to complete the payment|
|Invalid payment data. You are not configured for this currency or sub type (country or brand).||The acquirer/gateway does not support the currency, country, or brand of the card|
|Invalid Order Currency||The acquirer/gateway does not support the currency of the transaction|
|Transaction declined by authorization system||General decline message|
|Transaction declined (limit exceeded)||The user tried to pay more times that they are allowed|
We know that these look like a lot (and there are more!), but technology can come to our aid and prevent some of these errors from occurring in the first place. For example, we fix these errors by default for our clients:
A special mention must go to the “Do not honor” error message, which is by far the most generic and confusing one. In order to rescue genuine transactions flagged with this error (and all other rejected transactions that haven’t reached the issuer), you need an automatic transaction retry technology that submits a declined payment to fallback providers in real-time. You can read more about this further down.
You might think that a few lost transactions are no big deal: you’ve lost a couple of bucks (maybe a couple of hundred), so what? There are plenty of fish in the sea, as they say. Well, the repercussions of every sale lost to a declined card transaction go way deeper than the immediate loss, and will make you want to fix the problem and reduce declines as much and as quickly as possible. There are 5 levels of damage that your business sustains with every declined card payment:
Now that we are all on the same page about credit card declined meaning and repercussions, we can dive into the available solutions. There is a lot a merchant can do, and we are positive that some or all of the tips that follow can help you.
You can recover revenue by retrying soft declines, it’s that simple and it’s like picking up money from the floor. There are technologies available that submit a transaction declined by an acquirer/gateway to a series of fallback providers until the payment is approved.
In order to use these technologies, you must use multiple payment providers in your payment stack. You might ask, “Why should I use multiple payment providers, while my processor already offers transaction retries?”. While this is true for many providers, there are some issues with same-provider retries, let’s see what they are.
A lot of payment gateways have retries turned on by default, but these present several problems:
The most advanced payment operations platforms allow you to set fallback scenarios in which backup processors try to approve a transaction after it has been declined. This is how it works: when the transaction is declined by the first provider in the flow, the platform seamlessly retries it with the second provider and so on until it’s approved or all the processors have declined it. There are three main advantages to this ground-breaking technology:
Some may call it pre-dunning, but it all boils down to knowing your payment providers, and optimizing them in order to minimize declines at the checkout level.
As much as being proactive will limit declined transactions, some will always slip through the cracks, this is why improving your payment experience (PX if you like) is a great way to retain customers even if their payment failed.
Every user loves a personalized experience, especially when it comes to payments. The ideal flow encompasses:
From a technical point of view, all these things are very challenging to achieve, especially for SMEs (but enterprises could often use a hand too).
This is where a payment operations platform steps in. With a single software you can:
These are all things that minimize the risk of mistakes and declines because you allow your cross-border users to pay like locals.
Modern, international businesses are increasingly facing the need to offer multiple payment gateways. One of the main reasons is that, as Profitwell discovered, “if your processor is in the United States, but you have a customer you’re trying to charge in Finland, there’s a 250% increase in the probability of that charge getting falsely flagged as fraud”, and the same goes for any business, anywhere in the world, trying to process cross-border transactions. The simple truth is that when accepting international payments decline rates and false positives go through the roof.
A proactive solution to card declining caused by cross-border payments is to offer local payment methods (ewallets, ebanking, local vouchers, mobile payments, BNPL, and even crypto as it becomes more popular), and Profitwell rightly points out that local payment methods have lower decline rates and suggests that “you should have a business entity with a processor in each of the main regions you serve.” Unfortunately, this may be challenging and expensive for big enterprises and right-out impossible for SMEs and startups. A payment operations platform allows easy, codeless connection to many processors from one platform, allowing you to benefit from fewer credit card declines while saving you the humongous costs of integrating with multiple providers.
One last thing to mention when talking about payment provider optimization, is fraud filters. According to Chargebee “part of battling card declines is fine-tuning the fraud filters in your control so they don’t (for the most part) get in the way of good orders.” This is especially true considering that Ethoca found out that 52% of orders perceived as fraudulent are actually good. Moreover, this study estimated that only 1 transaction in 5 reported is actually fraudulent.
Every transaction goes through several fraud filters, and there are two categories of fraud prevention: known and unknown. These are the main types of fraud prevention systems you’ll come across:
Unfortunately, these tools don’t always collaborate, follow different rules, and might overlap. This means that they might catch good transactions and flag them as fraudulent; the infamous false positives.
Let’s see in detail each of the above-mentioned fraud prevention mechanisms, and how they influence declined card payments.
3D-Secure is a security layer that requires the cardholder to go through an additional step in order to verify their identity before a payment. Unfortunately, if a transaction is declined because the 3DS/3DS2 step was not completed successfully, there is not much you can do as a merchant.
These are fraud prevention mechanisms put in place by your processor, some of them are put on you as a merchant. The good news is that the vast majority of the declines generated by these filters can be retried and approved with fallback processors!
These are rules that you put in place in your processor’s back-office or in your payment operations platform. For example, you may decide to block a specific card bin or a card brand. By analyzing your payment data carefully, you can tune these restrictions until you are declining only fraudulent transactions.
Software like Riskified or Forter are meant to prevent and block fraudulent activities on your website, including malicious transactions. Just like your own fraud filters, you have control over these tools and you can fine-tune them based on data-driven insights.
Thanks for sticking with us all the way to the end! Declined credit card payments are no joke, and handling them (or not) can get expensive both in terms of money and resources.
Luckily, we at BridgerPay have listened to thousands of businesses and we created a technology that not only takes care of the actual problem of declined card payments but gives you all the tools and support to prevent them, unlocking new revenue in the process!
Moreover, with our self-onboarding flow, you can start reaping the benefit of an end-to-end payment operations platform immediately, and for free! Give it a try.
This is what Yehoshua Fried, CTO and Co-founder at Calypsa by ModLi, had to say about BridgerPay: