doesn't work

99% of the time this is because incorrect API creds were entered. Maybe you can double check that?

sorry, I could have been more clear:

I ran easy-setup twice.
I manually entered the credentials once.
I manually entered the credentials from another business once.

So I tried it 4 times.

Hi jborchart,

What version of OpenSSL is your server running? PayPal is going through some changes (more details here); if you’re running a version of OpenSSL older than 1.0.1, this could be causing the issues you’re seeing.

Thanks,
Matt Cole
Senior Integration Engineer, PayPal

Hi jborchart,
Thank you for initiating this thread. Could you also share what downgrade in functionality you have seen from the paid software version. I have been working with woo to make sure that the product features have parity with existing plugins in the woo community. Your feedback on whats missing would be hugely beneficial. We are working on phase 2 requirements for this plugin and will make sure the asks have been addressed.

Please advice,
Ekta Agarwal
Technical Account Manager, PayPal

For one, the payment process on the backend is not good. When your settings indicate authorizing payments in the plugin and someone submits an order, it gets added to your order list as “in process” when it should be “on hold”. When it is “in process”, you cannot edit the cart and update totals, etc. That’s essential.
Also, in the message log of the order, it says that the payment has been processed, when it should be saying that the payment has been authorized.
Also, since it’s status is “processing”, you have to manually change it back to on “hold” in order to edit the totals. Once you do that, the ability to capture the funds is removed from the actions list of the order. The order is locked as if you have already taken the funds.
When I go to paypal, the funds are still in authorization status only and remain that way until I manually capture the funds from paypal.com directly.
So, hopefully you can see how this is not working well.
Also, the popup Paypal Express from the cart has been broken since 1.0.
It has been several weeks since that was reported and confirmed.

All you need to do is get a copy of the old, paid plugin and the differences will be obvious.

I can get over some of the limitations at checkout as described above, but the backend process NEEDS to be fixed before we can use it.

just getting back to this, my hosting service (hostgator) is using 1.01, which is one of the current releases.

I downloaded the most recent version of this paypal gateway plugin and it does not work any better.

I contacted the developers of the previous version of the paypal gateway (skyverge) and they said that there was no reason for them ton continue to support that version, even if I paid for it.

I contacted my hosting service, hostgator, and they were clear that openssl is sha256 compliant.

At this time, there does not appear to be any method for woocommerce sites to use paypal express to meet the June 2016 requirements for SHA256. Shouldn’t there be a whole bunch of people freaking out about this?

There are lengthy discussions on the Internet about this very topic, and it is indeed one of the ‘hidden very big deals’ we see every so often because everyone working on it is posting in a different place with a slightly different topic.

The most detailed discussion is here.

There are 2 plugins that were written solely to address this issue. I have tested one of the plugins with the skyverge paypal express gateway and it works perfectly.

The other plugin simply has more options and details that may be needed depending on what hosting service you might use.

This fix should give the developers of the free gateway (which is where we are posting now) time to mature the product while we continue to use the paid gateway.

The plugin that works with skyverge and hostgator is here.
google drive

The plugin with more options is here.
reid

The new version 1.1.0 should resolve the credential issues.