How To Integrate The Authorize.Net Payment Gateway With Your Website
03-28-201208:56 AM - edited 03-28-201208:57 AM
You have registered your domain name, built your website and have added all the products or services that you'd like to sell. Now what? Your next step is to get a merchant account and a gateway account so that you can accept online payments from your customers.
Authorize.Net provides a number of ways to integrate your website to our gateway.
Authorize. Net’s integration methods:
Server Integration Method (SIM) is a website connection method that allows merchants to direct their customers to Authorize. Net’s secure server so that they can post transactions directly. It requires a transaction-unique token for transaction authentication. The site sends the fingerprint and transaction details to Authorize.Net, which will then attempt to recreate the fingerprint with the four pieces of data (API Login, Sequence Number, UTC Timestamp and Amount) and the transaction key stored in the account. If Authorize.Net is able to recreate the fingerprint, it allows the customer to access our hosted payment form to submit the transaction. The customer is taken to our secure, hosted payment form to enter their payment and shipping information and the process is completed with a confirmation receipt page that reports a summary of the transaction back to the customer. If the Authorize.Net system cannot create an identical fingerprint, then the transaction will be rejected. This method may require a web developer depending on your experience.
Advanced Integration Method (AIM) allows merchants to customize their own payment form and receipt, as well as submit transactions over a server- Secure Sockets Layer (SSL) connection. The only thing that happens on the gateway side is the authorization and verification of the transaction. Everything else is done on the merchant's site. This method may require a web developer depending on your experience.
Direct Post Method (DPM) provides merchants with several features for configuring transaction security options and further customizing their customer’s checkout experience. The customer leaves the merchant’s website very briefly and is immediately directed back again. The customer enters their payment details into a form presented by the merchant’s server. Upon submitting this form, they are sent directly to Authorize.Net and then immediately directed back to the merchant’s server to view a receipt page containing the transaction results. This method may require a web developer depending on your experience.
Simple Checkout is another tool that we offer which allows merchants to create 'Buy Now' and 'Donate Now' buttons for their website, providing a quick and easy integration method for connecting to the Payment Gateway. This does not require extensive programming skills. You are given a snippet of HTML code that you can copy and paste into your website code anywhere you'd like the buttons to be displayed.
Here is a summary of the Authorize.Net integration methods:
Server Integration Method (SIM)
◦ Simplifies PCI Compliance
◦ Scripting techniques to authenticate transaction
◦ Customizable hosted payment form
◦ No SSL required
Advanced Integration Method (AIM)
◦ Most common integration method
◦ Allows control over all phases of the customer’s online transaction experience
◦ Configurable transaction response integrates easily with merchant applications
◦ Merchant handles cardholder information
◦ SSL is required
Direct Post Method (DPM)
◦ Authorize.Net Payment Gateway handles all the steps in the secure transaction while remaining virtually transparent
◦ Simplifies PCI Compliance
◦ Full control over the checkout process including look and feel