Lesson 7 of 13

Cash capture.

How finance proves every order was paid: matching deposits to orders, and working the exceptions.

By Nagesh Koritala 4 min read Last verified: November 2026

Lesson 1: Improve the checkout
Lesson 2: The checkout flow
Lesson 3: Authorization
Lesson 4: Payment states
Lesson 5: Capture
Lesson 6: Clearing and settlement
Lesson 7: Cash capture (this lesson)
Lesson 8: Returns and refunds
Lesson 9: Disputes
Lesson 10: Tokens and stored credentials
Lesson 11: Transaction types
Lesson 12: Complete reference
Lesson 13: Payments compliance

All 16 pages in this guide

A deposit lands in the bank. It is one number, say $41,872.19, and it covers hundreds of orders, minus fees, minus refunds, minus any chargebacks. Finance has to prove every order inside it was paid. This is reconciliation, and the accounting step that clears each receivable is called cash application.

The key that makes this possible is the transaction ID. If your order record stores the gateway's payment ID for every authorization, capture, and refund, the match is automatic. If it does not, someone in finance matches by amount and date by hand. That is the moment a checkout design decision becomes an operating cost.

Sources for this guide

Card network rules change. Time limits, fees, and authorization windows here reflect published rules and provider documentation as of late 2026; confirm details with your processor before you build against them.

Sources

Your progress stays on this device.

Next: Lesson 8

Returns and refunds.

The return workflow, and how to choose between a void, a reversal, and a refund.

Start lesson 8 All lessons

Questions about payments? Email me. I read every note.