The Anatomy of a Payment: Where Your Money Actually Goes

A customer pays $100. The amount that eventually shows up in a seller's available balance is smaller than $100, arrives later than the moment of purchase, and passes through more intermediaries than the checkout page ever shows. Understanding that path makes every other part of payments — fees, holds, payout timing — make sense as consequences of a real process, not arbitrary deductions.

The parties involved

A single card payment typically involves at least four parties beyond the buyer and seller: the card network (Visa, Mastercard, etc.), the issuing bank (the buyer's bank, which issued their card), the acquiring bank or payment processor (the seller's side of the relationship, which submits the transaction to the network), and — if one exists in the arrangement — the merchant of record, standing in as the legal seller.

Authorization, capture, and settlement are three different events

Authorization happens at the moment of checkout: the issuing bank confirms the card is valid and has sufficient funds/credit, and places a hold. No money has moved yet — this is a promise, not a transfer.

Capture is when the seller (or the platform on their behalf) actually claims the authorized funds — sometimes immediate, sometimes delayed (common for physical goods that ship later; less common for instantly-delivered digital goods, where capture is usually immediate).

Settlement is the actual movement of funds between the banks and networks involved — batched, and typically landing one to a few business days after capture, not instantly. This is the origin of almost every "why isn't my money here yet" question in payments: settlement is a real batch process with real latency, not a configuration setting.

The deductions between gross and net

The $100 a customer pays is the gross amount. Before it becomes money a seller can withdraw, several deductions typically apply:

• Processor/network fees — a percentage plus a fixed amount per transaction, compensating the card network and processor for moving the money and bearing certain risks
• Platform fee — if a merchant-of-record or platform is involved, its own fee for the service (tax handling, chargeback liability, etc.)
• Currency conversion, if the sale and the seller's payout currency differ

What's left after these is the seller's net — and it's this net amount, not the gross sale price, that should be the number a seller actually plans around.

Why the money doesn't move instantly

Beyond settlement latency, a portion of processed payments are typically held back temporarily as a reserve — funds set aside against the possibility of a future chargeback or refund on that transaction. This isn't a fee; the money isn't taken, it's delayed, and it's released back to the seller's available balance after a holding period (the specific length is a policy decision, usually tied to how long a chargeback can realistically be filed for that payment method).

The result is that a seller's balance at any moment is really three separate numbers: available (can be paid out now), pending (settled but not yet past the holding period), and reserve (specifically held against dispute risk). Treating all incoming revenue as immediately spendable is one of the more common cash-flow mistakes a growing software business can make.

Refunds and chargebacks reverse the flow, imperfectly

A refund is the seller (or platform) voluntarily returning funds — straightforward, though whether the original processor fee is also refunded depends on the specific processor's policy, and isn't automatic.

A chargeback is different: the issuing bank, on the customer's behalf, forcibly reverses the transaction, usually accompanied by a dispute fee charged to whoever is the merchant of record — separate from the refunded amount itself, and charged regardless of whether the dispute is ultimately won or lost.

Why this matters even if someone else handles it

None of this requires a seller to personally reconcile settlement batches — that's exactly the kind of operational work a payments platform or merchant-of-record provider exists to absorb. But understanding the actual mechanics changes how a team reads its own dashboard: a "pending" balance isn't stuck, a reserve isn't a fee, and a delayed payout isn't necessarily a problem — it's usually just the settlement and hold-period process working as designed.