Authorizations are requests from a merchant to the cardholder's issuing bank confirming there's enough money or available credit — and reserving those funds if there is. How a merchant runs that process operationally, in real time or in batch, has real downstream consequences.
Real-time vs. batch, operationally
Real-time processing means a merchant knows immediately when a customer's payment won't go through — while the customer is still on the page, able to try another payment method, instead of finding out after the fact and losing the order entirely.
What operations teams need to know
- Authorizations expire and need re-verification before settlement
- Debit authorizations pull funds immediately — stacking several can trigger an overdraft
- Credit card authorizations only touch the credit limit, not an actual balance
- Prepaid card funds get held immediately, until completion or cancellation
Soft vs. hard declines
A soft decline means the bank wants more verification, not a refusal — these convert well once the extra step clears. A hard decline is a real refusal: insufficient funds, suspected fraud, an invalid number, or a system error.
Why real-time wins operationally
Real-time authorization lowers overall cost by filtering out transactions that were never going to convert, before they generate any customer service overhead — and it improves the customer experience by resolving payment problems in the moment, not after.