Checkout and authentication
Manual or Automatic Payment Capture on Shopify: Choose for Your Workflow
Choose manual payment capture when your team can reliably review authorized orders and complete capture within the actual authorization period. Choose automatic capture when immediate collection fits your operating model and you have a separate reliable process for reviewing goods before release. The better setting is the one your team can execute consistently.
Authorization and capture are different milestones. An authorized order is not automatically a captured payment, and changing the capture setting does not itself create a fraud-review process. The operational design needs an owner, a queue, an expiry check, and clear instructions for fulfillment.
Map the payment routes first
List the payment methods and providers used by the online store. Confirm which support the intended capture behavior. Shopify's authorization and capture guidance describes route-dependent behavior; a method that does not support manual capture can behave differently from the store's general setting.
Also identify any app or external system that captures payments. Two independent capture mechanisms can create conflicting behavior. The decision should specify which system owns capture and how staff see its outcome.
Do not assume the online-store setting controls every sales channel. Verify the scope of each route in the applicable documentation and record exceptions in the operating procedure. A single label such as “we capture manually” can conceal different behavior across the business.
Compare the operational tradeoffs
| Consideration | Manual capture | Automatic capture at checkout |
|---|---|---|
| Review before collection | Requires an explicit pre-capture decision | Collection can precede merchant review |
| Staff workload | Needs a monitored capture queue | Removes that routine manual action |
| Missed-step risk | Authorized orders can remain uncaptured | Review can still be missed before dispatch |
| Unavailable goods | Decision can occur before capture where supported | Payment may need a supported refund process |
| Fulfillment handoff | Must distinguish authorized from captured | Must still distinguish paid from approved to ship |
| Ownership | Named capture owner and backup | Named exception and refund owner |
Neither column guarantees fewer disputes. Manual capture creates time for a decision only if the team uses that time. Automatic capture saves an action but does not prove that the order is safe or fulfillable.
Consider the cost of operational failure alongside the intended benefit. A small store that cannot cover its authorized-order queue during absences may find manual capture difficult to run. A merchant with a deliberate pre-release review process may benefit from the separation if it also owns the capture deadline.
Design the queue before changing the setting
For manual capture, define the entry condition, reviewer, decision owner, capture operator, backup, and completion check. Record the actual authorization expiry for each relevant order rather than assuming an unlimited window. The detailed expiring-authorization decision belongs in its own workflow.
For automatic capture, define how questionable orders are held from dispatch and how cancellation or refund decisions are authorized. A paid status should not bypass a separate goods-release decision where the policy requires one.
Use Shopify's fraud-analysis guidance for the order-review context. Keep the recommendation, payment status, and fulfillment instruction as separate fields. Combining them into one “approved” label makes handoffs ambiguous.
Before rollout, test a normal order, an order requiring review, a payment method with different capture support, and the relevant app handoff using approved test methods. State what was observed rather than claiming untested behavior in production.
Two hypothetical operating models
A hypothetical merchant reviews a limited number of high-value orders each morning and has a trained backup. It chooses manual capture for supported routes, with a queue showing authorization expiry and a required payment-status check before release. The choice fits the team's existing decision capacity.
A second hypothetical merchant processes routine stocked goods continuously with a small team. It uses automatic capture and a separate fulfillment hold for orders requiring review. Its owner focuses on making that hold reliable and ensuring the payment action is reconciled when an order is canceled.
The examples are invented. They do not establish that a particular volume or price band mandates a capture mode. The relevant difference is the team's ability to own the additional step and the relationship between review, collection, and dispatch.
Make the change reviewable
Record the selected mode, affected routes, responsible system, owner, effective time, and treatment of orders already in progress. Do not assume a setting change retroactively modifies every existing authorization. Inspect those orders separately under the documented behavior.
Communicate the new handoff to support, finance, and fulfillment. Each team should know what payment status permits its next action and what status requires escalation. If an external partner requires paid orders before starting work, verify compatibility before choosing a workflow that authorizes first and captures later.
Revisit the decision when staffing, payment methods, or fulfillment timing changes. The right capture method is an operating commitment. It works when the merchant can explain who decides, who collects, how expiry is monitored, and how the warehouse knows the current payment and release state.
See the order and dispute information available in Lower Chargeback.
Related reading in this collection:
- Test Your Shopify Checkout for Dispute-Causing Surprises
- Capture at Fulfillment or per Fulfillment: Avoid Charging for the Wrong Scope
- Manual Payment Methods on Shopify: The Risk Moves to Payment Confirmation