Refunds are recorded twice in WP admin

@aaires – I believe this is related to the following issue: https://github.com/woocommerce/woocommerce-gateway-stripe/issues/838

Can you verify that when you say “when webhook is used”, are you referring to the Webhook Secret in your Stripe Payment settings in WooCommerce?

– Joey

Hi Joey,

yes it is related with the issue you mentioned.
When I say webhook I mean that it happens when we issue a refund through the website backoffice stripe runs a callback to the website and process a second refund.

Thank you

Hey @aaires

Can you confirm if this happens for every transaction that you refund?

For your webhook events, can I ask you to check and confirm what you use, please?
Click into your site URL from here – https://dashboard.stripe.com/webhooks and if you are using “All events”, can you press “Update details”, clear, then add these 12 events, please?

payment_intent.amount_capturable_updated
payment_intent.payment_failed
payment_intent.succeeded
review.closed
review.opened
source.canceled
source.chargeable
charge.refunded
charge.dispute.created
charge.succeeded
charge.failed
charge.captured

Having only those needed event types will reduce some of the load put on the webhook.

Let me know how you get on!

Thanks,

On our sites, it is every refund.

We will also adjust webhook entries if it helps?

– jeff

@dougaitken It does not happen on every refund.

I’ll see if you suggestion helps solving the issue.

Many thanks.

Hi @jeffpyebrookcom

Yes, please. I cannot say that this will resolve this but if you are seeing this on every refund then this would be a near term possible solution.

Do let us know how you get on!

Also, if you’re able to let us know any additional details on this thread or that GitHub Issue to narrow down the cause, we’d love to hear it!

Thanks,

Hi @jeffpyebrookcom @aaires

We haven’t heard back from you in a while – I do hope this means adjusting the webhook types helped. I’m going to mark this as resolved – if you have any further questions, you can start a new thread.

Thanks,