Bank debit is available in checkout but not in express buttons

Name the bank method and the component separately

Record the provider and exact method named in the merchant’s approval or account documents. Bank debit is a broad description; this comparison’s documented support statement is specifically about Stripe ACH Direct Debit. Do not apply that row to another bank-debit scheme, provider, country arrangement or plugin merely because the customer-facing label looks similar.

Next identify the component that renders the payment choice. Stripe Checkout, the Payment Element and the Express Checkout Element are distinct product names in the support table. A store page titled Checkout does not identify which component is installed. Use the actual integration record or maintainer’s configuration reference, including the plugin and version if a plugin supplies the surface.

Read support as a component capability

The Stripe table lists ACH Direct Debit as supported in Checkout and the Payment Element, and unsupported in the Express Checkout Element. That establishes a useful boundary: putting an express component beside an existing payment form does not make ACH available inside the express component. Moving buttons or treating the absent ACH button as a visual defect does not resolve this support mismatch.

The supported entries identify components to examine; they do not prove that this account has the method enabled or that this store’s integration exposes it. Compare the documented component capability with the merchant’s account configuration and the plugin’s own support for the installed version. Keep country, currency and buyer-context conditions attached to the actual approved method rather than inferring them from a general support mark.

This distinction also separates two investigations. An ACH option missing from the Express Checkout Element fits the documented boundary. An expected ACH option missing from the supported full flow needs its own configuration and integration evidence. Do not treat the support table as a diagnosis of that second problem.

Choose a visible route to the supported surface

If the merchant already has an approved and configured ACH route through Checkout or the Payment Element, preserve a clear way for buyers to reach it from the cart or payment step. Examine the actual labels and destination: a buyer looking for bank debit should not have to infer that an express-only area is the entire set of payment choices. Describe availability only to the extent the configured route supports it.

Use the worksheet to compare the existing full route with the express area. Identify which component can present the method, where the buyer enters that route, and which required store controls remain on it. If a change is proposed, specify the intended route and those controls before authorizing implementation. Do not remove required acknowledgments or misrepresent a different payment method as ACH to make the express area look complete.

Choose between the supported components from the integration the store actually operates and the work the maintainer can document. The support table alone does not justify a rebuild or establish which option would require less work. If the installed method is not Stripe ACH Direct Debit, the next evidence needed is that provider’s method-by-component support, not a guess based on this comparison.

Keep technical support separate from business approval

A working payment surface and an account’s eligibility are separate records. The provider decides whether it supports the disclosed research-only business and on what terms. This Stripe component table neither approves nor universally rejects that business category; it describes technical method support. Also keep method presentation separate from the status or timing of a real bank-debit payment. Seeing a choice does not establish that a payment completed.

A scoped Prism checkout consultation can start with the exact method, installed component, current customer route and observed omission. Prism’s public work includes storefront review and help with provider website questions. Confirm scope, responsibilities, fees and terms before work. Send the website, products and question without payment details, passwords or customer records. The inquiry receives email follow-up and does not book an appointment, purchase a change or submit a processing application.

Method-to-component comparison

Complete this for the method and integration actually used. The Stripe support statements below concern ACH Direct Debit only. A supported component is a candidate route until account permission, configuration and the installed integration are established.

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.