The Authorize.Net Developer Blog

Posts from Authorize.Net employees, community members and experts about integrating with the Authorize.Net Payment Gateway: sample code, tutorials, and problem-solving techniques, just to name a few.

HTTP GET Disablement Date - Updated 2X

by Administrator Administrator ‎04-10-2017 10:29 AM - edited ‎05-30-2017 05:47 PM (80,536 Views)

Update 2: Updated message returned as reason response code 66, "This transaction cannot be accepted for processing" if transactions attempted using GET.


Update 1: HTTP GET now disabled in sandbox.



As you are probably aware, HTTP GET methods no longer adhere to current PCI DSS protection requirements. As such, we are updating our sandbox and production environments to no longer allow HTTP GET methods for transaction requests.


The HTTP GET disablement dates are as follows:


Sandbox: April 12, 2017

Production: May 31, 2017

We are disabling the sandbox well in advance of production to allow you time to test your solutions and ensure you are no longer submitting HTTP GET requests. Any transaction request using HTTP GET that is submitted after May 31st will fail.


A change to the HTTP verb from GET to POST will remediate this issue, however, we recommend using this as an opportunity to upgrade your application to use the Authorize.Net API:


After April 12, 2017, all GET requests to the Sandbox endpoint will fail and will return a reason response code 66, "This transaction cannot be accepted for processing."


After May 31, 2017, all GET requests to the and endpoints will fail and will return reason response code 66, "This transaction cannot be accepted for processing."

by Catmanwagner
on ‎04-11-2017 04:54 AM

May 11, 2017: I have 4 ecommerce websites that are about 10 years old.  The developer is gone.  I have all the credentials.  I need someone to placae the new API code in to the shopping cart (I think), as we have moved from Paytrace to Authorize. net  Can anyone help? Do you know someone?  Me:

on ‎04-13-2017 02:12 AM

Hi All,

I am new to . 


Can anyone please let me know the validity of DPM ?


We are planning to use DPM with payment form having all the field which accept credit card info and post this form to .


Does going to stop support for this  or they are continue with this method ?


I have checked the upgrade guide in which they suggested to use accept.js but there are lots of challanges to integrate accept.js in our java based site.


Can anyone please let me know shall I continue with DPM (directly posting a form to with action giving in form) or use accept.js method ?


Please please help me !!

Thanks in advance.

‎04-13-2017 10:01 AM - edited ‎04-13-2017 10:01 AM

Hi @raviparmarce88,


As per our Upgrade Guide, DPM is officialy deprecated. It's still supported and will continue to work. However, deprecated means that we will remove support at some future time, after which it will no longer be available. We have not yet announced any end of life date for DPM. When we do announce a date, why try to put it as far in the future as practical.


Anyone continuing to use DPM should be investigating a new solution. We don't recommend that anyone start a new integration using DPM, as there will be a date in the future after which it will not work.

on ‎04-28-2017 07:38 AM

 Hi @Catmanwagner


The upgrading of your application to the new API typically doesn't require that much work. We have completed many such upgrades.


Contact us for more information.