Payment Error 26 invalid vendor account

Thank you for information, however I’m upset this has happened. Been with PayPal 20 years and never had a payment fail till we switched to WordPress :/

Also my Windows Defender will not allow me to download zip from your github. It says it detects a trojan and immediately deletes it.

This issue has not been resolved with update 1.4.1 on WP 4.7.4/WC 3.0.5

@angelleye

I am still getting the same error message. I even deleted the plugin and reinstalled it from wordpress. And I keep on getting the same error.

Updated to 1.4.1 and still getting the same error here as well. WooCommerce 3.0.4. I reentered all the merchant and user details and saved the settings as directed.

I’ve installed the latest update, and I still can’t process credit card transactions. I’ve confirmed that my vendor, partner and password are all correct.

@angelleye

I’m not sure if this is what’s causing this issue, but I’ve found a problem. In the PayPal for WooCommerce settings for PayPal Payments Pro 2.0 (PayFlow), it says to only enter a name in the Live PayPal User field if you have more than one user, otherwise leave it blank. I’m trying to leave it blank, but every time I save changes, it automatically fills that field with my Live PayPal Vendor name.

Again, I don’t know if that would cause this issue, but just a thought.

Ugh, okay, we’re looking into it. We were able to reproduce it locally, and then we made changes and after testing the changes it fixed the problem. Not sure why it’s still happening for you.

Please make sure you’ve cleared out any caching / CDN tools when running updates. Sometimes those can retain old settings even after the plugin gets updated.

I’ve switched this status back to unresolved, though, and we’re working on it diligently.

I actually did try clearing our caches with wpengine, and still ran into the problem.

@flippinroo2, I can understand your frustration. We got caught in a bit of a tight spot because our 1.4.0 update was going to consist of a bunch of changes anyway, and then WC 3.0 made lots of changes in the way code structure works, so we had to go back through and make a lot of adjustments. So there are a lot of pieces involved (WP, WC, PayPal for Woo, etc.) and also lots of big changes within those pieces that all need to play nicely together. This doesn’t happen often, but when it does it’s important to thoroughly test.

As mentioned, we’ve done internal testing, but it’s impossible to test every possible combination of pieces in play on all these different sites. When big updates like this are released, it’s always recommended that you test the updates on staging / test copies of your site before implementing them on a live site. This goes for any plugin, really, not just payments.

I am sorry again this has happened, but we are doing everything we can to get it resolved ASAP. If you have a backup you can revert back to prior version to get working again, or even revert back manually if you have to. Another option would be to use the PayPal Standard that comes with WooCommerce until you see that this has been fixed. Then you can simply re-enable the plugin at that point and you’ll be back to where you want to be.

Somehow I am simply not able to reproduce this problem on our 1.4.1 update. I’m going to need some more info.

In 1.4.0, when you enter credentials into the fields and click save they were getting encrypted and the encrypted value was being displayed in the settings fields. In 1.4.1, the actual values (except for the password which displays dots) are displayed.

So for those of you saying it’s still not working on 1.4.1, are you seeing encrypted values in the settings fields right now, or are you seeing actual values?

@angelleye the correct values are displayed in the fields however when test or live trx are processed the internal error 26 comes back and the order fails.

@jpdavy1, do you have any sort of database caching tools enabled?

@angelleye WP Engine and have purged all caches multiple times.

Argh…same issue here.

Okay, we’re on it. Just gotta figure out how to reproduce it at this point. We’ll get another update released ASAP!

@angelleye, sorry Varnish cache.