topic Re: New API Problem in Integration and Testing

New API Problem

edev — Wed, 24 Sep 2014 16:11:57 GMT

We have a massive J2EE application which uses Authorize.net. Within the application we have a payment system which uses two different accounts at Authorize.net.

The new API requires me to compile the API and Trans key. How can I resolve this issue without re-writing half of your source code?

Please respond to this problem ASAP.

Thank you,

Eric

Re: New API Problem

RaynorC1emen7 — Wed, 24 Sep 2014 16:23:18 GMT

The new API? you mean the new SDKs? you don't have to use it.

Re: New API Problem

edev — Wed, 24 Sep 2014 16:29:41 GMT

I have an email saying the IP Address we are hitting is no longer going to be used. The deprecated IP address is hard coded in the old API we are using.

I have to upgrade the new SDK to the latest version (only one I can find on authorize.net site).

We have two different bank accounts for one application which is now failing because the SDK needs to be compiled with the keys.

I would need to re-write the SDK to change the classes so they are different for the two bank accounts...

Re: New API Problem

RaynorC1emen7 — Wed, 24 Sep 2014 17:56:15 GMT

The API itself having changes much, wouldn't it be easier to change your old code to use domain name instead of IP address?

Re: New API Problem

edev — Wed, 24 Sep 2014 18:16:13 GMT

The IP Address appears hard coded in the SDK. I have checked our DNS and we have not hard coded it anywhere.

Re: New API Problem

RaynorC1emen7 — Wed, 24 Sep 2014 18:25:37 GMT

One way or the other, I guess you will have to rewrite it

Re: New API Problem

RichardH — Wed, 24 Sep 2014 18:57:56 GMT

Hello,

None of the Authorize.Net SDKs use an IP address for an endpoint.

Richard