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
RUSH: Authorize.net is a Retail (Card Present Account.) | Event Espresso - Staging Server

Support

Home › Forums › Ticketing › RUSH: Authorize.net is a Retail (Card Present Account.)

RUSH: Authorize.net is a Retail (Card Present Account.)

Posted: August 21, 2012 at 9:18 am

Viewing 1 reply thread


Ryan Boylston

August 21, 2012 at 9:18 am

Hi guys,

I wen’t to implement the ticketing system for my client this morning, and i received these errors. http://imgur.com/Oo3s5 After some a lot of digging around i realized that they have a retail (Card Present) account. Do you guys know of a way that i can make the payment transfer as a card present payment from your system to authorize.net? They currently use a third party company called Vendini that does this, so I would like to see if we could do this, instead of having to apply for a new merchant account.

Thanks,

JB


Chris Reynolds

  • Support Staff

    •

August 21, 2012 at 2:52 pm

Event Espresso doesn’t actually handle any funds, we just hook into the gateways and let them manage the money. So there isn’t a way within Event Espresso to transfer the payment to auth.net, and if there’s a third party service in between that handles this now, there would need to be a custom gateway integration built to send the transaction off to them to handle.
Viewing 1 reply thread

The support post ‘RUSH: Authorize.net is a Retail (Card Present Account.)’ 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.

Status: closed

Updated by Chris Reynolds 12 years, 5 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server