Partial shipment does not prove multiple captures are supported
Confirm that both the approved provider and the installed gateway support multiple captures against this particular authorization, including retention of the uncaptured remainder and the actual capture deadline. The ability to record partial fulfillment does not establish that capability. Stripe documents that most payments permit one capture and that a partial capture normally releases the remainder unless supported multicapture applies. Until the payment and integration evidence confirm otherwise, do not plan later shipments around repeated captures of the same hold.
For: A research-only store owner planning to ship an order in parts and collect card payment as each part ships.
Write the actual shipment plan first: which items and quantities are due in each shipment, which have already moved, and the remaining commitments. This tells you what the business needs from payment collection. It does not tell you what the existing authorization can do.
Where WooCommerce’s documented Fulfillments feature is present, individual fulfillment records can contain products, quantities, draft or fulfilled status and shipping or tracking details. The order can be partially fulfilled because some items are unassigned or a fulfillment remains in draft. Extensions can alter the model. Check what the installed store actually uses; neither a partial status nor a marked-fulfilled record proves a separate capture occurred or that a carrier moved the goods.
Capture later is not automatically capture repeatedly
Authorization and capture are distinct payment stages. Stripe’s capture-later documentation says that default capture takes the authorized amount and that capturing less normally releases the remaining amount. Most payments permit only one capture. A setting that delays capture therefore does not, by itself, establish permission to capture one portion now and another later.
Multicapture is the capability that needs specific confirmation when the intended workflow requires repeated captures while retaining a remainder. Keep that question separate from whether an authorization is still open. An open hold with time remaining can still be subject to a single-capture limit. Conversely, support for multiple captures does not remove the applicable expiry.
Use Stripe’s rule only for a Stripe payment. If another provider authorized the order, obtain its documented capture pattern for the actual method and account. Record the payment’s remaining capturable amount and deadline from its own records rather than deriving either from the unshipped order total.
Match provider capability to the gateway action
Identify the provider account, payment method, gateway or connector, installed version and capture configuration associated with the authorization. Obtain an answer that addresses this combination. A provider’s API feature list does not establish that the store extension exposes the feature or that this account and payment qualify.
The provider question is whether this authorization supports the planned capture sequence and what happens to the remainder after the first partial capture. The gateway question is which documented action implements that sequence, whether the remainder is retained, and how subsequent captures and the final capture are represented. A reply that only confirms partial capture leaves repeated capture unanswered.
Compare each planned shipment date with the deadline on the actual authorization. If a later shipment lies beyond that deadline, the proposed workflow remains unresolved even when multiple captures are supported. Do not substitute a generic number of days or assume the shipment record extends the hold.
Choose a plan from the confirmed limits
If both provider and gateway evidence support the sequence, record the allowed captures, remaining amount, deadline and person authorized to act. That establishes a capability basis for the shipment plan; it does not authorize this page’s reader to capture funds. If either side supports only a single capture, or the answer is missing, revise the collection plan with the responsible merchant and provider before promising collection on each shipment. Do not initiate a second charge just to find out what works.
A Prism checkout-review consultation can start with the shipment plan and the unanswered capability question. Describe the research-only catalog, store platform and gateway, and whether the uncertainty concerns the provider or the installed integration. Scope, responsibilities, fees and terms are agreed before work. Use the public form for that description without customer or payment records; follow-up is by email. A request is not a booked appointment, purchased implementation or processing application.
Shipment-to-capture capability
Complete this for one real authorization and its shipment plan. Treat the repeated-capture plan as unconfirmed if provider support, gateway support, the remaining amount or the deadline is missing. Use internal references only.
Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.
Shipment-to-capture capability. The last column is for temporary notes.
Capability question
Record to consult
Decision supported
Your evidence
Actual shipment plan
Record to consultItem quantities and dates from the order and fulfillment commitments.
Decision supportedEstablish how many collection events the plan would require; distinguish plans from dispatched goods.
Authorization reference
Record to consultThe provider payment associated with the order, including account and method.
Decision supportedEnsure the capability answer belongs to this payment rather than another account or method.
Provider capture capability
Record to consultWritten provider guidance applicable to the account and authorization.
Decision supportedDistinguish one partial capture from multiple captures retaining the remainder.
Gateway support
Record to consultInstalled connector name, version and documented capture actions.
Decision supportedConfirm the store can perform the provider-supported sequence; capture later alone is insufficient.
Earlier capture activity
Record to consultExisting capture records and current authorization state.
Decision supportedIdentify whether an earlier action has already released the remainder or changed what is available.
Remaining amount and deadline
Record to consultThe current capturable amount, currency and expiry recorded for this authorization.
Decision supportedCompare every remaining shipment with the actual limit; unshipped value is not proof of capturable funds.
Plan owner and open condition
Record to consultThe merchant decision and the specific unanswered provider or gateway question.
Decision supportedKeep the plan unconfirmed until the missing condition is answered; assign who resolves it.
These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.
Limits
Stripe capture behavior is specific to eligible payments and supported integrations; no universal capture window or merchant eligibility follows.
WooCommerce fulfillment records describe application state. Payment records and carrier events require separate evidence.
This worksheet does not authorize a capture, new charge, shipment or change to customer terms. Keep card data, authentication codes, credentials and customer records out of public inquiries.
Stripe authorization and capture: partial capture boundary — checked 2026-09-29. Default capture takes the authorized amount; partial capture normally releases the remainder. Most payments allow one capture, and retaining or capturing the remainder requires supported multicapture. Actual authorization expiry and integration support must be respected.
WooCommerce order fulfillment — checked 2026-09-29. Where the documented Fulfillments feature is present, records track products, quantities and fulfillment state. Partial fulfillment can reflect unassigned items or draft records; payment and carrier evidence remain separate.
Prism solutions — checked 2026-09-21. Prism can help prepare a provider question; any authorization-behavior assistance needs defined scope and authorized access. Scope, fees and terms are discussed before work, and the provider decides account terms.
Prism contact — checked 2026-09-21. The form asks for website, products and question without payment-card details, passwords or customer records. Follow-up is by email; the request is not an appointment, purchase or processing application.