Go to Bottom

POS Credit Card Gateways and eCheck Processing

A system parameter group was added to support the Point of Sale (POS) system introduced in version 4.601 Beta. The group is called Credit Cards POS and allows the user to use separate credit card gateways from those used at the Enter Orders Manually screen.

Previously, merchants who had two accounts with the same gateway (one for processing card present transactions, one for processing web orders) were not able use them separately, i.e. one with the Enter Orders Manually system and the other with the POS system. The Credit Cards POS parameter group eliminates this issue by isolating the POS card processing functions. Set the system parameter CreditCardProcessorPOS to direct the program to use a specific payment gateway for orders that originate at the POS system.

The CCTerminal or Credit Card tab (depending on the version) of the View Orders screen uses the POS system settings for orders created by the POS, including new sales (where funds are captured) and authorizations.


eCheck Processing


eCheck Processing is now possible with the Order Manager (not supported by all gateways) - however it is currently only supported at the POS (hand keyed only as CCD, PPD, TEL or WEB) - check reader support (POP) will be added later), Manual Orders, CCTerminal and Multi-Order Processor (when setting transaction type to "sale"). Support for eCheck processing from web orders will be limited at this point and will have to be addressed on a cart-by-cart basis.


Processors NOT supporting eChecks:



QBMerchant (QuickBooks Merchant Services)




VERY IMPORTANT NOTE: The Order Manager only "submits" eChecks for processing and receives a yes/no regarding submission. It cannot verify actual payment against the eCheck (this is a limitation of the gateway systems). The Order Manager will assume that payment is made should it receive a positive result from the submission, however, you will not have confirmation for up to 3-5 business days (and sometimes up to several weeks) that the check has actually cleared your account. It is up to the merchant to confirm receipt of payment with your gateway or banking institution.


IMPORTANT NOTE: There are specific rules that apply when initiating a debit to a consumer's bank account that the merchant must follow. These rules are established and maintained by the National Automated Clearing House Association (http://www.nacha.org/) and are published periodically in "ACH Rules: A Complete Guide to Rules & Regulations Governing the ACH Network". It is each merchant's responsibility to understand and abide by the published rules and regulations.





Card-Present and eCheck transactions are now supported by the Authorize.Net interface. One limitation to this is if you use a card present account with the POS, you will also need a card NOT present account to process eChecks. This account must be set up in the program level parameters (same account used with Manual Orders). All eCheck transactions will be redirected to that account.

New system parameters AuthnetTransactionKey and AuthnetPOSTransactionKey (for POS) address the issue with the new multi-user login system at AuthNet. The merchant must go to the AuthNet Admin panel and generate a "Transaction Key" for the Order Manager to use the AuthNet Web API. Enter that value in the appropriate AuthNet Transaction Key parameter in Order Manager.


A new parameter, AuthNetPOSAcctIsCardPresent (POS Only) was added to allow the merchant to declare whether the Authorize.Net account used by the POS is specifically designated for Card Present Transactions. This is needed because card present transactions are processed by a different Web Service at Authorize.Net than web based "card-not-present" transactions. If you are unsure, you will need to consult the documentation provided by Authorize.Net to determine the URL that you should use to send card processing requests to Authorize.Net.


If the URL is:



then your account IS NOT a card present account so the AuthNetPOSAcctIsCardPresent parameter should be set to False.


If the URL is:



then your account IS a card present account. Set the AuthNetPOSAcctIsCardPresent to True.





Support for CyberSource was added to the Order Manager. CyberSource can process all credit card transaction types supported by the Order Manager and supports eCheck processing as well.

To use CyberSource, each PC must meet the following:


• Windows 2000 or XP

• If using Windows XP: MSXML 4.0 Service Pack 2 (Microsoft® XML Core Services)

• If using an operating system earlier than Windows 2000 SP3: WinHTTP 5.0


Note: CyberSource recommends that your system use at least Windows 2000 SP3

because it comes with WinHTTP 5.1, which fixes bugs in the 5.0 version.


The following will need to be done for each workstation that will be used to run transactions via CyberSource:


1) You must download and install the CyberSource SOAP SDK for .Net 1.1 from the Stone Edge Technologies download page.

2) You must log on to the CyberSource Admin Panel and generate a "Security Key" file named "YourMerchantID.p12" where "YourMerchantID" is the Merchant ID established with CyberSource. Save this file to a shared location visible to all workstations. Once the file is established, set the location of the "Security Key" file in the CyberSourceSecurityKeyLocation (CyberSourcePOSSecurityKeyLocation for POS) parameter.

If you saved the .p12 file under another name, you will need to define the new name in the CyberSourceAlternateKeyFileName (CyberSourcePOSAlternateKeyFileName for POS) parameter.

3) Enter your CyberSource Merchant ID in the CyberSourceMerchantID (CyberSourcePOSMerchantID for POS) parameter.

4) If you want to run "live" transactions set the CyberSourceTestMode (CyberSourcePOSTestMode for POS) parameter to False.


ADVANCED: Additional CyberSource parameters exist for configuring the CyberSource SDK to use a proxy server or alternate URLs and URIs with the SOAP API. Review the parameter details for information regarding the use of these parameters.


CyberSourceAlternateNamespaceURI (CyberSourcePOSAlternateNamespaceURI for POS)

CyberSourceAlternateServerURL (CyberSourcePOSAlternateServerURL for POS)

CyberSourceProxyServer (CyberSourcePOSProxyServer for POS)

CyberSourceProxyUserName (CyberSourcePOSProxyUserName for POS)

CyberSourceProxyPassword (CyberSourcePOSProxyPassword for POS)





Card-Present and eCheck transactions are now supported by the Echo-Inc interface.


NOTE: Echo-Inc does not support "Voiding" Credit Card transactions or eCheck Transactions using their Web API.





JetPay is a merchant bank system (like Echo-Inc), not a "gateway" and has their own web interface for processing credit card and eCheck transactions. All transaction types that are available in the Order Manager are available through JetPay. This includes Card-Present, Card-Not-Present and eCheck transactions. Debit Card processing will be added in the near future.


Parameters to set to use the JetPay system:


JetPayMerchantID (JetPayPOSMerchantID for POS)

JetPayPassword (JetPayPOSPassword for POS)

JetPayTestMode (JetPayPOSTestMode for POS)


NOTE: If using JetPay in "test mode", a MerchantID and Password are not necessary





LinkPoint is now First Data Global Gateway. When Order Manager V5.929 is installed, the LinkPoint SDK described below is no longer supported. Refer to the Knowledge Base topic, First Data Global Gateway, for setup instructions.  

Support for the LinkPoint Gateway and the "YourPay" gateway was added in this release. To use LinkPoint, you will be required to download and install the LinkPoint SDK from the Stone Edge Technologies, Inc. download page. This will install and register the following library file: LpiCom_6_0.dll.


When you set up your LinkPoint account, you should have received a "Certificate" at the bottom of the "Welcome to LinkPoint Select API" email. Copy that data into a new file on your hard drive and name it "LinkPointStoreID.pem" where LinkPointStoreID is the ID number assigned to you by LinkPoint. Once you have created this file, you will need to enter the path to the file in the LinkPointCertFilePath (LinkPointPOSCertFilePath for POS) parameter.


Set the LinkPointPortNumber (LinkPointPOSPortNumber for POS) to the port number issued to you by LinkPoint (typically 1129).


Set the LinkPointServer (LinkPointPOSServer for POS) parameter to the name of the server you are to use with LinkPoint (should be in the "Welcome" email)


Set the LinkPointStoreID (LinkPointPOSStoreID for POS) parameter to your LinkPoint Store ID.


To run "live" transactions set the LinkPointTestMode (LinkPointPOSTestMode for POS) parameter to False.





At Verifone's insistence, the Order Manager's PCCharge interface was re-written to support PCCharge's new XML specification. The original interface with PCCharge used simple text for communications (.inp files) and is still supported for the immediate future for users of PCCharge 5.6 or older. If you make no changes in the Order Manager, the new XML interface will be used. If you use PCCharge 5.6 or older then you will have to set the PCChargeCommunicationMethod system parameter to "INP" instead of "XML".


A new flag was added to the PCCharge processing request to "keep connection alive" after processing a transaction. This will have the greatest impact on users who connect using a modem. At the completion of a transaction, PCCharge will keep the phone line open as it is expecting additional transactions. Keep in mind that the length of time the line can be kept open is at the discretion of the merchant bank.


With the new XML interface, the restriction of capturing the amount of an authorization has been lifted. The user can capture any amount less than or equal to the authorization amount.

eCheck Processing and Debit Card processing coming shortly



QuickBooks Merchant Services


Support has been added to the Order Manager for basic credit card processing using the QuickBooks Merchant Services gateway. To use the gateway the user must first set the QBMSTestMode (QBMSPOSTestMode for POS) parameter to false to run "live" transactions. See the knowledge base article, Using QuickBooks Merchant Services, for more detailed information.


On the very first transaction, the user will be prompted to log on to their QuickBooks Merchant Services Admin Panel and generate a "Connection Ticket" for the Order Manager. This ticket identifies the Order Manager to QuickBooks during each transaction and sets the Order Manager's permission level. Follow the instructions on screen to generate the Connection Ticket, then copy the ticket, close the browser window and paste the Connection Ticket into the Order Manager's Connection Ticket prompt. Connection Tickets may be needed for each cart using the gateway. Tickets are good for 18 months and are stored in encrypted format in the QBMSConnectionTicket (QBMSPOSConnectionTicket for POS) parameter. If you feel that the connection ticket has been compromised, you can easily request a new ticket by clearing the parameter and running a new transaction.


QuickBooks also requires a "Session Ticket" to process transactions. If the current Session Ticket has expired or has not been established, the user will be prompted to log on to their QuickBooks Merchant Services Admin Panel and generate a "Session Ticket". Follow the instructions on screen to generate the Session Ticket then copy the ticket, close the browser window then paste the Connection Ticket into the Order Manager's Session Ticket prompt. Session Tickets are only maintained in computer memory and are lost if the Order Manager is closed. Session tickets also expire within 1 hour of inactivity on the Merchant Services gateway or within a total of 24 hours.





This gateway has been updated to include support for card-present transactions and eCheck processing.



Verisign PayflowPro


This gateway has been updated to include support for card-present transactions and eCheck processing.




Created: 1/20/12

Modified: 1/30/13

Go to Top