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 accounts questions | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › authorize.net accounts questions

authorize.net accounts questions

Posted: February 17, 2013 at 10:26 pm

Viewing 1 reply thread


Charles Martin

February 17, 2013 at 10:26 pm

Site has two authorize.net accounts that are used for separate venues. Is it possible to create in the autnet gateway the ability to use two different accounts based on venue selected. For example, if user selects Venue A and it comes time to pay, load the auth.net page for the Venue A account. Likewise, if user selects Venue B, then load the payment page with the Venue B account?


Jonathan Wilson

  • Support Staff

    •

February 18, 2013 at 2:11 pm

Hi Charles,

At this time we do not have that feature. Any gateway that has been activated will show on every event. This would require custom development. We are currently booked up on custom dev work until spring. We can refer you to one of our Pro developers of you would like.
Viewing 1 reply thread

The support post ‘authorize.net accounts questions’ 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.

The original Forum description...

Status: closed

Updated by Jonathan Wilson 11 years, 11 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server