Authorize.Net

Contents of this Topic: ShowHide

Overview

If you use Authorize.Net to process credit card transactions, SEOM can interface directly with your Authorize.Net account.

Payments for orders that are pre-authorized on your website can be captured automatically when you approve those orders in SEOM. The Payment tab of the Process Orders screen synonymous with the Microsoft Access Form object or graphical user interface (GUI) allows you to process new charges, credits, etc. without re-typing the customer’s credit card information.

The Authorize.Net interface requires an open connection to the Internet, such as a DSL or ISDN line or a cable modem. It is not intended for use with dial-up Internet accounts, although it may work if the dial-up connection is always opened before SEOM attempts to send data to Authorize.Net.

Configure SEOM to work with Authorize.Net

Click Save after setting each system parameter.

1. Go to Main Menu > Settings > System Functions > Set System Parameters settings in Stone Edge that enable users to configure the program integrate with their business operations. Stone Edge includes hundreds of System Parameters to do just that. To change a system parameter, go to the Main Menu > Settings > System Functions > Set System Parameters..

2. Select to "left-click" the mouse on an object, usually a row in a table, in the context of Monsoon OMS documentation the Credit Card parameter group.

3. Set parameter CreditCardProcessor to Authorize.Net.

4. Make sure that the CCInfoPrefix parameter is set to *ANET*.

5. Enter your Authorize.Net API LoginID in the AuthNetUser system parameter and your Authorize.Net TransactionKey in the  AuthNetTransactionKey system parameter. You can find this information at the Authorize.Net website by searching for API Credentials under Account Settings. Make sure that there is no value specified in the AuthNetPassword system parameter.

NOTE: These system parameters can also be set specifically by shopping cart an e-commerce software system that allows a retailer to sell products on the Web. In the context of Monsoon OMS, it refers to the settings that describe a merchant's web store to the program, allowing it communicate with the online shopping cart and import orders and other information if you want to use different credit card processors for different carts. Users of legacy previously used, predecessor, or something from the past Authorize.Net accounts should still use their original username and password information in the SEOM AuthNetUser and AuthNetPassword system parameters, and leave the AuthNetTransactionKey parameter blank.

6. **Important**: Set AuthNetTestMode to TRUE while you are setting up and testing the system. Set it to FALSE when you are ready to begin processing real transactions.

7. Set AuthNetSendEmail to TRUE if you want Authorize.Net to send its own email confirmation to your customer upon the completion of a transaction. Set it to FALSE if you do not want Authorize.Net to send confirmation email to your customers.

8. Set the following system parameters as you wish to configure how SEOM handles your credit card transactions:

• AllowCaptureHigherAmount - If TRUE, the program lets you change the amount of a delayed capture to an amount greater than the pre-authorized amount. If FALSE, a delayed capture must be for an amount less than or equal to the pre-authorized amount.

 

• CaptureApprovedOrdersAtImport - If TRUE, when importing orders, if an order can be approved, the program tries to capture its pre-authorized credit card payment (if any). If the payment cannot be captured, the order is not be approved.

 

• CaptureAtFillBackorders - If TRUE, when using the Fill Backorders form, if an order can be approved, the program tries to capture its pre-authorized credit card payment (if any). If the payment cannot be captured, the order is not be approved.

 

• CaptureAtManualApproval - If TRUE, when orders are approved manually, the default is to capture the initial credit card charge if it has been pre-authorized but not captured. If FALSE, the default is to not perform the capture automatically.

 

• RequireAuthForManualOrders - If TRUE, when you enter a credit card order at the Manual Orders form, you must select the Authorization button to pre-approve credit card sales. Then, when you select Transmit, the payment is also captured. If FALSE, you can either do the same process, or skip the pre-authorization, and the program transmits the sale without a prior authorization.

9. Check the settings of the main and/or cart-based system parameter, WebTransactionType to make sure it agrees with your workflow. The choices are Pre-Authorize or Sale. If payments are captured via SEOM, it should be set to Pre-Authorize. If payment is captured at the web store, it should be set to Sale.

Configure the Order Manager Point of Sale System to work with Authorize.Net

Click Save after setting each system parameter.

1. Go to Main Menu > Settings > System Functions > Set System Parameters.

2. Click on the Credit Card POS abbreviation for Point-of-Sale. The cash register interface for use with walk-in business at "brick and mortar" stores. Used with barcode scanners and cash drawers. Sales made on the POS screen draw from the same inventory as orders imported from online stores. parameter group.

3. Set CreditCardProcessorPOS to Authorize.Net.

4. Enter your Authorize.Net API LoginID in the AuthNetPOSUser system parameter and your Authorize.Net TransactionKey in the  AuthNetPOSTransactionKey system parameter. You can find this information at the Authorize.Net website by searching for API Credentials under Account Settings. Make sure that there is no value specified in the AuthNetPOSPassword system parameter.

5. **Important**: Set AuthNetPOSTestMode to TRUE while you are setting up and testing the system. Set it to FALSE when you are ready to begin processing real transactions.

6. Set AuthNetPOSSendEmail to TRUE if you want Authorize.Net to send its own email confirmation to your customer upon the completion of a transaction. Set it to FALSE if you do not want Authorize.Net to send confirmation email to your customers.

7. Set AuthNetPOSAcctIsCardPresent system parameter to TRUE, if you are using a "card present" AuthNet account to process POS orders.

8. Optional: Set system parameter RequireAuthForPOSOrders to TRUE to require an authorization.

Authorize.Net: Automated Clearing House Check Processing (eCheck)

Created:

Revised: 8/9/12

Published: 04/13/16