A public support thread reported a WooCommerce order total of 43.52 euros while Stripe captured 40.95 euros, with the missing 2.57 euros matching shipping plus VAT on shipping.

Does this prove a universal WooCommerce Stripe bug?

No. Plugin support said they could not reproduce the issue and that it may already have been resolved by recent updates or another plugin change. The correct action is targeted order-level auditing.

What should affected stores do first?

Compare WooCommerce totals to Stripe captured amounts for orders in the exposure window, focusing on shipping, VAT, Adaptive Pricing, classic checkout, and any shipping-calculator plugins.

WordPress plugin change record

WooCommerce Stripe charged an order without shipping cost

Reviewed July 6, 2026Evidence confidence: Single public report plus support guidance; not a confirmed universal bugPrimary domain: Revenue / reconciliation

Current decisionIf Stripe captured less than the WooCommerce order total, do not treat the order as fully reconciled just because WooCommerce says paid. Audit the individual Stripe transaction, identify the missing amount, and handle the difference manually before closing accounting or fulfillment follow-up.

A public WooCommerce Stripe support thread reported an order where WooCommerce recorded 43.52 € including shipping and VAT, while Stripe captured only 40.95 €. The missing 2.57 € matched shipping plus VAT on shipping. The store was using WooCommerce Stripe Gateway 10.7.x when the affected order occurred, and the user said the issue had not reappeared after updating.

Plugin support said recent Adaptive Pricing, Optimized Checkout, checkout-update, and payment/session fixes may be related, but they did not confirm a universal root cause. Support recommended checking the Stripe Dashboard for the exact amount captured and handling the outstanding balance manually for the affected order.

This is a reconciliation problem, not just a plugin-update problem.If Stripe captured less than WooCommerce recorded, the accounting reality follows the captured Stripe amount.

What changed?

10.7.x: the reported under-captured order occurred on this release line.
10.8.0: Optimized Checkout Suite and Adaptive Pricing were enabled by default for eligible stores.
10.8.2 / 10.8.3: recent fixes touched Adaptive Pricing, checkout sessions, and payment handling, but support did not confirm a specific fix for the reported shipping/VAT mismatch.

Who is affected?

This record matters most for stores that used WooCommerce Stripe 10.7.x or early 10.8.x, had Adaptive Pricing enabled, used classic checkout, had shipping calculators or custom shipping/VAT logic, and saw Stripe capture less than the WooCommerce order total. It does not imply every 10.7.x store undercharged shipping.

What should you do?

Your situation	Primary decision	Safeguard
One order is fully paid in WooCommerce but Stripe captured less	Reconcile manually	Compare order total, shipping, tax, discounts, currency, Stripe captured amount, fees, and payout
The missing amount equals shipping or shipping tax	Audit shipping logic	Check shipping plugins, VAT settings, Adaptive Pricing, and checkout type before assuming Stripe is wrong
No new cases after updating	Monitor, do not overcorrect	Sample recent orders and keep a mismatch log for at least one sales cycle
Repeated mismatches are found	Escalate privately	Collect affected order IDs, Stripe transaction IDs, screenshots, system status, and Stripe logs

Safest audit sequence

Define the exposure window. Start with the period when 10.7.x or early 10.8.x was active.
Export suspect orders. Prioritize Stripe orders with shipping, VAT on shipping, discounts, multi-currency, or Adaptive Pricing.
Compare order-level totals. For each suspect order, compare WooCommerce total, Stripe captured amount, shipping, tax, discounts, currency, and payout.
Handle confirmed gaps individually. Support guidance in the thread suggested a manual order/payment link for the outstanding balance when Stripe captured less.
Update only after staging. Test latest Stripe Gateway with the same shipping, tax, and currency scenario before production deployment.
Monitor the next real orders. Compare Stripe and WooCommerce immediately for several orders after the update.

What is not yet proven?

The evidence does not prove a widespread Stripe 10.7.x shipping bug or a guaranteed fix in a specific later version. It proves a decision need: when WooCommerce and Stripe disagree on the amount captured, stores need transaction-level reconciliation before they assume the order was fully paid.

Escalate when: multiple orders are missing shipping or tax, the mismatch crosses currencies, refunds no longer match collected totals, or your accounting export assumes WooCommerce's higher amount instead of Stripe's captured amount.

Update log

June 8, 2026

Stripe Gateway 10.8.0 enabled Optimized Checkout Suite and Adaptive Pricing for eligible stores.

June 15, 2026

Stripe Gateway 10.8.2 added several Adaptive Pricing and payment-status fixes.

Late June 2026

A public support thread reported a 10.7.x order where Stripe captured less than the WooCommerce total by the shipping-plus-VAT amount.

July 6, 2026

This decision record was created from the official changelog and support thread.

Official sources

This is independent technical research, not official WooCommerce, Stripe, tax, or accounting advice. Verify your own transactions before contacting customers or adjusting financial records.