.php3> CCVS Check Verification Module Guide Version 3.3 Revised July 20, 2025 Red Hat, Inc. 2600 Meridian Pkwy Durham, NC 27713 919-547-0012 Back to main Documentation page   Table of Contents Overview Check Verification Protocols Transaction Arguments   Overview The CCVS Check Verification Module uses the same interface as the CCVS credit-card system. You should familiarize yourself with the CLI and API documentation for the language you will be using. The check-verification system differs from the credit-card system as follows: Different protocols CCVS currently supports the SCAN and TeleCheck check-verification protocols. Different transaction arguments There are a few new argument types specific to check verification, and several of the credit-card arguments are inapplicable. See "Transaction Arguments", below. Authentication only, no sale Since check verification never involves moving money, these protocols only support the "auth" command. You should not use the "sale", "reverse", "return", or "void" commands. After the transaction is authorized, you can delete it. No transaction uploading All check-verification transactions are handled by the ccvsd daemon. Since there is no off-line settlement, the cvupload program will never dial the modem or process transactions. However, you should still run cvupload regularly. It contains database-cleaning functions, which guard against potential corruption in the transaction lists. When you run cvupload with a check protocol, it will clean the databases and then exit with no output.   Check Verification Protocols SCAN Access to SCAN is handled through ArJay Data Corporation.. CCVS can process SCAN "Full MICR" and "Double ID" transactions. "Full MICR" requires the transit/routing number, bank account number, check sequence number, and the amount of the check. "Double ID" requires all of those plus driver's license data (the license number, and a code representing the state that issued the license.) If you have any problems with SCAN check verification, there is an ArJay Data help desk available by telephone, at 1-800-296-0170. TeleCheck TeleCheck is managed by TeleCheck International, Inc. CCVS can process TeleCheck transactions with either MICR data (the transit/routing number, bank account number, check sequence number, and the amount of the check) or driver's license data (the check sequence number, the amount of the check, the license number, and a code representing the state that issued the license.) If you have any problems with TeleCheck check verification, see TeleCheck phone contact list.   Transaction Arguments The following arguments are used (with the "add" command) when creating a transaction for check verification. Both the string name and C constant name are given. amount         CV_ARG_AMOUNT The amount of the check, in dollars and cents (for example, "29.95"). Note that "0.00" is usually an illegal amount. troutnum       CV_ARG_TROUTNUM The transit/routing number of the check. This is a nine-digit number. bankaccnum     CV_ARG_BANKACCNUM The bank account number of the check. checknum       CV_ARG_CHECKNUM The check sequence number of the check. This is typically in the upper right-hand corner. licensenum     CV_ARG_DVS_LICENSENUM The driver's license number used in verifying the check. This can consist of letters, digits, and occasionally an asterisk (*). Other characters are ignored. Note: The asterisk is only used in some old Washington state licenses. licensestate   CV_ARG_DVS_LICENSESTATE The state of the driver's license used in verifying the check. This should be the standard two-letter state abbreviation. (For a complete list, including Canadian provinces and other codes, see State Code List.) Other argument types are ignored. The computer-readable numbers typically printed at the bottom of a check should show the transit/routing number, the check sequence number, and the bank account number. They are often, but not always, in that order.   Revised July 20, 2025 Red Hat, Inc. 2600 Meridian Pkwy Durham, NC 27713 919-547-0012 Back to main Documentation page <.php3>