Choose the business event that should trigger capture
Common candidates include acceptance of an immediately delivered service or a confirmed shipment. The right event depends on the commercial terms, payment rules, and fulfillment process. The payment team should agree it with operations and customer support, then have the implementation enforce that event reliably.
An order placed today for an item that may ship much later needs a different design from a same-day digital purchase. A temporary authorization should not be treated as an indefinite deposit. If the planned fulfillment exceeds the supported authorization window, ask the provider about an appropriate approved flow and explain the arrangement clearly to the customer.
Assign an owner for orders awaiting capture. They need a view of the order, amount, fulfillment status, and remaining time. Otherwise, authorized orders can quietly expire while staff assume the payment step was completed at checkout.
References: Stripe Docs: Separate authorization and capture
Use a partial shipment to expose the configuration
Consider a hypothetical $900 order with $600 of goods ready to ship and $300 delayed. The intended result might be to collect only for the first shipment. Before implementing that approach, confirm whether the payment method and provider configuration support the required partial capture and treatment of the remainder.
Adyen documents a distinction between a single partial capture, which cancels the unclaimed amount, and supported multiple partial captures, which can retain it. Stripe also documents method-specific limitations. The business should not assume it can capture the remaining $300 later merely because the original authorization was for $900.
Ask the engineer to demonstrate the first capture, the remaining order, and the final payment or cancellation. Customer support should see enough information to explain the pending hold and actual collected amount without telling the customer that every visible bank entry is a completed charge.
References: Stripe Docs: Separate authorization and capture; Adyen Docs: Automatic, delayed, and manual capture
Keep the payment stages separate in operations
Use states with clear meanings in the order system. A single paid flag can hide the difference between a held amount and money that has moved further through the process.
| Stage | Operational meaning to verify |
|---|---|
| Authorized | A supported amount is held within a limited validity window |
| Capture requested | The collection request was sent; its result must be checked |
| Captured | The provider reports the capture result for that amount |
| Settled or paid out | The provider balance or bank movement is separately explained |
| Canceled or expired | The original hold can no longer support the intended capture |
| Refunded | A later money-back event remains linked to the original collection |
Handle a missing response without charging twice
The order system may send a capture request and lose the connection before receiving the result. A second request is not automatically the right response. The implementation needs to check the provider's current payment status and use its supported duplicate-prevention mechanism before retrying.
Test a delayed notification, an expired authorization, and a capture failure in the provider's test environment. Adyen documents capture-result notifications and failure handling, so the order process should account for the actual events in the configured flow. Decide whether fulfillment pauses while an uncertain payment is investigated and who makes that decision.
A canceled order needs its own route. If the amount is still only authorized, the relevant action may be to cancel the authorization. If collection has occurred, the process may require a refund. Have the provider confirm the right action for the observed status instead of using the same customer-service button for every case.
References: Stripe Docs: Separate authorization and capture; Adyen Docs: Automatic, delayed, and manual capture
Let accounting follow the evidence
Keep order, authorization, capture, refund, and payout identifiers connected. The accountant needs the actual transaction dates and amounts to apply the company's accounting policy and reconcile the processor balance. Capture timing alone does not determine when revenue should be recognized for a particular contract.
Review uncaptured orders and partially fulfilled orders at period end. The purpose is to find commercial and payment work that remains open, not to convert every authorization into cash or revenue. An expired hold with goods already shipped is an exception requiring action, even if the original checkout appeared successful.
Choose automatic capture when it fits the approved selling and fulfillment process. Choose a supported delayed or manual arrangement when the business needs that control and can operate the resulting queue. The successful design connects a clear fulfillment decision to a verified payment result, with a defined response when either side fails.
Sources
Requirements and product details can change. Check the linked guidance for the facts that apply to your situation.
Related reading
Need help with this work?
General information, not personalized accounting, tax, legal, or investment advice. Have the appropriate qualified professional review decisions that depend on your circumstances.