If a WooCommerce payment method is missing from the Checkout Block, an enabled gateway is only the first requirement. The extension must support the block checkout, and the method must be eligible for the current cart, address, currency, and customer. A subscription product can narrow the list again because the gateway must support the required renewal process.
This guide is for the hands-on owner of a growing store that sells subscriptions and physical goods at about 20–40 orders a day. A payment extension update or a move from Classic Checkout to the Checkout Block caused the search. The goal is to find which availability check removed the method, without testing risky changes on the live checkout.
Why an enabled payment method can still disappear
The Checkout Block builds its payment list dynamically. WooCommerce shows methods that are available in the store and compatible with the block. Each registered method also runs an availability check against the live cart. The check can use the products, totals, shipping need, customer addresses, selected shipping method, and payment requirements.
This explains a common confusing result: a method can appear in the editor preview or in WooCommerce > Settings > Payments, but not appear to the shopper. WooCommerce developer documentation states that the editor assumes a method is available, while the storefront runs its availability callback. Test the actual checkout page with a controlled cart.
| Symptom | Most useful first test |
|---|---|
| Method appears in Classic Checkout but not the Checkout Block | Check the extension’s current block compatibility |
| Method appears for a normal product but not a subscription | Check automatic or manual renewal support |
| Method appears for one country or currency only | Check the provider’s location and currency rules |
| All methods disappeared after an update | Confirm the assigned checkout page, enabled methods, and JavaScript errors |
| A wallet appears on one device but not another | Check device, browser, region, and wallet eligibility |
Run these eight checks in order
1. Reproduce the exact missing-method case
Use a staging copy and the payment provider’s test or sandbox mode. Record the extension version, WooCommerce version, active checkout type, cart contents, currency, billing country, shipping country, and customer state. Test the same conditions after each change.
- One ordinary physical product
- One subscription product
- The mixed cart that produced the problem
If the method works for the first cart but not the second, the Checkout Block itself is probably loading. Move to the subscription check instead of rebuilding the page.
2. Confirm the real checkout page and its Payment Options block
Go to WooCommerce > Settings > Advanced and confirm which page is assigned as Checkout. Edit that page or its Checkout template. Use List View to confirm that the main Checkout block still contains Payment Options. A duplicate page, an old shortcode page, or a checkout builder can make you edit one page while shoppers use another.
Open the assigned URL in a private window and add a real test product through the normal cart flow. Do not use the block editor preview as proof that the method is available to a shopper.
3. Check the gateway, connection, and operating mode
In WooCommerce > Settings > Payments, confirm that the intended gateway is enabled. Open its settings, confirm that the account connection or API credentials are complete, save the page, and check whether the extension reports an account restriction. Confirm that the store and your test use the same mode. Live credentials do not belong in a sandbox test, and test credentials do not accept live payment details.
Some gateway plugins have a main enable switch and separate switches for cards, local methods, or express wallets. For example, WooPayments and Stripe for WooCommerce document method-level settings. Check the current documentation for the exact extension you installed.
4. Verify Checkout Block support for that extension version
A payment gateway that works with the classic shortcode does not automatically work with the Checkout Block. The extension must register a server-side payment integration and a front-end payment method. WooCommerce compares those registrations. If the gateway exists only on the server side, WooCommerce treats it as not compatible with the block checkout.
Check the vendor’s current product page, compatibility table, changelog, and documentation. Look for explicit support for Cart and Checkout Blocks, not a general statement that the plugin supports WooCommerce. Update the extension on staging and repeat the same cart test. If the vendor does not claim block support, ask for a supported version or choose a gateway extension that documents the required checkout and subscription features.
5. Test the cart, address, currency, and shipping conditions
Complete every required billing and shipping field before you decide that a method is missing. Payment methods can use the cart total, physical shipping need, selected shipping rate, address, currency, and other requirements when they report availability. A local method can remain hidden until the customer enters an eligible country and currency. Cash on Delivery can also depend on the selected shipping method.
Change one condition at a time. Use a supported country, the store’s normal currency, a valid postcode, and a standard shipping rate. Then restore the original value. This test identifies an intended eligibility rule without disabling every conditional-payment setting.
6. Isolate the subscription filter
WooCommerce Subscriptions filters payment gateways when the cart contains a subscription. If manual renewals are not enabled, the checkout offers gateways that support automatic recurring payments. When manual renewals are enabled, any enabled gateway can be offered for a manual renewal workflow. Gateway support also varies by feature and by payment method inside one extension.
Do not assume that every method under one provider has the same renewal support. WooCommerce documents, for example, that some alternative methods within a gateway can accept one-time orders but cannot process automatic renewals. Compare the exact extension and payment method with the current Subscriptions payment gateway table. Before you replace an extension, ask the provider how it will handle existing saved payment methods and renewals.
7. Test wallets and express methods on an eligible device
Apple Pay, Google Pay, and other express methods are conditional interfaces, not permanent checkout labels. Their appearance can depend on the device, browser, region, currency, wallet setup, and whether the customer has an eligible saved payment method. Test the normal card method separately from its express wallet. Use the gateway’s own device and region checklist before you treat one missing button as a Checkout Block failure.
8. Check conflicts, scripts, caches, and logs
On staging, keep WooCommerce, the payment extension, and WooCommerce Subscriptions active when the cart needs it. Temporarily disable checkout builders, conditional payment plugins, script optimization, consent tools, security filters, and other checkout extensions. Switch to Storefront or a current default WordPress theme. Reactivate one item at a time and repeat the same test.
Exclude Cart, Checkout, and My Account from page caching. Clear the relevant cache after a settings change, then inspect the browser console for a failed payment script or Store API request. Enable the gateway’s debug logging only while you reproduce the problem, then read the result under WooCommerce > Status > Logs. Also save the System Status report. Remove customer details and credentials before you share any log or report.
Choose the smallest safe fix
| Cause | Practical fix |
|---|---|
| Gateway was disabled or disconnected | Correct its settings and test in the proper mode |
| Gateway extension lacks block support | Update it, use a documented compatible extension, or use Classic Checkout temporarily |
| Subscription cart removes the method | Choose a method that supports the required renewal model |
| Country, currency, shipping, or wallet rule removes it | Correct the rule or customer eligibility; do not force an unsupported method |
| Another extension breaks registration or scripts | Update, replace, or remove the confirmed conflicting component |
WooCommerce provides a supported way to transform the Checkout block to Classic Shortcode. Use that as a controlled temporary fallback when a required extension is not block-compatible. WooCommerce advises reverting both Cart and Checkout together. Test taxes, shipping, coupons, account creation, one-time payments, subscription sign-ups, and mobile checkout before you make the change live.
A missing payment method is not one problem. It is the visible result of a failed compatibility or eligibility check. When you keep the cart and customer conditions constant, you can identify that check and fix it without changing more of the checkout than necessary.
Sources
- WooCommerce: Checkout Block
- WooCommerce: Customizing Cart and Checkout, including compatibility and Classic Checkout
- WooCommerce developer documentation: Payment method integration
- WooCommerce developer documentation: How the Checkout Block processes an order
- WooCommerce Subscriptions: Payment methods and gateways
- WooCommerce: Troubleshoot payment errors
- WordPress.org support thread: merchant wording reference (used for problem language, not technical proof)
Clif Griffin
WooCommerce is my patronus. Husband of Jennifer. Father of three. Believer.