The items on this page represent API Implementations that are supported but no longer actively maintained or enhanced. For newer alternatives, please see below.
Using our current API guarantees that you will always have:
• The latest features
• Continual updates and improvements
• The most active community of fellow developers
Understanding the Authorize.Net API
If you previously integrated with the Authorize.Net platform, you may be used to seeing each of our features documented as separate and distinct APIs. Within our newer documentation, you’ll find that all of our features are a part of a larger cohesive API set.
API Support Status
|SOAP API||Deprecated||Use Authorize.Net API with XML or JSON|
|AIM||Supported||Recommend using Authorize.Net API|
|Hosted CIM||End of Life 3/1/2018||Use Accept Customer|
|SIM||Deprecated||Use Accept Hosted|
|WebLink||End of Life 4/30/2017||Recommend using Accept Hosted|
Supported - API is fully supported and maintained including updates and enhancements
Deprecated - API is now obsolete and in the process of being phased out. See comment field for suggested replacement.
End of Life - API is no longer supported and will return an error if used after specified date.
STATUS: End of Life May 31, 2017
A change to the HTTP verb from GET to POST will remediate this issue, however, we recommend upgrading your application to use the Authorize.Net API: http://developer.authorize.net/api/reference/
After March 31, 2017, all GET requests to the Sandbox endpoint https://test.authorize.net/gateway/transact.dll
will fail and will return status code 405 Method Not Allowed.
After August 31, 2017, all GET requests to the https://secure.authorize.net/gateway/transact.dll and https://secure2.authorize.net/gateway/transact.dll endpoints will fail and will return status code 405 Method Not Allowed.
The Authorize.Net API includes all of the SOAP API functionality plus additional features such as Authorize.Net Accept, creating one-time transactions and enhanced Customer Profile methods.
We have deprecated our SOAP API that offered support primarily for Customer Information Manager. We strongly recommend that developers move to the Authorize.Net API using XML or JSON. This will allow us to continue providing developers with the most up-to-date features and to support a single, consistent platform.
Advanced Integration Method (AIM)
STATUS: Supported but no longer updated
All of the transaction methods previously available through AIM are possible using the methods described in Payment Transactions in the the API Reference using XML or JSON. If you are using transaction methods documented as part of what we previously called our "AIM XML" API, these transaction methods have been incorporated into our current broader Authorize.Net API. These transaction requests can continue to be used as is.
If you are using our legacy AIM Name Value Pair (NVP) method, you're posting your transaction requests to a URL ending in "transact.dll", and the form field names begin with "x_". These types of transaction requests can be brought current by recreating them using the methods described in Payment Transactions in the the API Reference using XML or JSON.
If you are using our legacy AIM Name Value Pair (NVP) method and need to troubleshoot existing code, you may find it helpful to refer to the existing AIM NVP documentation:
STATUS: Deprecated / End-of-Life on March 1, 2018.
Upgrade to Accept Customer
Hosted CIM has been replaced by Authorize.Net Accept Customer, a fully hosted solution for capturing payment information that allows developers to leverage our Customer Profiles API while maintaining SAQ-A level PCI compliance. Our forms are mobile-optimized and designed to reduce friction in your consumer experience.
Hosted CIM pages at https://test.authorize.net/profile/ are no longer being updated and will return HTTP Error 410 after March 1, 2018.
Payment Form (SIM and DPM)
With the release of both Accept Hosted and Accept.js, we are beginning the process to deprecate and sunset our legacy SIM and DPM integration methods. Going forward, we will correct bugs with SIM/DPM, but will not add any new functionality.
We will soon announce an official end-of-life timeline for SIM and DPM, so we encourage you to upgrade any existing SIM/DPM solutions to use Accepted Hosted or Accept.js.
Authorize.Net Accept Hosted is a mobile-optimized, PCI DSS SAQ-A compliant solution for accepting payments. Accept Hosted is a replacement for SIM with many advantages, including the freedom to accept payments while reducing PCI scope and development efforts.
STATUS: End-of-Life on April 30, 2017
For a simple, secure payment form, which will work great on any device, we recommend
Authorize.Net Accept Hosted.
The WebLink integration method will be removed on April 30, 2017. From that date, all requests to https://secure.authorize.net/gateway/transact.dll that do not include complete authentication credentials will return an error response code of 92 (The gateway no longer supports the requested method of integration). An indication that you may be using WebLink would be the absence of a credential field such as x_tran_key or x_fp_hash in code similar to this:
<form action = "https://secure.authorize.net/gateway/transact.dll"> <input type = "hidden" name = "x_login" value = "MyLoginId"> <input type = "hidden" name = "x_version " value = "3.0"> <input type = "hidden" name = "x_show_form" value = "payment_form"> <input type = "hidden" name = "x_amount" value = "1.00"> <input type = "submit" value = "Click Here for Secure Order"> </form>