An authorization is a request from a merchant to the cardholder's issuing bank, confirming there's enough money or available credit to cover a purchase — and reserving those funds if there is.
Real-time vs. batch
Merchants can process authorizations in real time or in batch. Real-time processing lets a merchant know immediately when a customer doesn't have the funds, so they can offer an alternative payment method on the spot instead of finding out — and losing the sale — after the fact.
What to know about how authorizations behave
- Authorizations expire, and need to be verified as still valid before settlement
- Debit card authorizations pull funds from the account immediately — stacking several can cause an overdraft
- Credit card authorizations only reduce available credit, not an actual cash balance
- Prepaid card funds are held immediately until the transaction completes or the authorization is cancelled
Soft declines vs. hard declines
A soft decline means the bank wants additional verification — often triggered by enhanced internet security protocols or extra customer checks — and hasn't actually refused the transaction yet. These convert at a high rate once the extra step is completed. A hard decline is a real refusal: insufficient funds, suspected fraud, an invalid card number, or a system error or timeout.
Why real-time wins
Real-time authorization is the better default over batch processing — it filters out transactions that were never going to convert before they generate customer service overhead, which lowers overall cost per order.