Payment Failure
What Is a Payment Failure? Definition and How It Works
Definition
A payment failure is any transaction that does not successfully complete due to a decline, technical error, or processing issue at any point in the payment flow: at authorisation (issuer decline), at capture (gateway or processor error), or at settlement (clearing or settlement failure). Payment failures represent lost revenue for merchants and friction for customers, and their root causes determine the appropriate recovery strategy.
How it works
Payment failures occur at several stages and for distinct reasons.
Authorisation failures are the most common category. They include: hard declines (the issuer permanently rejects the transaction due to a closed account, stolen card, or other definitive reason that precludes retry); soft declines (the issuer temporarily rejects due to insufficient funds, exceeded credit limit, or a general do-not-honour response that may succeed on retry or with a different transaction structure); and fraud declines (the issuer or acquirer fraud system rejects due to a risk score exceeding the threshold, including false declines of legitimate transactions).
Technical failures include: gateway timeouts (the payment system did not receive a response within the required window and treated the transaction as failed); processor outages (the acquirer, card network, or issuer experienced a system interruption preventing authorisation); and connectivity failures (network issues between the merchant's system and the payment gateway).
Settlement failures occur after authorisation when a captured transaction fails to settle: typically due to missing required fields in the clearing message, settlement file formatting errors, or acquirer-specific clearing issues. Settlement failures are rarer than authorisation failures but can be harder to diagnose because they occur outside the real-time payment flow.
Recovery strategies vary by failure type. Hard declines should not be retried. Soft declines should be retried at optimal intervals (immediately after payday dates, after the card limit resets at month-end). Technical failures should be retried immediately or after a short delay. Fraud false declines may benefit from retry with additional authentication data or through a different acquirer.
Why it matters
Payment failure rates directly affect merchant revenue. An e-commerce merchant with a 5% payment failure rate and $10M in attempted monthly revenue is losing $500,000 per month in transactions that could potentially be recovered. Failure rates vary significantly by payment method, geography, card type, and merchant category; identifying the specific failure patterns affecting a merchant's transaction mix is the first step to meaningful recovery.
Customer experience consequences of payment failures extend beyond the declined transaction. A customer whose payment fails at checkout may not retry, may abandon to a competitor, or may lose trust in the merchant's payment infrastructure. For subscription businesses, a failed renewal payment that is not promptly recovered leads to service interruption and potential cancellation that damages the customer relationship disproportionately to the individual transaction value.
Systematic payment failure analysis enables prioritised improvement. Failure reasons (hard decline, soft decline, fraud, technical) indicate the appropriate response: changing acquirer routing, adjusting fraud model thresholds, implementing Account Updater for recurring billing, or fixing a specific data quality issue causing settlement failures. Payment failure analysis is therefore a standard payment optimisation discipline for merchants above a certain transaction volume.
With PXP
PXP recovers failed payments through decline analysis, smart routing, and retries across alternate acquirer paths. Talk to our team about how PXP can support your payment recovery.
Frequently asked questions
What is the difference between a hard decline and a soft decline?
A hard decline is a definitive rejection that should not be retried: the card is stolen, closed, or invalid; the transaction violates scheme rules; or the issuer has permanently blocked the card for the merchant. Retrying a hard-declined transaction will result in the same outcome and may damage the merchant's standing with the issuer. A soft decline is a temporary rejection that may succeed on retry: insufficient funds that may clear after payday, a credit limit that resets monthly, or a general risk policy decline that a different transaction structure or authentication approach may overcome.
How do gateway timeouts cause payment failures?
A gateway timeout occurs when the payment system sends an authorisation request and does not receive a response within the required time window (typically 30 to 60 seconds). The gateway cannot know whether the issuer received and processed the request or not. To avoid double-charging, the gateway treats the transaction as failed and notifies the customer. If the issuer did process an authorisation that the merchant then cancels, a duplicate charge risk exists. Proper timeout handling with idempotency keys (unique identifiers preventing duplicate processing) is essential infrastructure for reliable payment systems.
How can merchants reduce involuntary recurring payment failures?
The primary causes of recurring payment failures are stale card credentials (expired or replaced cards) and insufficient funds. Account Updater addresses stale credentials by refreshing stored card details before billing. Smart retry timing addresses insufficient funds: retrying after payday dates or at month-end when credit limits reset improves recovery rates significantly. Network tokenisation further reduces credential-related failures by automatically maintaining token validity when the underlying card changes.
Revolutionize your business with PXP
Take complete control of your commerce and payments with one platform.
Get Started