• Resolved Mark Westguard

    (@westguard)


    Hi support

    We tried to update to version 3 a few weeks ago and unfortunately found too many bugs in the reporting and elsewhere to confidently upgrade on production. Others are also experiencing issue with recent updates causing EDD to stop working so I’m not confident enough to upgrade yet.

    We are therefore currently on version 2.

    PayPal transactions are repeatedly failing for us resulting in customers getting double or triple charged due to errors during the checkout process.

    Is there a solution for those of us still on version 2?

    I played around with the connection tab in EDD settings and I have initially traced it to:

    File: easy-digital-downloads/includes/gateways/paypal/admin/connect.php
    Method: get_merchant_status

    It is making an HTTP request to: https://easydigitaldownloads.com/wp-json/paypal-connect/v1/

    Your remote script is returning: {“error”:“An unexpected error occurred. Error code: Invalid response code from PayPal (403).“}

    I’m assuming this issue in the connection to the oAuth app is what is causing this problem to occur?

    I don’t understand why these support tickets keep getting marked as resolved when there is clearly an issue that has been ongoing since early October.

    Any help would be greatly appreciated.

    Thanks

    Mark

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Chris Klosowski

    (@cklosows)

    @westguard The issue is a result of a configuration within PayPal’s infrastructure. We released an update to EDD 3 in version 3.1.0.1.1 to resolve this. It has to do with adding a specific user agent to the requests to paypal. I’ve been working with the merchant services team at PayPal to try and get this fixed and it is in the hands of their engineering team at this point. Our release was in an attempt to give their team something specific to look for in the requests to hopefully not reject the requests further.

    If possible you can apply this change from 3.0.1.1 to append the same user agent in 2.11.x. The line numbers may have changed but the files should be in the same place.

    https://github.com/awesomemotive/easy-digital-downloads/pull/9528/commits/0543b446f02c005589f1b854f3d679688992a2b2

    I do apologize for this continuing to be a problem, and our recent release, while it does allow requests to work, is not a long term solution as it could just as easily get caught in the same network rules on PayPal’s servers in the future. That being said we are working with PayPal to come to an agreement on a long term solution to this issue.

    Thread Starter Mark Westguard

    (@westguard)

    Hi @cklosows

    Thanks for the code change which we’ve implemented. I’ll let you know how we get on with this.

    Mark

    Plugin Author Chris Klosowski

    (@cklosows)

    @westguard Has this resolved the issue for you? If so, please let me know and we can mark this thread as resolved.

    Thread Starter Mark Westguard

    (@westguard)

    @cklosows so far so good. I’ve not had any further double PayPal charges. I’ll keep monitoring it but will mark this as resolved. I appreciate your help!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘PayPal Failing for Version 2’ is closed to new replies.