Revenue-stack breakage radar

WooCommerce checkout, payment, and reconciliation breakages we’re tracking

Use this when a software update or payment-flow issue may affect real orders: checkout availability, captured funds, order status, totals, shipping, tax, refunds, webhooks, payouts, or accounting reconciliation.

Open recovery checklist Get payment-stack alerts

Current read

The strongest validation pattern for What Just Changed is not broad WordPress plugin news or broad API-change summaries. It is urgent revenue operations: a customer paid, checkout changed, an order stayed pending, the processor total disagreed with WooCommerce, or a webhook/capture/reconciliation path became risky.

Use this tracker when: a WooCommerce store owner, developer, or agency needs to quickly triage whether a payment-stack change could affect real orders, checkout, captured funds, refunds, shipping, taxes, accounting, or customer support.

Evidence status labels

StatusMeaningHow to treat it
Confirmed fixA vendor changelog, issue, or official source explicitly identifies the defect/fix.Follow the vendor-supported update path, then reconcile affected orders.
Vendor acknowledgedAn official support channel, GitHub issue, or vendor response recognizes the behavior.Preserve evidence and monitor for the official fix or workaround.
Diagnostic matchThe symptoms match a known pattern, but causality is not fully confirmed.Verify your own order, gateway, webhook, and amount evidence before making changes.

Tracked revenue breakages

IssuePrimary riskFirst action
Payment succeeded but WooCommerce order stayed PendingMoney may have moved while fulfillment/order state stayed wrongFreeze evidence and reconcile gateway transaction state against WooCommerce order state
WooCommerce Stripe 10.8.x payments stuck in Pending PaymentSuccessful payments may not move orders correctlyReconcile paid Stripe transactions against WooCommerce order status
WooCommerce Stripe 10.8.3 checkout error after updateCheckout may fail or payment methods may not loadClear cache layers, exclude Stripe.js, and check Adaptive Pricing / WooPayments conflicts
WooCommerce PayPal 4.0.4 discount applied twice / amount mismatchPayPal and WooCommerce totals may disagreeAudit discounted, gift-card, negative-fee, and tax-sensitive PayPal orders
Stripe charged an order without shipping costStripe may capture less than the WooCommerce order totalCompare captured Stripe amounts against shipping, VAT, discounts, and order totals
Stripe captures only 1/100 amount with WPML Multi-CurrencyCurrency/decimal handling may undercharge ordersPause the risky currency path and compare captured amounts order by order
PayPal total missing shipping in WooCommerceShipping may not be collected in the PayPal totalCheck PayPal transaction total against shipping, shipping tax, coupons, and payouts
PayPal/card payments fail intermittently with OrderProcessor.php:109Some valid payment attempts may fail while others succeedPreserve logs, compare success/failure cases, verify captures, and escalate with evidence
Mollie cancelled payment order note loopRepeated order notes can create database bloat and server loadBack up, stop the loop, preserve evidence, and clean duplicates only after containment
Mollie removed Payconiq from its WooCommerce pluginA payment method may disappear after updatePrepare a tested replacement checkout method before updating affected stores

How to triage a revenue-stack issue

  1. Separate plugin noise from money risk. Ask whether checkout, capture, order status, refunds, shipping, tax, payouts, or accounting could be wrong.
  2. Identify the exposure window. Record plugin versions, update time, checkout type, payment method, cache/CDN state, and relevant integrations.
  3. Reconcile real orders. Compare WooCommerce totals and statuses against Stripe, PayPal, Mollie, WooPayments, payouts, refunds, and customer receipts.
  4. Preserve evidence before cleanup. Save system status, order IDs, payment IDs, logs, screenshots, and timestamps before clearing caches or deleting notes.
  5. Change one variable at a time. Use staging where possible. Do not update, disable plugins, change payment settings, clear caches, and delete evidence all at once.
What this tracker is not: It is not official support, legal advice, tax advice, or accounting advice. It is an evidence-backed triage layer that points to the smallest justified next action.