Credit Card Vendor Maintenance

You use Credit Card Vendor Maintenance in QAD CSS to define attributes of the credit card integration so that QAD CSS can invoke the processing tools defined by the service you select to handle your credit card transactions.

Important: The values that you specify in this function must match the corresponding values in the VeriSign initialization file, defined during installation. The initialization file is referenced by QAD EA functions and the values specified in Credit Card Vendor Maintenance are referenced by QAD CSS. You must ensure that they stay the same in order to prevent processing errors.

Credit Card Vendor Maintenance

Partner Name

Specify the name of the company that you are using for processing credit card transactions, such as VeriSign, Inc.

Partner Host’s Name

Specify the host server name supplied by your credit card processing company. This is used by the API when transactions are sent to be authorized.

Partner Host’s Port Number

Specify the port number supplied by your credit card processing company. This is used by the API when transactions are sent to be authorized. This is typically set to 443.

Partner Prefix

Specify a prefix that represents your credit card processing service; for example, specify the vs prefix for VeriSign. This prefix is used to locate the appropriate QAD CSS error message to display for VeriSign error codes. This feature lets you customize the content of the error message displayed to users based on your business requirements, rather than displaying the VeriSign return code description directly.

Use QAD CSS Error Message Maintenance to modify message text if needed.

Example: The error code 12 is returned by VeriSign. The system constructs a message ID based on the credit card module ID (cc), Partner Prefix (vs), and return code (0012). It then looks for a message with the ID ccvs0012 in the QAD CSS message table and displays that message content to the user.

Separate messages are set up in QAD CSS for most of the possible error codes that the credit card vendor system can return, detailing the specific error reasons. You may want to modify these messages if such detailed information is not needed.

Since messages may not exist in QAD CSS for all possible return codes, a default message ID of ccvs000x is supplied with the system. If the system receives a VeriSign return code that is not registered, it displays the message content associated with the default error code. The system also sends an e-mail containing detailed error information to the CSR, based on e-mail event EX070.

Important: Do not delete the ccsv000x message, since it is the system default.

Vendor Name

Specify the name that identifies you to your credit card processing service. This is the name by which you do business on the Internet. You specify this name when you complete the application to use the processing partner’s services.

User

Specify the user name that identifies you to your credit card processing company. This is typically the same as Vendor Name.

Password

Specify the secure password associated with the user previously entered. This is the password required for transmitting credit card transactions.

Transaction Timeout

Specify the number of seconds that should be allowed for a credit card authorization to complete. This should typically be set to 30 seconds. If the transaction does not complete within this time, an error is displayed.

Path to a temporary file directory

Specify the fully qualified path to the directory that should be used to create temporary scripts when sending credit card transactions. This should be on the same server as the security certificate and processing program directories. Also ensure that the correct permissions are set on this directory to allow the system to create files.

Path to a Security Certificate directory

To enable the client to authenticate the payment processing server, specify the fully qualified path to the directory containing the security certificate that was created when you installed the integration components.

Path to a Processing Program directory

Specify the fully qualified path to the directory containing the executable programs required for sending credit card transactions.

Note: The system assumes the final component of the path is a directory named /bin and appends /bin to the path you enter in this field.

Credit Card Type

Enter a comma-delimited list of credit card types that users can specify when placing an order. Valid choices are: VISA, MASTERCARD, AMERICAN EXPRESS, and DISCOVER. Spaces between values are ignored if entered.

Verification Method.

Specify whether or not to use a verification method and if so, which method to use.

•

None

Do not use any verification method.

•

Address

Communicate Address Verification Service (AVS) codes with your credit card processing partner.

AVS is a credit card fraud prevention tool designed specifically for ordering environments in which the customer is not physically present to show identification. It allows mail order and electronic commerce merchants to verify addresses by comparing a portion of the billing address from the order with the cardholderís address data. Note that not all merchant banks use AVS codes.

When this option is selected, an additional screen displays during credit card payment that lets the user view and update billing address information to be sent with the credit card transaction.

•

CSC

Communicate Credit Security Codes (CSC) with your credit card processing partner.

Credit Security Code is a three or four-digit number that appears on the credit card and provides a cryptographic check of the information embossed on the card.

When this option is selected, an additional field displays during credit card payment that lets the user enter a Credit Security Code to be sent with the credit card transaction.

Transaction Log will be kept

Indicate if a log of transaction activity should be kept in the wpro_cc_log table in QAD CSS. When this field is Yes, you can view the transactions maintained in the system using Credit Card Transaction Report on the Administration menu. See Credit Card Transaction Report.

The four Proxy fields are currently not implemented.