Re: Upgrading the Authorize.net AIM API

[Michael Brohl]

+1




This should not block any work on integration updates.

Regards,

Michael


Am 26.09.18 um 03:00 schrieb Scott Gray:

Once there is an agreement for the integration strategy, we can update all 3rd party integrations accordingly.

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, <jacques.le.r...@les7arts.com>
wrote:

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
other,  should be completed first.

Many times aspects regarding this has been brought forward in other

threads

and in tickets.



Best regards,

Pierre Smits

*Apache Trafodion <https://trafodion.apache.org>, Vice President*
*Apache Directory <https://directory.apache.org>, PMC Member*
Apache Incubator <https://incubator.apache.org>, committer
*Apache OFBiz <https://ofbiz.apache.org>, contributor (without

privileges)

since 2008*
Apache Steve <https://steve.apache.org>, committer

On Sat, Sep 22, 2018 at 1:39 PM, Nameet Jain <jnam...@gmail.com> wrote:

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
https://developer.authorize.net/api/upgrade_guide/
https://developer.authorize.net/api/reference/index.html

Thanks
--
Regards,
Nameet Jain

smime.p7s
Description: S/MIME Cryptographic Signature