|
Troubleshooting Authorizer problems
is easy and straightforward
for the Reporting to the MAX
When a customer calls with an Authorizer problem,
the first thing to establish is whether or not Authorizer
works as a standalone. This can be verified by running
the Authorizer executable file and inputting a sale
through the Authorizer interface. The modem should
dial and an approval code should appear in the status
box. If this doesn't happen they either have modem
problems or setup problems with Authorizer.
The customer can test the modem by verifying that
it works with other communication software. If it
doesn't work with other communication software then
they either have hardware problems or the modem is
not installed correctly in the operating system. They
can try re-adding the modem through the Windows®
control panel. The modem should be detected and configured
automatically. If it does not, they should replace
the modem.
If the modem works but Authorizer does not, the customer
should verify that they have all of the needed information
from their bank and call Atomic Software for help
setting up their Authorizer application.
After you have verified that Authorizer functions
as a stand alone application, you can integrate it
to POS or OE so credit card transactions are automatically
authorized and captured from within the POS/OE entry
screen. The first step is to go into Constants Maintenance
(DOS products) or Module Preferences (Windows®
products) in the module where transactions are processed.
Find the setting that turns on credit card verification.
In POS/WIN and OE/WIN this line is labeled "CC
Verification Software.” In OE/DOS it is labeled
"Credit Card Verify" and in POS/DOS it is
labeled "Draft Capture.” Select the setting
for this field that is appropriate for the customer's
operations.
Next, go into the entry screen and enter a test credit
card transaction. The following is a test credit card
number that you can use to get an authorization without
actually charging the card: 4005 5500 0000 0019 x,12/05.
When you save the transaction, the modem should dial
and after a few seconds (7 - 15 is normal) return
an authorization code. If the modem doesn't dial,
"ALT""TAB" out of CMS (leave the
entry screen in the "Waiting for Answer"
mode). At the Windows® desktop do a Start - Find
- Files or Folders and search for AUTH000?.IN. This
is the file that CMS writes each time a credit card
sale is processed. The “?” in the file name
comes from the Terminal Number field in the Register
Code. Each register must have a different terminal
number so that requests and answers are routed to
the appropriate terminal. If the terminal number in
the Register Code is 001, then the file name will
be AUTH0001.IN and the response from Authorizer will
be in a file named AUTH0001.OUT.
If the AUTH000?.IN file is not found, then the CC
Verification settings are not correct in CMS. If the
file is found, check the time stamp to verify it is
not an old one. If it is an old one, delete it and
start the test again. If the time stamp matches the
current time (within a few minutes), then Authorizer
either is not running in the background or it is not
pointed to the folder where CMS writes the file. If
Authorizer is not running in the background, launch
it and start the test again. If it is running in the
background, bring it up, click on SETUP -- ADVANCED
and put the path to the AUTH000?.IN file in the API
DIRECTORY field.
|
