1. WebStore application on the merchant's web site
2. Authorize.Net Gateway Server
3. Merchant account processing center
4. Cardholder's financial institution

1. The WebStore order form on the merchant's web site collects the customer's billing address, shipping address, payment information, etc.
2. This information is converted to an authorization request and sent to the Authorize.Net Gateway.
3. The gateway sends the request to the merchant account processing center.
4. The processing center contacts the cardholder's financial institution to obtain authorization for the payment.
5. The financial institution sends an authorization response (authorized, declined, or referred) which is returned to all previous points in the process.
6. WebStore informs the customer of the outcome.
   If the transaction is authorized, the order is accepted.
   If the transaction is not authorized, the customer must provide another payment method for the order.

1. WebStore application on the merchant's web site
2. Authorize.Net Gateway Server
3. e-Check processing center
4. Check writer's financial institution

1. The WebStore order form on the merchant's web site collects the customer's billing address, shipping address, payment information, etc.
2. This information is converted to an authorization request and sent to the Authorize.Net Gateway.
3. The gateway sends the request to the e-Check processing center.
4. The e-Check processing center contacts the check writer's financial institution to verify the checking account is valid obtain authorization for the payment.
5. The financial institution sends an authorization response (authorized or declined) which is returned to all previous points in the process.
6. WebStore informs the customer of the outcome.
   If the transaction is authorized, the order is accepted.
   If the transaction is not authorized, the customer must provide another payment method for the order.

• An Internet merchant account obtained from an Authorize.Net agent
• System requirements:
  • Perl 5.005+
  • Telnet access if installing Perl modules and OpenSSL
  • An SSL (Secure Socket Layer) implementation consisting of:
    • Net::SSLeay 1.05 Perl module - download entire Net::SSLeay module now
    • openssl-0.9.5 or openssl-0.9.6 c library
  • Digest::MD5 Perl module - download entire Digest::MD5 module now
• WebStore's store setup file configured for Authorize.Net
• WebStore's merchant configuration file for Authorize.Net contains merchant account details

$merchant_file = 'merchant.authorizenet.cfg';

• Move the /Library sub-directoy to an area which can not be accessed using a web browser or place the /Library sub-directoy under HTACCESS.
• Rename the /Library sub-directoy defined in $libr_directory in WebStore's global setup file, ws_global.setup.
• Rename the merchant file.
• Store the merchant file under a sub-directory:
  1. Create a directory under the /Library sub-directory
  2. Store the merchant file under the newly created sub-directory
  3. Set $merchant_file = 'sub-directory/merchant.xxxx.cfg';
     
     

%form_files = (

# KEYS     zero                                        one
  '10' => ['OrderForm.AuthorizeNet.CreditCard.setup',       'Credit Card'],
  '11' => ['OrderForm.AuthorizeNet.Check.setup',            'Personal Check - US citizens'],
  '12' => ['Demo.OrderForm.AuthorizeNet.CreditCard.setup',  'AuthorizeNet Demo: Credit Card'],

); # DO NOT REMOVE - terminates %form_files

x_Login testing

x_Password password

x_Type AUTH_CAPTURE  # AUTH_CAPTURE or AUTH_ONLY

x_MD5

x_Email_Customer FALSE  # TRUE or FALSE

x_Email_Merchant FALSE  # TRUE or FALSE

$merchant_log = 'AuthorizeNet.log';

$merchant_log_size = '100000';  (log file size = 100K)

$pr_type = 'https';
$pr_host = 'secure.authorize.net';
$pr_path = '/gateway/transact.dll';
$pr_port = '443';

$pr_login_test    = 'testing';
$pr_password_test = 'password';

• Visa credit card
• Credit card number 4222222222222
• Valid expiration month and year

• x_Login
  Change the value of x_Login to the merchant ID number you received when you established your Authorize.Net account.
• x_Password
  Change the value of x_Password to the merchant password you received when you established your Authorize.Net account.

THE IMPORT/EXPORT OR USE OF STRONG CRYPTOGRAPHY SOFTWARE IS ILLEGAL IN SOME PARTS OF THE WORLD. YOU ARE ADVISED TO PAY CLOSE ATTENTION TO ANY IMPORT/EXPORT OR USE LAWS WHICH APPLY TO YOU. RDC SOFTWARE IS NOT LIABLE FOR ANY VIOLATION OF LAW YOU MAKE WITH RESPECT TO THE IMPORT/EXPORT OR USE OF STRONG CRYPTOGRAPHY SOFTWARE. IT IS YOUR RESPONSIBILITY.