__________________________________________________________________________________________

PayFuse
User's Training Guide
__________________________________________________________________________________________

First National Merchant Solutions

1620 Dodge
Omaha, Nebraska 68197
(800) 228-2443 ext. 6751

Web: www.foomp.com
Email: [email protected]

Revision Date: January 23, 2004

PayFuse User's Training Guide

Contents
First National Merchant Solutions Contact Information ............................................................3

System Requirements ………………………………………………………………………….3

Registering for PayFuse……….………………………………………………………...……..3

Objective of Training Guide.…...……………………………………………………………...4

Glossary of Navigation Buttons...……………………………………………………………...4

Lesson 1 - Login and Navigation………………………………………………………………5

Lesson 2 - Orders (Transaction Processing)……...……………………………………………8

Lesson 3 - Reports…………………………………………………………………………….13

Frequently Asked Questions…………………………………………………….……………18

Glossary..……………………………………………………………………………………...21

Trademark Notices
PayFuse, its logotype and the name First National Merchant Solutions are service marks of SPC, Inc. d/b/a
First National Merchant Solutions. Other trade and service marks in this document are properties of their owners.
No part of this publication may be reproduced, introduced to, or stored in a retrieval system, nor transmitted in
any form or by any means (electronic, mechanical, photographic, audio, or otherwise) without prior written
permission from First National Merchant Solutions.

The above notwithstanding, permission is granted to reproduce and distribute this document on a nonexclusive,
royalty-free basis, provided: (i) this copyrights notice and the beginning paragraphs are prominently displayed at
the beginning of each copy, and (ii) this document is accurately reproduced in full, complete form with formal
attribution of the document to First National Merchant Solutions.

The information contained in this document is CONFIDENTIAL to the business and operations of SPC, Inc. d/b/a First
National Merchant Solutions, and shall not be duplicated or disclosed in whole or in part without the prior written
2
permission of First National Merchant Solutions.
PayFuse User's Training Guide

First National Merchant Solutions Contact Information

First National Merchant Solutions
1620 Dodge
Omaha, NE 68197

For managed accounts, please contact your account manager. For all other accounts, please call (800)
228-2443 and request Customer Service.

System Requirements

Minimum Requirements

PC Requirements:
486 processor or higher
16 MB of RAM or higher

Web Browser Requirements:

MS IE 5.5 SP2 with 128 bit encryption on Microsoft Windows
MS IE 6.0 on Microsoft Windows
Netscape 6.2.X and 7.0 on HP-UX, Sun Solaris, or Microsoft Windows

Recommended Requirements

PC Recommendations:
Pentium III processor or higher
32 MB of RAM or higher

Browser Recommendations:
MS IE 6.0 on Microsoft Windows

Registering for PayFuse

To sign up for PayFuse you only need to follow these two easy steps.

1. Registering a Merchant Account. If you do not have a merchant account, please contact either
your First National Merchant Solutions representative, or email us at [email protected]
Once you have registered with a First National representative, you may receive several emails
(depending on your configuration), and you will receive a letter via U.S. Mail within 10 business
days.

2. Authentication Information. The letter will contain your User ID, Password, Client ID, and
URL for accessing your account on PayFuse. Using this information, login to your PayFuse
account and you can begin processing transactions online.

The information contained in this document is CONFIDENTIAL to the business and operations of SPC, Inc. d/b/a First
National Merchant Solutions, and shall not be duplicated or disclosed in whole or in part without the prior written
3
permission of First National Merchant Solutions.
PayFuse User's Training Guide

Objective of Training Guide

This training guide provides a quick step-by-step tutorial for accessing and using your PayFuse
account. New PayFuse merchants are most interested in two aspects: 1) generating transactions (for
example, authorizations and credits) and 2) viewing reports. Within the context of three lessons, the
user will be able to efficiently navigate, and input transactional data into PayFuse. Advanced
competency will develop with continued usage.

Glossary of Account Navigation

1. Orders - Describes functionality associated with generating and maintaining transactions,
including using the Internet Virtual Terminal (IVT) for processing authorizations and credits.
2. Reports – Generate reports for viewing and executing transactions and orders.
3. Risk Management – Create and manage rules which let you build a customized fraud protection
system (not covered).
4. Administration - Allows you to administer users and configure store parameters (not covered).

Note: The store administration should be used with caution, as any changes to these parameters may
cause transaction processing to fail.

The information contained in this document is CONFIDENTIAL to the business and operations of SPC, Inc. d/b/a First National
Merchant Solutions, and shall not be duplicated or disclosed in whole or in part without the prior written permission of First
4
National Merchant Solutions.
PayFuse User's Training Guide

Lesson 1 – Login and Navigation

Objective: Learn how to log into PayFuse and familiarize the user with navigation within PayFuse.

1. Once you have obtained the authentication information via mail or from a First National
representative, log into your PayFuse account at the following secure URL:

https://www.payfuse.com/cgi-bin/clearcommerce_engine.exe/<ClientID>

Save this URL reference to your favorites in your web browser for easy future access.

The Client ID is a unique integer identifier associated with the User ID and Password, which is
appended to the end of the URL above. Alternatively, an alias (a unique string identifier) may be
provided to you and may be used in place of the Client ID.

The information contained in this document is CONFIDENTIAL to the business and operations of SPC, Inc. d/b/a First National
Merchant Solutions, and shall not be duplicated or disclosed in whole or in part without the prior written permission of First
5
National Merchant Solutions.
PayFuse User's Training Guide

2. Input your User ID and Password and select the Login button. The Store Administration tool
will be displayed.

This window allows the user to navigate the PayFuse account between four major categories.
Read the text description in the window to familiarize yourself with each category. Press the Help
hypertext in the upper right-hand corner on any window to display the online help system.
Likewise, press the Sign Off hypertext in the upper right-hand corner to logout of your PayFuse
session.

1. Orders - Describes functionality associated with generating and maintaining transactions,

including using the Internet Virtual Terminal (IVT) for processing authorizations, voids, credits,
and many other transactions. Use reporting mechanisms to view lists of transactions and operate
on more or more of those transactions.
2. Reports – Generate reports for viewing transactions and orders.
3. Risk Management – Create and manage rules which let you build a customized fraud protection
system.
4. Administration - Allows the user to administer users and configure store parameters.

The information contained in this document is CONFIDENTIAL to the business and operations of SPC, Inc. d/b/a First National
Merchant Solutions, and shall not be duplicated or disclosed in whole or in part without the prior written permission of First
6
National Merchant Solutions.
PayFuse User's Training Guide

Note: The store administration should be used with caution, as any changes to these parameters may
cause transaction processing to fail.

Note: You should always log out of your session if you are going to be away from your terminal
and close your web browser. This is strongly recommended in order to prevent unauthorized
users from accessing and or compromising consumer sensitive data.

The information contained in this document is CONFIDENTIAL to the business and operations of SPC, Inc. d/b/a First National
Merchant Solutions, and shall not be duplicated or disclosed in whole or in part without the prior written permission of First
7
National Merchant Solutions.
PayFuse User's Training Guide

Lesson 2 – Orders (Transaction Processing)

Objective: Learn the basic functionality associated with the Orders hypertext link, including
processing transactions.

Once logged in, you will see the different hypertext links labeled in a caption at the top of the page.
Select the Orders hyperlink to access the Point of Sale (POS), also known as the Internet Virtual
Terminal (IVT).

The information contained in this document is CONFIDENTIAL to the business and operations of SPC, Inc. d/b/a First National
Merchant Solutions, and shall not be duplicated or disclosed in whole or in part without the prior written permission of First
8
National Merchant Solutions.
PayFuse User's Training Guide

Select the Point of Sale hypertext on the left-hand side of the window. The POS (a.k.a. the IVT) is
displayed.

Processing Credit Card Transactions

In summary, this window can process any type of transaction described by the drop-down list
associated with Transaction Type. Depending on the transaction type selected, the contents of the
window will change. Those fields marked with ‘*’ are required fields. For example, to generate an
authorization, use the PreAuth or Auth transaction types. These transactions require the credit card
number, the expiration date associated with the credit card, and the total requested for authorization.
Additional information is optional. (NOTE: Refer to the Glossary at the end of this guide for
definitions and differences between PreAuth and Auth transactions).

The Processing Mode will default to Production, which means the transaction is live. If the
processing mode is Approved, Declined, Random, or Test, then the transaction is executed in a test
mode and the transaction is not actually processed through the payment vendor. For production
transactions, PayFuse is utilizing Vital as the third-party transaction processor for authorization and
First National for settlement.

The information contained in this document is CONFIDENTIAL to the business and operations of SPC, Inc. d/b/a First National
Merchant Solutions, and shall not be duplicated or disclosed in whole or in part without the prior written permission of First
9
National Merchant Solutions.
PayFuse User's Training Guide

Billing Information is required (specifically, the numeric portion of the street address, and the zip)
for AVS checking. However, this information is optional.

Finally, Periodic Billing Information can be input into PayFuse to process recurring payments on a
subscription or installment basis; i.e. PayFuse can automatically generate authorization requests on a
periodic basis.

Example: Generating an Authorization

From the POS, input the following data:

Activity = Credit Card transaction

Transaction Type = Auth
Card Number = 4242424242424242 (This credit card # will pass the Mod10 check)
Expiration Date = 01/2004
Amount = 1.25
Processing Mode = Approved

The information contained in this document is CONFIDENTIAL to the business and operations of SPC, Inc. d/b/a First National
Merchant Solutions, and shall not be duplicated or disclosed in whole or in part without the prior written permission of First
10
National Merchant Solutions.
PayFuse User's Training Guide

Your input will appear as follows:

The information contained in this document is CONFIDENTIAL to the business and operations of SPC, Inc. d/b/a First National
Merchant Solutions, and shall not be duplicated or disclosed in whole or in part without the prior written permission of First
11
National Merchant Solutions.
PayFuse User's Training Guide

Select the Process Transaction button. A ‘Point of Sale – Receipt’ window will appear.

If the Order ID and Group ID are not input into the POS, PayFuse will generate unique IDs,
respectively. In this example, the processing mode is Approved, which indicates that the resulting
Authorization Code is simply a PayFuse generated test result.

Settlement Processing

The default mode for processing settlement is to settle all captured transactions on a daily basis at
11:00 PM CST. Setting the time for daily, automatic settlement to occur is a store administration
function located under the Administration hypertext (see page 63 of the Store Administration Guide
for more information). Settlement can be executed manually by utilizing the Settlement transaction
for the Activity type within the POS. However, utilizing this manual transaction will batch up all
existing captured transactions and only mark them as bulk ready.

Note: First National batches up ALL bulk ready transactions for ALL existing merchants at 1:00 AM
Central Time on a daily basis and submits this batch settlement file for processing; i.e. this
architecture allows the merchant to ONLY mark batches manually, but no batches are physically
processed until 1:00 AM Central Time.

The information contained in this document is CONFIDENTIAL to the business and operations of SPC, Inc. d/b/a First National
Merchant Solutions, and shall not be duplicated or disclosed in whole or in part without the prior written permission of First
12
National Merchant Solutions.
PayFuse User's Training Guide

Lesson 3 – Reports
Objective: Learn the navigation features associated with Reports and how to derive report results
and execute some operational features on those results.

The most useful types of PayFuse reporting revolve around the ability to query orders and
transactions by date range. Likewise, the user has the ability to execute transactions from query
results.

1. Reporting by Orders. Once logged in, select the Orders hypertext link. The following window
will be displayed:

For immediate results from ‘canned’ report queries, select the This Month or Unshipped
hypertext on the left-hand side of the window to view orders associated with the current month, or
only those unshipped orders for the current month, respectively.

The information contained in this document is CONFIDENTIAL to the business and operations of SPC, Inc. d/b/a First National
Merchant Solutions, and shall not be duplicated or disclosed in whole or in part without the prior written permission of First
13
National Merchant Solutions.
PayFuse User's Training Guide

To generate search criteria associated with orders, select the Orders hypertext on the left-hand
side of the window. The following window will be displayed:

The information contained in this document is CONFIDENTIAL to the business and operations of SPC, Inc. d/b/a First National
Merchant Solutions, and shall not be duplicated or disclosed in whole or in part without the prior written permission of First
14
National Merchant Solutions.
PayFuse User's Training Guide

Select the desired search criteria and select the Search button. The following window describes an
example of what a report may yield by inputting Order Search Criteria:

Note the check boxes marked Ship and Credit in the left-hand columns of the results. By simply
clicking on any of those check boxes and utilizing the Operations hypertext on the left-hand side
of the window, a user may execute a transaction without returning to the Point of Sale. Any
orders that only have authorizations may be marked as shipped, and the Ship orders hypertext
may be checked to issue a PostAuth transaction for the selected order. Any orders that have both
authorization and capture and are ready for settlement, may be credited by checking the desired
orders and selecting the Credit orders hypertext. Note the Order IDs within the report.
Underlined values within the user interface are hypertext for drilling down on more detailed
information. Therefore, clicking on an Order ID will yield detail information associated with that
order.

The Current Batch report simply displays all transactions which are marked as ready for
settlement.

The information contained in this document is CONFIDENTIAL to the business and operations of SPC, Inc. d/b/a First National
Merchant Solutions, and shall not be duplicated or disclosed in whole or in part without the prior written permission of First
15
National Merchant Solutions.
PayFuse User's Training Guide

2. Reporting by Transactions. Once logged in, select the Reports hypertext link. Alternatively, a
user may generate reports associated by transaction ID. For immediate results from ‘canned’
report queries, select This Month on the right-hand side of the window to view transactions
associated with the current month. To generate search criteria associated with orders, select the
Transactions hypertext link. (NOTE: The user may also select reports based on Order ID as in
the previous discussion, but the user will NOT be able to operate on any of those transactions
through the Reports mechanism as was the case via the Orders hyperlink).

Search criteria for transactions can also be input in a similar manner as it is input for searching for
orders. To accomplish this, press the Transactions hypertext link on the left-hand side of the
window. The following window will be displayed:

Note: PayFuse is currently configured to only process credit cards as the Payment Mechanism; i.e.
PayFuse is NOT currently configured to process checks.

The information contained in this document is CONFIDENTIAL to the business and operations of SPC, Inc. d/b/a First National
Merchant Solutions, and shall not be duplicated or disclosed in whole or in part without the prior written permission of First
16
National Merchant Solutions.
PayFuse User's Training Guide

Select the desired search criteria and select the Search button. The following window describes what a report
may yield by inputting Transaction Search Criteria:

The information contained in this document is CONFIDENTIAL to the business and operations of SPC, Inc. d/b/a First National
Merchant Solutions, and shall not be duplicated or disclosed in whole or in part without the prior written permission of First
17
National Merchant Solutions.
PayFuse User's Training Guide

Frequently Asked Questions

1. Do you need a PC to operate PayFuse?

The Internet Virtual Terminal requires a PC and an Internet connection to operate. Right now
PayFuse is NOT currently supporting PDA’s or wireless phone connections.

2. Is PayFuse web hosted?

PayFuse utilizes the Internet as the means to process transactions, just like a physical terminal uses a
phone line to process a transaction. PayFuse is hosted internally on FNBO servers.

3. I cannot access the PayFuse login window from my web browser?

Troubleshooting steps:

a) Access the PayFuse login window from a web browser on a different PC. Be sure to clear the
local cache in the web browser. This step will ensure that the PayFuse web server is up and
running. The PayFuse URL is:

https://www.payfuse.com/cgi-bin/clearcommerce_engine.exe/<clientID>

b) Verify the URL is accessing a secure http connection; i.e. https NOT http
c) Verify the exact URL is being utilized as specified in Step (a) above.
d) Can commonly used web sites (e.g. cnn.com, yahoo.com, etc… ) be accessed? If not, contact
your ISP.

If all of the above steps are not successful, contact First National Merchant Solutions.

4. I am able to access the PayFuse login window, but unable to login?

Troubleshooting steps:

Verify the correct login information:

i) Client ID in the PayFuse URL (remember to press <Enter> after inputting the Client ID at
the end of the URL)
ii) Username (case sensitive)
iii) Password (case sensitive)

If all of the above steps are not successful, contact First National Merchant Solutions.

5. What is the minimal information required to generate an authorization/preAuthorization

from Virtual Terminal (POS)?

The information contained in this document is CONFIDENTIAL to the business and operations of SPC, Inc. d/b/a First National
Merchant Solutions, and shall not be duplicated or disclosed in whole or in part without the prior written permission of First
18
National Merchant Solutions.
PayFuse User's Training Guide

The minimal information for generating an authorization is:

i) Transaction Type
ii) Credit Card #
iii) Expiration Date
iv) Amount

Only fields denoted with a (*) are required fields. All other fields are optional for executing any
given transaction.

6. Do I need to input an Order ID?

No. PayFuse will generate a unique Order ID for tracking if one is not supplied by the merchant.
The merchant may supply his/her own order ID. PayFuse generates unique Transaction IDs for all
transactions. PayFuse will generate a fairly lengthy Order ID & Transaction ID (up to 36 characters
each) based on the MAK address of the workstation and the timestamp of the transaction.

7. I am not generating any results when querying for orders or transactions?

Verify proper date ranges for generating results. Simply selecting the Search button will not yield
desired results. Consider all input parameters when generating reports.

8. I am attempting to login but am not able to. I am receiving the following error which is
displayed on the PayFuse login window:

Session error: Invalid Arvgument: “(‘errCode’ is ‘7’, ‘StatusCode’ is ‘524’)

What is wrong?

The error above is generated after an inactive PayFuse session has timed-out. The error is associated
with the PayFuse session cookie and is a security mechanism within PayFuse. To clear the error,
simply exit the browser session and start a new browser session pointing to the PayFuse URL.

The information contained in this document is CONFIDENTIAL to the business and operations of SPC, Inc. d/b/a First National
Merchant Solutions, and shall not be duplicated or disclosed in whole or in part without the prior written permission of First
19
National Merchant Solutions.
PayFuse User's Training Guide

9. I am attempting to generate an authorization from the Internet Virtual Terminal

(IVT)/Point of Sale (POS) from within the PayFuse User Interface. However, when
attempting to process the transaction, I received the following error message:

5 – Did not find Authorization Routing Information for ClientId <Client ID

(Integer)>/CardType <CardType (Integer)>

What is wrong?

The error above is generated when the user attempts to enter a card type which is not currently
supported by the merchant’s store configuration. Desired card types can be added or deleted to the
merchant’s configuration by using the ‘Routing’ hypertext under the ‘Administration’ hypertext
link from within the Store Administration Tool (NOTE: Other processes must happen within the
confines of First National for the desired card type to be supported). The entries below describe the
integer associated with each card type within PayFuse:

1 - Visa
2 - MasterCard
3 - Discover
4 - Diners
5 - Carte Blanche
6 - JCB/JCL
7 - enRoute
8 - American Express
9 - Solo
10 - Switch
11 - Electron

10. Why am I getting a Soft Settle Error for my batch?

In rare cases when using VirtualNet as the Settlement vendor (settlement will normally be settled
through First National), it is possible that Vital will reject the entire settlement batch if there is a
single problem within the batch. For instance, if the American Express transactions have been
authorized, but settlement has not been setup within Vital or the Bank, the entire batch will fail. One
resolution is, of course, to setup Vital and FNBO to accept American Express. A second means is to
credit all of the American Express transactions (a call to ClearCommerce is required to remove the
Soft Settle state).

The information contained in this document is CONFIDENTIAL to the business and operations of SPC, Inc. d/b/a First National
Merchant Solutions, and shall not be duplicated or disclosed in whole or in part without the prior written permission of First
20
National Merchant Solutions.
PayFuse User's Training Guide

Glossary

account administrator
The person responsible for administering merchant account activities,
including setting up merchants and managing user IDs and permissions.
Frequently, a commerce service provider acts as an account administrator.
See also commerce service provider (CSP).

acquiring bank
See merchant bank.

acquiring processor
See payment processor.

Address Verification Service (AVS)

A service used to verify that the billing street address and zip code supplied
by the customer (on the merchant’s Web site) match the data on record at the
card-issuing bank. AVS is supported by most U.S.-based payment
processors. AVS is not supported outside of the U.S. Benefits of using AVS
include enhanced fraud protection which, in turn, can protect the merchant’s
discount rate.

API
See application programming interface.

application programming interface (API)

A set of routines or definitions that are part of an operating system or
application program. An API is used by programmers when they write an
application so that the application can make requests to the operating system
or another application program.

Auth
A transaction type in which a transaction is preauthorized and
postauthorized in one step. In the U.S., Auth is typically used to process
purchases of goods or services that do not require a physical shipment. For
example, in the U.S., Auth would be used for memberships or subscriptions
that are purchased electronically and used immediately.
Contrast this term with PreAuth and with PostAuth, which are transaction
types used for purchases of hard goods (which must be shipped).
A payment processor might refer to this transaction type as
preauthorization/postauthorization.

The information contained in this document is CONFIDENTIAL to the business and operations of SPC, Inc. d/b/a First National
Merchant Solutions, and shall not be duplicated or disclosed in whole or in part without the prior written permission of First
21
National Merchant Solutions.
PayFuse User's Training Guide

authorization
A request to the payment processor (who then makes a request to the cardissuing
bank) to approve the reservation of funds in a customer’s account.
The request can involve several transaction types, including Auth, PreAuth,
PostAuth, ReAuth, and RePreAuth.

authorization reversal
See partial reversal.

authorize only
See PreAuth.

authorizer
The card-issuing bank or its assigned representative that approves or
declines transactions during authorization.
See also card-issuing bank and authorization.

AVS
See Address Verification Service.

Bank Identification Number (BIN)

A number, defined by the American Bankers Association, that identifies the
card-issuing bank. The BIN is typically the first six numbers of a Visa or
MasterCard credit card account number.

batch
A group of transactions waiting for settlement. See also settlement and
Settle.

batch ID
A unique numeric identifier assigned to a batch by the payment processor.
(Not all payment processors assign their own batch IDs.)
See also settlement ID.

BIN
See Bank Identification Number.

bulk settlement
A type of settlement in which all transactions that have a status of Bulk
Ready, that are configured to be sent to the same processor, and that are
associated with the same SysAdmin or CSP entity are sent to the processor
together.
Contrast with single-store settlement. See also settlement.

The information contained in this document is CONFIDENTIAL to the business and operations of SPC, Inc. d/b/a First National
Merchant Solutions, and shall not be duplicated or disclosed in whole or in part without the prior written permission of First
22
National Merchant Solutions.
PayFuse User's Training Guide

cancel
See Void.

card association
A fee-based, membership-driven group of financial institutions that uses
common processing and administrative facilities according to common
operating rules. Examples are Visa and MasterCard credit cards.
See also card organization.

cardholder
An individual to whom a card is issued, or who is authorized to use an issued
card.

Card Identifier (CID)

One of several types of Card Verification Methods; a 3- or 4-digit code,
typically printed on the card. The CID is submitted as part of an
authorization request.
See also Card Verification Method (CVM) and Card Verification Value 2
(CVV2).

card-issuing bank
The financial institution that issues credit cards to individuals and
businesses.
Also known as credit-card issuing bank.

card-not-present
Pertaining to a credit card transaction that does not require the cardholder to
be physically present. All Internet transactions are card-not-present
transactions.

card organization
A fee-based processing institution that uses proprietary processing and
administrative systems to facilitate card processing for its merchants and
cardholders. American Express and Discover are examples of card
organizations.

card-present
Pertaining to a credit card transaction in which the cardholder and the card
are physically present. Typically, the credit card passes through a card reader
and the cardholder signs a receipt.
Contrast with card-not-present.

The information contained in this document is CONFIDENTIAL to the business and operations of SPC, Inc. d/b/a First National
Merchant Solutions, and shall not be duplicated or disclosed in whole or in part without the prior written permission of First
23
National Merchant Solutions.
PayFuse User's Training Guide

Card Verification Method (CVM)

Any of several methods used to ensure that a credit card being used in a
purchase is in the possession of its owner. Examples of CVMs are Card
Verification Value 2 (CVV2) and Card Identifier (CID). See these terms for
more information.

Card Verification Value 2 (CVV2)

One of several types of Card Verification Methods; a 3- or 4-digit code,
typically printed in the signature panel on the back of the card. The CVV2
is submitted as part of an authorization request.
See also Card Verification Method (CVM) and Card Identifier (CID).

chargeback
The reversal of a previously Settled transaction in which the merchant bank
debits the amount of the sale from the merchant’s account because the
cardholder has disputed the charge.

Chargeback
A transaction type used to record in the database that the merchant bank has
reversed a previously settled transaction through a chargeback.

commerce service provider (CSP)

A company that provides businesses with the hosting services, the
transaction processing capability, and the software that the businesses need
to sell products over the Internet.

credit card processor

See payment processor.

Credit (independent)
A transaction type that transfers funds to the cardholder's account, rather
than from the account. An independent Credit does not relate the credit to a
previously existing order.
A payment processor might refer to this transaction type as refund or rebate.

Credit (on existing order)

A transaction type that transfers funds to the cardholder's account, rather
than from the account. This transaction type is typically used to refund a
customer’s money for an order that was previously settled.
A payment processor might refer to this transaction type as return, refund,
or rebate.

The information contained in this document is CONFIDENTIAL to the business and operations of SPC, Inc. d/b/a First National
Merchant Solutions, and shall not be duplicated or disclosed in whole or in part without the prior written permission of First
24
National Merchant Solutions.
PayFuse User's Training Guide

CSP
See commerce service provider.

customer
In e-commerce, a person who makes a purchase at an online store.

detail capture
See settlement.

digital receipt
An electronic acknowledgement of an order placed from a commerceenabled
Web site.

discount fee (or rate)

The fee a merchant pays to a merchant bank for acquiring the merchant’s
transactions. The fee is usually a small percentage of each purchase amount
and of each settlement deposit.
See also interchange fee (or rate).

draft capture
See settlement.

e-commerce
The practice of buying and selling products over the Internet.
Also known as electronic commerce.

encryption
A method used to prevent unauthorized parties from reading data that is
transmitted over a network or stored in a database.

ForceInsertAuth
A transaction type in which an approved Auth transaction is inserted into the
database. It can be used for transactions that have been approved using a
method other than the Engine, such as transactions approved by phone.

ForceInsertPreAuth
A transaction type in which an approved PreAuth transaction is inserted into
the database. It can be used for transactions that are approved using a
method other than the Engine, such as transactions approved by phone.

ForceUpdateAuth
A transaction type that forcibly approves an Auth transaction and updates its
authorization code.

The information contained in this document is CONFIDENTIAL to the business and operations of SPC, Inc. d/b/a First National
Merchant Solutions, and shall not be duplicated or disclosed in whole or in part without the prior written permission of First
25
National Merchant Solutions.
PayFuse User's Training Guide

ForceUpdatePreAuth
A transaction type that forcibly approves a PreAuth transaction and updates
its authorization code.

interchange fee (or rate)

A fee paid by the merchant bank to the issuing bank to compensate for
postsettlement financial services.
See also discount fee (or rate).

Internet service provider (ISP)

A company that provides Internet access to individuals or businesses.

Internet Virtual Terminal (IVT)

See POS.

IP address
A unique address of a device using the TCP/IP protocol stack. No two
devices have the same IP address.
IP addresses are expressed in dot notation, such as 127.0.0.1. All IP
addresses have the same format, and each number in the address must be
between 0 and 255.

ISP
See Internet service provider.

Level I data
The minimum data required to electronically process credit card
transactions. This data includes card account number, expiration date,
transaction amount, and basic information about the merchant. Level I data
is supported by any payment processor that accepts credit cards. Credit
cards are authorized and associated with normal transaction data through
settlement.

Level II data
Data that is associated with Level II purchase card transactions. In addition
to Level I data, Level II data includes a purchase order (PO) number and
sales tax amount. Level II data is required by the payment processor at the
time of settlement.

The information contained in this document is CONFIDENTIAL to the business and operations of SPC, Inc. d/b/a First National
Merchant Solutions, and shall not be duplicated or disclosed in whole or in part without the prior written permission of First
26
National Merchant Solutions.
PayFuse User's Training Guide

Level III data

Data that is associated with Level III purchase card transactions. In addition
to Level I and Level II data, Level III data includes summary and line-item
information such as product codes, descriptions, duty amounts, quantities,
and ship-to postal data.

mail order/telephone order (MO/TO)

A type of transaction in which a cardholder orders goods or services from a
merchant and neither the credit card nor the cardholder is physically present
at the time or place of the order. For example, an MO/TO might take place
by telephone, through the mail, or on the World Wide Web.

merchant
A person or company that owns one or more stores.
See also store, store administrator.

merchant bank
A financial institution that does business with merchants, enabling them to
accept credit cards. Examples of merchant banks are Chase Merchant
Services, Paymentech, and BankOne.
Also called acquiring bank.

merchant ID (MID) number

A number issued to a merchant by a merchant bank. The merchant bank uses
the MID to identify a specific merchant in credit card transactions.
Different MIDs are required for each type of business that an individual
merchant performs. For example, a different MID is required for MO/TO
(card-not-present) transactions because the merchant banks charge different
discount fees for MO/TO and card-present transactions.
See also terminal ID (TID) number.

MID
See merchant ID number.

MO/TO
See mail order/telephone order.

OLTP
See online transaction processing.

The information contained in this document is CONFIDENTIAL to the business and operations of SPC, Inc. d/b/a First National
Merchant Solutions, and shall not be duplicated or disclosed in whole or in part without the prior written permission of First
27
National Merchant Solutions.
PayFuse User's Training Guide

online transaction processing (OLTP)

The act of sending and receiving data to complete preauthorization,
postauthorization, and settlement of a transaction.
Through the use of PayFuse, online transaction
processing includes fraud checking, transmission of the data to a payment
processor, receipt of approval or rejection of the transaction from the
processor, capture (or postauthorization) of the transaction, and settlement.

open-to-buy
Pertaining to the portion of a cardholder’s available credit that can be used
immediately for purchases. An authorization transaction decreases the
cardholder’s open-to-buy balance, in effect reserving funds for the eventual
settlement.

order ID
A unique numeric identifier assigned to an order by either the storefront or
the Engine.
See also transaction ID.

partial shipment
A process in which a store ships only some of the goods in a single order
and, therefore, submits a PostAuth for less than the amount of the approved
PreAuth for the order. Sometimes a partial shipment initiates a partial
reversal.
See partial reversal for more information.

PayFuse
A software product that provides real-time transaction processing, including
sorting and packaging the transaction information so that the information
can be read by the payment processor. The Engine also can provide fraud
checking and tax and shipping calculations. It also provides a tool that
enables store administrators to manage their online store’s transactions.

payment processor
The financial institution that is typically responsible for routing and
handling authorization and settlement. The PayFuse Engine uses
payment solution software to communicate with the payment processor.
Also known as card processor or processor.

point of sale
Physical or virtual location where a transaction is initiated by the merchant.

The information contained in this document is CONFIDENTIAL to the business and operations of SPC, Inc. d/b/a First National
Merchant Solutions, and shall not be duplicated or disclosed in whole or in part without the prior written permission of First
28
National Merchant Solutions.
PayFuse User's Training Guide

POS characteristics
Characteristics of the input environment expressed as values that become
part of the transaction request packet that is sent to a payment processor.

PostAuth
A transaction type that prepares an approved PreAuth transaction for
settlement. In the U.S., this transaction type typically occurs only after the
purchased goods have been shipped.
A PostAuth is preceded by a PreAuth.
A payment processor might refer to this transaction type as ticket only or
capture.

PreAuth
A transaction type in which a cardholder’s account is verified to be in good
standing and Address Verification Service is performed (if supported). If the
verifications are approved by the authorizer, the total amount of the order is
reserved against the cardholder’s open-to-buy balance. The cardholder’s
available credit is not changed, however.
In the U.S., PreAuth is used as the first stage of processing purchases of
goods that must be physically shipped to the customer. An approved
PreAuth is followed by PostAuth.
Contrast this term with Auth.
A payment processor might refer to this transaction type as authorization or
authorize only.

processor
See payment processor.

ReAuth
A transaction type in which an Auth or a PostAuth transaction is resubmitted
for processing.

rebate
See Credit (on existing order) and Credit (independent).

refund
See Credit (on existing order) and Credit (independent).

RePreAuth
A transaction type in which a PreAuth transaction is resubmitted for
processing.

The information contained in this document is CONFIDENTIAL to the business and operations of SPC, Inc. d/b/a First National
Merchant Solutions, and shall not be duplicated or disclosed in whole or in part without the prior written permission of First
29
National Merchant Solutions.
PayFuse User's Training Guide

return
See Credit (on existing order).

reversal
See Void.

Secure Sockets Layer (SSL)

An industry-standard security protocol that provides secure transmission of
private information sent over the Internet. The protocol provides data
encryption, server authentication, message integrity, and client
authentication for TCP/IP connections.

Settle
A transaction type that begins the transfer of funds to the merchant’s
account (in the case of a sale) or from the merchant’s account (in the case of
a credit).

settlement
A process in which money is transferred between a merchant and a
cardholder. For a sale, money is transferred from a cardholder’s account to
a merchant’s account. For a credit, money is transferred from a merchant’s
account to a cardholder’s account.
See also bulk settlement and single-store settlement.

settlement ID
A unique numeric identifier assigned to a batch by the PayFuse Payment Engine.
See also batch and batch ID.

SSL
See Secure Sockets Layer.

store
An online business establishment that offers goods and services for sale
through online ordering. Sometimes called online store.

store administrator
A person responsible for managing an online store’s e-commerce activity.

The information contained in this document is CONFIDENTIAL to the business and operations of SPC, Inc. d/b/a First National
Merchant Solutions, and shall not be duplicated or disclosed in whole or in part without the prior written permission of First
30
National Merchant Solutions.
PayFuse User's Training Guide

Store Administrator Tool

A graphical user interface that enables store administrators who have the
appropriate permissions to manage configuration of Store entities, view
reports of Store activities, manage fraud, initiate point of sale transactions,
and manage settlement on the Engine.
See also store administrator and Store entity.

storefront
A Web site designed to handle electronic transactions over the Internet.

system administrator
A person who is responsible for administering Engine-level activities,
including ensuring successful communication with payment processors and
monitoring server performance.

terminal ID (TID) number

A number assigned by a payment processor to identify a specific point-ofsale
terminal.
In a retail store, one TID is typically assigned to each device used to
authorize credit card transactions. For Internet transactions, one TID is
typically assigned to each merchant Web site or business unit.
See also merchant ID (MID) number.

third-party transaction processor

An entity that acts on behalf of a card-issuing bank, merchant bank, or
payment processor during transaction processing.
See also card-issuing bank, merchant bank, and payment processor.

ticket only
See PostAuth.

TID
See terminal ID number.

transaction
Any action between a cardholder and a merchant that results in activity on
either account. One example of transaction is the process that takes place
when a cardholder makes a purchase with a credit card. Another is the
process when a merchant credits all or part of an order back to a customer.

transaction ID
A unique numeric identifier assigned to a transaction by the Engine.
See also order ID.

The information contained in this document is CONFIDENTIAL to the business and operations of SPC, Inc. d/b/a First National
Merchant Solutions, and shall not be duplicated or disclosed in whole or in part without the prior written permission of First
31
National Merchant Solutions.
PayFuse User's Training Guide

transaction processing
See online transaction processing.

Transmission Control Protocol/Internet Protocol

(TCP/IP)
A protocol for communication between computers, used as a standard for
transmitting data over networks and as the basis for standard Internet
protocols.

Void
A transaction type that cancels a transaction that has not yet settled.
A payment processor might refer to this transaction type as reversal or
cancel.

The information contained in this document is CONFIDENTIAL to the business and operations of SPC, Inc. d/b/a First National
Merchant Solutions, and shall not be duplicated or disclosed in whole or in part without the prior written permission of First
32
National Merchant Solutions.