Posted: October 17, 2024 at 1:14 pm
|
Hello, The following message is being displayed on Event Espresso Payment Methods: https://eventespresso.com/product/eea-authorizenet-accept/ page displays: Are you currently using Event Espresso for your event registrations on your WordPress website? Event Espresso includes a payment gateway for Authorize.net AIM. Authorize.net Accept is a replacement for the Authorize.net SIM service which is being discontinued by Authorize.net. Question: FAQ: Question: Best, |
|
|
Hello, The following message is being displayed on Event Espresso Payment Methods: https://eventespresso.com/product/eea-authorizenet-accept/ page displays: Question: FAQ: Question: Best, |
|
|
Hello, The following message is being displayed on Event Espresso Payment Methods: https://eventespresso.com/product/eea-authorizenet-accept/ page displays: Question: FAQ: Question: Best, |
|
|
Hi Walt, Thank you for that information. Event Espresso does not currently support recurring payments. So, when it comes to processing registrations and tickets, Accept can do that along with the other methods we support (Stripe, Square, PayPal). It sounds like you might be taking individual transactions and manually setting up a subscription after the first transaction is completed. Something like that? |
|
|
Hello Garth, Apologies for the redundant posts, it appeared that the system was not displaying/accepting my entries… To register our members (S2Members), we’re using shortcode s2Member-Pro-AuthNet-Form passing in ccaps, ta=”0″ tp=”0″ tt=”D” ra=”$price” rp=”1″ rt=”Y” -> resulting in 1 year recurring memberships. The initial transaction is paid, then after a year the Authorize.net ARB is kicked in. 2. I’m still not sure if I need to replace the current EE (membership registration) payment method using Authorize.net AIM with Authorize.net Accept? [Authorize.net Accept is a replacement for the Authorize.net SIM service which is being discontinued by Authorize.net]. I don’t see a similar statement “Accept is a replacement for the Authorize.net AIM” – I only see “The following payment integrations will be removed: PayPal Standard, PayPal Express, PayPal Smart Buttons, PayPal Pro, Braintree, Payflow Pro, Authorize.net SIM and Authorize.net AIM” Again, somewhat unclear about the need to migrate to Accept. Best, |
|
|
Hi Walt,
If you are setting up Memberships through S2Member and users are purchasing their memberships through S2 then that’s totally separate from Event Espresso and if S2 is using AIM that will continue to work for as long as they support it. Event Espresso payment methods only apply to the Event Espresso checkout, so ticket selection, then our Single Page CheckOut process (SPCO for short) which loads the registration form and payment methods.
Wait… “EE (membership registration) payment method”? You mentioned above your using S2 for membership registration but now it sounds like you’re using EE for membership registration? Which is it? In terms of EE, we do not have a direct replacement for Auth.net AIM and the closest replacement is Auth.net Accept so if you want to continue taking payments through Auth.net for Event Espresso registrations you’ll need to switch to Accept by 2025 (as the deprecated payment methods will no longer work within EE at that point). Something to note, Auth.net AIM is an ONsite payment method which means you load the payment fields on your own server. Your server processes the payment data and sends it to Auth.net to process the payment. All of that means you need the one of the highest levels of PCI compliance, SAQ-D, see HERE. Generally, most people aren’t ready for that level of compliance as its pretty strict so we’ve moved away from ONsite payment methods (as most e-commerce plugins have) unless there is a specific requirement for them.
In terms of Event Espresso, the Auth.net AIM payment method for Event Espresso itself will no longer work in 2025. So for EE registration payments, you’ll need to migrate Accept to work with Auth.net. But, there seems to be some confusion as to what that payment method is actually used for here, its not clear how you’re setting this up so what the above will affect, I don’t know. It sounds like you are using S2 Member to handle memberships and take payments for those memberships using AIM within S2Member and if that’s the case that’s completely separate from EE and its Auth.net AIM payment method. |
|
|
Hello Tony, Thanks for the detailed response(s)!! √ It sounds like you are using S2 Member to handle memberships and take payments for those memberships using AIM within S2Member and if that’s the case that’s completely separate from EE and its Auth.net AIM payment method. Yes, we’re using S2Member to register our CTS organization’s users (vs. conference registrations). Great, no problems there. Apologies for tossing generic words (registration) around. re: So for EE registration payments, you’ll need to migrate Accept to work with Auth.net. Thank you, we will migrate from AIM to Accept for the EE “conference” Event registrations. Best, |
|
No apology needed 🙂 I just don’t want to make assumptions based on the term used and give you the wrong info.
Awesome, any problems please let me know. |
|
The support post ‘Do I have to migrate Authorize.net “AIM” to Authorize.net “Accept”?’ 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.
