Every update is like gambling …

Hi there,

We deeply regret the inconvenience you’re facing and genuinely value your feedback.
To provide some context and clarity:

Every PayPal Payments update undergoes rigorous testing to ensure optimal performance and reliability. Our commitment is always to provide updates that enhance the user experience.

The timing of our recent update, unfortunately, coincided with an ongoing service disruption at PayPal. This wider disruption is affecting numerous integrations, not just PayPal Payments. We realize how the overlap in timing can lead to misconceptions about the root cause.

We are in continuous dialogue with PayPal regarding this disruption and are doing everything in our capacity to assist and stay informed. From the data available, the issue seems to occur sporadically, but please rest assured that PayPal is actively working towards a solution.

As we navigate these external challenges, our priority remains to keep our community informed and ensure the consistent performance of the PayPal Payments plugin. For updates and clarifications, we recommend keeping an eye on our support forums and reaching out to the PayPal Merchant Technical Support.

Please also be aware that the 403 error REFUSED_MARK_REF_TXN_NOT_ENABLED you may have seen in the PayPal dashboard is unrelated to the reported issue and does not have any negative implications beyond potentially cluttering the API request log.

Thank you for your patience and understanding during these times. For any further questions or suggestions, please open a thread in the support forums. Thank you!

Kind regards,
Niklas

You might have already observed, but I’d like to report that PayPal has confirmed the resolution of the issue discussed earlier. I understand how the timing of our recent plugin updates with the unpublicized issue at PayPal, may have suggested a connection. However, I assure you that this was purely a coincidence.

We acknowledge an unexpected occurrence during the 2.2.1 release, prompting a swift 2.2.2 release. But it’s crucial to highlight that this likely had no significant impact on your site’s operations.

Additionally, I’d like to address the 403 error mentioned earlier. Following our next update, those API calls should no longer clog up the API log. An error caused the cached value to be overlooked, leading to repeated calls for the Reference Transactions status to PayPal’s API. While this was not intentional, it’s worth noting that this had no negative effect on payment processing; the PayPal API is robust enough to handle such loads.

If you have any more questions or need further clarification, please don’t hesitate to reach out to our support team. Your understanding and patience have been invaluable, and we appreciate it immensely.