What Just Changed turns payment-stack failures into practical recovery records: what changed, who is affected, what can break, how to verify it, and the safest next action before real revenue gets mishandled.
Current product direction: the broad API-change test got impressions but no clicks. The only pages that actually earned Google clicks were urgent WooCommerce/Stripe payment and checkout problems. So the site is now focused on ecommerce revenue-stack breakage: checkout failures, pending orders, amount mismatches, shipping/tax undercollection, refunds, webhooks, and reconciliation.
Freeze evidence, compare gateway transaction state against WooCommerce order status, check webhook delivery, reconcile totals, and avoid duplicate fulfillment or refunds.
Open the checklistSuccessful Stripe payments may not move WooCommerce orders correctly. First action: reconcile paid Stripe transactions against store order status before manually changing orders.
Read the issue recordCheckout errors after a plugin update can stop revenue immediately. First action: check cache layers, Stripe.js loading, Adaptive Pricing, and WooPayments conflicts.
Read the issue recordGateway totals and WooCommerce totals can disagree because of discounts, shipping, tax, currency, rounding, or refund handling. First action: compare captured amount against every order-total component.
Read the PayPal mismatch recordThe product being tested is simple: save your WooCommerce payment stack and get notified when a Stripe, PayPal, Mollie, WooPayments, checkout, webhook, refund, total, or reconciliation issue could affect real orders.
The API pivot produced impressions but did not produce clicks. Those records remain available as a secondary archive while the site tests the more urgent revenue-breakage angle.
Open API archive