In this Topic: Show
Authorize.Net AIM integrates with Monsoon Stone Edge to process electronic credit card transactions for web, phone, fax or POS orders.
AIM supports authorizations/delayed capture, sales, void/credit (depends on whether batch is closed).
eChecks (ACH) are supported at Process Orders, Manual Orders and the Multi-Order Processor. Stone Edge does not currently support eCheck hardware, so all check information must be manually keyed at the POS or Manual Orders screens.
eChecks are supported for web orders as long as the shopping cart provides the correct data points.
eCheck payments must be manually verified with Authorize.Net, in three to five business days, to be sure the funds are received. If the check was refused by the ACH system, the user must manually edit the Amount Received in the Stone Edge transaction record to $0.00 to reflect the balance due from the customer.
Authorize.Net highly recommends that you do not ship the goods until you have confirmed that the check cleared ACH Processing.
At Multi-Order Processor, eChecks are only "processed" if you set the Credit Card Mode to "Sale".
Support for AuthNet CIM begins in V7.1.
Go to the Main Menu>Settings>System Functions>Set System Parameters. The Set System Parameters dialog box opens. If you use different payment accounts for each of your shopping carts, set the parameters listed below in the PC & Cart Based parameters (Special System Parameters).
Set system parameter, WebTransactionType to match the transaction type used by the shopping cart. The choices are Pre-Authorize or Sale. If payments are authorized at the cart and a delay capture/post is submitted by Stone Edge, set this parameter to Pre-Authorize. If payment is captured in full at the web store, set this parameter to Sale.
Select the Credit Card parameter group.
Set CreditCardProcessor to Authorize.Net.
Select Save.
Make sure that the CCInfoPrefix parameter is set to *ANET*. Be sure to select Save if you are making a change.
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.
While testing the integration, set parameter AuthNetTestMode to TRUE, and set it to FALSE when you are ready to begin processing "live" transactions.
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 a confirmation email to your customers.
Review the following order processing system parameters and set them according to how you want Stone Edge to behave when processing electronic payments:
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. (This depends on the payment processor's ability to capture a small percentage of the balance due over the amount authorized.)
CaptureApprovedOrdersAtImport - If set to TRUE and an order containing an authorization can be approved during import, the program tries to capture the payment at the time of import. If the payment cannot be captured, the order is not approved.
CaptureAtFillBackorders - If set to TRUE and an order containing an authorization is approved through the Fill Backorders feature, the program tries to capture the payment at that time. If the payment cannot be captured, the order is not approved.
CaptureAtManualApproval - If set to TRUE and an order contains a pre-authorization for payment, the program attempts to capture the payment when the order is approved. If set to FALSE, and an order contains a pre-authorization for payment, the program does not attempt to capture the payment when the order is manually approved.
RequireAuthForManualOrders - If set to TRUE and you are creating an order at Manual Orders, the program requires you to authorize the payment before it can be captured (as opposed to Sale). You must select Get Data from Order,and then select Authorization and Transmit to pre-approve the credit card payment.
Go to the Main Menu>Settings>System Functions>Set System Parameters. The Set System Parameters dialog box opens. If you use different payment accounts for each of your shopping carts, set the parameters listed below in the PC & Cart Based parameters (Special System Parameters).
Select the Credit Card POS parameter group.
Set CreditCardProcessorPOS to Authorize.Net.
Select Save.
Make sure that the CCInfoPrefix parameter is set to *ANET*. Be sure to select Save if you are making a change.
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 AuthNetPassword system parameter.
While testing the integration, set parameter AuthNetPOSTestMode to TRUE, and set it to FALSE when you are ready to begin processing "live" transactions.
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 a confirmation email to your customers.
Set AuthNetPOSAcctIsCardPresent system parameter to TRUE, if you are using a "card present" AuthNet account to process POS orders.
Optional: Set system parameter RequireAuthForPOSOrders to TRUE to require an authorization.
Created: 10/20/14
Modified: