Important Note

Legacy API integration and features including Advanced Integration Method (AIM), Server Integration Method (SIM), Direct Post Method (DPM), Relay Response and Silent Post are now obsolete and in the process of being phased out. We strongly suggest using one of our modern integration methods with your Authorize.net account. Visit our Developer Center and Upgrade Guide for more information on our updated APIs.

Authorize.net Integration Options

Authorize.net offers a variety of integration options, each tailored to meet specific merchant needs. Here are the recommended options:

Authorize.net API

Replaces: Advance Integration Method (AIM), SOAP API
Requirements: API Login ID, Transaction Key, Authorize.net API
Alternative Authentication Support: OAuth
Description: All transaction methods previously available through AIM can be achieved using the methods described in Payment Transactions in the API Reference using XML or JSON.
Supported Products: 

• Payment Transactions (Credit Card, eCheck/ACH)
• Customer Profiles
• Recurring Billing 
• Fraud Management
• Transaction Reporting

Accept.js

Replaces: Direct Post Method (DPM)
Requirements: API Login ID, Public Client Key, Transaction Key, Authorize.net API
Alternative Authentication Support: OAuth for follow on Transaction creation call.
Description: Accept.js allows you to use your own custom payment form, reducing PCI DSS burdens as you never directly handle the data. You can submit your payment data directly to Authorize.net and receive a temporary token for the actual transaction processing. The Authorize.net API supports using the temporary token in place of actual payment data.

Accept Hosted

Replaces: Server Integration Method (SIM)
Requirements: API Login ID, Public Key, Transaction Key, Authorize.net API
Alternative Authentication Support: OAuth
Description: Accept Hosted offers a hosted, mobile-optimized payment form that provides greater flexibility. You can use the Authorize.net API to request a hosted payment token, then use the token to invoke the form. You can choose to embed it or redirect to it.

Accept Customer

Replaces: Hosted Customer Information Manager (CIM)
Requirements: API Login ID, Transaction Key, Authorize.net API
Alternative Authentication Support: OAuth
Description: With Accept Customer, you can use the Authorize.net API to store CIM customer and payment profiles. It offers a hosted, mobile-optimized payment form that lifts the PCI DSS burden from merchants and complies with PCI SAQ-A.

In-Person (includes Apple Pay, Google Pay)

Replaces: --
Requirements: API Login ID, Transaction Key, CSRs for alternate payments
Description: The In-Person SDK allows merchants to build semi-integrated POS systems, where the POS system and the system processing the payment data are separate. You can integrate EMV and MSR into one customizable system, effectively reducing the burden of both EMV and PCI certification.

Webhooks

Replaces: Silent Post
Requirements: API Login ID, Transaction Key, REST API
Alternative Authentication Support: OAuth
Description: Webhooks is our next-generation, fault-tolerant notification system that provides greater awareness of your processing. You can be notified of system events from your transaction processing, the Advanced Fraud Detection Suite, Automated Recurring Billing, and Customer Information Manager. You can manage your Webhooks using our new REST API, or through the Merchant Interface. We will retry failed notifications for up to five days.

To view all Authorize.net integration options, please refer to the API documentation.

Certified Solutions

Solutions such as shopping carts are ideal for merchants with minimal Web development resources. Shopping carts are Internet companies that host or provide payment form solutions for merchant websites.