The First Resort Credit Card Interface
INTRODUCTION:
This document is designed to provide an overview of
the credit card interface for introductory purposes.
Questions that are not covered in this document should
be directed to First Resort Technical Support.
First Resort Credit Card Interface Overview
What is the First Resort credit card interface? The
First Resort credit card interface is a module of
software that contains the functionality to let the user
perform entire credit card transactions within First
Resort software. This functionality includes;
- Swiping or manual entry of credit cards.
- Automation of the authorization of a transaction.
- Batch processing including the review of a
transaction batch and the settlement of a transaction
batch.
- Reporting and review of authorized and settled
transactions.
How does the First Resort credit card
interface differ from a dedicated credit card
authorization unit?
The First Resort credit card interface utilizes
similar technology to a Verifone or Xion credit card
swiper, however the interface builds this functionality
into First Resort software so you can authorize a credit
card transaction and enter it onto the folio in one
series of keystrokes instead of entering a transaction
in First Resort and then authorizing and settling a
separate transaction entry outside of the First Resort
software.
Use of the First Resort credit card interface,
front office and back office.
The front office part of the credit card interface is
where transactions are made, put into a batch (the batch
is discussed further in this document), and posted onto
a folio. The menu options for the front office credit
card features are accessed from the folio by selecting
< T > for transactions. There is then an option to
select credit card transactions.
The following are the transaction types that can be
made;
- AUTH = Authorization - authorizes credit
card for a set amount
- SALE = Sale - Actual sale charged to a
credit card
- PAS = Prior authorized sale - uses auth
previously made for sale
- VOID = Void - voids a sale in the current
batch
- RETURN = Return - reverses a sale in a
previous batch
- VOID RETURN = Void Return - voids a return
in the current batch
The back office part of the credit card interface is
where transactions batches are processed. Batches can be
reviewed and reported on as well within the back office
features. The menu options for the back office credit
card features are located by pressing 'P' from the main
menu then selecting 'C' for Credit Card Back Office.
These options are not visible until the credit card
interface is installed.
The following menu appears when 'P' is activated;
- B = Batch Settlement - Initiates the
settlement of the current batch
- C = Review Current Batch - Allows review of
the current batch
- E = Exception Reporting - Allows
transactional review through filters
- S = Review Settled Batches - Allows review
of settled batches
- U = Unmatched Authorizations - Allows
review of Auth's not tied to a sale
- V = View Transaction Log - Reviews every
logable credit card action
Batches
In our Credit card interface transactions made are
placed into a batch for settlement. The batch consists
of the transactions made from the time the previous
batch was settled to the present. This batch then
needs to be "settled", which means it must be
transmitted via modem to a "host processor" who then
debits or credits the card holders account for the
transactions in the batch and then initiates the
deposits into the customers bank account. Batches are
typically settled daily . In our system batches cannot
be edited, if a SALE transaction is incorrect it must
be voided in the current batch by running a VOID
transaction. If the sale occured in a prior batch a
RETURN must be done to reverse the SALE amount.
Application Codes
This interface requires an application code { I }
in the contractual options, the business setup page 2,
AND ONLY ON THE ONE USER CODE THAT THE CREDIT CARD
SERVER USES TO AUTO LOG IN...NOT ON ANY OTHER USER
CODES. For the other credit card options described in
section 2 A & B to appear the interface must be
properly installed, as there are no application codes
controlling the appearence of the credit card options.