Re: Upgrading the Authorize.net AIM API

+1 Once there is an agreement for the integration strategy, we can update all 3rd party integrations accordingly. This should not block any work on integration updates. Regards, Michael Am 26.09.18 um 03:00 schrieb Scott Gray: Maybe, but I see no reason to have an architecture discussion

Re: Upgrading the Authorize.net AIM API

+1 Nameet, sounds good. Thanks & Regards --- Arun Patidar Director of Information SystemsHotWax Commerce On Wed, Sep 26, 2018 at 6:31 AM Scott Gray wrote: > Maybe, but I see no reason to have an architecture discussion as a > prerequisite for a simple API update. > >

Re: Upgrading the Authorize.net AIM API

Maybe, but I see no reason to have an architecture discussion as a prerequisite for a simple API update. Regards Scott On Tue, 25 Sep 2018, 06:03 Jacques Le Roux, wrote: > I guess Pierre is referring to > https://markmail.org/message/zf5tz7qpgokldvtl and above... > > Jacques > > > Le

Re: Upgrading the Authorize.net AIM API

I guess Pierre is referring to https://markmail.org/message/zf5tz7qpgokldvtl and above... Jacques Le 22/09/2018 à 14:12, Pierre Smits a écrit : I believe first the discussion on how we’re going to deal with these kind of 3rd party solution integrations, whether they be fintech, logistic or

Re: Upgrading the Authorize.net AIM API

I believe first the discussion on how we’re going to deal with these kind of 3rd party solution integrations, whether they be fintech, logistic or other, should be completed first. Many times aspects regarding this has been brought forward in other threads and in tickets. Best regards,

Upgrading the Authorize.net AIM API

Hello Team, While researching around Advanced Integration Method (AIM) Authorize.net API, I found that the AIM API has now been deprecated. Authorize.net suggest upgrading the AIM support to XML or JSON based support. Please let me know your thoughts. Here is the link for your reference