Absolutely unacceptable
-
It is inconceivable that a plugin for such an important service is this poorly built. Every new version introduces new bugs and fresh problems instead of fixing existing ones. I am currently unable to connect the APIs — neither through the guided setup nor manually — as the plugin keeps returning an invalid key error despite correct credentials.
This is not an isolated issue: the plugin has a long history of instability that wastes developers’ time and damages client relationships.
Absolutely unacceptable for a service of this caliber.
-
Hi @inpsydekrystian ,
my negative review comes from weeks of concrete issues experienced across several ecommerce sites, and I’d like to explain the context in detail.
We manage multiple WooCommerce stores, and over the past months we’ve encountered different problems with “WooCommerce PayPal Payments”.
Client 1 – Hosting SiteGround
About a year ago we enabled Google Pay and Apple Pay through your plugin. They were later disabled for reasons unrelated to the plugin itself. In the meantime, the plugin was updated and when we tried to re-enable them, the options were no longer available because advanced card payments were missing.
In the plugin we only see the standard payment option available (PayPal, PayPal Later and Credit Card in the same row), while we know that advanced card payments are listed separately together with Apple Pay and Google Pay. In addition, the standard card payment option is not compatible with the block-based checkout.
We assumed this might be related to a PayPal account/contract configuration issue and contacted PayPal support, who recommended using this alternative plugin:
https://wordpress.org/plugins/pymntpl-paypal-woocommerce/
With that plugin everything worked immediately.
Client 2 – Hosting Kinsta
The client was receiving duplicate order confirmation emails and many orders were failing.
We opened this thread:
https://wordpress.org/support/topic/duplicate-order-notification-emails-5/
and also contacted support here:
https://paypal.inpsyde.com/docs/request-support/
We were provided with a patch, but it did not resolve the issue.
Again, after switching to “Payment Plugins for PayPal WooCommerce”, the problem disappeared completely.
Client 3 – Hosting AWS with Wordfence and Object Cache
After a plugin update, the site started being overwhelmed by requests toapi-m.paypal.com, causing slowdowns and outages.
We reported the issue here:
https://wordpress.org/support/topic/paypal-woocommerce-plugin-v4-0-2-possible-api-rate-limiting-issue/
We tried several suggested workarounds without success.
The alternative plugin does not show the same behavior.
However, we still need to use “WooCommerce PayPal Payments” due to compatibility with WooCommerce Subscriptions. After regenerating the API keys, we also found ourselves unable to save them because the new keys start with the letter “B”, and the plugin appears to reject them: https://wordpress.org/support/topic/failed-connect-apis/
As a result, we were blocked and unable to continue testing the main issue.
I could provide more similar cases.
I understand a negative review may sound harsh, but I don’t believe the dissatisfaction is isolated. The plugin currently has a 2.8-star average rating, and the GitHub repository shows many open bugs:
https://github.com/woocommerce/woocommerce-paypal-payments/issues?q=is%3Aissue%20state%3Aopen%20label%3Abug
From our perspective, the main issue is that every update becomes a source of concern for production stores.
That said, I have no problem revising my review if we see real improvements in stability and in how these issues are handled.
You must be logged in to reply to this review.
