|
Alaska Tactical
|
November 13, 2024 at 2:46 pm
I need instructions on how to update the existing Authorize AIM account to the API version that you now require.
|
|
Alaska Tactical
|
November 13, 2024 at 2:46 pm
We currently use the Authorize AIM for payment processing and I’m seeing your notification that this will no longer be supported. Can we purchase the Authorize.net Accept plugin and will this correct those configurations that need to be made?
|
|
Tony
|
November 14, 2024 at 6:37 am
Hi there,
I’ve merged your 2 threads together just becuase they are both related to Auth.net AIM.
The Auth.net AIM integration method has been deprecated by Auth.net themselves (see HERE) so we are force to follow to keep up to date, so this isn’t technically our own requirement.
We don’t have a direct replacement for AIM but the closest we have is Auth.net Accept:
https://eventespresso.com/product/eea-authorizenet-accept/
and yes, we recommend you switch from Auth.net to Accept.
The credentials you need from your Auth.net account are the same with your API Login ID and Transaction Key:
https://support.authorize.net/knowledgebase/Knowledgearticle/?code=000001271#:~:text=Steps%20to%20Generate%20Your%20API%20ID%20and%20Transaction/Signature%20Key
You will also need to enable transaction reporting from within your Auth.net account:
https://developer.authorize.net/api/reference/features/transaction-reporting.html
|
