The PayPal IPN Issue
The problem is that we got the IPN turned on, with a valid url (not localhost, our real one), but after we got paid (Subscriptions), we receive no IPN massage. It has just not being generated at all. We used to receive the ipn's but after 28.04.2021 it just stopped being generated.
Does someone has the same issue or can advise me what can be done to get the IPN fixed?
Only thing to do is log into the sandbox receiver account at https://www.sandbox.paypal.com/webscr?cmd=_display-ipns-history to see if anything is being generated and attempted to send. If nothing is, contact PayPal for support as it's likely a temporary bug/sandbox issue.
Related
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.
I purchased the Tickera wordpress plugin from Tickera.com. I have repeatedly requested support from them, but they don't respond.
I installed this plugin on a client's website to sell tickets for an event. The plugin works. The visitor buys the ticket via paypal and then they are sent an e-mail with a PDF attachment of the ticket which can be scanned at the event.
The problem is that with each transaction, my client gets an e-mail from PayPal with this statement:
Please check your server that handles PayPal Instant Payment Notifications (IPN). IPNs sent to the following URL(s) are failing:
and then it has my client's URL with the folder where the WordPress lives and then ?ipn=paypal.
Do I need to open a IPN account on PayPal to stop the error e-mail? I have been afraid to do this, in case it screws up the function of the plugin. It is working now.
Does anyone have experience with this?
-w
It sounds like the plugin must be setting the IPN URL using the NotifyURL parameter of API requests, or just the notify parameter in a standard HTML button/form. That would override anything you set up in your PayPal profile anyway.
It sounds like there must be some sort of a problem with the IPN script itself that is causing it to send a failure code of some sort back to PayPal's IPN server. You should be able to check your web server logs for the times that URL is getting hit and see the result there so you can look at the error and resolve it.
I would be very reluctant using this plugin - see Facebook for more than enough reasons. As to not try to say too much, I will just say "client side only validation" and "tickera == name your own price ticket system". What made this bug even worse is that it could be triggered accidentally by merely using normal browser behavior and so a kid with no knowledge of Javascript or the sort could still easily add 4 tickets, proceed to payment, click back in the browser and again proceed and get 4 tickets for the price of 1... Someone with a bit more knowledge and malicious intent could mess with a client side value array and set prices to $0.01/ea if they wished... I was consulting for someone in an attempt to clean up the mess from using this plugin and quickly discovered Tickera to be less than helpful on the support front... Best I can tell, the client-only-validation "bug" (horrible design) is still in play.. When notified of the bug, they were pretty much like "Oh, no biggie - just review all sales and cancel/refund/etc manually" - an unacceptable solution for medium/large events and just bad business for an event of any size... There are some serious security concerns with this plugin and their lack of response or support is just the icing on the cake... Beware.
I have a wordpress site with Membership and Events. I am using Paid Membership Pro for memberships and Event manager Pro for events. I am using Authorize-net payment gateway and most event bookings are successful.
But I can see some booking in the Admin with the status Processing(Authorizenet AIM).
I have log to the Authorizenet and there is no processing transaction for this booking.
Could you please help me to solve this. What is the reason for that status?
Thanks
You will need to have SSL enabled for you site otherwise this will not work. Events manager will always force the https connection if a booking form accepting Authorize.net is used.
Wideload Shipping may be correct here, if you don't have a valid SSL certificate or SSL enabled then the booking process won't work with Authorize.net since you must be able to send card info securely.
I'd suggest you ask this on our pro forums, as a pro customer we'd be happy to help you troubleshoot there. If you supply us a link we can also probably have a better idea about what's going wrong and provide you with further steps to remedy the issue.
I noticed this same behavior starting to happen on my Events Manager Pro as well. Seemingly randomly some bookings will show "Processing (Auth.net)" while others show "Completed" (as they should).
From this thread's suggestion, I took a look at my https URLs. I found that sometime in the last month, we ran an update that has inserted some link hrefs and other unsecured URLs in the source code.
I had been using HTTPS plugin to force https on the events pages, but since the site URL was http only, it was pulling in these "external" files as http. I noticed in Firefox that my SSL connection showed broken. While in Chrome, it felt it was secure. My GUESS at this time is that the ones that go thru are where the page in the browser looks to be secure. While the ones that only get "Processing" are happening on the broken SSL browser views.
I've now changed my site URL to https as the base URL which ensures Wordpress uses it throughout. I now don't get a broken SSL in Firefox. My presumption is that this will fix this issue. Time will tell. I'll come back to update IF I'm wrong. But hopefully that might help for you to look at URLs, such as wp-json and other link rel URLs.
Of note, it seems the credit cards ARE authorizing/captured for those transactions. So it's more likely the return trip from Auth.net for the silent URL to changes the status of the booking?
I've been using my seller's and buyer's Paypal sandbox accounts to purchase fakes on my ecommerce and everything was working fine up until 1 hour ago.
Nothing has changed in my code, and I even tried to create and add new API credentials for my site, but every time I try to pay with Paypal Express I land to a "Session Expired" error page.
On someone else's machine the thing is still working.
It seems like no one on the net knows why, is it something to do with my browser?
Apparently, for no apparent reason, after a while you use Paypal's sandbox, you have to do the cleaning and delete all your cookies from Paypal to make it work.
I am using ubercart paypal module as payment gateway in drupal.. when the user pays the money the order confirmation is sent twice. this should not happen..
please help me..
thanks in advance
This is caused by the Paypal IPN sending out multiple requests which in turn causes the Conditional Actions module to invoke the email action twice.
Comment #25 in this post presents a possible solution. You should also check these links out:
http://www.ubercart.org/forum/support/10422/multiple_emails_single_purchase
http://www.ubercart.org/forum/support/8790/stock_level_reduced_twice
http://www.ubercart.org/forum/support/8930/stock_reduced_twice
http://www.ubercart.org/forum/support/14097/duplicate_notifications_file_download_sales_upgrading_uc_20
http://www.ubercart.org/forum/bug_reports/13313/paypal_duplicate_actions_taken
http://www.ubercart.org/forum/bug_reports/13716/stock_levels_decrease_twice_latest_update_6x20
http://www.ubercart.org/forum/support/13794/file_download_user_notified_twice
http://www.ubercart.org/forum/support/5192/stock_decreased_2_times_once_customer_buys_once_customer_pays_paypal
They all talk about the same problem in one way or another.