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.


Advanced Integration Method (AIM)

STATUS: Now referred to as Payment Transactions in the the API Reference.

If you still need to reference the AIM NVP documentation, please see the following guides:


PayPal AIM NVP Guide (PDF)   


Hosted CIM

STATUS: Deprecated / Upgrade to Accept Customer

DESCRIPTION: Authorize.Net Accept Customer, a fully hosted solution for payment information capture which allows developers to leverage our Customer Profiles API while still maintaining SAQ-A level PCI compliance. Our forms are mobile-optimized and designed to reduce friction in your consumer experience.

As of June 6, 2016 our old Hosted CIM pages available at https://test.authorize.net/profile/ will no longer be updated with any feature enhancements or updates.  Going forward, Authorize.Net may move to an official end-of-life status for /profile/ pages.


Server Integration Method (SIM)


ALTERNATIVE SOLUTIONS:SIM is now referred to as Payment Form.

DESCRIPTION: Our hosted payment form and Direct Post Method (DPM) still use our SIM API. You can find everything you need to know about integrating with those features in our Server Integration Method (SIM) Guide (PDF).



Merchant Web Services API (Returns API)


End-Of-Life Notice


Authorize.Net Reporting API is now the supported method for retrieving eCheck Returns information.  http://developer.authorize.net/api/reference/features/transaction_reporting.html

The Merchant Web Services API (GetReturns) will be removed on July 20th, 2016. From that date forward all requests to https://account.authorize.net/api/merchantapi.asmx will return a response with status code 410 Gone.  On August 20th the endpoint will be removed completely.  Our standard Reporting API methods of GetTransactionList and GetTransactionDetails can be used to return the same returns data as returned in the GetReturns API.