|
TheGCA
|
May 23, 2023 at 10:26 am
We recently purchased and installed EE5 on our WordPress site. We already have a merchant account plus an authorize.net payment portal for credit card processing. However, authorize.net AIM does not show up as a payment option under Event Espresso payment methods like the documentation says it should.
|
|
Tony
|
May 23, 2023 at 11:07 am
Hi there,
Authorize.net have deprecated the AIM integration method and so we have deprecated our AIM Payment method in favour of Auth.net Accept:
https://eventespresso.com/product/eea-authorizenet-accept/
|
|
carlmbrservices@aol.com
|
May 23, 2023 at 3:14 pm
Why would EE software that was purchased only a month ago not be up to date?
We use authorize.net with a different event espresso account on another WordPress site which is currently taking registrations for an event, and this is not an issue for that site even with an older version of EE. So it is confusing to be advised to pay another $99 for something we should not need??
|
|
Tony
|
May 24, 2023 at 5:41 am
Why would EE software that was purchased only a month ago not be up to date?
I don’t follow, how is EE not up to date?
Authorize.net have an AIM integration which we built a payment method using, Auth.net have deprecated the AIM integration and so we have deprecated the payment method which uses the AIM integration.
See: https://developer.authorize.net/api/upgrade_guide.html
When AIM deprecate an integration they are basically saying you can use it as is but it will no longer be maintained and eventually discontinued completely (become EOL, end of life) so if issues come up with it that can’t be fixed on our end it leaves the customer stuck.
So we deprecated the AIM payment method and it is hidden on new installs, if it has been previously used on the site then it will continue to show there but if issues come up with it the advice will be to switch to the Accept integration.
So it is confusing to be advised to pay another $99 for something we should not need??
I’m sorry it’s confusing but we do not control which integration method a merchant chooses to deprecate, if they deprecate an integration method we have to deprecate our payment method as it relies on their server, not ours.
The AIM integration (on Auth.net’s side) has likely been deprecated in favour of more modern practices (which the Accept.js integration uses) and also helps reduce PCI compliance issues for the end user.
|
