Introduction
The Charge Cards module in Salesware supports five systems: ProtoBase, DirectNET, Ingenico, Tender Retail/Moneris and Payment Express. It also supports EZCharge cards, which are similar to In-House Cards items except that the guest’s credit card is charged instead of having an amount subtracted from an in-house debit card. This section describes how to install and configure these systems. The vast majority of Siriusware clients use ProtoBase, so detailed configuration directions are provided for ProtoBase only; installation of the other Charge Card systems follow the steps provided for ProtoBase, modifying where necessary (as explained in the DirectNET, Ingenico or Tender Retail/Moneris section below). If you chose to install support for Salesware Charge Cards module when you were installing the core Salesware modules the.INI settings were written into your Sales32c.INI file, depending on which radio button you selected.
This document uses the following terminology:
1. Authorization – The process of verifying that the cardholder has sufficient credit left to pay for the transaction. This does not actually put the money in your bank. It does allocate the money from the person’s credit for seven days, though.
2. Settlement – The process of collecting the money from all of your authorizations.
3. Issuer – This is the bank from which the cardholder receives his card.
4. Acquirer – A bank that has a business relationship with a merchant and receives all credit card transactions from that merchant; the acquirer gets the money and deposits it into the merchant’s account.
5. Processor – A company that handles credit card transactions and batches for acquirers (e.g., PaymentTech, Moneris, 5th/3rd, Vital, etc.).
6. Integration – Siriusware® Inc. codes to a single spec and the product with which Salesware integrates translates the single format that we send to the format required for any given number of processors (e.g., Tender Retail Merchant Connect [a.k.a., CreditCheq], Elavon ProtoBase, etc.).