Capture
The step where a previously authorized payment is finalized and submitted for settlement.
Why it matters
Capture matters because delayed fulfillment, hotel deposits, travel bookings, partial shipments, cancellations, and fraud review workflows often need authorization first and capture later.
How it works
Operationally, the merchant receives an authorization, decides whether the order should be fulfilled, sends a capture request for the full or partial amount, and the acquiring or processor chain moves the transaction toward clearing and settlement.
Risks and pitfalls
The main pitfall is missing the capture window or capturing the wrong amount. Weak capture logic can cause expired authorizations, duplicate customer friction, reconciliation gaps, and avoidable support disputes.
Regional notes
In BIST/MOEX/global payment analysis, capture behavior should be mapped to merchant category, fulfillment timing, local acquiring configuration, FX handling, and scheme rules around authorization validity.
Related terms
Compare with
AuthorizationBuild from
Payment GatewayPrimary sources
Stripe
2026-04-30Stripe Docs: Separate authorization and capture
Primary implementation source for authorization holds, capture timing, and manual capture windows.
Adyen
2026-04-30Adyen Docs: Capture an authorized payment
Primary implementation source for payment capture after authorization, manual capture, and capture request behavior.
Visa Developer
2026-04-30Visa Developer: VisaNet Connect Acceptance
Primary network source for acquirer-facing authorization, capture, clearing, settlement, and issuer decision routing.
Reviewed
5/4/2026
Common questions
What does Capture mean?
The step where a previously authorized payment is finalized and submitted for settlement.
Why does Capture matter in fintech?
Capture matters because delayed fulfillment, hotel deposits, travel bookings, partial shipments, cancellations, and fraud review workflows often need authorization first and capture later.
What risks should teams watch with Capture?
The main pitfall is missing the capture window or capturing the wrong amount. Weak capture logic can cause expired authorizations, duplicate customer friction, reconciliation gaps, and avoidable support disputes.