Which payment methods remain when capture is deferred?

The capture setting changes the available method set

Switching to authorization first changes more than when staff expect to collect payment. In the WooCommerce Stripe extension, manual capture also filters the methods checkout can offer. The official guide names cards, including express checkout methods, Affirm, Afterpay and Klarna as the supported set. Methods outside that set are hidden when manual capture is enabled. A missing debit option can therefore be consistent with the chosen mode even though the business still wants to offer it.

Read this as a compatibility statement about that extension. It does not say that every research-only merchant can use the listed methods, that all countries support them, or that the version installed on your store implements every feature described. It also does not establish a general rule for another Stripe integration or another payment provider. Confirm the gateway's identity before applying this list to the store.

For ACH Direct Debit, the useful conclusion here is narrow: it is not in the extension's documented manual-capture set. Do not turn that observation into a claim about every bank-debit product, or infer that changing this setting will repair a debit payment already in progress. Method visibility and the outcome of an existing payment are separate records.

Compare the saved mode with the observed disappearance

Start with the real configuration change. Record the extension name and version, the previous capture setting if documented, the current saved setting, and when it changed. Then identify the exact method that disappeared and the checkout location where it had been seen. Keep the earlier observation separate from the current one. If there is no record of the earlier setting or visibility, mark it unknown rather than reconstructing it from memory.

Compare three distinct facts for each method: what your provider has confirmed for this account and catalog, what the extension documents for manual capture, and what the checkout actually shows. Written permission does not supply missing software support. Software support does not supply permission. A visible method does not by itself establish either the account terms or the capture behavior of a payment.

When capture later is enabled and an unlisted method disappears, the records are consistent with the documented filtering rule. That gives you a specific workflow decision to make before investigating a button defect. When a listed method disappears, the manual-capture list alone does not explain its absence; continue with the method's other availability requirements and the installed version. If the capture setting did not change, this particular explanation remains unestablished.

If the affected channel is agentic commerce, record that channel separately. The same WooCommerce guide describes an additional capture-mode prerequisite in the Stripe Dashboard for that flow. The extension toggle alone is therefore insufficient evidence that capture will be deferred across every channel.

Choose the workflow before trying to restore the method

Write why capture is being deferred: identify the actual business decision that must happen before collection, who makes it, and which existing operating instruction requires it. Separately identify why the missing approved method matters to the store. This comparison prevents a visibility fix from silently undoing the payment-timing decision that prompted the change.

If authorization first is the requirement, compare the store's approved methods against the documented manual-capture set and record which candidates satisfy both. A method outside that intersection does not become suitable merely because staff want to keep its button. Do not add Affirm, Afterpay or Klarna solely because the guide lists them; the provider must permit the actual business and relevant method.

If retaining the affected debit method is the requirement, evaluate whether the business can use a supported workflow without the extension's manual-capture setting. Removing this particular filter is not a guarantee that the method will appear: the account, country and installed implementation still need to support it. Have the authorized owner decide the timing change before anyone edits the setting.

If both requirements are mandatory and your documented setup cannot satisfy both, record the conflict as unresolved. Define the needed combination precisely for the provider and site maintainer. A custom display change would not establish that the payment method supports the requested capture behavior. Keep existing payment records under their own documented workflow rather than assuming a setting change alters them.

Turn the comparison into a scoped checkout request

A useful handoff names the extension version, current mode, missing method, documented support and required operating workflow. State the proposed outcome: retain deferred capture with compatible approved methods, evaluate a supported workflow that retains the debit method, or resolve a documented incompatibility before changing anything. For any authorized change, agree that the resulting method visibility and actual payment capture behavior must be checked separately; a restored button alone does not finish the work.

Prism's checkout-review consultation is the relevant starting point for discussing the storefront and provider question. Describe the website, research-only products, mode change and method affected. Prism confirms scope, responsibilities, fees and terms before work; the provider decides eligibility and account terms. The public consultation request receives follow-up by email and does not book an appointment, purchase implementation or submit a processing application. Leave out card details, passwords and customer records.

Capture-mode method matrix

Complete the last column only for methods your store actually uses or is evaluating under its provider's terms. Enter the current saved capture mode, shown or hidden with observation date and checkout location, the reference for account permission, and the desired workflow or decision. Keep unknowns explicit. A listed method that is hidden needs another availability check; an unlisted method hidden in manual-capture mode matches the documented filter. Compare the completed rows before authorizing a setting change. Do not enter payment credentials or customer records.

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.

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.