Payment Authorization and Capture

Payment authorization and capture are distinct stages in supported payment methods. Authorization approves or reserves an amount; capture requests collection against that authorization. An uncaptured authorization can expire. Neither an authorization nor a capture record alone proves that a payout reached the merchant’s bank.

For example, a merchant might authorize 100 USD and capture 80 USD after confirming the final order. Preserve both amounts and their identifiers. Do not count the 100 and the 80 as 180 USD of sales. Whether the unused amount is released and whether another capture is allowed depend on the payment method and provider configuration.

Keep payment attempts separate from orders, and preserve capture, refund, dispute, and payout identifiers at their own grains. One order can involve several attempts; a payout can contain many movements. A refund and a dispute also need their own states rather than being forced into a single status ladder.

Validate observed history against the supported contract, including expiration and partial-capture behavior. Missing authorization evidence can mean an incomplete export. Quarantine and investigate the history instead of assuming that the provider executed an impossible payment.

See Integrating Payment, Commerce, and Finance Data for worked examples.

Reference: Stripe: separate authorization and capture.