There are several options and features available for processing Credit Card Payments as a form of Payment on Account. Although the initial implementation is designed to integrate with the optional PC Charge interface software, the modular design can potentially allow for other software options in the future. This document will not cover the installation and setup of the PC Charge Application, and it is assumed that PC Charge is already setup and running properly.

These programs were designed to allow users to create a Payment for the total balance of a particular account, or select a group of transactions with a specific reference (i.e. Purchase Order Number) to arrive at a payment amount. Once the credit card transaction is processed and approved, a receipt will be generated, along with an optional confirmation fax or email to the customer. The resulting Payment(s) must be posted just like any other payment. If a mistake was made when creating the payment, they will have the ability to Void the credit card transaction prior to posting, which also deletes the Payment. No other changes to the payment are allowed. All credit card transactions can be viewed or printed via a log report.

The following are the prompts available in the setup program:

1) Type - Currently only one type available: <PCC>

2) Directory Path - This is the location of the directory in which Credit Card Charge Requests are dropped off, and Responses are picked up.

3) User ID(s) - These must be valid PC Charge User Names.  They are used for the naming of the Request and Response files. If the user has an unlimited user license for PC Charge, leave this blank to allow the program to automatically create the User Name(s).

4) Processor ID - User must provide this information.

5) Merchant ID - User must provide this information.

6) Transaction Timeout - Value in seconds at which the monitoring program stops looking for a response from the credit card processor. Minimum value: 30 seconds. Under normal conditions, processing should only take a few seconds.

7) Send Confirmations - Sets the default response when creating credit card payments. Customers can be setup individually as to confirmation preference.

8) Create Customer Memo - Does the user want Customer Memos created when credit card payments are created? Options include: D - Declined Transactions Only, A - Accepted Transactions Only, and B - Both Accepted and Declined Transactions, Leave Blank to not create Customer Memos.

9) Lock Payment Batch - If set to <Y> (recommended), users will not be able to manually enter a payment with the same Batch number as an unposted Batch of Credit Card Payments.

10) Amex Description - Some processors require a specific description of products sold when processing an American Express credit card charge. The user should check with their service provider to determine what, if anything needs to be entered into this field.