For over a week now, we have been patient with amember support. Continued requests for solving this issue have gone without resolve. Here is the situation: About 2 weeks ago the amember script simply stopped functioning. There were no changes on our part, so we were baffled at why it suddenly stopped working. Upon finding out that there was a problem (from emails from our potential members trying to sign up!), we immediately contacted amember and our merchant vendor. Amember suggested that it was an Authorize.net problem. We quickly found out that this was not the issue from Authorize.net (not to mention that our two shopping carts on the same server worked just fine). We then contacted amember again on our findings. Amember then replied that it was not a problem with the script, and to have Authorize.net check a link made by the amember script. We followed through, and again Authorize.net said that the problem cannot be with them, as the transaction information is not sent by amember nor is processed by the amember script. It is also important to note that our two shopping carts have been working fine this whole time. Now, it has been over a week, and this issue is still unresolved. Amember insists that it is not a problem with their script even though our two shopping carts have continued to work just fine throughout this whole ordeal. We are now at a standstill on this issue, and amember is at a loss, only suggesting that the server time may be incorrect. We are now being forced to look at other solutions for processing our memberships unless amember stands up to the plate and fixes this problem. It is also important to note that our 6 months access to free updates is over. I am thinking that the whole issue may be to get us to purchase more updates...
Just a suggestion: Get a testing card # from Auth.net. Run it. Call the Auth.net Customer Service again (or just stay on the phone with em) and verify that the request is showing in their system. It does sound like there is something on your end, espicially if your cart transactions are going through OK, and if they are with Auth.net. If the problem is only with existing members, it may be a Cron problem (yea I know that sounds too obvious - but it's worth checking) If none of your daily batches are showing in your Auth.net account, then the problem is somewhere with you. Are you getting your daily email summaries from Auth.net? I'm sure you already doubled checked and triple checked all the info on the aMember Auth.net page in your admin settings. If it is only new members with the problem and existing members are fine, then a db field may have gotten screwed. Double check your products. Make sure all of the dates and periods are good. Contact your host and ask if they have done any recent reboots, updates, or anything that may have offset dates or times. Can't believe the aMember team hasn't helped more, IMHO these guys have some of the best customer service around. Good Luck.
Thank you for your advice. We have checked the script, and have checked with Authorize.net on processing the transactions. Authorize.net said that the problem is on our end because amember does not process the transactions within the script (the user actually leaves the script to an Authorize.net form). Most often, the error received when applying to become a new member is a 97 error. From what Authorize.net and our merchant vendor say, this is a timeout error. Therefore, amember suggested that the problem lies with the server clock. Our server host and our merchant vendor are one in the same, so we contacted them to verify the server clock time. They have responded that the server clock is correct, and insist that the problem lies with the script itself. I have again today urged them to check the server clock again, and they are resetting it just in case as I write this. To answer your advice, we have done test transactions, and they have went through fine (except for amember). Our shopping carts are working just fine, which adds more confusion to the issue. The admin settings have not been changed, and have been rechecked just to make sure all settings are correct. It is possible that a database field has gotten messed up, but I don't have another database to check the fields against. Hopefully amember support will check this out. Right now, were are just frustrated, and at a loss on how to fix the problem. This is right in the middle of our busy season!
Alright, here is an update on this: Alex was correct on his suggestion that it the problem was due to the server clock settings. Apparently, my server host was incorrect when they let me know that the server clock was initially set correctly. It was only upon pushing our server host that they finally updated the server clock. Thank you Alex and everyone for your help in resolving this issue!
I am having this same issue, only I use PayPal. Shopping carts work fine on the same server, yet when customers try to sign up for the subscription service, they get the following error: "your session has timed out, please log in again." The recurring subscription payments also work fine and most customers are able to sign up, but there are several per week that get the time out error. Any assistance that can be provided would be greatly appreciated.
I'm also experiencing this same issue just recently with Paypal and haven't made any changes. Anyone else know what could be causing this problem? Wendy
I was receiving a " Internal processing error : curl_exec error 60 SSL certificate problem, verify that the CA cert is OK. Details: error:14090086:SSL routines:func(144):reason(134 " error whenever users tried to make a Paypal payment (Pro or Regular). I don't know if this is the same thing you are receiving...but the problem was resolved when my host provider ran a Cpanel update.