Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Contributor angelleye

    (@angelleye)

    That looks like an error that would be coming from PayFlow as opposed to Express Checkout, and it seems like the type of error that might occur if you’re using credentials that are valid, but simply don’t have API permissions enabled.

    Within the PayFlow account you can go into the Manage Users section and check on that. The user that you’re using within the plugin needs to have API_FULL_ACCESS rights (or overall FULL_ACCESS would work, too)

    Please check on that and let me know if that’s the issue.

    Plugin Contributor angelleye

    (@angelleye)

    I have not heard back from you on this, so I’m going to go ahead and close this ticket. Let me know if you have any other questions or concerns, though. Thanks!

    I am getting a similar error
    Payment error: 52-Insufficient permissions to perform transaction

    but can not find the parameters under user accounts under paypal manager.

    Another thing, is payflow now called paypal payment advanced? That seems to be what I currently have now.

    Thank You.

    Plugin Contributor angelleye

    (@angelleye)

    Payments Advanced and Payments Pro are two separate products that each work through the PayFlow API.

    Our plugin does not yet support Payments Advanced, but it will soon. We actually have it done in our GitHub repo already. Just need to get it tested and fully merged into the core plugin code.

    I’m getting the same error.

    I’ve created a new user that has API_FULL_ACCESS and I’ve made the appropriate changes to the settings portion to reflect the new user. Any further suggestions?

    Plugin Contributor angelleye

    (@angelleye)

    This error is pretty specific, so there must be something going on with the user or credentials you created/entered. Please double check all of that and if you continue to struggle you can submit a ticket here so we can work with you more directly.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Payment error: 52’ is closed to new replies.