Error: 10413

That’s odd. We ran all sorts of test to ensure that wouldn’t happen. We must have missed something.

Do you have logging enabled in the plugin? I would need to see log created at /wp-content/uploads/wc-logs/ to see what the issue might be.

Just to confirm, this is happening with DoDirectPayment?

Can you tell me how you have your tax settings in WooCommerce, as well as shipping, discount codes, etc. configured? I need to be able to reproduce the problem here and then I’ll get it fixed right away.

Oh, nevermind, I see it shows PayFlow in your error message. So I would need to the PayFlow log that got saved.

In the meantime – shall I roll back? I just had another client payment fail so it’s causing customer issues?

I would recommend jumping into the PayFlow plugin settings and clicking save on that page even if you don’t adjust anything. It’s possible the new feature to send line items didn’t hold and that could be causing an issue. So just to eliminate that possibility, please go in there and click save.

If you’re having customer payments fail, then yeah, I guess I would roll back for now.

I’m running more tests here right now and I cannot seem to produce this error with PayFlow, so I’m very curious how you have things configured and what your log shows.

We have standard UK VAT set up, but don’t really use Shipping as we sell training places. We use The Events Calendar: WooCommerce Tickets plugin for that. There are percentage discounts on some products.

Okay I have clicked save and enabled logging. I might try a test purchase to see if the logs capture any issues or is saving has resolved it.

Do the orders that are failing have a discount applied?

In WooCommerce -> Settings -> Tax tab, how do you have the following set?

– Prices Entered with Tax
– Calculate Tax Based On:
– Display Prices in the Shop
– Display Prices During Cart and Checkout
– Display Tax Totals

Also, what tax rules do you have configured?

Re-saving the settings seems to have worked. Our test payment has completed okay.

Thank you.

Ok, well that’s good news. Please keep me posted if anything else comes up, but I’m going to go ahead and mark this thread as resolved.

I also get below errors after updating plugin.

10412 – Payment has already been made for this InvoiceID.

@yogesh.patel.thesslstore, that error means a previous transaction was sent to your paypal account with the same ID that the new order got sent with.

This can happen if you have multiple sites sending orders to the same PayPal account or if the order IDs simply match up with any other payment in your account.

One way to avoid that is to go into the Express Checkout settings and set a value for Invoice ID Prefix. I like to use AEWC- as my prefix (for Angell EYE WooCommerce). This way the invoice IDs that get sent to PayPal will be something like AEWC-1234 instead of just 1234 and the odds of that matching anything else that was processed with my account are very slim.

Thanks for quick reply.

I have only single sites and i have already set a prefix. Below is the screenshots of my settings page.

https://nimbus.everhelper.me/client/notes/share/237784/NhIcRo3Qyf5GHrlTMZPPBoyiPUzs72WJ

Somehow that same order number must have been sent from your site to PayPal that had already been used previously. The plugin simply pulls the WooCommerce order ID and adds the prefix you have set (if any), and that’s what it sends in the PayPal request.

If PayPal is rejecting it saying the ID already exists then it must have already been used somehow.

What you could do, though, is disable this blocking feature in your PayPal account.

– Login to your PayPal account.
– Click on the Profile link.
– Click My Selling Tools
– Click the Update link next to Block Payments.

Depending on your account version you may just need to look for “Payment Receiving Preferences” in your profile if the steps above don’t work for you.

Once you’re there, you’ll find an option to “Block accidental payments: You may prevent accidental payments by blocking duplicate invoice IDs.”

Set that option to no, and then this problem won’t happen anymore.