Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Authorize.net Issues | Event Espresso - Staging Server

Support

Home › Forums › Translations › Authorize.net Issues

Authorize.net Issues

Posted: June 3, 2013 at 11:29 pm

Viewing 3 reply threads


chase henslee

June 3, 2013 at 11:29 pm

I paid $180 to you guys in the intention on have a worry free event plugin for my business site. I have spent hours researching both the calendar and payment options to make this site working. I am using authorize.net and have found no tutorials on how to apply it. I am annoyed after paying that kind of money for a plugin I even need to look! I logged in and still could not see admin comments due to it saying I didn’t have access? I used event registration free and had this working in minutes; the only reason for paying the cash was for the images on calendar option.

I know you guys work hard to satisfy customers, so please help me make this happen! I also need help resizing images on the calendar to make multiple picture fit on the same day.

 

Thanks in advance for your help.


Bryant Henslee

June 4, 2013 at 8:52 am

The following errors have occurred.
(99) This transaction cannot be accepted.


Bryant Henslee

June 4, 2013 at 8:53 am

I am using the SIM option with all checkboxes off


Josh

June 4, 2013 at 11:21 am

The error code 99 indicates that some account info might not be entered correctly. Can you double check the auth.net Login ID and auth.net Transaction key that is entered in Event Espresso>Payment Settings under “Authorize.net SIM Settings”?

One thing to look out for is any leading or trailing white space that may have been copied and pasted into the fields there.

You can also generate a new transaction key, disable the old transaction key, and enter the new transaction key in the payment settings. To get a new transaction key:

1. Log into your Merchant Interface at https://account.authorize.net.
2. Click Account from the main toolbar.
3. Click Settings in the main left side menu.
4. Click API Login ID and Transaction Key.
5. Enter your Secret Answer (the answer to your Secret Question configured at account setup).
6. To disable the old transaction key, click the check box labeled Disable Old Transaction Key.
(Note: If the Disable Old Transaction Key check box is not selected, the old transaction key will automatically expire in 24 hours.)
7. Click Submit to continue. Your new Transaction Key is displayed.
Viewing 3 reply threads

The support post ‘Authorize.net Issues’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

Post any questions about the language files, translating Event Espresso, or issues with our GlotPress site for translations here.

Status: closed

Updated by Josh 11 years, 7 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server