A customer taps Pay and sees a tick two seconds later. Behind that tick, four things happen at four different moments, and a merchant who knows which is which can read their own dashboard — and argue with their provider from a position of knowledge.
1. Authorization is a promise, not money
The card details go to the issuing bank, which checks the funds, the fraud rules and the card status, and answers yes or no. A yes puts a hold on the customer's balance. Nothing has moved yet. That hold expires on its own — usually within a week — if nobody claims it.
This is why a customer can see a charge on their app that you cannot see as settled: they are looking at the hold, you are looking at your ledger.
2. Capture claims the money
Capture is the instruction that turns the hold into a real debit. For an ordinary online sale it happens immediately, in the same second as the authorization. For a business that ships goods later, it can be delayed on purpose so the customer is only charged when the parcel leaves.
An authorization that is never captured is not a failed payment and not a refund. It is a hold that quietly expires, and it is the single most common reason a customer writes to ask why they were "charged twice".
3. Settlement moves funds between banks
At the end of the processing day the captured transactions are batched, and the card schemes move the money from the issuing banks to the acquiring bank. Interchange and scheme fees come out here. Settlement is why your available balance lags your sales figure by a day or two, even when nothing is wrong.
4. Payout puts it in your account
The last step is the one merchants actually care about: the transfer from the acquirer, through your provider, to your own bank account or wallet, on an agreed schedule and minus the agreed fees. Anything held back — a rolling reserve, an open dispute — is held here, and should be visible to you line by line.
Where it goes wrong
- Authorized, never captured: the customer sees a hold, you see nothing. Capture on a schedule you can explain, or capture immediately.
- Captured, then refunded: the interchange on the original sale is usually not returned, so a refunded sale often still costs you the fee.
- Settled, then disputed: a chargeback reverses money that has already reached you. Your balance can go negative for a sale you thought was closed weeks ago.
- A hold that outlives its authorization: charge again and you are charging a customer who was never debited the first time.
What to watch on your own dashboard
Three numbers tell you whether the pipeline is healthy: the share of attempts that get an authorization, the share of authorizations that are captured, and the share of captures that come back as disputes. A drop in the first is usually the issuer or 3-D Secure. A drop in the second is nearly always your own integration.
Not sure which step your problem is in? Send us an order id and we will trace it — sales@utopia-payments.com.