Before sending campaign traffic to a WooCommerce store, write down the routes shoppers can actually use to buy. Reaching the regular checkout page answers one question. A wallet button on a product or cart page introduces another route that deserves its own review. This guide uses the current WooPayments documentation to help you keep those checks and their evidence clear.
List the payment routes you offer
Start with the payment extension and methods your store already offers. WooPayments documents different behavior for its express methods, including button placement, browser support and product conditions. Use the documentation for the extension installed on your store. Settings or results from another gateway should not be assumed to apply.
Make a small review list for your team: the method, the page where shoppers encounter it, a representative product, and the device and browser being used. Mark anything you have not checked as unverified. The point is to make the coverage understandable before a campaign, rather than treating one successful visit as evidence for every route.
Review button visibility in the intended context
For Apple Pay through WooPayments, the official guide describes configurable placement on product, cart and checkout pages. Review the locations intended for your store, then inspect them using an eligible device and browser. A missing button needs context before it is treated as a checkout fault.
The same guide distinguishes seeing an Apple Pay button from being able to finish a purchase: a card in Apple Wallet is required for the purchase, but not for the button to appear. Record what you observed precisely. Button visibility, opening a wallet interface and completing a test payment are different observations.
Give required product information a separate check
Review any information your business needs from the customer, such as a required checkout field. WooPayments specifically documents that fields added by the Checkout Field Editor extension are not collected through Apple Pay, Google Pay and Amazon Pay because those methods bypass the usual checkout form. This is a specific compatibility note, not a rule for every field extension.
If your process depends on that information, have the responsible developer review the actual combination before you rely on it. Include the relevant product type and account requirements in the review. Keep any open compatibility question visible in the campaign handover, with a named person responsible for the next check.
Keep wallet testing separate from monitoring
Our StoreCalm checkout checks use an isolated, anonymous cart and stop before order submission and payment. Healthy describes one configured run reaching the expected checkout. It does not verify wallet authorization, a completed payment or every gateway. Inconclusive requires investigation and is not Healthy.
For payment acceptance, arrange a controlled test with the responsible team using the provider's documented test process. WooPayments has separate instructions for testing each express method. Do not assume that the test-card steps for the ordinary card form are also the wallet procedure. Plan the session so payment settings are not changed casually while shoppers are placing real orders.
WooPayments also explains that test-mode payments create WooCommerce orders. Review the resulting order and transaction evidence as described in its testing guide. Keep test records clearly identified, and review any connected fulfillment or notification workflow as part of your team's test plan. A test result should describe the method and environment actually used.
Leave a clear campaign decision
Record the date, extension configuration, product and device context alongside each observation. Separate confirmed results from work still waiting for review. After a relevant checkout change, repeat the affected route and compare like with like. This gives the next person a practical record of what was checked and what remains uncertain.
StoreCalm provides ongoing availability and checkout-readiness monitoring within its published scope. Our product guide and plans are linked below, together with the free StoreCalm Connector download. Use monitoring alongside the separate acceptance work your store needs, so the meaning of each result stays clear.
Sources and further reading
- StoreCalm: Checkout monitoring guide
- StoreCalm: Free Connector and download
- WooCommerce: WooPayments express checkout compatibility
- WooCommerce: Accepting Apple Pay with WooPayments
- WooCommerce: Testing WooPayments
Sources checked on 26 October 2026.