Authorizing vs. Capturing a WooCommerce Payment
How the Two WooCommerce Steps Work
When a gateway authorizes a payment, it verifies the card is valid and has sufficient funds, then places a temporary hold for that amount — the customer sees this as a pending charge, but it hasn't actually settled. Capturing converts that authorization into an actual, final charge. Most stores never think about this distinction because their gateway is configured to authorize and capture in the same instant at checkout, but it's a genuinely separate two-step process underneath.
Why a Store Might Delay Capture
- Made-to-order or pre-order products where the store doesn't want to actually charge the customer until the item is ready to ship, while still confirming upfront that the payment method is valid.
- High-risk or high-value orders some stores manually review before capturing, giving a window to catch fraud before money actually moves.
- Authorization holds have a time limit (commonly around 7 days, though this varies by card network and gateway) — if capture doesn't happen within that window, the authorization expires and the store would need to re-authorize, which isn't guaranteed to succeed a second time.
- Not every gateway plugin supports delayed capture as a WooCommerce-configurable option, so this needs specific confirmation before relying on it for an order fulfillment workflow.
Setting This Up Correctly
- Check whether the active gateway plugin supports authorize-only mode with a separate manual or automatic capture step.
- If using delayed capture, build a clear process for capturing before the authorization window expires — typically tied to order fulfillment status.
- Test the full flow including what happens if an authorization does expire before capture, so the fallback behavior is understood ahead of time.
Need a delayed-capture workflow built around your fulfillment process? See custom WooCommerce development.