topic Re: Discussion for Important Authorize.Net Network Change in Integration and Testing

Testing Akamai in the Sandbox

RichardH — Mon, 22 Feb 2016 17:36:50 GMT

Sandbox URLs are unchanged and are already configured with Akamai for testing
Version 1.8.5 of our language SDKs are configured to use the new Akamai endpoints

Re: Discussion for Important Authorize.Net Network Change

zan — Wed, 15 Jul 2015 01:03:54 GMT

Hi,

Is there any changes to the url for the sandbox too? I couldn't find any information on this in the article and FAQ

Thanks,

Zan

Re: Discussion for Important Authorize.Net Network Change

RichardH — Wed, 15 Jul 2015 01:29:47 GMT

Hello @zan

The sandbox URLs are unchanged. They now include the Akamai network changes and are ready for you to begin testing.

Richard

Re: Discussion for Important Authorize.Net Network Change

mbalog99 — Fri, 17 Jul 2015 11:14:04 GMT

That doesn't make sense. If the change in production is just to change the URL to Secure2, but the sanbox URL is unchanged? Then what am I testing in the sandbox? The network changes that are going on behind the scenes? So If I sned to the same Gateway url for the sanbox and everthing seems to work, then the productionURL will work?

Re: Discussion for Important Authorize.Net Network Change

RaynorC1emen7 — Fri, 17 Jul 2015 12:25:09 GMT

Phase One (Now through June 2016) – We have created three new URLs for transaction processing that are hosted by Akamai. You can update your website or payment solution to point to the new transaction URLs today, which will provide the immediate benefits detailed above. Come October, merchants connected to Akamai should no longer be affected by planned downtimes.
Phase Two (June 2016) – We will automatically direct all of our existing transaction processing URLs to connect through Akamai in June of 2016. After this change, all transaction URLs will connect to Authorize.Net through Akamai.

Because for production, they need to make sure it work before moving to everyone.

On sandbox, it call sandbox for a reason, it the test server.

Re: Discussion for Important Authorize.Net Network Change

egdavis — Fri, 17 Jul 2015 18:36:42 GMT

So, @RaynorC1emen7, in response to @mbalog99's question, are you basically saying that sandbox orgs have already entered into Phase One (transaction processing automatically being directed through Akamai), while production orgs are still in Phase Two (the user has an option to switch to a new url in order to test transaction processing through Akamai)?

Re: Discussion for Important Authorize.Net Network Change

RichardH — Fri, 17 Jul 2015 18:50:12 GMT

Hello @egdavis

Your summary is absolutely correct, our sandbox uses Akamai now.

Richard

Re: Discussion for Important Authorize.Net Network Change

RaynorC1emen7 — Fri, 17 Jul 2015 18:51:15 GMT

Akamai is available for testing now in our sandbox environment. We strongly encourage you to test your solution prior to making any production change to ensure that you will not experience any disruptions to transaction processing.

The way I read it, yes. The sandbox is using it.

Then on production phase two, will push to the old url (for everyone). I would said if anyone have connection issue on production shold try the new url.

Re: Discussion for Important Authorize.Net Network Change

egdavis — Fri, 17 Jul 2015 19:00:35 GMT

Great, thanks!

Re: Discussion for Important Authorize.Net Network Change

kandha — Mon, 20 Jul 2015 08:39:03 GMT

Hello Richard,

Is this new url updated in sdk libraries? If not when will get update?

Re: Discussion for Important Authorize.Net Network Change

RaynorC1emen7 — Mon, 20 Jul 2015 11:18:49 GMT

Change it if you want to, on phase two, it will roll out to the existing url.

Re: Discussion for Important Authorize.Net Network Change

gadellnet — Mon, 20 Jul 2015 19:34:59 GMT

I second @kandha inquiry regarding SDK updates. We are using the nuget package for CIM transactions on our website.

Re: Discussion for Important Authorize.Net Network Change

oskar — Mon, 20 Jul 2015 21:32:01 GMT

I thought the implementation of Akamai had already gone live in production. Am I mistaken?

We were unable to process transactions about 1 month ago. That's when I learned of the Akamai project.

Did I read the FAQ wrong? Am I imagining that we were unable to process transactions? Opening the firewall solved our problem.

Any info would be appreciated.

Thanks!

Re: Discussion for Important Authorize.Net Network Change

RaynorC1emen7 — Mon, 20 Jul 2015 22:59:24 GMT

If you read the link. Phase one now to June, 2016, to use Akamai, you will need to change the production url.

Phase two, on June, 2016, change it to the existing production url.

About a month about they change their SSL cert.

Re: Discussion for Important Authorize.Net Network Change

oskar — Tue, 21 Jul 2015 19:29:45 GMT

For the record, I can read and have read both the current FAQ and the message posted to this developer forum. I fully understand the time table and the implications.

I read the FAQ at that time of our issue, June 26-27. I could swear that the time table was different from the current posted FAQ. There is no history and it's not at archive.org. If someone can confirm that prior to June 26 the schedule for implementation was the same as it is now then that would be helpful.

The time of our issue does coninside with the SSL cert change. However, we've already worked through the issue of certificate validation when we created the payment workstations. Good idea...

Re: Discussion for Important Authorize.Net Network Change

sreekanthreddyi — Fri, 24 Jul 2015 05:23:08 GMT

Hi Sir,

In production each transaction is giving error after pointing to the new Akamai transaction URLs. It is because of the Python Authorize.net API (Authorizesauce) https://github.com/sreekathreddyila/authorizesauce which is giving errors like AVS issue, Split() function error and General errors etc.,

Please provide me the Request and Response code documentation of the New Akamai URLs, so that we will update the Authorize.net Python API.

Currently reverted again to the Previous transaction URLs. Please let me know if I dont update my Python library will these errors come even after June 2016 in Phase2.

Thanks,

Sreekanth

Re: Discussion for Important Authorize.Net Network Change

RaynorC1emen7 — Fri, 24 Jul 2015 19:39:44 GMT

Not a python programmer, but sound like the code assuming it getting some delimited response but not. Can it output the raw response instead of trying to split the non-delimited response?

Re: Discussion for Important Authorize.Net Network Change

RichardH — Fri, 24 Jul 2015 20:25:28 GMT

Have you tested this in the sandbox? The sandbox is setup now for testing with Akamai prior to changing your URL to the production Akamai endpoint.

Richard

Re: Testing Akamai in the Sandbox

mlingidi — Mon, 27 Jul 2015 09:03:54 GMT

Hi,

We are using Authorize.net in our application which is already developed. How to know weather we are connecting to Authorize.Net via IP address or url's.

I am able to see two urls are used in our applictaion are as follows :

TEST_URL = "https://apitest.authorize.net/xml/v1/request.api";
public const string URL = "https://api.authorize.net/xml/v1/request.api";

Please let us know.

Thanks,

Murali

Re: Testing Akamai in the Sandbox

mbalog99 — Mon, 27 Jul 2015 10:41:59 GMT

SOunds like you answered your question.... you found URL's