CCVS Administrator's Guide Version 3.3 Revised February 15, 2025 Red Hat, Inc. 2600 Meridian Pkwy Durham, NC 27713 919-547-0012 Back to main Documentation page   Table Of Contents: Introduction Features Overview Requirements Platforms Modems Merchant Account Your Computer Installation Before You Install setup.txt Installing CCVS from Red Hat Linux 6.2 CDs Installing CCVS by Download The Configuration Script Multiple Merchant Accounts Administrative Commands Starting CCVS Making Money Move Special Language Considerations C Java Perl Python PHP TCL Supporting CCVS Licensing Agreement Spec Sheet Introduction Credit Card Verification System, or CCVS, uses your computer and modem to simulate a credit card swipe box. CCVS is designed as a stand-alone product with several APIs (Application Programming Interfaces) that allow it to be customized and integrated with third party software applications or database products. CCVS is safe, secure, and easy to use. Written in ANSI C and conforming to POSIX standards, CCVS is portable and designed to be easily integrated with modern operating systems, programming languages, and the Internet. It is designed for easy scripting and programming, so users can use CCVS to automate web commerce, batch processing, or enhance any application that requires credit card processing. Some examples of uses for CCVS: Alice wants to open a web storefront. She creates a CGI program using our C interface, and accesses it via HTML forms. Now she can accept credit card payments over the web, and can use our AVS features to prevent fraud. Bob wants to set up a system for a dozen telephone operators to take catalog orders over the phone. He uses our Tcl extension to create a Tcl/Tk GUI that presents a simple interface for telephone operators. Since the operators are just using simple X terminals and all the software is running on Bob's central server, he only needs to install our software on one computer, and the operators don't have to wait for an available phone line -- all of their transactions will go out over the same phone call. Carol has an ISP, with a customer database kept on a database server. She writes a Perl script, combining our Perl module with a module for her database system. Now, every month she can just run the script, and it will read out her customer data, process monthly billing, and update the records in the database to indicate payment has taken place. Table Of Contents Features CCVS's powerful features can be accessed in a number of ways. We offer users: A C library with a documented API empowers users to integrate CCVS seamlessly with existing applications. A TCL extension enables use of CCVS with server-side TCL such as NeoWebScript. A Perl 5.0 module allows CCVS to work with the most popular CGI programming language in use today. The ability to quickly construct custom GUIs using Tcl/Tk. Typical development time is less than a day! Python, PHP3, and Java modules enables CCVS to work with other common programming languages. CLI programs for interactive use. Call programs from any UNIX shell. Program in the UNIX language you like best! Fraud protection with Address Verification System (AVS) and Card Verification Value 2 (CVV2), allowing merchants to check for stolen credit cards. Many clearing houses offer a better rate to merchants who use AVS, even on orders taken over the phone. Support for multiple merchant accounts, which allows users to open their very own virtual malls with unlimited storefronts. The ability to conduct multiple transactions in a single session, approaching leased line performance (two seconds per transaction!) with no extra cost or complexity. The reassurance of being able to test and do development programming on the product without charging real credit cards. Year 2000 compliance. See our compliance statement. Table Of Contents Overview The credit card verification process involves several steps. First, a consumer presents credit card information to the merchant. The merchant transmits this data, along with her merchant id code, to a clearinghouse (also referred to as a processor or acquirer). This can be done by reading the card and merchant numbers over the phone, by using a credit card terminal, or by using CCVS or some other piece of software to transmit the information from a computer. The clearing house may be the bank that has issued the merchant his credit card account, but it is more likely a firm that has contracted with the merchant's bank to clear charges in exchange for a flat fee and a percentage of every charge processed. The clearing house contacts the bank that issued the consumer's credit card and verifies that the charge is acceptable. Upon acceptance, the clearing house then sends a confirmation message to the merchant. At the same time the available credit from the customer's credit card is frozen by the amount of the transaction. At the end of a business day, the merchant (or the merchant's computer or credit card terminal) calls the clearing house and verifies all transactions for that day to ensure that he and the clearing house agree on what has happened that day. After this upload the clearing house starts the process of transferring the money from the credit card bank to the merchant's bank account. Table Of Contents Requirements Platforms: CCVS runs on selected POSIX compliant platforms: AIX 4.2 BSDI FreeBSD 2.2.6+ Alpha Linux SPARC Linux Intel Linux Caldera Linux Debian Linux 1.3+ Red Hat Linux 4.2 Red Hat Linux 5.1 Red Hat Linux 6.2 S.u.S.E Linux 5.1 PowerPC Linux ARM Linux (Corel Netwinder) SCO OpenServer 5.0+ SPARC Solaris 2.5 If you do not see your operating system in the list, please express your interest in getting a version of CCVS running on your platform. We have additional platforms under development.   Modems: Credit card protocols do not support compression or error correction during modem connects. We can provide you with information about how to turn off such features on the following modems: Hayes Optima US Robotics Courier US Robotics Sportster Chase Research PCI-RAS Additional modem compatibilities are always under development. If your modem does not appear on this list, give us a call, or look through your modem manual to find the string which turns off all compression and error correction, and the string which resets your modem for normal usage.   Merchant Account: We support the clearing house protocols offered by the following organizations: First Data Corporation's ETC PLUS protocol (a.k.a. FDR7, ETC+, ETC7, "Omaha") First Data Corporation's South Platform protocol (a.k.a. "Nabanco") Global Payment Systems' MAPP protocol (a.k.a. "St. Louis") Global Payment Systems' NDC protocol (a.k.a. "Atlanta") Visa International's VITAL protocol (a.k.a. Visanet, Visa 2nd generation, "K format") Paymentech's UTF protocol (a.k.a. GENSAR) NOVA Information Systems protocol If your merchant account provider uses these protocols, you will be able to use CCVS.   Your Computer: The following requirements allow CCVS to run smoothly and efficiently. Please make sure you are following all these guidelines before attempting to run CCVS: Do not run other software applications that need to access the modem while you are running CCVS; they can interfere with CCVS's operations. All operations must be performed from a single user account (we suggest a "ccvs" account). We require this so that all file ownerships and permissions are correctly set and protected. This account must always be used when accessing CCVS. The dedicated account must have access to the serial port, the serial lock directories, and the CCVS data spool directories. For TCL to work, you must install TCL version 7.6 or greater in order to run the included Graphic User Interface or to use the included Tcl/Tk APIs to develop your own graphical front end. For Perl to work, you must install a version of Perl of at least 5.0 or later. Table Of Contents Installation Before You Install CCVS Before running the installation program, please thoroughly read all documentation and errata that came with the program. The document setup.txt is a worksheet which will explain the different information required when configuring CCVS to use particular protocols. Fill out the worksheet before attempting to configure CCVS. The CCVS install program will ask you several things about your modem, so be prepared with the appropriate information. Currently CCVS only documents the init strings for three modems: Hayes Optima or ACCURA \r~~~\rAT &D3 X4 E0 &K0 &Q0 U.S. Robotics Sportster or Courier \r~~~\rAT E0 L0 M1 V1 X4 &K0 &M0 +FCLASS=0 Chase Research PCI-RAS \r~~~\rAT E0 %C0 \\N0 (If your modem does not appear on this list, look through your modem manual to find the string which turns off all compression and error correction, and the string which resets your modem for normal usage.) Once you have familiarized yourself with the product and agreed to the licensing terms, you may begin the installation procedure. Table Of Contents     Installing CCVS from Red Hat Linux 6.2 CDs If you have purchased the Red Hat Linux 6.2 Professional or Deluxe Editions for the Intel archiecture, you can install CCVS from RPMs. These can be found on the Workstation Applications CD and on the Secure Web Server CD. (If you have the Red Hat Linux 6.2 Standard Edition, or if you have Red Hat for the Alpha or SPARC architecture, see the next section.) If you didn't install CCVS during the installation of Red Hat Linux, you can use RPM or Gnome-RPM to install the packages: CCVS - The core CCVS programs CCVS-devel - The C developer's kit CCVS-perl - The Perl interface for CCVS CCVS-python - The Python interface for CCVS CCVS-php3 - The PHP3 interface for CCVS CCVS-tcl - The Tcl interface for CCVS CCVS-java - The Java interface for CCVS (included as source code) CCVS-examples - Sample source code, needed for development In these RPMs the configuration directory is "/var/ccvs". (You will see this values as a default in the configuration script.) Once the appropriate packages are installed, proceed to the Configuration Script. No other installation program is necessary. Table Of Contents     Installing CCVS by Download If you did not install Red Hat Linux from CD, or if you have the Red Hat Linux Standard Edition, or if you have Red Hat Linux for the SPARC or Alpha architectures, or if you are using a different operating system entirely, you must download CCVS and run an installation program. Begin by downloading the appropriate file for your platform from the download page on our web site. The web site contains RPMs for some platforms; it also has tar files for every platform CCVS supports. Unless you are upgrading an existing CCVS installation, you will probably want to use an RPM file, if one is available. Download the RPM files, and then install them as described above. No other installation program is necessary. If there is no appropriate RPM, download the tar.gz file instead. Unpack this file (we'll use ccvs-3.3-i86-freebsd22.tar.gz as an example) into a temporary directory. At your UNIX prompt, type: mkdir /tmp/scratch cd /tmp/scratch tar zxf ~/ccvs-3.3-i86-freebsd22.tar.gz Included in the distribution is a file named ccvs_install. You must run this installation program as root. The installation process will install a configuration file named ccvs_configure in the directory you designate (the default location is /usr/local/ccvs). You must run this configuration program as the user account that has permission to access CCVS. (The CCVS user account will have full access to all credit card information, so we recommend creating a special user. We use "ccvs".) Note that the CCVS Interface to Java must sometimes be built after the rest of CCVS is installed. See Special Language Considerations. Before you install CCVS, you must first do the following: 1. Decide which user CCVS will run as, and make sure that user exists on your system. This may not be root. The CCVS user account will have full access to all credit card information, so we recommend creating a special user. (We use "ccvs".) 2. Decide which directories CCVS will be installed in, and make sure that those directories exist. The recommended default locations are /var/local and /usr/local. At your shell prompt, su to root. Then type: ./ccvs_install You'll see the following screen:                             V                            V        CCC     CCC    V   V   SSS       C   C   C   C   V   V  S       C       C        V V    SSS       C   C   C   C    V V       S        CCC     CCC      V     SSS    Installation Program for CCVS 3.3      Red Hat, Inc.                            http://www.redhat.com/products/ccvs/ Hit Enter to see the CCVS software license. (It will be displayed through "more" or your chosen $PAGER program.) > If you have not su'd to root, you will get the following error: This installer must be run as root. Please su to root and run  the program again. Please thoroughly read all documentation and errata that came with the program! Failure to install the software properly can cause security problems, allowing unauthorized users access to your data. At the prompt, hit Enter to read the CCVS software license. You can use the standard scrolling and paging commands of more, or whichever paging program you have set in your PAGER environment variable. When you have read the license and exited the pager, you will see: Type "accept" to accept this license, or anything else to exit. > Type the word "accept" to signify your assent. You will then see this screen: This program creates the directories for the CCVS binaries,  libraries, and data files. Before you continue, you must first do the following:   1: Decide which user CCVS will run as, and make sure the user exists. This may not be root. All software that directly accesses CCVS must run as this user. It must have access to the serial devices and serial lock directory on your system.   2: Decide which directory CCVS will be installed in, and which directory the software's data will be written in. You should make sure that those directories exist. The data directory must go on a local filesystem that is not shared over the network.      The recommended default locations are /var/local (for installation) and /usr/local (for data).      (Note that if you choose locations other than the defaults, CCVS programs will have to be run with command-line switches or  environment variables to specify the nondefault directories.) Have you done these things? [Enter Y to continue, or N to stop here:] Press "Y" and then Return. You will then be prompted for information about how you wish to install CCVS. What user do you want to run CCVS as? This may not be root. The default is "ccvs". Enter user, or Return for default value, or . by itself to exit. > Where do you want to install the CCVS binaries? The default is "/usr/local". Enter directory, or Return for default value, or . by itself to  exit. > Where do you want to install the CCVS data files and transaction  queues? The default is "/var/local". Enter directory, or Return for default value, or . by itself to  exit. > Please make a note of your response; you will need to use the same directory when you run the configuration program. (If you choose the default values, everything will simply work.) You will then be asked to confirm your choices: CCVS user will be "ccvs". CCVS install directory will be "/usr/local". CCVS data directory will be "/var/local". Are these the correct choices? [Enter Y to install, or N to stop here:] If you enter "Y" and press Return, there will be a few seconds of activity, and then you will see: CCVS is now installed, running as user "ccvs". You must now configure CCVS. Please switch to that user, and run  the configuration program, which is:  /usr/local/ccvs/sbin/ccvs_configure (Of course, if you selected a different CCVS user or installation directory, the output will be slightly different.) Now you must configure CCVS. Go on to the next section.   The Configuration Script You must configure CCVS for your system, either in demo mode or for processing real data. At your shell prompt, su to the user account that has permission to access CCVS. (This is the user that you selected during the install process.) Now run the ccvs_configure program. If you installed the software from RPMs, you would type /usr/sbin/ccvs_configure If you installed from tar files, using the default location of /usr/local, you would instead type /usr/local/ccvs/sbin/ccvs_configure Either way, you'll see the following screen:                                 V                            V        CCC     CCC    V   V   SSS       C   C   C   C   V   V  S       C       C        V V    SSS       C   C   C   C    V V       S        CCC     CCC      V     SSS    Configuration Program for CCVS 3.3      Red Hat, Inc.                            http://www.redhat.com/products/ccvs/ Hit Enter to see the CCVS software license. (It will be displayed through "more" or your chosen $PAGER program.) > At the prompt, hit Enter to read the CCVS software license. You can use the standard scrolling and paging commands of more, or whichever paging program you have set in your PAGER environment variable. When you have read the license and exited the pager, you will see: Type "accept" to accept this license, or anything else to exit. > Type the word "accept" to signify your assent. You will then see this screen: This program creates the configuration file for CCVS functions. To do this, you will require the following information:   1: The clearing protocol you will be using. This may be MAPP, ETC+, or any of the other protocols which CCVS supports. There is also a demo protocol; if you have downloaded the free demo of CCVS, you will be using the demo protocol.   2: The unique number which identifies you to the clearing house. This may be your merchant account number or a terminal id number, depending on what protocol you will be using. This number will be supplied when you set up your merchant account.   3: Your modem type, and the serial port your modem is attached to. You will also need modem configuration strings. (We can supply modem configuration strings for many popular modems.)   4: The location of your data directory. This is where the configuration file and data directories will be placed.   5: Other information as needed for particular protocols. This information will generally be supplied when you set up your merchant account. We supply a worksheet which you can use to organize all this information, including the details for each protocol. See the file "setup.txt" in the CCVS installation directory. The configuration program is running as user "ccvs". It is important that this be the same user which the actual CCVS software will run as. (We recommend creating a special user account for just this purpose.) Do you wish to continue configuring CCVS as user "ccvs"? [Enter Y to continue, or N to stop here:] If you are still su'd to root, you will instead get the following error. (If this happens, you should su to the CCVS user and re-run ccvs_configure.) The configuration program may not be run as root. You must run  this as the same user which the actual CCVS software will run as.  (We recommend creating a special user account for just this  purpose.) When you continue, the program will begin prompting you for information. At any time, you can back up to a previous prompt by typing "." (period) by itself and pressing Return. Do you want to configure CCVS for the free demo, or a working  merchant account? (If you have not purchased a license for CCVS,  only the demo configuration is available.)  [Enter Y to use the demo configuration, N for a real configuration,  or . to exit:] If you have downloaded the free demo of CCVS, enter "Y". This installs a demo configuration, which does not dial the modem or use a real merchant account. If you have purchased a license and are ready to install a working configuration, enter "N". Where do you want to place the CCVS configuration files and  transaction queues? This should be a directory name which is  writable by the current user.  The default is "/var/local/ccvs". Enter directory, or Return for default value, or . by itself to  back up. > In the tar-file installation procedure, we asked you to make note of a particular directory. Put a "/ccvs" on the end of it and use that here. For example, if you entered "/opt/hks" there, put "/opt/hks/ccvs" here. Again, if you used the default values when installing, or if you used the RPM installation, you can use the default value here, and everything will work. What do you want to name this configuration? This should be a  short filename. The default is "ccvs". Enter name, or Return for default value, or . by itself to back  up. > For example, if you had a web site that represented 40 different merchants, you might have a configuration called "tshirt" for the guy that sells T-shirts, and "music" for the guy that sells Hammond organs. You would use the name you enter here to distinguish between configurations. The demo protocol requires no other information; if you chose it, you will immediately see: Writing "/var/local/ccvs/ccvs.conf"... The CCVS system is now configured. You can now begin testing the demo software. (This acts just like the full CCVS software, except that it does not dial the modem or talk to a real merchant processor.) If you have a license for the full version of CCVS, and you chose to install a real configuration, you will see:  Which protocol and merchant processor will you be using? Credit card clearing protocols:   1: ETC PLUS (FDR7/ETC7/FDR "Omaha"): First Data Corporation   2: South Platform (FDR "Nabanco"): First Data Corporation   3: MAPP: Global Payment Systems "St. Louis"   4: NDC: Global Payment Systems "Atlanta" / NDC   5: VITAL (Visa 2nd generation, K format): Visa / Total System Services   6: UTF: Paymentech Inc.   7: NOVA: NOVA Information Systems [Enter a number, or . by itself to back up:] Select the protocol for which you have a CCVS license and a valid merchant account. What is the number of your merchant account? Enter number, or . by itself to back up. > This number should have been provided with your merchant account. What is your CCVS software customer number? Enter number, or . by itself to back up. > This number will have been provided with your CCVS license. What is your CCVS software license key? Enter number, or . by itself to back up. > This number will also have been provided with your CCVS license. What is the phone number of your merchant processor? Enter number, or . by itself to back up. > The following screen is only applicable to the MAPP and NDC protocols; it will not appear if you are configuring any other protocol. Do you want your credit card processor to accept duplicate  transactions (same value, same card number)? If you answer "yes",  it is possible that you will encounter more chargebacks. If you  answer "no", it is possible that you will lose some charges,  because the acquirer rejects apparent duplicates as erroneous. [Enter Y or N, or . to back up:] You must now enter information about how to communicate with your modem. Do you want to configure a pool of several modems? (If you answer  yes, all the modems must be exactly the same make and model. If  you want to use just one modem, answer no.) [Enter Y or N, or . to back up:] If you have several identical modems, you can configure CCVS to use them all, as a pool. Each CCVS process which needs to use a modem will draw one from the pool, if any are available. Several CCVS configurations can share a set of modems this way. You can also configure a single configuration with two modems, so that authorizations and batch settlement can occur at the same time. What serial port is your modem connected to? (Do not include the  "/dev/" prefix.) The default is ttyS0. The modem should be  connected and ready now, so that the serial port can be tested. Enter port name, or Return for default value, or . by itself to  back up. > The program will test the serial port you enter. (Each of them, if you configure more than one.) This may take up to thirty seconds if the modem does not respond. What type of modem do you have? This information makes it possible to suggest modem configuration strings. If your modem is not listed, you can choose "none of the above"; but you will then have to create your own configuration strings, which is a difficult process.   1: USR Sportster/Courier   2: Hayes Optima   3: Chase Research PCI-RAS   4: None of the above [Enter a number, or . by itself to back up:] You will then be prompted for the modem initialization, dialing, and hang-up strings. (If you configure a pool of modems, they must all be identical, so they will all use the same strings.) The modem initialization string should set the modem to do no  protocol negotiation. What string do you want to use? A string which works for your modem is:    \r~~~\rAT E0 L0 M1 V1 X4 &K0 &M0 +FCLASS=0 Enter string, or Return for suggested value. > The modem dial string should dial the modem. (Do not include a  phone number.) What string do you want to use? A string which works for your modem is:    ATDT Enter string, or Return for suggested value. > The modem hang-up string should hang the modem up if it's  connected. What string do you want to use? A string which works for your modem is:    ~~~+++~~~~~~~~~\rATH0\r~~~ Enter string, or Return for suggested value. > Initialize: \r~~~\rAT E0 L0 M1 V1 X4 &K0 &M0 +FCLASS=0 Dial: ATDT Hang up: ~~~+++~~~~~~~~~\rATH0\r~~~ Are these the values you want? [Enter Y to accept, N to change, . to back up.] (The suggested defaults will of course vary depending on which modem you selected.) The next question is baud rate: What baud rate do you want to use? You should use the  default unless you have explicit information that another  value is appropriate.  The default baud rate is 1200.  Enter rate, or Return for default value, or . by itself to  back up. > There may then be additional questions required by particular protocols. For example, VITAL continues with several more prompts about your business's name, address, bank, and so on. You should already have prepared this information when you got your VITAL merchant account. When you have finished entering configuration information, you will see: Writing "/var/local/ccvs/ccvs.conf"... The CCVS system is now configured. Multiple Merchant Accounts In order to install new merchant accounts, simply follow the configuration procedure again. Use a different configuration name each time. Different configurations may share the same serial port, or the same pool of serial ports. The modems will be used first-come-first-served. Table Of Contents Administrative commands Starting CCVS In order to actually run CCVS you must run the ccvsd program. This daemon is the part of the system that actually makes the phone calls and conducts the transactions. For example, if you want to start processing transactions for the Hammond organ salesman we mentioned earlier, and you used the RPMs, you would type: /usr/sbin/ccvsd music For the tar-file install, if you installed the software in its default location of /usr/local/ccvs, you would type: /usr/local/ccvs/sbin/ccvsd music For more information, see the ccvsd man page. Table Of Contents Making Money Move Some transactions (such as authorizations) occur in real time, when you issue them. Other transactions (such as sales and returns) occur off line, and are not processed immediately. They are batched up and processed as a group from time to time. The program that CCVS uses to do this is called cvupload. We recommend invoking cvupload from your cron system, so it is automatically run without any intervention on your part. You should set it up to run at least once a day. To do the periodic processing for the Hammond organ merchant we've been using for our examples, from the RPM install, you would issue the following command: /usr/sbin/cvupload music For the tar-file install, you would type: /usr/local/ccvs/sbin/cvupload music For more information, see the cvupload man page. Table Of Contents Special Language Considerations C The C library is automatically installed when you install CCVS. When compiling C programs that use CCVS, if you used the tar-file installation, then you should use the include files and link in the CCVS library in the manner usual for your system. (For example, -I<include-directory> and -L<library-directory> -lccvs.) If you installed from RPMs, then the header and library files are in the standard system directories, and you do not need to specify directory names. Java The CCVS Interface to Java must sometimes be built after the rest of CCVS is installed. This is the case, for example, when you're using an OS distribution that doesn't come with a version of JDK -- if we can't make sure we're using the same version of the JDK that you are, it's not really safe for us to distribute a pre-built version of our Java interface for you. Please see Building the CCVS Java Interface. Perl The Perl interface to CCVS must sometimes be built after the rest of CCVS is installed. This is the case, for example, when you're using a distribution that doesn't always come with the same version of Perl, or which doesn't by default include Perl at all. If we can't make sure we're using the same version of Perl that you are, it may not be safe for us to distribute a pre-built version of the Perl interface. Please see Building the CCVS Perl Interface. Python The Python interface to CCVS must sometimes be built after the rest of CCVS is installed. This is the case, for example, when you're using a distribution that doesn't come with a version of Python. If we can't make sure we're using the same version of Python that you are, it may not be safe for us to distribute a pre-built version of the Python interface. Please see Building the CCVS Python Interface. PHP The CCVS PHP3 interface must sometimes be built after the rest of CCVS has been installed. This is the case, for example, when you're using a distribution that doesn't come with a version of PHP. If we can't make sure we're using the same version of PHP that you are, it may not be safe for us to distribute a pre-built version of the PHP interface. Please see Building the CCVS PHP Interface. TCL The TCL interface is always installed as part of the general CCVS installation. You do not have to do anything special for it.   Table Of Contents Supporting CCVS Support for CCVS can be purchased from Red Hat. When you purchase your key to activate CCVS, be sure to review the support options available. See the CCVS web page for more information about purchasing a key and support options. When you contact us for support, please have the following information ready: Your company name The version of CCVS you are using Your merchant number Your CCVS customer number Your operating system. The contents of your configuration file. Red Hat technical support will attempt to address any issues that deal directly with CCVS. We cannot support third party products, except for issues regarding integration with CCVS. Table Of Contents Licensing Agreement SOFTWARE LICENSE AGREEMENT Single User 1. ACCEPTANCE OF TERMS LICENSEE acknowledges that the Licensed Software, as defined below, cannot be installed and enabled for use without the LICENSEE's assent to the terms of this Agreement. LICENSEE agrees that the terms and conditions of this Agreement are accepted, and that LICENSEE's assent thereto may be signified during the download and/or installation and enabling procedure, when LICENSEE clicks the "ACCEPT" button displayed contemporaneously with the text hereof, types "ACCEPT" after the text hereof is displayed, or signifies assent in any other way. By paying the license fee and enabling and using the Licensed Software, LICENSEE is deemed to have accepted and agreed to the terms of this Agreement. 2. DESCRIPTION OF LICENSED SOFTWARE Licensed Software shall include all executable or object files necessary to perform the functions of the program as set forth in the user documentation, sample source code, installation programs and user documentation. Also included is source code for the following Application Programming Interfaces (APIs): Tcl, Python, Perl, Java, and CLI. 3. GRANT OF LICENSE In consideration of payment of the license fee, Red Hat, Inc., as licensor, grants to you, the LICENSEE, a perpetual, nonexclusive non-transferable right (1) to use the Licensed Software on a single computer at a single location to verify credit card purchases under a single merchant account number; (2) to access the source code for the APIs for the sole purpose of integrating the Licensed Software with the LICENSEE's software; and (3) to modify the sample source code. Red Hat, Inc. reserves all rights not explicitly granted to the LICENSEE. 4. OWNERSHIP OF SOFTWARE LICENSEE acknowledges that the Licensed Software (including all modifications thereto) is, and shall continue to be, in its entirety, the sole and exclusive property of Red Hat, Inc. and that LICENSEE has no rights with respect to the Licensed Software except the license granted under Paragraph 3 herein. All intellectual property rights, including all copyright rights, patent rights, trademark rights and trade secrets associated with the Licensed Software are, and shall continue to be, the sole and exclusive property of Red Hat, Inc. 5. USAGE RESTRICTIONS LICENSEE may not modify, adapt, translate, reverse engineer, decompile, or disassemble the Licensed Software. LICENSEE may not create derivative works of the Licensed Software with the exception of the right granted in Paragraph 3 herein to modify the sample source code. LICENSEE may not defeat, or attempt to defeat, the licensing mechanism in the Licensed Software which restricts use of the Licensed Software with a single merchant account number, nor may LICENSEE use the Licensed Software with more than one merchant account number. LICENSEE is hereby prohibited from using the Licensed Software to process transactions for other merchants, or otherwise using the Licensed Software in any manner which would violate the terms of the LICENSEE's agreements with any credit card transaction processor or financial institution. 6. TRANSFER RESTRICTIONS The Licensed Software is licensed solely to the LICENSEE, and may not be used or accessed by any third party. LICENSEE may not transfer, assign, rent, lease, sell, or otherwise dispose of the Licensed Software on a temporary or permanent basis. 7. TERMINATION Red Hat, Inc. reserves the right to immediately terminate LICENSEE's right to use the Licensed Software if LICENSEE violates any provision or restriction set forth herein or if LICENSEE uses the Licensed Software in an illegal or fraudulent manner. Should LICENSEE's rights to use the Licensed Software be terminated pursuant to this paragraph, the license fee shall be forfeited by the LICENSEE. 8. LAWS GOVERNING AGREEMENT This Agreement shall be governed by and construed in accordance with the laws of the State of North Carolina. 9. NO WARRANTY. THE LICENSED SOFTWARE PROGRAMS ARE PROVIDED AND LICENSED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE. 10. LIMITATION OF LIABILITY TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT WILL RED HAT, INC. BE LIABLE TO YOU FOR ANY DAMAGES, INCLUDING LOST PROFITS, LOST SAVINGS, OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES, ARISING OUT OF THE USE OR INABILITY TO USE THE SOFTWARE PROGRAMS, EVEN IF RED HAT, INC. OR A DEALER AUTHORIZED BY RED HAT, INC. HAD BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. 11. LEGAL FEES AND COSTS If any action at law or in equity is necessary to enforce the terms of this Agreement, the losing party shall pay the reasonable attorney's fees, costs, interest, and necessary disbursements of the prevailing party, in addition to any other relief to which the prevailing party may be entitled. 12. PARTIAL VALIDITY If any provisions of this Agreement is held by a court of competent jurisdiction to be invalid, void, or unenforceable, the remaining provisions shall nevertheless continue in full force without being impaired or invalidated in any way. 13. MISCELLANEOUS The parties agree that the terms and conditions herein constitutes the entire and exclusive agreement between them and supersedes all prior or contemporaneous communications, representations or understandings, either oral or written. This Agreement may be amended only by a writing stating the intent to amend this Agreement and signed by authorized representatives of Red Hat, Inc. and LICENSEE. Amendments may not be effected by the preprinted terms and conditions of purchase orders or other forms used by either party. This Agreement may not be modified or supplemented in any other manner including usage of trade, course of business, or oral understandings, either within the industry or between the parties. Table Of Contents Spec Sheet Features: Includes Command Line Interface (CLI) for ease of use. Interacts well with most scripting languages (CGI and shell scripts). Issues instant credit authorizations. Capable of supporting multiple modems. Processes multiple transactions per call. Includes various APIs for use in custom software. Includes an easy-to-use Tk/Tcl user interface as an optional front end. Supported Platforms CCVS runs on selected POSIX compliant platforms: AIX 4.2 BSDI FreeBSD 2.2.6+ Alpha Linux SPARC Linux Intel Linux Caldera Linux Debian Linux 1.3+ Red Hat Linux 4.2 Red Hat Linux 5.1 Red Hat Linux 6.2 S.u.S.E Linux 5.1 PowerPC Linux ARM Linux (Corel Netwinder) SCO OpenServer 5.0+ SPARC Solaris 2.5 Supported Modems The modems we define as "supported" have been tested in-house to verify their functionality with CCVS. However, almost any modem is compatible with CCVS. If your modem does not appear on this list, look through your modem manual to find the string which turns off all compression and error correction, and the string which resets your modem for normal use. You will need these strings because credit card protocols do not support compression or error correction during modem connects. We can provide you with information about how to turn off such features on the following modems: Hayes Optima US Robotics Courier US Robotics Sportster Chase Research PCI-RAS Supported Protocols First Data Corporation's ETC PLUS protocol (a.k.a. FDR7, ETC+, ETC7, "Omaha") First Data Corporation's South Platform protocol (a.k.a. "Nabanco") Global Payment Systems' MAPP protocol (a.k.a. "St. Louis") Global Payment Systems' NDC protocol (a.k.a. "Atlanta") Visa International's VITAL protocol (a.k.a. Visanet, Visa 2nd Generation, "K format") Paymentech's UTF protocol (a.k.a. GENSAR) NOVA Information Systems protocol Application Programming Interfaces (APIs) C library Tcl Extension Perl 5 Extension Python module Java class PHP3 module CLI programs Revised February 15, 2025 Red Hat, Inc. 2600 Meridian Pkwy Durham, NC 27713 919-547-0012 Back to main Documentation page <.php3>