A customer taps “pay.” Their card is charged. Money arrives in your account. Three things that feel like one event are actually three separate steps, each handled by different parties on different timelines. Authorization takes seconds. Settlement takes days. And the gap between them is where $118.5 billion in global payment failures happen every year (Retail TouchPoints, 2024).
Understanding how authorization and settlement work, and where they break, is the difference between recovering revenue and writing it off.
Key takeaways:
- Failed payments cost merchants $118.5 billion globally per year, most of it in the gap between authorization and settlement
- 70% of declined ecommerce transactions come from legitimate customers, not fraudsters
- A 1% authorization rate improvement recovers $10 million in revenue on $1 billion in volume
- Payment orchestration improves authorization rates by 2-3% on average through dynamic routing
- 82% of merchant executives cannot identify why their payments fail
What is payment authorization?
Authorization is the first checkpoint in every card transaction. It answers one question: can this card pay for this purchase right now?
When a customer submits their payment details, the merchant’s payment processor sends an authorization request to the card network (Visa, Mastercard, Amex, Discover), which forwards it to the issuing bank. The issuer checks three things: is the card valid, is the account in good standing, and are there sufficient funds or credit available? The whole process takes 1-2 seconds.
If the answer is yes, the issuer returns an authorization code and places a hold on the cardholder’s available balance for the transaction amount. That hold reserves the funds but does not move them. The merchant gets a “yes,” the customer sees a pending charge, and the money stays in the cardholder’s account.
If the answer is no, the transaction is declined. The customer sees an error. The merchant loses the sale unless they can route the transaction to a different processor or offer an alternative payment method.
How the authorization process works
The authorization flow involves six parties in under two seconds:
- The cardholder submits payment at checkout.
- The merchant’s payment processor or gateway receives the transaction data and formats it for the card network.
- The card network (Visa, Mastercard) routes the request to the issuing bank.
- The issuing bank evaluates the card status, available funds, fraud risk, and any velocity checks. It returns an approval or decline code.
- The card network relays the response back through the processor to the merchant.
- The merchant receives the authorization code (approved) or decline code with a reason.
Authorization rates vary widely. Worldpay’s 2024 data shows global averages between 85% and 90%, meaning 10-15% of legitimate transaction attempts fail at this step. Best-in-class merchants achieve 97% or higher (Worldpay, 2024). That gap represents real money. For a business processing $1 billion annually, moving from 90% to 91% authorization rates recovers $10 million in revenue that would otherwise be lost to declines.
Key stat: 70% of declined ecommerce transactions come from legitimate customers, not fraudsters (Alexander Jarvis, citing Riskified). These false declines put $443 billion at risk globally each year (Aite-Novarica via Payrails, 2024).
And 42% of customers who experience a false decline abandon their purchase entirely (PYMNTS, 2024).
What is payment settlement?
Settlement is when money actually moves. After authorization approves a transaction, settlement transfers the funds from the cardholder’s bank to the merchant’s bank account, minus processing fees.
Where authorization is a question (“can this card pay?”), settlement is an action (“move the money”). Authorization happens in seconds. Settlement typically takes 1-3 business days for card payments, though it varies by processor, card network, and merchant category (Stripe, Gr4vy, Visa Developer docs).
A successful authorization does not guarantee settlement. The transaction must still clear the card network’s batch processing, pass any post-authorization fraud checks, and survive the settlement window without a chargeback or expired hold. The gap between “approved” and “money in your account” is where many payment problems hide.
How settlement works: clearing, batching, and fund transfer
Settlement is a three-phase process that runs largely in the background:
| Phase | What happens |
|---|---|
| Clearing | The merchant’s processor submits the captured transaction details to the card network. The network validates the transaction data, calculates interchange fees, and routes the financial obligation to the issuing bank. |
| Batching | The processor collects a day’s worth of captured transactions and submits them as a batch, typically once every 24 hours. A transaction captured at 11pm might not enter the batch until the next business day. |
| Fund transfer | The issuing bank debits the cardholder’s account and transfers funds through the card network to the acquiring bank, which deposits the money (minus interchange fees, network fees, and processor markup) into the merchant’s account. |
Clearing is the accounting step. Batching determines timing. Fund transfer is when cash moves.
Most ecommerce merchants receive net settlement, where all fees are deducted before funds land in their account. Brick-and-mortar merchants more commonly see gross settlement, where the full transaction amount arrives and fees are charged separately. The distinction affects cash flow forecasting and reconciliation.
Authorization vs capture vs settlement: the three-step flow
Most articles about payment authorization and settlement skip the middle step. Capture is what connects them.
| Step | Who acts | What it means | Timing |
|---|---|---|---|
| Authorization | The bank | “Yes, this card can pay $150. We’ll hold those funds.” | Seconds |
| Capture | The merchant | “I’m ready to collect that $150 now.” | Immediate to days later |
| Settlement | The bank | “Here’s the $150, minus fees.” | 1-3 business days |
Authorization is the promise, capture is the instruction, settlement is the action.
These three steps can happen in different patterns depending on the business model. An ecommerce store selling digital downloads might authorize and capture simultaneously at checkout because the product delivers instantly. A hotel authorizes at check-in but captures days later at checkout, after the final bill is calculated. A subscription platform authorizes a monthly charge and captures it immediately, but settlement still takes 1-3 days.
The timing between authorization and capture matters for two reasons. First, authorization holds expire. Visa requires merchants to capture within 7 days for most categories; hotels and car rental companies get up to 31 days (Visa Authorization Best Practices). If you miss the window, the hold drops and you need a new authorization, which may be declined if the cardholder’s balance has changed.
Second, card networks charge misuse fees for authorizations that are never captured or reversed. Visa reason code 12.1 (Late Presentment) applies when merchants submit settlement after the authorization window closes. These fees add up for businesses with complex fulfillment timelines.
Where payments fail between authorization and settlement
The window between authorization and settlement is where most post-transaction payment problems occur. A transaction can be authorized successfully and still never settle.
| Failure type | What happens | Who’s affected most |
|---|---|---|
| Expired authorization holds | Merchant waits too long to capture; hold expires, funds return to cardholder, re-authorization may be declined | Made-to-order goods, backordered inventory, advance-sale events |
| Batch processing errors | Formatting error, duplicate submission, or processor outage during batching causes transactions or entire batches to fail | High-volume merchants batching once daily |
| Pre-settlement chargebacks | Cardholder disputes with issuer before settlement completes; issuer reverses the authorization | All merchants, especially those with delayed fulfillment |
| Processor outages | Primary processor goes down before settlement; transaction is stuck with no backup routing path | Single-processor merchants |
Merchants may not discover batch or settlement failures until reconciliation, days after the original transaction.
Expired authorization holds are the most common issue. If a merchant waits too long to capture, the hold expires and the funds return to the cardholder’s available balance. The merchant must re-authorize, and the second attempt may be declined. This is especially common for businesses with long fulfillment cycles, such as made-to-order goods, backordered inventory, or event tickets sold weeks in advance.
Batch processing errors can prevent settled transactions from completing. A formatting error, a duplicate submission, or a processor outage during batch processing can cause individual transactions or entire batches to fail. The merchant may not discover the failure until reconciliation, days later.
Chargebacks filed between authorization and settlement can intercept the funds. If a cardholder disputes a transaction with their issuer before settlement completes, the issuer can reverse the authorization. The merchant loses the sale and faces a chargeback fee.
Processor outages during the settlement window create a different kind of problem. The transaction was authorized on Processor A, but if Processor A goes down before settlement, the transaction is stuck. Without a backup routing path that can handle in-flight transactions, the merchant waits for the processor to recover or manually reprocesses.
Key stat: 82% of merchant executives cannot identify why their payments fail, because transaction data is fragmented across multiple processors and systems (PYMNTS, 2024). The authorization-to-settlement gap is where that visibility matters most.
What authorization and settlement mean for your revenue
Authorization and settlement aren’t just technical processes. They directly determine how much of your gross transaction volume converts to cash in your bank account.
| Revenue impact area | Example scale ($500M annual volume) | Root cause |
|---|---|---|
| Failed authorizations | ~$39.5M lost (7.9% avg decline rate) | False declines, issuer risk models, network errors |
| Settlement float | $30M perpetually in transit (3-day lag) | Batch timing, processor settlement schedules |
| Reconciliation errors | Hours of weekly finance team effort | Different formats, schedules, and fee structures per processor |
| Involuntary subscription churn | $129B industry-wide by 2025 | Failed recurring authorization, no retry logic |
Sources: Alexander Jarvis, citing Riskified (decline rates); PYMNTS, 2024 (subscription churn projection).
Failed authorizations are immediate lost sales. With ecommerce authorization decline rates averaging 7.9% globally (Alexander Jarvis, citing Riskified), a business processing $500 million in annual transaction attempts is losing roughly $39.5 million at the authorization step alone. Failed payments account for 15% of lost ecommerce sales, according to Adyen’s 2024 Retail Report.
Settlement timing affects cash flow. A three-day settlement delay on a $10 million daily transaction volume means $30 million is perpetually in transit. For businesses operating on thin margins or managing rapid growth, that float has real cost. Processor choice, batch timing, and settlement schedules all influence when authorized transactions become available cash.
The gap between authorization and settlement also creates reconciliation complexity. If you use multiple payment processors, each has its own settlement schedule, batch cutoff times, fee structures, and reporting format. Matching authorized transactions to settled funds across three or four processors is a manual process that finance teams spend hours on weekly. Errors in reconciliation mean disputed amounts, delayed reporting, and inaccurate revenue recognition.
For subscription businesses, the stakes compound. Involuntary churn from failed authorization on recurring charges is projected to cost subscription businesses $129 billion by 2025 (PYMNTS, 2024). Each failed recurring authorization is a customer who may never re-engage, not just a single lost transaction.
How orchestration improves authorization rates and settlement reliability
Payment orchestration addresses both sides of the authorization-settlement equation by routing transactions intelligently and normalizing settlement data across providers.
On the authorization side, an orchestration layer routes each transaction to the processor most likely to approve it, based on card type, issuing country, transaction amount, and real-time processor performance. Capgemini research shows this dynamic routing improves authorization rates by 2-3% on average (Capgemini via Gr4vy, 2025). On $1 billion in volume, a 2% improvement recovers $20 million in revenue.
Orchestration also enables automatic failover. If your primary processor declines a transaction or goes down entirely, the orchestration layer reroutes to a backup processor in real time. The customer sees a successful payment. You see recovered revenue. Without failover, that transaction is simply lost.
On the settlement side, orchestration solves the multi-processor reconciliation problem. When you route transactions across multiple processors and gateways, each returns settlement data in a different format, on a different schedule, with different fee breakdowns. An orchestration platform normalizes this into a single view: which transactions authorized, which captured, which settled, and which failed, regardless of which processor handled them.
This visibility is what most merchants lack. When 82% of executives can’t identify why payments fail, the root cause is usually fragmented data across the authorization-to-settlement chain. Orchestration closes that gap by maintaining a unified transaction record from initial authorization through final settlement.
The routing logic that improves authorization rates also reduces processing costs. Sending a European card to a European processor, or a domestic transaction to the processor with the lowest interchange rate for that card type, optimizes both approval probability and cost per transaction.
FAQs
Does a successful authorization guarantee the payment will settle?
No. Authorization confirms the card is valid and funds are available at that moment, but settlement can still fail. Chargebacks, expired authorization holds, or batch processing errors can prevent funds from reaching the merchant. The gap between authorization and settlement is where most post-transaction payment problems occur.
How long does settlement take after authorization?
Typically 1-3 business days for card payments, though it varies by processor, card network, and merchant category. Some high-risk industries face longer settlement windows. Batch timing also matters: merchants who batch once daily see slower settlement than those batching multiple times.
What is an authorization hold and when does it expire?
An authorization hold reserves funds on the cardholder’s account without transferring them. Holds typically expire after 5-7 days for most merchants, though hotels and car rentals can hold for up to 31 days. If the merchant doesn’t capture the transaction before the hold expires, the authorization drops and a new one is needed.
Can a merchant settle for a different amount than was authorized?
Yes, within limits. Restaurants add tips post-authorization, and hotels adjust for minibar charges. Card networks allow settlement amounts to exceed the authorized amount by a small percentage (typically 15-20%), but larger discrepancies trigger declines or chargebacks.
How does using multiple payment processors affect settlement?
Each processor has its own settlement schedule, batching rules, and reporting format. Without orchestration, merchants reconcile each processor separately, a manual and error-prone process. An orchestration layer normalizes settlement data across processors into a single view.
What is the difference between capture and settlement?
Capture is the merchant’s action, requesting the authorized funds be collected. Settlement is the bank’s action, actually moving the money. Capture triggers settlement but they’re separate steps. Some merchants authorize at checkout and capture only when goods ship, which delays settlement.
How does payment orchestration improve authorization rates?
Payment orchestration routes each transaction to the best-performing processor based on card type, geography, and real-time performance data. Capgemini research shows orchestration improves authorization rates by 2-3% on average (Capgemini via Gr4vy, 2024). For a business processing $1 billion annually, a 1% improvement recovers $10 million in revenue (Worldpay, 2024).
What is the difference between gross and net settlement?
Gross settlement processes each transaction individually, where the merchant receives the full amount and fees are charged separately. Net settlement batches transactions together and deducts processing fees before transferring funds. Most ecommerce merchants use net settlement. Gross settlement is more common in brick-and-mortar retail.
What happens if a merchant doesn’t capture before the authorization expires?
The authorization hold drops and the reserved funds return to the cardholder’s available balance. The merchant must obtain a new authorization to complete the transaction. Card networks like Visa may impose misuse fees for authorizations that are neither settled nor reversed within required timeframes.