LINK<\/a><\/p>\r\n\r\n\r\n\r\nConfigure\u00a0SEOM\u00a0to work with Authorize.Net<\/h2>\r\n\r\n\r\n\r\n
Click\u00a0Save<\/strong>\u00a0after setting each system parameter.<\/p>\r\n\r\n\r\n\r\n\r\n- Go to\u00a0Main Menu > Settings > System Functions > Set System Parameters.<\/em><\/li>\r\n
- Select the Credit Card<\/strong>\u00a0parameter group.<\/li>\r\n
- Set parameter\u00a0CreditCardProcessor<\/strong>\u00a0to\u00a0Authorize.Net<\/strong>.<\/li>\r\n
- Make sure that the\u00a0CCInfoPrefix<\/strong>\u00a0parameter is set to\u00a0*ANET*<\/strong>.<\/li>\r\n
- Enter your Authorize.Net API LoginID in the\u00a0AuthNetUser<\/strong>\u00a0system parameter and your Authorize.Net TransactionKey in the \u00a0AuthNetTransactionKey<\/strong>\u00a0system 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\u00a0AuthNetPassword<\/strong>\u00a0system parameter.<\/li>\r\n<\/ol>\r\n\r\n\r\n\r\n
NOTE<\/strong>: These system parameters can also be set specifically by shopping cart if you want to use different credit card processors for different carts. Users of legacy Authorize.Net accounts should still use their original username and password information in the SEOMAuthNetUser and AuthNetPassword system parameters, and leave the AuthNetTransactionKey parameter blank.<\/p>\r\n\r\n\r\n\r\n\r\n- **Important**:<\/strong>\u00a0Set\u00a0AuthNetTestMode<\/strong>\u00a0to\u00a0TRUE<\/strong>\u00a0while you are setting up and testing the system. Set it to\u00a0FALSE<\/strong>when you are ready to begin processing real transactions.<\/li>\r\n
- Set\u00a0AuthNetSendEmail<\/strong>\u00a0to\u00a0TRUE<\/strong>\u00a0if you want Authorize.Net to send its own email confirmation to your customer upon the completion of a transaction. Set it to\u00a0FALSE<\/strong>\u00a0if you do not want Authorize.Net to send confirmation email to your customers.<\/li>\r\n
- Set the following system parameters as you wish to configure how\u00a0SEOM\u00a0handles your credit card transactions:<\/li>\r\n<\/ol>\r\n\r\n\r\n\r\n
\r\n- AllowCaptureHigherAmount<\/strong>\u00a0– 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.<\/li>\r\n<\/ul>\r\n\r\n\r\n\r\n
\r\n- CaptureApprovedOrdersAtImport<\/strong>\u00a0– 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.<\/li>\r\n<\/ul>\r\n\r\n\r\n\r\n
\r\n- CaptureAtFillBackorders<\/strong>\u00a0– 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.<\/li>\r\n<\/ul>\r\n\r\n\r\n\r\n
\r\n- CaptureAtManualApproval<\/strong>\u00a0– 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.<\/li>\r\n<\/ul>\r\n\r\n\r\n\r\n
\r\n- RequireAuthForManualOrders<\/strong>\u00a0– If TRUE, when you enter a credit card order at the Manual Orders form, you must select the\u00a0Authorization<\/strong>\u00a0button to pre-approve credit card sales. Then, when you select\u00a0Transmit<\/strong>, 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.<\/li>\r\n<\/ul>\r\n\r\n\r\n\r\n
<\/p>\r\n
\r\n- 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\u00a0SEOM, it should be set to Pre-Authorize. If payment is captured at the web store, it should be set to Sale.<\/li>\r\n<\/ol>\r\n\r\n\r\n\r\n
Configure the Order Manager Point of Sale System to work with Authorize.Net<\/h2>\r\n\r\n\r\n\r\n
Click\u00a0Save<\/strong>\u00a0after setting each system parameter.<\/p>\r\n\r\n\r\n\r\n\r\n- Go to\u00a0Main Menu > Settings > System Functions > Set System Parameters.<\/em><\/li>\r\n
- Click on the\u00a0Credit Card POS<\/strong>parameter group.<\/li>\r\n
- Set\u00a0CreditCardProcessorPOS<\/strong>\u00a0to\u00a0Authorize.Net<\/strong>.<\/li>\r\n
- Enter your Authorize.Net API LoginID in the\u00a0AuthNetPOSUser<\/strong>\u00a0system parameter and your Authorize.Net TransactionKey in the \u00a0AuthNetPOSTransactionKey<\/strong>\u00a0system 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\u00a0AuthNetPOSPassword<\/strong>\u00a0system parameter.<\/li>\r\n<\/ol>\r\n\r\n\r\n\r\n
\r\n- **Important**:<\/strong>\u00a0Set\u00a0AuthNetPOSTestMode<\/strong>\u00a0to\u00a0TRUE<\/strong>\u00a0while you are setting up and testing the system. Set it toFALSE<\/strong>\u00a0when you are ready to begin processing real transactions.<\/li>\r\n
- Set\u00a0AuthNetPOSSendEmail<\/strong>\u00a0to\u00a0TRUE<\/strong>\u00a0if you want Authorize.Net to send its own email confirmation to your customer upon the completion of a transaction. Set it to\u00a0FALSE<\/strong>\u00a0if you do not want Authorize.Net to send confirmation email to your customers.<\/li>\r\n
- If you are using a “card present” AuthNet account to process POS orders, set the AuthNetPOSAcctIsCardPresent system parameter to TRUE.<\/li>\r\n
- Optional:\u00a0Set system parameter\u00a0RequireAuthForPOSOrders<\/strong> to TRUE to require authorization.<\/li>\r\n<\/ol>\r\n
Authorize.net CIM\u00a0<\/h2>\r\n
Functionality added in Stone Edge release 8.006 March 7th, 2024.<\/p>\r\n
Note:<\/strong> No changes are needed in Stone Edge to enable this feature. Contact your Authorize.net to make sure you have this functionality on your account.<\/p>\r\nNote:\u00a0<\/strong> If updating from version 7.1xx or 7.5xx, please get in touch with Support@stonedge.com. All previous Transaction history will not be used, and you will need to collect new payment information.<\/p>\r\nHow to use CIM in Stoneedge<\/h4>\r\n
When using Auth.net as your payment processor and needing the CIm function, there are a few processes for referencing previous transactions so customers’ information does not need to be recollected.\u00a0\u00a0<\/p>\r\n
Manual Orders Screen:<\/h6>\r\n
When placing a manual order for a returning customer. All steps are the same till you get to the payment screen if the customer is returning since moving to 8.006 or later.\u00a0<\/p>\r\n
![\"\"](\"https:\/\/stoneedge.com\/kb\/wp-content\/uploads\/2019\/04\/ScreenThatShowsUpWhenClickingRefTransatVOandMagnifyingGlassAtMO.png\"){kind=spacer}
<\/li>\r\n![\"\"](\"https:\/\/stoneedge.com\/kb\/wp-content\/uploads\/2019\/04\/RefTransButton.png\"){kind=spacer}
<\/p>\r\n