When looking at the Upgrade Guide it only indicated the solution for AIM NVP, so I automatically assumed it was that, but looking deeper, we're apparently using AIM ARB.
Since AIM ARB wasn't included in the list of End of Life and deprecated methods in the upgrade guide (https://developer.authorize.net/api/upgrade_guide/), is it still recommended to upgrade AIM ARB to Authorize.Net API? If so, how would we be able to upgrade it?
Solved! Go to Solution.
05-09-2019 04:00 AM
You should be good if you are using the ARB API.
05-10-2019 08:43 AM
Not sure I understand the question, what do you mean by AIM ARB? AIM is only for single transaction processing. For recurring you will need the Authorize.Net XML/JSON API https://developer.authorize.net/api/reference/index.html#recurring-billing
Hope this helps,
Brian
05-10-2019 08:06 AM
@brianmc wrote:Not sure I understand the question, what do you mean by AIM ARB? AIM is only for single transaction processing. For recurring you will need the Authorize.Net XML/JSON API https://developer.authorize.net/api/reference/index.html#recurring-billing
Hope this helps,
Brian
Hi Brian,
Sorry, I'm not yet familiar with Authorize.Net so I thought ARB is also part of AIM. What I meant is just ARB.
Basically, I was asking whether our ARB code needs to be upgraded to the latest Authorize.Net API or not because I'm not sure if our code is outdated or not.
Thanks :)
05-10-2019 08:19 AM
You should be good if you are using the ARB API.
05-10-2019 08:43 AM
@brianmc wrote:You should be good if you are using the ARB API.
Awesome! Thanks Brian :)
05-10-2019 08:44 AM