Authorize.net CIM Payment Module

REQUIREMENTS

• Authorize.net Account Support Authorize CIM Development by Clicking Here to Sign Up for an Account now

• CURL is required and MUST be compiled into PHP with TLS/SSL support

• Your API login ID and transaction key (generated in your authorize.net account area)

• You need to have HTTPS/SSL active on your site to protect your customers’ sensitive data

INITIAL SETUP

You need to generate your username and transaction key:

1. Log in to your Authorize.net account on the authorize.net website.

2. Click on “Account” in the Main Menu Bar.

3. Click on the “API Login ID and Transaction Key” link under Security settings.

4. Your username will be shown. Record it.

5. To generate a new Transaction Key (which is required for new accounts, and also recommended if switching from test mode to production mode), fill in the answer to the security question, and check the box to disable the old key.

6. Copy and paste your Transaction Key into your Zen Cart settings.

CONFIGURING THE MODULE

1. Login to your Zen Cart Admin

2. Go to Modules

3. Go to Payment

4. Select New Credit Card (authorizenet_cim) and click Install

5. Enter your Login ID and Transaction Key as recorded earlier

6. Configure the rest of the settings as desired:

7. Transaction Mode - Set this to Production for normal use, or simulate some tests using the Test option (See below for testing instructions). NOTE: This can be set to “Test” or “Production” regardless of whether your Authorize.net account is in Test mode.

8. Authorization Type - In most cases you will want to do an “Authorize+Capture” to capture payment immediately. In some situations, you may prefer to simply “Authorize” transactions, and then manually use your Merchant Terminal to formally capture the payments (esp if payment amounts may fluctuate between placing the order and shipping it)

9. Request CVV Number - If enabled, this will cause the customer to be asked for their 3-or-4 digit number off the back of their card. This is important for card validation, and should usually be enabled.

10. Validation mode - should card info be validated.

11. Sort Order of Display – Any value greater than zero will cause this payment method to appear in the specified sort order on the checkout-payment page

12. Payment Zone - if you want only customers from a particular zone to be able to use this payment module, select that zone here.

13. Set Completed Order Status - For Captured and Approved orders, what order-status should be set?  Default recommended is “Processing”

14. Set Refunded Order Status - For transactions that are refunded, this order status setting will be used. Recommended: “Pending”

15. Debug Mode - If you need to diagnose what details are sent to and received from the Authorize.net gateway, enable this option. Logs will be stored in the /cache folder and numbered in obscurity to prevent snooping. Set it to “Alerts Only” if you want to be emailed if payment system errors occur but not clutter log folders on the server.

16. Once properly configured the Authorize.net Card on File - COF will now also be enabled.

TESTING

You’ll probably find that even for testing you’ll need to have an SSL certificate on your store. Transactions may be rejected if not submitted over SSL.

To test your shop,

• Set your  Authorize.net Transaction Mode to “Test”. You DO NOT need to have your actual account in Testing mode; this will simulate a test even against a Production account.
• Run a transaction in your shop. 
• Once satisfied, set the Transaction Mode to ‘Production’

========================================================

TRANSACTION DATA SHOWN IN ZEN CART

1. Incorporated with each successful order is a listing of:

• Authorize.net Transaction ID
• Approval Code
• Amount

2. This module creates its own payment table. From within the admin, there are easy to read buttons, to void transactions, settle on authorizations, refund transactions, as well as collect more money from card on file transactions if you add items to the order.