Upgrade Guide

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

For questions about migrating an existing solution, please contact our developer support team.


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


API Method Status Comments
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 Supported
Recommend using Accept Hosted
DPM Supported Recommend using Accept.js
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: Deprecated 

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

Use the methods described in Payment Transactions in the the API Reference using XML or JSON.

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:

AIM NVP Guide (PDF)PayPal AIM NVP Guide (PDF)   


Hosted CIM

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.


Server Integration Method (SIM) and Direct Post Method (DPM)

STATUS: Supported

For new hosted payment form implementations, we recommend using Accept Hosted.  For new DPM implementations, use Accept.js.

SIM provides ways to assist developers with PCI compliance. Using SIM, a developer could send the customer to a payment form generated and hosted on the Authorize.Net site. Using DPM, a developer could have their own form send payment data directly to the Authorize.Net site for processing.

The Accept suite of tools provide a modern implementation of these functions in a way that's more flexible and reliable for developers. We recommend developers looking to implement a hosted payment form use Accept Hosted. Developers who want to create and host their own form without processing or storing sensitive information on their server can use Accept.js to receive a one-time use "payment nonce" to use in place of the card data.

Developers using the SIM hosted payment form or DPM should consider moving to the Accept tools. Developers still using SIM can find archival documentation in our Server Integration Method (SIM) Guide (PDF).




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">