|
Bob Flynn
|
July 24, 2015 at 10:15 am
I am running EE3 and I am using Authorize.Net AIM for payments. No transaction is approved apparently because EE3 is not getting to my merchant account. The bank states that the transaction never makes it to them, approved or declined. The restrict key is correct as well as the account number. The settings in EE3 payment gateway screen are correct, I believe that the problem probably lies in the plug in file for WP that is in the c-panel of my web site, but I don’t know where to look or what to look for. Can someone please help me?
|
|
Josh
|
July 24, 2015 at 10:29 am
Bob, Do you have a reason why you think the problem is in the plugin file?
Usually when this happens, it is because web server does not have cURL enabled. Can you check with your host to see if cURL is enabled? It will also help if you can check the server’s PHP error logs for errors, that will help narrow down the cause of the error.
|
|
Bob Flynn
|
July 24, 2015 at 10:48 am
I don’t know where to find the log files, but I will contact Host Gator regarding cURL…
|
|
Josh
|
July 24, 2015 at 11:35 am
They’ll also be able to show you where the log files are.
|
|
Bob Flynn
|
July 24, 2015 at 12:11 pm
cURL is enabled. I have the log file, but I do not know what to do with it now
|
|
Lorenzo Orlando Caum
|
July 24, 2015 at 2:50 pm
Hi Bob, I had a question about your original post, specifically this comment:
The restrict key is correct as well as the account number.
Authorizenet AIM uses an API Login ID and a transaction key for payment processing. Could you confirm those are what you are referring to when you say restrict key and account number?
—
Lorenzo
|
|
Bob Flynn
|
July 24, 2015 at 3:39 pm
That is correct, the transaction key and login ID
|
|
Bob Flynn
|
July 24, 2015 at 5:09 pm
I called the payment processor and they said no transactions are hitting their servers. I also had them watch for a transactions as I tried to put through a charge on the website:
Payment Type: authorize.net AIM
Payment Date: July 24, 2015
Amount Paid/Owed: $1.00
Payment Declined
Payment Status: Payment Declined
Registration ID: 124-55b2c3f02d65d
Transaction ID: 0
There are no errors in the log posting when a transaction fails.
Here are a few entries:
[17-Jun-2015 18:33:27 America/Chicago] WordPress database error Table ‘lisar100_wrdp1.wp_contact_form_7’ doesn’t exist for query DESCRIBE wp_contact_form_7 made by do_action_ref_array, call_user_func_array, wpdbBackup->cron_backup, wpdbBackup->db_backup, wpdbBackup->backup_table
[24-Jun-2015 18:28:04 America/Chicago] WordPress database error Table ‘lisar100_wrdp1.wp_contact_form_7’ doesn’t exist for query DESCRIBE wp_contact_form_7 made by do_action_ref_array, call_user_func_array, wpdbBackup->cron_backup, wpdbBackup->db_backup, wpdbBackup->backup_table
[01-Jul-2015 18:28:21 America/Chicago] WordPress database error Table ‘lisar100_wrdp1.wp_contact_form_7’ doesn’t exist for query DESCRIBE wp_contact_form_7 made by do_action_ref_array, call_user_func_array, wpdbBackup->cron_backup, wpdbBackup->db_backup, wpdbBackup->backup_table
[08-Jul-2015 18:33:18 America/Chicago] WordPress database error Table ‘lisar100_wrdp1.wp_contact_form_7’ doesn’t exist for query DESCRIBE wp_contact_form_7 made by do_action_ref_array, call_user_func_array, wpdbBackup->cron_backup, wpdbBackup->db_backup, wpdbBackup->backup_table
[15-Jul-2015 18:31:44 America/Chicago] WordPress database error Table ‘lisar100_wrdp1.wp_contact_form_7’ doesn’t exist for query DESCRIBE wp_contact_form_7 made by do_action_ref_array, call_user_func_array, wpdbBackup->cron_backup, wpdbBackup->db_backup, wpdbBackup->backup_table
[22-Jul-2015 18:25:26 America/Chicago] WordPress database error Table ‘lisar100_wrdp1.wp_contact_form_7’ doesn’t exist for query DESCRIBE wp_contact_form_7 made by do_action_ref_array, call_user_func_array, wpdbBackup->cron_backup, wpdbBackup->db_backup, wpdbBackup->backup_table
[23-Jul-2015 16:41:09 America/Chicago] PHP Warning: preg_match_all(): Compilation failed: invalid range in character class at offset 42 in /home3/lisar100/public_html/wp-content/plugins/espresso-https.1.0/espresso-https.php on line 425
[23-Jul-2015 16:41:10 America/Chicago] PHP Warning: preg_match_all(): Compilation failed: invalid range in character class at offset 42 in /home3/lisar100/public_html/wp-content/plugins/espresso-https.1.0/espresso-https.php on line 425
[23-Jul-2015 16:41:11 America/Chicago] PHP Warning: preg_match_all(): Compilation failed: invalid range in character class at offset 42 in /home3/lisar100/public_html/wp-content/plugins/espresso-https.1.0/espresso-https.php on line 425
|
|
Lorenzo Orlando Caum
|
July 27, 2015 at 10:12 am
Hi Bob, if nothing is being received, then there may be an issue with the credentials or there is a problem with the connection.
Could you try regenerating your API credentials and updating those in Event Espresso –> Payments Methods –> Authorizenet AIM? Be sure to save changes after adding the updated information. Also, be careful of extra spacing before or after the credentials when copying and pasting them into the fields.
Here are the steps to do so:
https://support.authorize.net/authkb/index?page=content&id=A405
Next, temporarily deactivate all plugins and only reactivate Event Espresso 3. Then try another transaction. Does it work as expected?
—
Lorenzo
|
|
Bob Flynn
|
July 27, 2015 at 11:32 am
Hi Lorenzo,
We will try what you suggested.
Question, are these the error messages that Espresso would generate for failure to connect due to improper credentials with Authorize.net?
Payment Declined
Payment Status: Payment Declined
|
|
Lorenzo Orlando Caum
|
July 27, 2015 at 12:29 pm
Hi Bob, declined is a generic message that it wasn’t processed. I helped another member earlier today with Authorizenet and it was an issue with their credentials.
Could you try the steps that I shared earlier and then share feedback here?
https://eventespresso.com/topic/ee3-and-auth-net-aim/#post-166394
—
Lorenzo
|
|
Bob Flynn
|
July 27, 2015 at 12:49 pm
I changed the transaction key and saved it, then updated EE3 with the new key, however the transaction was still declined…
|
|
Lorenzo Orlando Caum
|
July 27, 2015 at 2:18 pm
Hi Bob, we have a set of test credentials that we would like to try out on your site. Could you follow up with us here:
https://eventespresso.com/send-login-details/
If we are not able to process the transaction with our test credentials, then this could be an issue on the server.
However, if it works, then we’ll need you to follow up with Authorizenet support to ensure that your account is enabled for production mode.
Thanks
—
Lorenzo
|
|
Bob Flynn
|
July 28, 2015 at 4:05 pm
Lorenzo,
Did you get the access to my web site that you require? If not, please let me know exactly what your needs are, and I will take care of it immediately…
|
|
Lorenzo Orlando Caum
|
July 28, 2015 at 6:37 pm
Hi Bob, I’ll reply privately.
Thanks
—
Lorenzo
|
|
Bob Flynn
|
July 28, 2015 at 7:57 pm
Re-submitted the logon credentials.
We did test that they work.
|
|
Lorenzo Orlando Caum
|
July 29, 2015 at 7:22 am
Thanks. The updated information worked and I was able to complete the needed testing. I’ve shared the results via email.
Please take a look at the email and then reply there.
—
Lorenzo
|
|
Bob Flynn
|
July 29, 2015 at 2:53 pm
Ok, found the problem. We are using a payment processor that uses Authorize.net emulation and its not actually Authorize.net.
We need to make the following change to the posting URL somewhere:
Change this link: https://secure.authorize.net/gateway/transact.dll
To:
https://www.eprocessingnetwork.com/cgi-bin/an/transact.pl
Is there any way to do this via functions.php or another way that won’t be overwritten with each Espresso update?
Thanks for all your help getting us pointed in the right direction!
|
|
Lorenzo Orlando Caum
|
July 29, 2015 at 3:24 pm
Hi Bob, here are some steps based on what you shared.
1) Login to your WordPress site with your preferred SFTP or FTP client. FileZilla and Cyberduck are free options.
2) Browse to this location: /wp-content/plugins/event-espresso/gateways/AIM
3) Download a copy of the AIM folder to your computer
4) Using your preferred FTP or SFTP client, browse to this location: /wp-content/uploads/espresso/gateways
5a) Upload the AIM folder that you recently downloaded to the location above
6) Next, browse to the AIM folder that you just uploaded. Then browse into the lib folder and then open the AuthorizeNetAIM.php file for editing. Here is the location:
/wp-content/plugins/event-espresso/gateways/AIM/lib/AuthorizeNetAIM.php
7) At around line 45, you’ll see the URL for Authorizenet (http://cl.ly/image/0z413g2R0J0t)
8) Change it to the new URL and then save changes.
Thanks
—
Lorenzo
|
|
Bob Flynn
|
July 30, 2015 at 1:18 pm
We are good on the gateway!
Have 2 related questions:
How do we make the confirmation email got out after a successful payment instead of right after form submission.
How do we change the Autorize.net gateway picture to NOT include Amex?
|
|
Josh
|
July 30, 2015 at 2:23 pm
Hi Bob,
You can make the confirmation email go out after successful payment by going to Event Espresso > General Settings > Email Settings and set Send registration confirmation emails before payment is received? to No.
You can change the button image that opens up the credit card form by following Lorenzo’s tutorial:
https://gist.github.com/lorenzocaum/db9eaf64922d8354024a
|
|
Bob Flynn
|
July 30, 2015 at 3:14 pm
Thanks Josh, that is very helpful!
Is that method safe from plugin updates then?
|
|
Josh
|
July 30, 2015 at 3:17 pm
If you’ve copied over the aim folder from the plugin to /wp-content/uploads/espresso/gateways, and make your changes there, yes.
|
