Your Cart
WooCommerce authorize and capture

WooCommerce Authorize and Capture: When to Use Manual Payment Capture

WooCommerce authorize and capture divides a card transaction into two separate stages: first, the payment provider checks the card and reserves the amount; later, the merchant captures some or all of that authorized amount. This can be useful when the final price or fulfillment decision is not known at checkout, but it also creates an operational responsibility: authorized orders must be reviewed before the authorization expires.

This article focuses on the documented WooPayments workflow and highlights why gateway-specific documentation matters. The WooCommerce Stripe extension documents a different set of supported payment methods, so the terms, payment-method availability, expiry period and administration screens should not be treated as universal rules for every WooCommerce gateway.

Authorization vs. capture: the payment lifecycle

A two-stage payment flow

In the documented WooPayments process, authorization verifies the card and reserves funds without transferring money to the merchant. The customer’s available funds are temporarily held, while the order waits for a later decision. Capture is the subsequent step that transfers some or all of the authorized amount.

This distinction is important for store owners. An authorization is not completed revenue and should not be treated as a guaranteed payment. Before capture, the merchant can cancel the authorization, which releases the reserved funds and prevents a later capture. If the authorization expires without capture, the funds are also returned and the payment can no longer be completed through that authorization.

After a payment has been captured, the operation is different. A captured payment cannot be cancelled as an authorization, although it can be refunded. Therefore, staff should decide whether an order should be captured, partially captured or cancelled before completing the charge.

When manual capture makes sense

Variable totals and fulfillment decisions

Manual capture is relevant when a merchant needs an upfront payment hold but does not yet know the final amount or whether the order should be fulfilled. WooCommerce documentation gives equipment rentals and custom orders as examples. It also describes hotel-style workflows and pay-at-the-pump scenarios, where the final decision or amount may be determined after the initial checkout stage.

For an equipment rental, the merchant may need to confirm availability or determine the final charge before transferring the authorized amount. A custom order may require a final price decision before fulfillment. A service business may also consider this approach when the final bill depends on work completed, but the documented information does not establish a universal rule that every service workflow is suitable.

The practical trade-off is flexibility versus administration. Immediate capture completes the payment during checkout. Manual capture requires staff to monitor authorized orders, make a timely decision and ensure that the final amount stays within the original authorization. The workflow is appropriate only when the provider’s timing rules, supported payment methods and internal process fit the business.

WooCommerce payment-method and gateway limitations

Why gateway-specific documentation matters

WooCommerce does not impose one universal authorize-and-capture behavior across all payment extensions. In the documented WooPayments workflow, authorize and capture is limited to cards and express checkout methods. Local payment methods and buy-now-pay-later methods are not supported in that workflow.

The WooCommerce Stripe extension documents a separate implementation. Its documented supported methods include cards, express checkout methods, Affirm, Afterpay and Klarna. When manual capture is enabled there, other payment methods may be hidden. This difference shows why a store owner must identify the exact payment extension before planning checkout, fulfillment and staff procedures.

Do not assume that a payment method available with one gateway will remain available when manual capture is enabled with another. Check the documentation for the extension used by the store, including its supported methods, capture rules, expiry behavior and administration labels. The seven-day period and screen locations described below apply to the documented WooPayments process, not automatically to every WooCommerce payment processor.

How to enable manual capture in WooPayments

Configuration and pre-launch checks

In the documented WooPayments interface, manual capture is enabled from Payments > Settings. In the Transactions section, enable Enable manual capture. This setting changes the payment workflow, so it should be reviewed together with the store’s payment methods and fulfillment process before live transactions are accepted.

Before enabling the setting for live use, test authorization, capture, partial capture and cancellation in the payment provider’s test mode. The test should also confirm that staff can identify authorized orders and understand which action to take. A setting alone does not create an operational process: the team still needs to decide who reviews uncaptured payments and when that review occurs.

Confirm that the final amount will normally be known within the provider’s authorization window. If an order may exceed the original authorization, plan for a new customer payment rather than assuming that the difference can be captured later.

How to capture an authorized payment

The two administration routes

In the documented WooPayments workflow, an authorized order appears with the On Hold status. This status indicates that the payment is authorized and waiting for capture; it does not mean that the funds have already been transferred to the merchant.

Staff can complete the charge through the order administration screen:

  1. Open WooCommerce > Orders.
  2. Open the authorized order with the On Hold status.
  3. Choose Capture charge in Order Actions.
  4. Update the order to complete the action.

There is also a transaction-level route. Open Payments > Transactions and use the Uncaptured tab to locate the authorized payment and capture it. The two routes support the same operational goal, but the order view connects the payment decision with the customer’s order, while the transaction view helps staff monitor payments that are still waiting for action.

Monitoring should be deliberate rather than occasional. Uncaptured orders need a decision within the documented authorization period. If the final order should not proceed, cancel the authorization instead of leaving it unattended.

Partial capture, cancellation and over-authorization limits

Choosing the final amount

A partial capture allows the merchant to capture less than the originally authorized amount. In WooPayments, the order total can be edited to an amount no higher than the original authorization before Capture charge is selected. This can be useful when the final charge is lower than the temporary hold.

There are two important limits. First, WooPayments permits only one capture per order. After a partial capture, the remaining authorized amount is released and cannot be captured later. Second, the merchant cannot capture more than the amount originally authorized. A partial capture is therefore not an initial instalment that leaves the rest available for a second capture.

If the final amount is higher than the original authorization, the difference cannot simply be added to the capture. The documented process requires the merchant to cancel the authorization and have the customer complete a new purchase. This constraint should be considered before authorizing an order whose price may change.

When the authorization should be cancelled

Cancellation is appropriate when the authorized order should not be charged. In the documented WooPayments workflow, the merchant can set the order to Cancelled or select Cancel authorization from Order Actions. Cancellation releases the reserved funds and prevents a later capture.

This is not the same as a refund. Cancellation applies before capture, while a captured payment cannot be cancelled as an authorization and instead follows a refund process. Keeping these actions separate helps staff communicate accurately with customers and avoid treating a temporary hold as completed revenue.

What happens after seven days

Operational checklist before expiry

For WooPayments, an authorization expires after seven days if it has not been captured. When it expires, the reserved funds are returned to the customer, the order is cancelled and the payment can no longer be captured. The merchant cannot rely on the expired authorization remaining available for a later fulfillment decision.

Seven days is specific to the documented WooPayments workflow. It should not be presented as a universal expiry period for every WooCommerce payment processor. Other extensions may document different rules, so the selected gateway’s documentation must be checked before the store adopts a manual-capture process.

A practical internal review should identify authorized orders before the deadline and assign one of the available actions:

  • Capture the supported final amount when the order is ready and the amount does not exceed the original authorization.
  • Use a single partial capture when the final amount is lower, remembering that the unused authorized amount will be released.
  • Cancel the authorization when the order should not be charged.
  • Arrange a new customer payment when the final amount may exceed the original authorization.

Reviewing the On Hold orders and the Uncaptured transactions view can help staff find payments that still require a decision. The process should be tested before live use and adjusted to the provider’s documented rules.

Authorize and capture is most relevant when a merchant needs to reserve funds before deciding on the final capture. It can support documented scenarios such as equipment rentals and custom orders, but it introduces clear limits: payment-method compatibility depends on the gateway, WooPayments allows one capture per order, the captured amount cannot exceed the original authorization, and an uncaptured authorization expires after seven days. Merchants should verify the rules for their selected extension, test the workflow and create an internal review process. Explore our WordPress plugins, WooCommerce extensions, themes and membership plans to find the right tools for your website.

Free Worldwide shipping

You can download the products right away at wpbetterplugins.com

Immediate delivery

After the payment is credited, the product is ready for download

International Warranty

Offered in the country of usage

100% Secure Checkout

Stripe / Apple Pay / Google Pay / MasterCard / Visa

Zadzwoń