@rogierlankhorst @specialk
Chris here again. I’m in contact with PayPal every day regarding this issue.
We have had some of the issues occur on our end which is why I’m keeping this line of communication open daily between not just Merchant Services but key personnel within PayPal who are in charge of merchant services. We’ve had a limited number of items affected, but yet we have experienced it ourselves as well.
What we know
At this point we know the following; there is an intermittent issue where the requests for web hook verifications are failing to be correctly created due to the PayPal system rejecting the requests in their network layer. Initially it was brought up that it was due to the ‘user agent’ string that is sent along with the requests, which would explain why some sites have the issue present more often than other as the WordPress APIs that send these http requests may have different user agents that are sent.
While there may be a way to fix it in code, they could not provide an exact remediation step in order to prevent the rejections from continuing to occur without giving us insights into possible security steps they take on their end, so they opened an issue with their engineering team to solve this within the PayPal infrastructure.
The reason that PayPal Standard and Express continue to work is due to the fact that these are their legacy platforms that rely on IPN, not the new Webhooks system they are using. For the meantime, PayPal Express is a valid replacement, however we do see that as a temporary solution just due to the fact that PayPal has focused their attention on the new Webhook API for new product growth and features.
I am personally committed to getting this solved with PayPal and we are taking it seriously. Due to the nature of the issue, I’m moving parts of the process forward that I can by looking for other solutions in the EDD codebase that might help (but they are not guar netted to work at this point, just try and avoid the issue in their platform), until PayPal can resolve the issues within their API infrastructure.
We’re going to release a very minor point release (3.1.0.1.1) that contains an updated user agent string (as that was pointed out by the PayPal team as the possible issue, recently). There is no guarantee that this will resolve the issue long-term, but it appears to be working in the mean time, until their engineering team can resolve the issue within their infrastructure.
– Chris K.