• I expected that the bad reviews were due to people not setting up the plugin right, or not using it correctly, but we’ve been very careful about reading the documentation and doing everything right. In the last week or so, most of the paypal transactions have been fine, and that was in line with our own testing. Then yesterday we see that the Woocommerce status for one of the paypal payments was showing that it failed, yet Paypal itself shows that the payment was successfully charged to the customer and we have their money.

    I guess what I don’t understand is why the older plugin couldn’t be maintained. We never had a problem with it. When we saw the urgent message in our plugins area suggesting we change to the new plugin, we decided to wait as long as possible because we saw the bad reviews and issues in the support forum. We thought that by now most or all of the issues would have been fixed, but that’s definitely not the case.

    I feel bad about the plugin authors doing this to us. Not cool at all.

Viewing 1 replies (of 1 total)
  • Plugin Support Syde Niklas

    (@niklasinpsyde)

    Hi there @skunkbad,

    Thanks for providing feedback.
    The previous plugin was using outdated PayPal technology which will be disabled on PayPal’s end at some point. While it still works, this makes it difficult to implement more recent features such as advanced card payments or Vaulting, as two examples.
    The Checkout plugin will continue to work for the foreseeable future but at some point, when PayPal turns off functionality or when newer WordPress/WooCommerce versions are breaking features, then it won’t be updated. The main limitation is no more plugin support. This means when reaching out to the support, you would be referred to PayPal Payments instead.

    The new integration has been developed with a future-proof architecture that will enable it to be maintained for a long time. PayPal Payments can do (almost) everything the previous integration could and we are putting lots of work into filling eventual gaps and providing the smoothest possible migration.
    The recent update 1.7.0 had a focus on improving the migration from the old to the new plugin and also comes with updated documentation to provide more details about the setup.

    The new version should be more transparent if anything goes wrong, but we are glad to assist further in the support forums if anything remains unclear.
    Anyway, I hope that explains a bit why a new integration was needed.

    Kind regards,
    Niklas

Viewing 1 replies (of 1 total)
  • The topic ‘The old plugin worked fine, now this…’ is closed to new replies.