Current read
The strongest early validation pattern for What Just Changed is not broad WordPress plugin news. It is urgent WooCommerce payment operations: checkout availability, payment capture, order totals, shipping/tax mismatches, payment methods, and database/server-load problems caused by payment flows.
Use this page when: a WooCommerce store owner, developer, or agency needs to quickly triage whether a payment-plugin change could affect real orders, checkout, captured funds, refunds, shipping, taxes, accounting, or customer support.
Tracked payment issues
| Issue | Primary risk | First action |
|---|---|---|
| WooCommerce Stripe 10.8.x payments stuck in Pending Payment | Successful payments may not move orders correctly | Reconcile paid Stripe transactions against WooCommerce order status |
| WooCommerce Stripe 10.8.3 checkout error after update | Checkout may fail or payment methods may not load | Clear cache layers, exclude Stripe.js, and check Adaptive Pricing / WooPayments conflicts |
| WooCommerce PayPal 4.0.4 discount applied twice / amount mismatch | PayPal and WooCommerce totals may disagree | Audit discounted, gift-card, negative-fee, and tax-sensitive PayPal orders |
| Stripe charged an order without shipping cost | Stripe may capture less than the WooCommerce order total | Compare captured Stripe amounts against shipping, VAT, discounts, and order totals |
| Stripe captures only 1/100 amount with WPML Multi-Currency | Currency/decimal handling may undercharge orders | Pause the risky currency path and compare captured amounts order by order |
| PayPal total missing shipping in WooCommerce | Shipping may not be collected in the PayPal total | Check PayPal transaction total against shipping, shipping tax, coupons, and payouts |
| PayPal/card payments fail intermittently with OrderProcessor.php:109 | Some valid payment attempts may fail while others succeed | Preserve logs, compare success/failure cases, verify captures, and escalate with evidence |
| Mollie cancelled payment order note loop | Repeated order notes can create database bloat and server load | Back up, stop the loop, preserve evidence, and clean duplicates only after containment |
| Mollie removed Payconiq from its WooCommerce plugin | A payment method may disappear after update | Prepare a tested replacement checkout method before updating affected stores |
| WooCommerce PayPal enabled Pay with Crypto by default | Payment-method mix may change without store-owner intent | Inspect payment settings and checkout before assuming the old configuration remained unchanged |
How to triage a payment issue
- Separate search noise from money risk. Ask whether checkout, capture, order status, refunds, shipping, tax, payouts, or accounting could be wrong.
- Identify the exposure window. Record the plugin version, update time, checkout type, payment method, cache/CDN state, and relevant integrations.
- Reconcile real orders. Compare WooCommerce totals and statuses against Stripe, PayPal, Mollie, payouts, refunds, and customer receipts.
- Preserve evidence before cleanup. Save system status, order IDs, payment IDs, logs, screenshots, and timestamps before clearing caches or deleting notes.
- Change one variable at a time. Use staging where possible. Do not update, disable plugins, change payment settings, and clear 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.