I'm using the Paypal Payflow api and receiving the following response error when trying to go live or in test:
RESULT=52&PNREF=xxxxxxxxxxx&RESPMSG=Insufficient permissions to perform transaction
From searching it seems there is a lot of people having issues with this. I also can't find error code 52 in any documentation that might help me resolve the issue. This thread explains the same unresolved issue: Paypal forum
Apparently my clients account was signed up for Payments Advanced and not Payments Pro. The upgrade has to be done over the phone, the online form will tell you that the application has already been approved.
Related
I am running a Wordpress website with WooCommerce and Cartflows installed. I want to take subscription payment using the official WooCommerce Subscription plugin, however, I am facing an issue with the recurring payment process. The initial authorization is successful, but when the plugin tries to charge the recurring payment, I get an error and a failed order.
I checked the failed-scheduled-actions log file, and the following error message appeared: "DEBUG WooCommerce couldn't retrieve the order ID from order key in the URL." I have tried to troubleshoot the problem on my own, but I have not been able to find a solution.
If anyone has any experience with this issue or has any suggestions, I would greatly appreciate it. Thank you in advance for your help.
We got a message to migrate to the new Google Identity Service.
We do a direct usage of GAPI.Client for authentication and not the Javascript Platform library.
Does anyone know if the deprecation would affect us?
According to this blog post, it doesn't seem to be affected but we are getting the emails from Google asking us to migrate.
We installed the Woocommerce Paypal Payments plugin on our website. We're switching to a different Paypal account (US instead of Canada), which necessitated us to install the new app.
Immediately after switching payments to the new app, about half our customers reported that they were unable to purchase.
This is the error that we're seeing in the backend:
Failed to process the payment. Please try again or contact the shop admin. [UNPROCESSABLE_ENTITY] The requested action could not be performed, semantically incorrect, or failed business validation. https://developer.paypal.com/docs/api/orders/v2/#error-PAYMENT_DENIED ************************* [UNPROCESSABLE_ENTITY] The requested action could not be performed, semantically incorrect, or failed business validation. https://developer.paypal.com/docs/api/orders/v2/#error-PAYMENT_DENIED ********************* Order status changed from Pending payment to Failed.
We have switched back to our old payments setup for now, but we'd like to get this fixed.
I spoke to the Woocommerce Paypal Payments plugin developer. His feedback was:
'The “PAYMENT_DENIED” issue is most likely caused by a bank or PayPal denying the transaction and needs to be investigated by PayPal Merchant Technical Support.
We have no access to the backend logging of PayPal, so we cannot see why this transaction was denied. Please contact PayPal Merchant Technical Support to get this investigated.'
When I submitted a ticket to Paypal, they told me that the cards were declined 'based on risk', which is fairly obviously not the case. We've had customers' cards declined by Paypal due to risk in the past. It looks nothing like this.
It seems that there is probably an issue with this new Paypal account. Does anyone know what might be going on?
WooCommerce 7.0.1
WooCommerce PayPal Payments 1.9.5
When I submitted a ticket to Paypal, they told me that the cards were declined 'based on risk', which is fairly obviously not the case.
It is the case, the PayPal API returns PAYMENT_DENIED when PayPal has rejected the transaction, generally due to it being detected as involving potential fraud or other compliance/risk issues.
For the live environment, since it's a business rather than technical issue, the account's owner can contact PayPal's general customer support via https://www.paypal.com/smarthelp/contact-us and inquire about the declines. It helps to have the details of specific payer examples, including their exact amounts, date+times, and any other identifiers
I'm currently troubleshooting the Retail Merchant Services Plugin for WooCommerce and receiving an invalid Signature error :
ERROR: 66343 - ERROR CODE (RC_INVALID_SIGNATURE)
Given the lack of support from ERMS and my lack of coding skills beyond Html 5 and CSS. I am looking for an alternative payment plugin that works out of the box ! (the reason I find myself looking at Woo Commerce and their Sagepay Payment Plugin and find myself in Stackoverflow)
Can anyone tell me if there are generic test settings / generic account setup for the WooCommerce Sagepay Plugin to test it without having a Sagepay Account ? or better yet if there was a way to test the plugin before spending $79 to find myself no where nearer solving a payment gateway issue ?
I have an account for ERMS but given the lack of support I wanted to try an alternative.
Any help is appreciated.
If this isn't the appropriate forum to ask my apologies.
That message appears when the Test Merchant ID and Test Merchant Secret are incorrect.
In my case (Opencart rather than Woocommerce), the test account information in the email from RMS was incorrect. The correct Test Merchant ID and Test Merchant Secret were shown in the placeholder text on the Gateway Config screen.
Setting up a site for someone and using Sage Pay, the site is built in WooCommerce and it is using a plugin for the payment gateway from the Sage Pay site.
Currently i am getting this error: 5080 : Form transaction registration failed.
The Sage Pay account holder said to fix it i need to have a success and failure page. However between WooCommerce and the plugin i cant imagine those would not be included. Would this be a issue with the setup of Sage Pay or am i missing something?
I recommend you look in My Sage Pay. Under Transactions -> Invalid, you may have an entry which corresponds to the transaction - this will have an error message which actually relates to the specific failure (instead of the generic 5080 error)
Issue was the surcharges, once deactivated it worked fine.