Stripe Payout doubles?

Hey there, @duetit! Thanks for contacting us. I’m happy to help you.

Have you had other orders after that? If so, were they correct?

Can you please share a screenshot of the order notes on one of those? Please remove any sensitive information before sharing it here. I recommend using https://snipboard.io. You can share the direct link to the image as a response to this topic.

Here’s an example of what we need:

https://snipboard.io/ga15Gu.jpg

Furthermore, I’d like to understand your site properly. Please share with us the necessary information below for us to investigate the issue further:

System Status Report which you can find via WooCommerce > Status > Get system report > Copy for support.
Fatal error logs (if any) under WooCommerce > Status > Logs. Then you can use the selector to search for Fatal Errors.
You could copy and paste your reply here or paste it via https://gist.github.com/ and send the link here.

Looking forward to your reply.

Have a wonderful day!

Hello @carolm29

Appreciate the response. No other orders yet, we’re staying alert if the error continues. Here is a screenshot of the order notes: https://ibb.co/hfTwQ11

This is the system report: https://pastebin.com/KL3i5Na6

No fatal errors is shown in the Woocommerce log.

Regards!

Hello Brian B

Thank you for your reply.

Could you please translate the text in these order notes?
It would be helpful if they are in English. ??
You may use a tool like Google Translate and share the text directly here.
https://ibb.co/hfTwQ11

Also, I noticed you have two active plugins serving the same purpose:
– WooCommerce Sequential Order Numbers Pro: af SkyVerge – 1.21.2
– Sequential Order Numbers for WooCommerce: af WebToffee – 1.6.1
Is this by intention?
This could lead to conflict and random errors.

I suggest not to wait for a real customer to make an order.
Instead, create a product with a minimum price and place an order yourself.

Let me know about your thoughts. ??

Best regards.

Hi @doublezed2

Yes of course – and appreciate the input on the plugin, we tested both and forgot to delete one of them. ??

Basically the order details is (from bottom to top):

• #1 Order status changed from Draft to Pending payment.
• #2 Stripe payment intent created (Payment Intent ID: xxx)
• #3 Order charge successful in Stripe. (Charge ID: xxx)
• #4 Order status changed from Pending payment to Processing
• #5 Order charge successful in Stripe. (Charge ID: xxx) <- This Charge ID is identifical to #3)

So maybe the 2x “charge successful” has something to do with the error? But as said in my first post, everything looks perfectly normal in the Stripe Dashboard.

Regards!

Hey, @duetit! Thanks for translating ??

You are correct, showing charge successful twice is connected with showing the total doubled.

To confirm, you were paid the correct amount, not the double one, right?

If you check the site Analytics, is the price correct there or is it double too?

Would you be able to set Stripe back on testing and run a test order to check if it is still working correctly? When you do this, please try with the same product on this order.

It is important to consider as well a staging functionality in case you would not like to touch your production site (you can ask your host if they offer this service), or you can use WP Staging for quickly spinning up a new test site.

Looking forward to your reply.

Have a wonderful day!

@carolm29

Hello again!

Yes, the price for the order is shown correctly everywhere on the site and in the Stripe Dashboard. Even the Stripe fee is shown correctly (not doubled), it is only the Stripe net payout (_stripe_net) that is doubled for some reason on the order page.

All tests showed no issues. Unless you have any ideas, I think we’ll wait for a few more orders and see if it proceeds, maybe it was a standalone error or it could be related to a specific credit card type perhaps?

As a last resort, maybe it’s possible to make a script that fetches the _stripe_net value and create a new meta_key with that number divided by two so we can fetch this new correct number for our invoices. Not the most elegant solution, but it could work. ??

Regards!

Hi @duetit

This is indeed unusual, and unfortunately, I couldn’t replicate the issue on my testing site. I tried in many ways, but everything seems to be working fine.

However, I noticed you’ve two Stripe plugin active:

• Payment Plugins for Stripe WooCommerce: af Payment Plugins [email protected] – 3.3.61
• WooCommerce Stripe Gateway: af WooCommerce – 8.2.0

Can you please verify which plugin you’re currently using? Are both plugins active and configured? If that’s the case, then there is a possibility the issue is coming from that plugin conflict. Could you try deactivating one of them and then run another test to see if it makes any difference?

Let us know how that goes. Looking forward to helping you.

Hi @shameemreza

Thank you for your reply!

Very understandable, we were not able to recreate the issue ourselves on the test site despite many attempts. We will try to see if future orders does the same thing, in that case we’ll simply make a script that divides the number by two. (Not the most elegant solution, but a solution none the less)’

And you are correct, we are using two Stripe plugins along with Conditional Payments for WooCommerce as we need the payment sent to different accounts depending on if they’re tax deductable or not – that is not an ideal solution either, but to my knowledge no one makes a Stripe payment plugin that allows for two Stripe accounts. For that reason we are not really able to disable the other plugin.

Regards! ??

Hi @duetit

Very understandable, we were not able to recreate the issue ourselves on the test site despite many attempts. We will try to see if future orders does the same thing, in that case we’ll simply make a script that divides the number by two. (Not the most elegant solution, but a solution none the less)’

That sounds like a plan.

However, please note that while it’s possible to write a script fetching the _stripe_net value and creating a new meta_key with that number divided by two, this is not a recommended solution as it may lead to other issues.

Also, while this might work, we recommend monitoring the situation closely to ensure no other issues arise.

And you are correct, we are using two Stripe plugins along with Conditional Payments for WooCommerce as we need the payment sent to different accounts depending on if they’re tax deductable or not – that is not an ideal solution either, but to my knowledge no one makes a Stripe payment plugin that allows for two Stripe accounts. For that reason we are not really able to disable the other plugin.

You’re correct, there isn’t a Stripe plugin that supports multiple Stripe accounts. However, I’d recommend keeping your plugins up to date and ensuring they’re compatible with each other to avoid potential conflicts.

As always, we’re here to assist you. If you encounter any further issues or need additional help, feel free to ask.

Thanks!

Hey ?? We haven’t heard back from you in a while, so I’m going to mark this as resolved – we’ll be here if and/or when you are ready to continue.