Stripe Charged the Wrong Amount in WooCommerce? Causes & Fix

The WooCommerce order says one number; the Stripe dashboard says another. Sometimes that gap is money you genuinely never received — and in July 2026 there is one specific, patched gateway bug to rule out first. Here's how to tell a real undercharge from a fee, a currency conversion or an uncaptured charge.

Last updated: 17 Jul 2026 · ~7 min read

What "Stripe charged the wrong amount" actually means

There are three different numbers in play, and most of the panic comes from comparing the wrong two. The order total is what WooCommerce recorded at checkout. The charge is what Stripe actually collected from the customer's card. The payout is what lands in your bank — the charge minus Stripe's fees, usually bundled with other orders.

A payout that's smaller than the order total is normal. A charge that's smaller than the order total, in your own store currency, is not — that difference is money you never received, and the customer has a receipt for the lower figure. The causes below are ordered so you rule out the genuine loss first.

The most common causes (most likely first)

1. The Adaptive Pricing bug in Stripe gateway 10.6.0–10.8.3 (patched 14 July 2026)Your gateway version is in that range and Adaptive Pricing is on — note that 10.8.x could switch it on automatically after an update, so "I never enabled that" doesn't clear you. The charge in Stripe is lower than the order total, and in the GitHub reports the missing amount was exactly the shipping cost plus its tax. WooCommerce's official advisory confirms the payment processed by Stripe could differ from the order total under these conditions.
2. You're comparing the payout, not the chargeThe difference is small and roughly proportional per order — it's Stripe's processing fee. Open the payment in Stripe: if the charge itself matches the order total, no money is missing. The payout is always the charge minus fees, and a single payout often bundles several orders, which makes eyeball comparisons misleading.
3. Adaptive Pricing converted the currency — the number is different, not wrongThe charge is in a different currency from your store. Adaptive Pricing lets the customer pay in their local currency while you're still paid out in your store currency, so the raw figure on the charge won't match the order total. Check the converted amount on the payment instead before concluding anything was lost.
4. An Apple Pay / Google Pay total built from a partial addressOnly express-checkout (wallet) orders are affected, and the gap is the tax or shipping. Before payment is authorised, the wallet only shares a partial address with your store — postcodes can arrive truncated, and the billing address isn't available at all until after authorisation — so tax or shipping worked out in the wallet sheet can differ from what the full checkout page would have calculated.
5. The charge was authorised but never captured (or captured late)The payment shows as uncaptured in Stripe, or disappeared entirely after a week. With the gateway's Capture charge immediately setting unticked, checkout only places an authorisation — you have to capture it yourself, and uncaptured charges expire in 7 days, after which no money moves at all.
6. The order changed after the payment was takenThe charge was right when it was made. The order notes show a partial refund, an added fee, or an item edit dated after the payment — the WooCommerce total moved, the Stripe charge didn't. Nothing to fix on the gateway side.

Where to look first

• Open the payment in Stripe (Payments in the Stripe dashboard — searching the customer's email finds it fastest) and compare the charge amount and currency against the WooCommerce order total. Charge matches, payout doesn't? That's fees — cause 2, and you're done.
• Charge in a different currency? That's Adaptive Pricing's conversion at work — cause 3. Compare the converted amount on the payment before assuming a loss.
• Charge genuinely lower in your store currency? Check the WooCommerce Stripe Payment Gateway version on your Plugins screen. Anything from 10.6.0 to 10.8.3 with Adaptive Pricing on is cause 1: update to 10.6.2, 10.7.1 or 10.8.4+ now, or untick Adaptive Pricing in the Stripe settings until you can.
• Was it a wallet order? If the shortfall is exactly the tax or shipping and the order came through Apple Pay or Google Pay, that's cause 4 — the wallet sheet priced from a partial address.
• Charge sitting as uncaptured? Check the Capture charge immediately setting in WooCommerce → Settings → Payments → Stripe — cause 5. Capture anything outstanding before the 7-day expiry.

How to know you fixed it

Frequently asked