10.6.0

  • alcym

    (@alcym)


    1 month, 1 week ago

    The latest Stripe plugin update (10.6.0) is double charging every single subscription renewal. Every customer with a recurring payment is being billed twice. This is not an edge case — it is happening on every renewal without exception.

    Our site auto-updated from 10.5.3 to 10.6.0 this morning. Within an hour, customers started getting double charged. We had to emergency-deactivate WooCommerce Subscriptions to stop the bleeding, manually refund over a dozen customers, and eat the Stripe processing fees on every duplicate charge.

    We traced it through Stripe’s API logs. For every renewal, two separate payment intents are being created 3-5 seconds apart with different idempotency keys. The Stripe webhook is arriving between the two and triggering a second payment before the first one finishes processing. Rolling back to 10.5.3 immediately fixed the problem.

    This is directly related to the race condition reported in your GitHub issues #3568 and #5042 — the order locking fix you shipped in 9.6.0 does not cover the subscription renewal path.

    What is also concerning is why does it say say her eon ww.wp.xz.cn that 10.5.3 is the latest version, when 10.6.0 is what’s actually the latest version (and listed on the WooCommerce ) ? That means other stores with WooCommerce Subscriptions are potentially updating this and may also be silently double charging their customers. After rolling back to 10.5.3 the issue was resolved.

    There are few bugs bug serious than charging customers twice!

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support shahzeen(woo-hc)

    (@shahzeenfarooq)

    1 month, 1 week ago

    Hi there,

    We completely understand how serious and frustrating this situation is especially given the impact on your customers and the time spent handling refunds. Double charging is definitely not something to take lightly, so we appreciate you sharing such detailed findings.

    It’s good to hear that rolling back to 10.5.3 stabilized things on your end. Based on what you’ve described, this does sound like something that needs deeper investigation, and we’d strongly recommend escalating this internally so the development team can review it further.

    To help move this forward as quickly as possible, could you please share a few additional details:

    • Your System Status Report (WooCommerce → Status → Get system report)
    • Stripe logs from the time the issue occurred

    To enable and collect the Stripe logs:

    1. Go to WooCommerce → Payments → Stripe → Settings
    2. Scroll to the Advanced tab and enable Error Log
    3. Then go to WooCommerce → Status → Logs
    4. Open the log file related to Stripe payments
    5. Copy the relevant entries and share them here

    Please use https://pastebin.com/ or https://gist.github.com/ and share a link to that paste in reply here. This will help us better understand the behavior you’re seeing and support escalation to the appropriate team.

    Regarding the version mismatch you mentioned, we understand how that can be confusing, and we’ll flag that internally as well so it can be reviewed.

    Thanks again for bringing this to attention once we have the logs and report, we’ll be in a better position to assist further.

    Plugin Support shahzeen(woo-hc)

    (@shahzeenfarooq)

    1 month, 1 week ago

    Hi there!

    This is a follow-up message to inform you that our team has already been able to replicate the issue, and there is no need to share any further details at this time. Here is the github bug link: https://github.com/woocommerce/woocommerce-gateway-stripe/pull/5325 for further updates.

    They are currently working on a fix and will release it as soon as possible. In the meantime, the workaround for this issue is to disable the “Optimized Checkout” option under WooCommerce → Settings → Payments → Stripe → Settings.

    I’m sharing this solution in case anyone else encounters the same issue, so they can use the workaround until the fix is released.

    Thank you for your cooperation and understanding.

Viewing 2 replies - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.