Electronic Payments

Use this screen to configure your Electronic Data Capture (EDC) settings. If you will not process credit cards through CMS, leave Use Charge Card Processing cleared and complete the Payments Accepted screen (Setup > Payment > Payments Accepted).

CMS includes built-in credit card and eCheck processing through Authorize.Net. CMS sends approvals, captures, credits and voids directly to Authorize.Net, so you don't have to re-key transactions into a separate terminal.

Select the check box to integrate credit card processing with CMS.

Select Authorize.Net.

Selects which Authorize.Net interface CMS uses for credit card transactions:

§ v1. The original Authorize.Net connection. This is the default.

§ v2. Authorize.Net's current API. Select v2 to use card Tokens (see the Options sub-tab).

Both versions use the Login ID and Transaction Key entered below. The version setting applies to credit cards only; eChecks always use the v1 connection.

Three account types are available:

§ MOTO

§ ECOM

§ POS

Enter your login ID and transaction key for each appropriate account type. MOTO is the default: if you leave the ECOM or POS fields blank, CMS uses the MOTO login ID and transaction key for those transactions.

Authorize.net can limit from which IP addresses it accepts connections (see http://reseller.authorize.net/learn/key/fds/) If this feature is used, connections from CMS may also be refused. To avoid this problem, specify the external IP of your server here.

The default is to process Approvals as "Authorize Only." Select this check box if you wish to both authorize and capture upon approval. If you choose this option, any subsequent modifications to an order’s financials will require a refund, a new payment, or that the existing payment be voided.

This tells the Processor that you want them to monitor for submissions of duplicate charges sent for the same amount, on the same card, on the same day. If they detect a duplicate charge they will decline it if this option is checked.

The purpose of test mode is to test the communications from CMS to the payment gateway. Transactions entered in test mode are not captured.

Select this check box when testing your account setup. Real charge cards can be submitted for authorization to ensure that the connection and account is working, without charging any customer’s card or affecting your daily batch balance.

And of course, you'll need to clear the check box when you're ready to "Go Live"!

Controls whether CMS sends the customer's email address to Authorize.Net with POS (retail) transactions, so Authorize.Net can email the customer a receipt. If this box is cleared, CMS leaves the email address off POS transactions. Phone and mail orders always include the email address.

For Authorize.Net, this option appears only when Auth.net Version is set to v2. Switching back to v1 clears it.

When selected, CMS stores the customer's card with Authorize.Net (as an Authorize.Net customer payment profile) and keeps only a token for it in CMS, instead of the card number. The card is sent to Authorize.Net when the order is saved and on its first approval, and later approvals and charges use the token.

If Authorize.Net can't create the token when the order is saved, CMS warns you and saves the order with the card details as before.

Record your Customer Service phone number here. This will appear on customer statements as the number they should call if they question a charge.

Select the check box to integrate eCheck processing with CMS.

Select Authorize.Net.

eChecks have their own Authorize.Net Login ID and Transaction Key, separate from the credit card settings, so you can process eChecks through a different Authorize.Net account. IP Substitute works the same as on the credit card Authorize.Net sub-tab. eChecks always use the v1 Authorize.Net connection.

Select this option if you generally capture payments only on shipped orders. This will filter the list of Charge Cards ready for capture in the EDC window to include only shipped orders.

This feature was implemented to address requirements from Visa and other card brands. At one time the requirement was that you to ship the order before capturing the card. Now it states that you must ship within seven days of capturing the card, but capturing upon shipment is still recommended. The Visa regulation is from http://usa.visa.com/download/merchants/visa-international-operating-regulations-main.pdf.

There is an option to Create Debug Log used for support purposes and we do not recommend enabling this option unless directed to by a NewHaven Software or Authorize.Net representative. This log file will contain real credit card data although the card numbers have been masked. The security risk is small but the file should still only be used when absolutely necessary.