Support

January 15, 2025 at 1:27 pm

Hi there,

The Auth.net AIM Gateway was removed from our EE Payment plugin despite the updated April date being communicated.

In order for that to happen the site must have still be using 5.0.31.p earlier today, correct?

I can see it’s updated to 5.0.32.p now so can you see Auth.net AIM within Event Espresso -> Payment methods now?

January 15, 2025 at 1:47 pm

This is the full notice posted:

Effective April 15, 2025 (extended from January 15, 2025 in Event Espresso version 5.0.32.p), Event Espresso will discontinue several outdated payment integrations, including: PayPal Standard, PayPal Express, PayPal Smart Buttons, PayPal Pro, Braintree, Payflow Pro, Authorize.net SIM, and Authorize.net AIM. Users are encouraged to transition to supported payment methods such as Stripe, Square, Authorize.net Accept, or PayPal Commerce to ensure continued functionality and enhanced security. For more information please read the full announcement, and for assistance, please contact the Event Espresso support team.

The first line of the article you linked to HERE has the same:

On April 15 2025 (extended from January 15, 2025, in Event Espresso version 5.0.32.p), we will deprecate…

Personally, I thought it was clear here that this change applied in 5.0.32.p onwards but I’m sorry for any confusion this has caused.

January 15, 2025 at 2:08 pm

I guess this is a difference in perspective here then. We pushed multiple notices and multiple warnings stating that the payment methods would be deprecated on Jan 15th.

Then we pushed an update out to prevent the deprecation from happening and in the notice stated that as of that update (version 5.0.32.p) the timeline was extended. If you’re not then using that version, may I ask what else is expected to happen here? We don’t have any remote code execution within Event Espresso (and likely never will) so we can’t remotely remove/disable/enable payment methods on the fly.

If it were a feature release stating, “As of version 5.1.11, users can cancel their own registrations via email”, you wouldn’t expect that feature to be within a previous version, right?

For me, it’s the same logic here, and I guess that’s where the misunderstanding has come from. It’s too late to do anything useful about it now (I can update the doc, but as the date has already passed, it doesn’t help) but will note to try and be clearer should something like this come up again.

So currently, I can only apologise for any confusion caused by this.