cancel
Showing results for 
Search instead for 
Did you mean: 

changes requiered for updated Authorize.Net/Akamai

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.

sysadmin
Member
11 REPLIES 11

Hello @sysadmin

 

You can read more about these changes here: https://community.developer.authorize.net/t5/The-Authorize-Net-Developer-Blog/Important-Authorize-Ne...

 

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

RichardH
Administrator Administrator
Administrator

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.

 

abuttitta
Member

make sure it just

 

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

 

and nothing else

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

What was the exact full url you trying to use?

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

  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.

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

  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.

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