 Back
Getting Started
Logging on
The system is quite easy to use. Each merchant that uses the system has
a unique login ID and password that are used to gain
access to the system. Your RTWare.net Agent (usually
the same as your merchant account provider) will provide
you with your login ID and your password once your account
has been created on the system. Your account will not
be "live" (ready to process real transactions)
until your merchant account is active.
To login to the system, you first must have access to the Internet. If
you need Internet access, contact a local Internet Service
Provider (ISP), who will set your computer up to "dial
in" to the Internet using your computer modem.
Once you have connected to the Internet successfully,
open your Internet browser. With your Internet browser
open, you are ready to login to the system by following
the “Merchant Login” link from our home page.
The Merchant Menu
The first time you log in to the system, you will be required to answer
some basic account information questions and to change
your password from the one that your Agent has given
you. You will also be required to read and agree to
the software license and service agreement.
Once these steps are completed, you will have full access to the system,
which starts with the Merchant Menu. The Merchant Menu
is the central area from which you can access all of
the system’s configuration, reporting, and processing
features.
Basic
configuration options
By clicking on the Settings
item on the Merchant Menu, a merchant can configure
many things about their account. Configuration options
are discussed in greater detail in the User's Guide. To get started
processing credit cards, there are some general settings
that should be checked first. To begin, select the General Merchant Settings item in the Settings menu and click the Go button. In this area are options to set
the account to test mode, set the merchant's time zone,
and change the merchant's password.
Test Mode
Test Mode is a special mode of interacting with the system that is useful
during the initial setup phase, where a merchant may
want to test their setup without processing live card
data. To set an account to test mode, click the Test
Mode checkbox in the General Settings area of the Settings menu.
When an account is set to Test Mode, all transactions appear to be processed
as real transactions, with the exception that a payment
processor is never contacted, and so all transactions
are approved. Transactions submitted in test mode are
not stored on the system, and will not appear in any
reports or lists. It is strongly suggested to leave
an account in Test Mode until it is sure that all aspects
of a merchant's interaction with the system are functioning
properly, so as to avoid possibly incorrectly charging
real credit cards.
How
to charge credit cards
Virtual Terminal
The Virtual Terminal is the tool for manual entry of transactions on the
system. The effect of the Virtual Terminal is very similar
to a traditional electronic credit card terminal. Some
of the reasons you might need to use the Virtual Terminal
are:
·
You
received an order by phone, fax, or mail and need to
process the transaction
·
You need
to perform a credit transaction according to your own
refund policy
·
You previously
received a voice authorization by phone and now need
to submit the transaction to be captured. (Also called
a Post-Authorization)
The Virtual Terminal allows you to do many different kinds of transactions,
including credits/returns (for refunding money to a
customer's credit card), authorization only, post auth/ticket
only, and of course a normal authorization for funds
capture. You don't need to have a web site to use Virtual
Terminal. Simply login to the system and choose Virtual
Terminal on the Merchant Menu.
How to charge using WebLink
In addition to charging credit cards and processing eCheck transactions
with the Virtual Terminal, the real power and flexibility
of the system is seen in its integration with the World
Wide Web. The quickest and easiest way to integrate
a web page with the system is by using the WebLink method.
At its most basic level, interaction between a web page and the system
takes the following form:
1.
A
customer navigates through a merchant's web page, selecting
what they would like to purchase.
2.
The
customer fills in the information that is needed to
begin processing the transaction. This is done using
an HTML form that has been set up to post the information
in the form to the system.
3.
The
customer is then connected directly to the system, which
displays the Payment Form. The Payment Form provides
a place for the customer to enter any information that
it needed which wasn't provided by the merchant's form.
When submitted, the Payment form validates the credit
card.
4.
If
the transaction is not approved, the result is displayed
to the customer, and they are given the opportunity
to correct any information that they may have submitted
in error. If the transaction is approved, a Receipt
Page is shown to the customer, which the customer can
print out or save for their records.
5.
The
Receipt Page that is shown to the customer can have
a link back to the merchant's site to complete the transaction
6.
Unless
otherwise specified, a receipt will be e-mailed to the
customer, as well as to the merchant.
Examples of connecting
to the system using WebLink
The system supports many variations
on the WebLink method of connecting to the system. The
following are some examples of HTML code that can be
customized and inserted into a merchant's own web site
to provide easy ways to integrate the web site with
the system. Please note that all interaction with the
system is done by posting information to https://secure.RTWare.net/gateway/transact.dll.
Example 1 - Bare minimum requirements
The following HTML code
represents the bare minimum that would need to be inserted
into a page to provide a connection to the system.
<FORM METHOD=POST
ACTION="https://secure.RTWare.net/gateway/transact.dll">
<INPUT TYPE=HIDDEN
NAME="x_Version" VALUE="3.0">
<INPUT TYPE=HIDDEN
NAME="x_Login" VALUE="your login ID goes
here">
<INPUT TYPE=HIDDEN
NAME="x_Show_Form" VALUE="PAYMENT_FORM">
<INPUT TYPE=HIDDEN
NAME="x_Amount" VALUE="amount goes here">
<INPUT TYPE=SUBMIT
VALUE="Click here for secure payment form">
</FORM>
The result of the above
HTML code snippet is a button, which when clicked, will
take the user to the system's Payment Form, which will
be already set up to charge a predetermined amount.
The Payment Form will get the rest of the necessary
information from the customer, such as card number and
expiration date, and process the transaction.
This type of connection
would not include any of the other fields that might
be desired, such as names, customer IDs, or descriptions.
Example 2 - Suggested minimum requirements
The following HTML code
provides the ability to pass a little more information
to the system which will then be included in the Payment
Form or Receipt Page.
<FORM METHOD=POST
ACTION="https://secure.RTWare.net/gateway/transact.dll">
<INPUT TYPE=HIDDEN
NAME="x_Version" VALUE="3.0">
<INPUT TYPE=HIDDEN
NAME="x_Login" VALUE="your login ID goes
here">
<INPUT TYPE=HIDDEN
NAME="x_Show_Form" VALUE="PAYMENT_FORM">
<INPUT TYPE=HIDDEN
NAME="x_Amount" VALUE="amount goes here">
<INPUT TYPE=HIDDEN
NAME="x_Cust_ID" VALUE="a customer identification
number or string goes here">
<INPUT TYPE=HIDDEN
NAME="x_Description" VALUE="description
of transaction">
<INPUT TYPE=HIDDEN
NAME="x_Invoice_Num" VALUE="invoice number
goes here">
<INPUT TYPE=SUBMIT
VALUE="Click here for secure payment form">
</FORM>
The result of this HTML
code snippet is a button, which when clicked, sends
the customer to the system's Payment Form with some
more information than in the previous example. The Payment
Form will already display information about the description,
the customer ID number, and the invoice number, and
this information will appear on the receipt and e-mail
confirmation.
Example 3 - Using
a form to gather information
The following HTML code
demonstrates the ability to send additional information
to the system, and have some of that information specified
by the customer.
<FORM METHOD=POST
ACTION="https://secure.RTWare.net/gateway/transact.dll">
<INPUT TYPE=HIDDEN
NAME="x_Version" VALUE="3.0">
<INPUT TYPE=HIDDEN
NAME="x_Login" VALUE="your login ID goes
here">
<INPUT TYPE=HIDDEN
NAME="x_Show_Form" VALUE="PAYMENT_FORM">
<INPUT TYPE=HIDDEN
NAME="x_Amount" VALUE="amount goes here">
<INPUT TYPE=HIDDEN
NAME="x_Cust_ID" VALUE="a customer identification
number or string goes here">
<INPUT TYPE=HIDDEN
NAME="x_Description" VALUE="description
of transaction">
<INPUT TYPE=HIDDEN
NAME="x_Invoice_Num" VALUE="invoice number
goes here">
Enter your first name:
<INPUT TYPE=TEXT
NAME="x_First_Name"><BR>
Enter your last name:
<INPUT TYPE=TEXT
NAME="x_Last_Name"><BR>
Enter any special shipping
instructions:
<INPUT TYPE=TEXT
NAME="Shipping_Instructions"><BR>
<INPUT TYPE=SUBMIT
VALUE="Click here for secure payment form">
</FORM>
The result of this HTML
code snippet is a page that displays a form allowing
the customer to specify their name and any specific
shipping instructions they have. The x_First_Name and
x_Last_Name fields are normal fields recognized by the
system. The Shipping_Instructions field is not a field
recognized by the system, and so it is treated as a
user field. User fields can be named anything that doesn't
conflict with one of the system's fields, and can contain
any information that might be useful in the transaction.
These user fields will be echoed back with the results
of the transaction, and will be displayed on the receipts.
Many more fields can
be sent to the system in this way. For complete details
on the operation of all of the fields, please see the
Developer's Guide, or the Functional Reference in Appendix
B
ADC and other forms of interaction
The system supports
many other forms of integration, including the Automated
Direct Connect (ADC) methods, which bypass the Payment
Form and Receipt Page and permit much more advanced
integration between a merchant's server and the system.
For more information on ADC, please see the Developer's
Guide.
Last updated: Monday,
September 27, 19998:33 PM MDT
Back to Home
|
.gif){kind=small}
