Payment intent using old webhook_id

  • philc87

    (@philc87)


    1 year, 4 months ago

    On a site using WooCommerce Subscriptions, a customer’s monthly payment was taken twice. Checking in Stripe, the payment metadata had an incorrect webhook_id. So I think the first payment sent confirmation to an incorrect webhook_id, which means WooCommerce never received it and did not know the payment was successful and therefore tried again on the next cron.

    I searched the site database for the same incorrect webhook_id, and I can see it in a lot of postmeta with name ‘_payment_intent’.

    Should I search and replace the old webhook_id with the correct one? Will that fix this type of issue or is it likely to cause further issues?

    Thanks for any help/advice

    Viewing 1 replies (of 1 total)
    • Plugin Author Clayton R

      (@mrclayton)

      1 year, 4 months ago

      Hi @philc87

      The webhook_id in the metadata of the payment intent does not control where notifications are sent, it’s just a helper property used by the plugin to know if it should process the incoming webhook. It’s very common for merchants to use the same Stripe account on multiple websites, so the webhook_id in the metadata helps keep track of where a request originated from.

      The stripe.com > developers > webhooks page is where Stripe keeps track of where notifications are sent.

      Also, webhooks don’t control when a Woo Subscription is processed. That’s managed by Woo Subscriptions via a scheduled action in the WordPress actions table.

      Kind Regards

    Viewing 1 replies (of 1 total)

    The topic ‘Payment intent using old webhook_id’ is closed to new replies.