***************************************************************************
**                 COPYRIGHT (c) 2003 BY TRI-8, INCORPORATED.            ** 
**                    A L L  R I G H T S  R E S E R V E D.               **
***************************************************************************

OneStep Charge General Information
----------------------------------

Thank you for your interest in OneStep Charge, the Pure Progress payment
processing authority.  This README file serves as a quick index and
introduction to the OneStep Charge (OSC) documentation set as well as
providing other necessary general information.

OneStep Charge is a very powerful facilitator for payment processing with
the Progress[tm] 4GL.  The OneStep Charge Pure Progress approach delivers 
a wealth of benefits to the end-user as well as the software developer.


PURE EASE:
The basic structure of OSC use is to include the standard OSC API (an
include file) in your Progress[tm] program, then simply create a
temp-table record (or records), assign the various fields as you need
them, and call the OSC Engine, passing in your temp-table.  OneStep Charge
will handle the rest, and you can simply retrieve all of the results via
the temp-table that you passed to the OSC Engine.  This simple process
allows you to focus on integrating OSC calls into your existing
application framework and developing whatever frontends you would like to
use.

PURE POWER:  
OneStep Charge boasts real-time payment authorizations, such as for credit
cards, in less than 2 seconds in various benchmarks, using machines with
*quite limited* processor power.  OneStep Charge and its underlying
technology boast certification with all major payment processing networks,
with constant development for any new certifications needed (including
private processors), including Vital, Paymentech, Nova, Global Payments,
Promisant, Atlantic Payments and First Data (pending).  With OneStep
Charge's network compliance and the abilities of even the processing
networks themselves to interact, virtually any U.S. merchant account can
use OneStep Charge.

PURE SOLUTIONS:
OneStep Charge is thoroughly configurable and allows various forms of
usage, including single-transaction and batch processing models.

PURE PROFIT:
Solutions built with OneStep Charge take advantage of a fully-qualified 
processing approach that achieves maximum processing fee savings.  In 
addition, fully-automated solutions built with OneStep Charge power are 
renowned for outstanding overhead reduction and general cost minimization.


Throughout the OneStep Charge documentation set you will find the "$OSC"  
convention used to refer to the installation directory for OneStep Charge.
This basically corresponds to the directory into which you have extracted/
untarred the OSC distribution.  For example, if you have untarred your
OneStep Charge distribution into /opt on a UNIX machine, $OSC will refer
to "/opt/OneStepCharge" for your installation.


Organization of $OSC
--------------------
The OSC distribution contains five directories: doc, conf, tri8osc,
samples, and broker.

$OSC/doc: OneStep Charge documentation set 
The full User's Guide is located in the documentation directory and is
distributed in PDF format (OSC_users_guide.pdf).  Other guides and
documentation are found in this directory.  To begin using or testing
OneStep Charge immediately, see the QuickStart Guide located in
QuickStart.txt.

$OSC/conf: OneStep Charge configuration directory
This directory contains sample OSC configuration files.

$OSC/LICENSE.txt: OneStep Charge license specifications
This file contains licensing information.

$OSC/tri8osc: OneStep Charge software
The actual OneStep Charge software is located in the "tri8osc" directory.  
In order to use OSC you will need to place the tri8osc directory somewhere
in your PROPATH.  This can be done by modifying your PROPATH to include
your $OSC/tri8osc directory, or you may copy/move the tri8osc directory
into a location already included by your existing PROPATH.  This latter
method eliminates the need to make changes in startup scenarios and
parameters and is generally the easiest approach.

$OSC/samples: OneStep Charge sample programs/templates
This directory contains some sample programs and code snippets that
illustrate how one might go about implementing OneStep Charge in an
application.

$OSC/broker: OneStep Charge Broker files
This directory contains the OneStep Charge Broker (OSCBroker).  The
OSCBroker is a Java utility that handles OneStep Charge's premium 2048-bit
encryption and triple-redundant failover capabilities.  It operates as a
system daemon and must always be running in order for OneStep Charge to
operate.  Please note that you may run the OSCBroker on a separate machine
from OneStep Charge itself if you desire, though be advised that the
communications between OneStep Charge and the OSCBroker are NOT encrypted.


Please see the full documentation set in $OSC/doc, including the OneStep 
Charge User's Guide.


If you have any questions not answered by the documentation set or
associated FAQs, or for further information or inquiries, please contact
Tri-8, Inc.:

Tri-8, Inc.
820 South Main Street 
Suite 2000
Stillwater, OK  74074
(v) 405.377.3888
(f) 405.533.1136
http://www.onestepcharge.com
mailto: psupport@onestepcharge.com