|
The DOS credit card processing software referred to here
has been replaced by a full 32-bit Windows server and client.
The integration method retains the simplicity of the DOS integration,
supports ALL platforms and includes many improvements.
What are the components of SoftEFT ?
SoftEFT provides two components to make up an overall EFT
solution -
-
a server part that is responsible for authorising transactions,
going online to the bank for authorisation if required
and storing transactions. The server can be implemented
as either a TSR program, or can be run as a foreground
program on a dedicated EFT PC.
-
a client part that is the user interface and which accepts
the card information and sales value and leads the user
through the card authorisation process. The client program
is DOS based and will run on a PC or PC based EPOS system
with a VGA screen.
What are the basic hardware and software requirements in
order to integrate SoftEFT?
A PC based EPOS application running under DOS or Windows
operating system. To support more than a single point of sale
then all terminals must be networked together and must allow
the mapping of a logical drive. Hardware requirements are
a VGA screen if the SoftEFT supplied client is to be used.
How do I Integrate my existing EPOS application with SoftEFT?
The easiest method of integration is to use the supplied
client part of SoftEFT. In order to do this your EPOS system
must meet the requirements above. Within your EPOS application
you would define a tender as payment by EFT and allow an amount
to be tendered against this tender type. From your EPOS application
you create a text file that contains details of the sales
transaction, i.e. whether it is a sale or refund and the amount
to tender. You then call the SoftEFT client program from within
your software. The SoftEFT client will then read the information
from the file and display a screen showing the sale amount
and prompting for the credit card to be swiped. From this
point the SoftEFT client software will process the card transaction
- checking the validity of the card, checking the hot card
file, handling any voice referrals, manual authorisations,
and printing the credit card voucher. At any time in the process
it is possible to abort the credit card tender. When the credit
card processing is complete the SoftEFT client creates an
output text file that indicates the success or failure of
the transaction and returns control to the EPOS application.
Your EPOS software should then read the output file and either
complete the sale if successful or request an alternative
tender/void the sale if unsuccessful.
What if the POS screen I am using is a smaller display than
a normal PC?
In this case you will need to write a front-end EFT client
yourself and interact directly with the server. This will
mean a little more development time as your software will
need to react in the prescribed manner to the responses given
by the SoftEFT server. The interface again is kept very simple
by using the text file interface. (SoftEFT Rtext) For greater
speed a binary interface using 'C' structures is available
but this should only be considered in extreme cases as the
development is much more complicated. Both of these methods
are described in detail in the manual. There will be some
testing required by the acquiring banks in the case of replacing
the SoftEFT supplied client.
SoftEFT Technical Specifications
|
