The following is a list of problems & solutions we have encountered with the Credit Card Interface. If you do not find your particular problem listed below, please contact the First Resort Support Department for assistance.

• Resubmitting a transaction prior to getting a response back from the host. Every transaction will get a response. If you do not receive a response, check your credit card server to make sure it is up and running prior to resubmitting the transaction.

• Always read your network broadcast message prior to pressing Ctrl Enter to clear the screen. These messages are important and tell you the status of the transaction.

• Transactions should not be deleted, you should reverse the transaction. If reversing the transaction is not acceptable to you, it is possible to delete a transaction on the back of a folio, if the transaction has not yet processed and is OPEN. There should be one person in the office designated to take care of this type of issue. It is very IMPORTANT that you take down the Credit Card Server while you delete this transaction. This is a safety measure to insure that the transaction does not slip through and process.

• It is required that the Credit Card Server and the workstation where you are entering the credit card both run the same version of AVMAIN (as of 8/21 version 8.89 or greater). If this is not so, the transactions will not post to the correct RSD records.

• Batches need to be settled in a timely fashion. Once a batch approaches 100 transactions, ProtoBase can not handle such a large data set and it will cause the Credit Card Server to crash. The number of transactions in the current batch can be determined by looking at the Review Current Batch report on the Credit Card Back Office menu (P-C-C). Most credit card companies offer a better rate if you settle your batch every day prior to midnight.

• The following is a list of processor oddities which we have discovered;
  1. With Visanet you can not VOID a PAS, you must issue a RETURN.
  2. In a batch, Gensar voids show up as $0.00.
  3. In a batch, Visanet voids show the amount of the purchase.
  4. In a batch, Envoy voids do not show at all.

• If a client is using an external Practical Peripheral modem and they are getting a communications error (3 or 103) and they can't seem to get connected try adding \N to the initialization string in the pbconfig file, modem devices section.

• Bravo Card. This card is a product of Discover and will work fine with our Credit Card Interface. There is one possible change that may need to be made. The ranges on the top section of the PBCONFIG.CFG file may be out of date if installed prior to 2/96. The range for Discover should be "601100-601199". We may see this with other clients and we may see other cards be affected.

• Envoy's processor message for a good batch is simply "Complete C Acknowledged".

• Whenever SDC (Southern Data Com) asks you to set up the Debug at the client site, what they are talking about is;
  1. Bring CC Server off line
  2. Type in at DOS prompt - set pbdebug=PBCOM (-level2, -FILECOM.LOG)
  3. Bring CC Server back on line
  4. Do a few transactions
  5. Bring CC Server off line. Print COM.LOG and fax to SDC
  6. Reboot CC Server

• Error Message I died with reason "0"
  This is a Protobase error message indicating that there has probably been a hardware problem which caused a file lock. Go to the PB directory and type del *.lck. This will release the lock.

• The latest version gives us an important diagnostic tool. If you have a hardware sounding question on the Credit Card Interface, go to the Credit Card Server and press the Down Arrow key. This will bring up the diagnostic listing for your Server. Press CtrlD (print screen) and fax it to the First Resort Support Department. This can be a real time saver in some situations.