WooCommerce reported a payment validation issue in Stripe for WooCommerce 10.6.0 through 10.8.3 when Adaptive Pricing is enabled. Patched versions are 10.6.2, 10.7.1, and 10.8.4. The useful response is to update first, then compare WooCommerce order totals with the Stripe PaymentIntent amount and currency for the affected window.
Use this for merchants, agencies, and finance teams that operated an affected Stripe for WooCommerce version, especially stores with multiple currencies, tax changes, discounts, partial refunds, or manual order edits.
Quick answer
Confirm the installed Stripe extension is on a patched line, record when the patch completed, and export candidate orders from the affected period. For each order compare line items, discount, shipping, tax, order currency, exchange-rate context, WooCommerce total, Stripe amount, refund activity, and settlement. Escalate any unexplained difference before issuing corrective payments.
What to check first
- Record the exact Stripe for WooCommerce version, Adaptive Pricing state, WooCommerce version, active currency configuration, patch timestamp, and affected sales window.
- Export WooCommerce order IDs with totals, currency, tax, discounts, shipping, status, payment method, transaction ID, refunds, and order-note timestamps.
- Match each transaction ID to its Stripe PaymentIntent, amount, currency, captured amount, refunded amount, dispute state, balance transaction, and creation time.
- Separate expected exchange-rate or rounding differences from mismatches between the order total and the amount that Stripe processed.
- Run controlled test orders after patching across base currency, Adaptive Pricing currency, coupon, tax, shipping, refund, and failed-payment paths.
Diagnostic table
Use this table to keep the work practical. It connects the symptom to evidence and a verification step.
| Action | Evidence to collect | How to verify |
|---|
| Patch the affected release line | Record the exact Stripe for WooCommerce version, Adaptive Pricing state, WooCommerce version, active currency configuration, patch timestamp, and affected sales window. | Every managed site reports a patched version and its Adaptive Pricing state. |
| Define the review window | Export WooCommerce order IDs with totals, currency, tax, discounts, shipping, status, payment method, transaction ID, refunds, and order-note timestamps. | Candidate orders join to one expected PaymentIntent and currency. |
| Join orders to PaymentIntents | Match each transaction ID to its Stripe PaymentIntent, amount, currency, captured amount, refunded amount, dispute state, balance transaction, and creation time. | Every non-zero difference has a documented cause, owner, and customer action. |
| Classify every difference | Separate expected exchange-rate or rounding differences from mismatches between the order total and the amount that Stripe processed. | Post-patch test orders match across WooCommerce, Stripe, refunds, and reporting. |
Why this usually happens
- The order and payment systems store money in different units and may present converted amounts differently.
- Manual order changes or refunds after capture can make current order totals differ from the original charge without indicating the advisory issue.
- Automatic updates can leave some sites on another release line or can fail silently because of filesystem or deployment controls.
- A dashboard total can hide the exact PaymentIntent amount, currency, and event sequence needed to explain the case.
Useful command or data shape
Adapt paths, IDs, and privacy handling to the site before running commands or storing data on production.
order_id: 18422
plugin_version: 10.8.4
adaptive_pricing: enabled
order_currency: EUR
order_total_minor: 12840
payment_intent: pi_redacted
stripe_amount_minor: 12840
refunded_minor: 0
difference_minor: 0
Safe fix order
Do the work in a sequence that makes each result easy to prove. Stop if a step produces new evidence that changes the incident scope.
- Patch the affected release line
- Define the review window
- Join orders to PaymentIntents
- Classify every difference
- Retest and monitor
Decision rule
A case is reconciled only when the WooCommerce total at capture time equals the Stripe amount for the same currency, or a documented conversion, refund, or later order edit explains the difference. Do not treat current order total alone as historical payment evidence.
What to tell the client or owner
Share the site, plugin version before and after patching, Adaptive Pricing state, review window, order ID, transaction ID, currency, minor-unit totals, refund and dispute state, mismatch classification, customer action, and final verification.
Production verification checklist
- Every managed site reports a patched version and its Adaptive Pricing state.
- Candidate orders join to one expected PaymentIntent and currency.
- Every non-zero difference has a documented cause, owner, and customer action.
- Post-patch test orders match across WooCommerce, Stripe, refunds, and reporting.
Mistakes to avoid
- Do not compare formatted currency strings instead of integer minor units.
- Do not issue refunds before checking existing refunds and disputes.
- Do not assume the latest plugin label proves the patch ran on every web node.
- Do not mix payment-date exchange rates with current rates.
Questions teams ask during testing
Which Stripe for WooCommerce versions were affected?
WooCommerce lists 10.6.0 through 10.8.3 when Adaptive Pricing is enabled. The advisory names 10.6.2, 10.7.1, and 10.8.4 as patched versions for those release lines.
Should every order in the period be refunded?
No. Reconcile first. A refund is a financial decision for a confirmed case, not a substitute for matching the WooCommerce order, Stripe payment, currency, and later adjustments.
When HandL WP should help
HandL WP can inventory affected stores, complete the patch, join WooCommerce orders to Stripe evidence, isolate real mismatches, test the checkout matrix, and produce a finance-ready exception report.
If this is active on a production site, audit Stripe Adaptive Pricing payments.
Related HandL WP guides
Use these related guides when the same issue touches tracking, security, checkout, or crawler visibility.
Helpful references