topic Re: changes requiered for updated Authorize.Net/Akamai in Integration and Testing

changes requiered for updated Authorize.Net/Akamai

sysadmin — Thu, 25 Feb 2016 06:47:53 GMT

Hi,

For :-

AUTH_CAPTURE, AUTH_ONLY, PRIOR_AUTH_CAPTURE, CREDIT and VOID

what are changes requiered for updated Authorize.Net/Akamai by which our existing source code will work properly.

Re: changes requiered for updated Authorize.Net/Akamai

RichardH — Thu, 25 Feb 2016 16:10:34 GMT

Hello @sysadmin

The changes are primarily about how your system connects to Authorize.Net, not the API calls themselves.

Our sandbox is already configured with Akamai, so you can begin testing immediately.

Richard

Re: changes requiered for updated Authorize.Net/Akamai

abuttitta — Fri, 22 Apr 2016 21:52:40 GMT

I've tried several times to use the new URL (https://api2.authorize.net/xml/v1/request.api).

(3 are given, but I assume (?) that I should use the XML version for a Linux server not using SOAP.)

The transactions have all failed. The log message is typically:

Fri, 22 Apr 2016 08:33:28 +0000:Response from AnetApi:
You do not have permission to view this directory or page.

I have no problems when I use the previous URL (https://api2.authorize.net).

I believe that transactions will be re-routed automatically after June 30, 2016. If so, then I'll simply continue to use the previous URL unless someone can explain what the problem is.

Re: changes requiered for updated Authorize.Net/Akamai

RaynorC1emen7 — Fri, 22 Apr 2016 22:15:36 GMT

make sure it just

https://api2.authorize.net/xml/v1/request.api

and nothing else

Re: changes requiered for updated Authorize.Net/Akamai

abuttitta — Fri, 22 Apr 2016 22:20:20 GMT

Yes, the only change I've made is to the URL. The one I showed.

Re: changes requiered for updated Authorize.Net/Akamai

RaynorC1emen7 — Sat, 23 Apr 2016 01:09:02 GMT

What was the exact full url you trying to use?

https://api2.authorize.net just the server it doens't have the full path

Re: changes requiered for updated Authorize.Net/Akamai

abuttitta — Sat, 23 Apr 2016 01:37:05 GMT

You misunderstand. Here is the code from the ANetEnvironment.php file in the

net/authorize/api/constants directory:

const PRODUCTION = "https://api2.authorize.net";

There's nothing more to it. It's been working for months.

The code I'm trying to use, from the instructions given, is:

const PRODUCTION = "https://api2.authorize.net/xml/v1/request.api";

This hasn't worked at all.

Re: changes requiered for updated Authorize.Net/Akamai

RichardH — Sat, 23 Apr 2016 01:59:05 GMT

Hello @abuttitta

If you are using our PHP SDK, it has already been updated to use the Akamai endpoint, you don't need to change anything.

RIchard

Re: changes requiered for updated Authorize.Net/Akamai

abuttitta — Sat, 23 Apr 2016 18:11:13 GMT

The SDK doesn't set the PRODUCTION or SANDBOX constants from what I see.

It doesn't even use the PRODUCTION version.

Who or what sets the constants? Do I need to? Your instructions on the Akamai changes

are confusing, and they've wasted my time. Treat your customers better.

Re: changes requiered for updated Authorize.Net/Akamai

RichardH — Sat, 23 Apr 2016 18:22:25 GMT

If you're using our new controller model with the PHP SDK, switching from sandbox to production is as simple as changing the following from SANDBOX to PRODUCTION:

$response = $controller->executeWithApiResponse( \net\authorize\api\constants\ANetEnvironment::PRODUCTION);

See the example in our readme at https://github.com/AuthorizeNet/sdk-php/blob/master/README.md

Hope this helps.

Richard

Re: changes requiered for updated Authorize.Net/Akamai

abuttitta — Sat, 23 Apr 2016 18:37:46 GMT

No, this doesn't help. Do I need to change the values of the constants or don't I?

If I don't need to change the values, then why did your company notify me about

using the new URLs?

I'd love to end this conversation and get on with my life.

Re: changes requiered for updated Authorize.Net/Akamai

Lilith — Mon, 25 Apr 2016 21:20:09 GMT

The current SDK uses the new URLs.

However, we have sent reminders to all our merchants to ensure they are aware of the coming Akamai SureRoute changes, and to ensure they've taken the necessary steps.

If you're using an updated SDK, then you shouldn't need to take any further steps, since api2.authorize.net is the correct domain.

Specifically, you should stick with the "const PRODUCTION = "https://api2.authorize.net";" setting. The only differences between our Production and Sandbox URLs is the domain name, so the constants "PRODUCTION" and "SANDBOX" only set the domain name, and the rest of the URL is appended to that.

I'll see if we can update our technical reminders to let merchants know that using the current SDK ensures they're already migrated. We apologize for any confusion this might've caused.