Authorize.net Payment Solutions

Authorize.net provides two types of payment solution

• AIM (Advanced Integration Method)
• SIM (Server Integration Method)

AIM (Advanced Integration Method): AIM is a customizable payment processing solution that gives the merchant control over all the steps in processing a transaction, including:

• Collection of customer payment information through a custom application
• Generation of a receipt to the customer
• Secure transmission to the payment gateway for transaction processing
• Secure storage of cardholder information
• And more, depending on the merchant’s business requirements.

The security of an AIM transaction is assured through a 128-bit Secure Sockets Layer (SSL) connection between the merchant’s Web server and the Authorize.Net Payment Gateway.

AIM is an ideal integration solution because it allows merchants the highest degree of customization and control over their customers’ checkout experience.

AIM Minimum Requirements: Before you begin, check with the merchant to make sure that the following AIM requirements have already been met. It is strongly recommended that you work closely with the merchant to ensure that any other business and Web site requirements (for example, bank or processor requirements, Web site design preferences) are included in their AIM integration.

• The merchant must have a U.S. based merchant bank account that allows Internet transactions.
• The merchant must have an e-commerce ( Card Not Present) Authorize.Net Payment Gateway account.
• The merchant must have a valid Secure Sockets Layer (SSL) certificate and their Web site must be capable of initiating both client and server-side SSL connections.
• The merchant’s Web site must have server-side scripting or CGI capabilities such as ASP Classic, C#, Cold Fusion, Java, Perl, PHP or VB.Net.
• The merchant must be able to store payment gateway account data securely (for example, API Login ID or Transaction Key)

Features of AIM: In addition to basic transaction processing, AIM provides merchants with several features for configuring transaction security options and further customizing their customers’ checkout experience. These features are listed in the AIM Feature Selection Guide provided below. Please take a few moments to discuss these with your merchant and select which features they would like to include in their integration.

Features of AIM: In addition to basic transaction processing, AIM provides merchants with several features for configuring transaction security options and further customizing their customers’ checkout experience. These features are listed in the AIM Feature Selection Guide provided below. Please take a few moments to discuss these with your merchant and select which features they would like to include in their integration.

SIM (Server Integration Method): SIM uses scripting techniques to authenticate transactions with a unique transaction fingerprint.

The Authorize.Net Payment Gateway can handle all the steps in the secure transaction process - payment data collection, data submission and the response to the customer - while keeping Authorize.Net virtually transparent.

• Payment gateway hosted payment form employs 128-bit SSL data encryption.
• Digital fingerprints enhance security, providing multiple layers of authentication.
• Customize the look and feel of the payment gateway hosted payment form and/or receipt page.

SIM Minimum Requirements: Before you begin, check with the merchant to make sure that the following SIM requirements have already been met. It is strongly recommended that you work closely with the merchant to ensure that any other business and Web site requirements (for example, bank or processor requirements, Web site design preferences) are included in their SIM integration.

• The merchant must have a U.S.-based merchant bank account that allows Internet transactions.
• The merchant must have an e-commerce (Card Not Present) Authorize.Net Payment Gateway account.
• The merchant's Web site must be capable of performing an HTML Form POST to request the secure payment gateway hosted payment form.
• The merchant's Web site or hosting provider must have server scripting or CGI capabilities such as ASP Classic, Cold Fusion, PHP or Perl.
• The merchant must be able to store payment gateway account data securely (for example, API Login ID, Transaction Key, And Secret Answer).

Features of SIM: In addition to basic transaction processing, SIM provides merchants with several features for configuring transaction security options and further customizing their customers' checkout experience. These features are listed in the SIM Feature Selection Guide table below. Please take a few moments to discuss these with your merchant and select the features they would like to include in their integration.

Available API Options

• Simple Checkout (http://developer.authorize.net/api/simplecheckout/)
• Direct Post Method (http://developer.authorize.net/api/dpm/)
• Server Integration Method (http://developer.authorize.net/api/sim/)
• Advanced Integration Method (http://developer.authorize.net/api/aim/)
• Automated Recurring Billingâ„¢ (http://developer.authorize.net/api/arb/)
• Customer Information Manager (http://developer.authorize.net/api/cim/)
• Card Present Integration (http://developer.authorize.net/api/cardpresent/)
• Transaction Details API (http://developer.authorize.net/api/transaction_details/)

How Authorize.net Works

• The merchant submits a credit card transaction to the Authorize.Net Payment Gateway on behalf of a customer via secure connection from a Web site, at retail, from a MOTO center or a wireless device.
• Authorize.Net receives the secure transaction information and passes it via a secure connection to First Data Independent Sales.
• First Data Independent Sales submits the transaction to the Credit Card Interchange (a network of financial entities that communicate to manage the processing, clearing, and settlement of credit card transactions).
• The Credit Card Interchange routes the transaction to the customer’s Credit Card Issuer.
• The Credit Card Issuer approves or declines the transaction based on the customer’s available funds and passes the transaction results, and if approved, the appropriate funds, back through the Credit Card Interchange.
• The Credit Card Interchange relays the transaction results to First Data Independent Sales.
• First Data Independent Sales relays the transaction results to Authorize.Net.
• Authorize.Net stores the transaction results and sends them to the customer and/or the merchant. This communication process averages three seconds or less!
• The Credit Card Interchange passes the appropriate funds for the transaction to the Merchant’s Bank, which then deposits funds into the merchant’s bank account. The funds are typically deposited into your primary bank account within two business days.