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.
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.
Am using WooCommerce with WooCommerce PayPal Payments plugin, on checking out (live environment) am getting the error below;
[UNPROCESSABLE_ENTITY] The requested action could not be performed, semantically incorrect, or failed business validation. https://developer.paypal.com/docs/api/orders/v2/#error-TRANSACTION_REFUSED
To add on, sandbox works without any issue.
I will be grateful for any assistance.
TRANSACTION_REFUSED is not a technical problem, and so cannot be fixed. It is a decline by PayPal.
Have the customer use a different payment method, or contact PayPal for information about why the payment might have been declined.
Note that payments to your own production account are not permitted. If the payer information is at all connected to the receiving account, this is why it was declined.
I have correctly configured payments with PayPal in WooCommerce, sometimes I get orders and pay for PayPal and everything is fine, but sometimes some customers pay and WooCommerce does not change the status of the order to "Paid", and for that reason customers contact me to tell me that they already paid and yes.
Does anyone feel the same?
PS: This error is occasional, I do not know what it could be.
You could always just log in to your PayPal account and see if the transactions that show an incorrect status in WooCommerce do actually exist in your PayPal transaction log with the correct status. If so, then you should contact WooCommerce support for them to explain why those same transactions do not show up with the correct status in their portal. If WooCommerce tells you that it's an issue with PayPal (and thus, there is nothing to be corrected at their side), then open a case with PayPal support and they can look into the logs being sent from WooCommerce's API calls into PayPal to confirm whether or not they are doing it properly.
PayPal Standard that comes with WooCommerce uses IPN to update the order status. Unfortunately, their IPN integration is not great, and it often fails.
If you use my PayPal for WooCommerce instead, and setup Express Checkout, this problem will not happen. Also, you'll have a lot more features and functionality.
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.
When attempting to process a credit card with Woocommerce Authorize.net DPM plugin, the browser does not redirect after processing through the gateway. Instead it is "stuck" in the gateway and echoes the following message below. It has only been happening since we upgraded Woocommerce. We have version 2.1.12 and version 1.5.0 of the Woocommerce authorize.net DPM. I have tried disabling other plugins while checking out, no errors in the error log, making sure no values are in the relay urls on the account, etc. I'm pulling my hair out! Please help if you know what could be going on!
An error occurred while trying to report this transaction to the
merchant. An e-mail has been sent to the merchant informing them of
the error. The following is the result of the attempt to charge your
credit card.
This transaction has been approved. It is advisable for you to contact the merchant to verify that you will receive the product or
service.
I had a similar issue recently, caused by our security plugin (iThemes, in this case) blocking requests with no user agents. I think this block may have come about in a recent update as I was able to resolve my issue by disabling the HackRepair.com's blacklist feature. If in fact this is your problem, you'd be looking for a line in your htaccess that looks similar to RewriteCond %{HTTP_USER_AGENT} ^$.
This is a Relay Response error. As noted here, this means that "that Authorize.Net is unable to connect to the page that you have specified as your relay response URL".
According to Woocommerce's article about troubleshooting common problems with the authorize.net DPM payment gateway, a good place to start is by deactivating nonessential plugins to see if there is a conflict.
As I just learned from encountering this problem, another possible cause for this (somewhat vague) error message is an empty MD5 field in the woocommerce settings if an MD5 Hash Value has been set for the merchant. You can check or set the MD5 hash value in authorize.net by going to Account > Settings > Security Settings > MD5-Hash.
If no hash value has been set through authorize.net, that setting can be left blank. But if it has been set, leaving it blank will apparently produce a Relay Response error.
Hope this helps someone.
I contacted woocommerce for this issue and it was resolved by changing to permalink setting for woocommerce to something other than default. You can change this setting in the Settings > Permalink page at the bottom.