woocommerce / woocommerce-gateway-stripe

The official Stripe Payment Gateway for WooCommerce
https://wordpress.org/plugins/woocommerce-gateway-stripe/
232 stars 203 forks source link

single order, dublicate payment processed on stripe #3220

Closed heavestudio closed 3 months ago

heavestudio commented 3 months ago

Using both woocommerce subscription and woocommerce stripe payment gateway.

everything was working fine, but for more than a week i can see that every order on the website create two payment request on stripe.

Only one api webhook active.

Tried to remove totaly the connection between the site and stripe and reset.

Change the way cron are triggered.

Nothing changes, still have a duplicate payement for every order

Describe the bug A clear and concise description of what the bug is.

To Reproduce Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior A clear and concise description of what you expected to happen.

Screenshots If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

Additional context Add any other context about the problem here.

aheckler commented 3 months ago

Sounds like this might be an instance of https://github.com/woocommerce/woocommerce-gateway-stripe/issues/2307, but I can't be sure?

@heavestudio

every order on the website create two payment request on stripe.

Are there any differences between the requests in the logs? Does one have Level 3 data and the other not?

heavestudio commented 3 months ago

at begining it had failed payment, but now, all payment are suceed Capture d’écran 2024-06-25 162218

aheckler commented 3 months ago

Ah OK, so judging by the French there, this probably isn't a Level 3 data issue, since Stripe only supports Level 3 for U.S. merchants.

My suggestion would be to contact our support staff, explain the details of the error, give them any logs you have, etc. and see what they can help you find out. Without this being a confirmed bug in our code, GitHub really isn't the best place for the problem.

Thanks!