What Is Capture? Definition, Payment Flow, and Examples
Capture is the merchant's confirmation after authorization that submits the transaction toward clearing; it is not completed interparty settlement. This guide focuses on Capture's real role, boundaries, and common points of confusion.
Key points
- Definition: Capture is the merchant's confirmation after authorization that submits the transaction toward clearing; it is not completed interparty settlement.
- Flow position: After authorization, a merchant may capture according to order status or void before capture.
- Do not confuse: Capture / Authorization
How it fits into the payment flow
For Capture, the relevant process is as follows: After authorization, a merchant may capture according to order status or void before capture. Clearing exchanges transaction detail and determines positions; settlement moves funds between participants. A refund is a later credit, while pending and posted describe account-facing states.
A practical review of Capture should account for this: order systems, merchant dashboards, and banking apps can update at different times. Preserve the original transaction identifiers and check the formal statement instead of treating a push notification as final accounting.
Practical example
An online store captures an approved authorization when goods ship, submitting the transaction toward clearing. Successful capture still does not mean issuer-acquirer settlement is complete.
How it differs from related terms
| Term | Definition |
|---|---|
| Capture | is the merchant's confirmation after authorization that submits the transaction toward clearing; it is not completed interparty settlement |
| Authorization | is the issuer-side decision on whether to approve a transaction based on account, amount, and risk data; it does not mean final merchant payment |
| Clearing | is the stage where participants exchange transaction data, verify amounts, and calculate obligations |
Capture focuses on the fact that it is the merchant's confirmation after authorization that submits the transaction toward clearing; it is not completed interparty settlement. Authorization, by contrast, is the issuer-side decision on whether to approve a transaction based on account, amount, and risk data; it does not mean final merchant payment. They can appear in one transaction while answering different questions.
Use cases and limits
A key limit of Capture is the following: void and refund apply at different stages. An uncaptured transaction commonly calls for a void, while a processed transaction may require a refund. Using the wrong operation can cause duplication, delay, or reconciliation gaps.
Frequently asked questions
These answers address two common search questions about Capture.
Is it the same as Authorization?
No. Capture is the merchant's confirmation after authorization that submits the transaction toward clearing; it is not completed interparty settlement. Authorization is the issuer-side decision on whether to approve a transaction based on account, amount, and risk data; it does not mean final merchant payment. Compare the object, processing stage, and responsible party.
Are a refund and a void the same operation?
For Capture, no. A void commonly applies before capture is complete, while a refund credits a transaction that has already been processed. Interfaces and timing vary by processor and network.
These primary sources support the definition and process for Capture. Current product, network, and local rules still control a real transaction.