Salesware Charge Cards

Charge Cards Reference
Version 4.2
Siriusware, Inc.
302 Camino de la Placita
Taos, NM 87571
575.751.0633
www.siriusware.com/docs
www.siriusware.com/training
google.siriusware.com
1
Copyright
Copyright 2013 Siriusware®, Incorporated. All rights reserved.
NOTICE: All information contained herein is the property of Siriusware, Incorporated. No part of this
publication (whether in hardcopy or electronic form) may be reproduced or transmitted, in any form or by
any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written
consent of Siriusware, Incorporated. The software, which includes information contained in any databases,
described in this document is furnished under a license agreement and may be used or copied only in
accordance with the terms of that agreement.
This publication and the information herein is furnished AS IS, is subject to change without notice, and
should not be construed as a commitment by Siriusware, Incorporated. Siriusware, Incorporated assumes
no responsibility or liability for any errors or inaccuracies, makes no warranty of any kind (express,
implied, or statutory) with respect to this publication, and expressly disclaims any and all warranties of
merchantability, fitness for particular purposes, and non-infringement of third party rights.
2
Charge Cards
CHARGE CARDS REFERENCE ............................................................................................................ 1
COPYRIGHT ........................................................................................................................................... 2
CHARGE CARDS ................................................................................................................................... 3
INTRODUCTION ..................................................................................................................................... 6
INSTALLING AND USING PROTOBASE CHARGE CARDS ................................................................ 6
General notes ............................................................................................................................................................................................... 6
Pre-install instructions ........................................................................................................................................................ 7
Scheduling the installation of ProtoBase with Elavon ......................................................................................................................... 7
Setting up your hardware and network prior to the ProtoBase installation date: ................................................................................. 8
On the ProtoBase PC:...................................................................................................................................................................... 8
ProtoBase installation ......................................................................................................................................................... 8
Configuring ProtoBase for Salesware ................................................................................................................................. 8
Configuring the salespoint credit card settings .................................................................................................................................... 9
Inserting the IP address of the ProtoBase server ................................................................................................................................ 11
Configure payment types ................................................................................................................................................................... 12
Disabling unique identifier protocol from PBAdmin in version 6.01 ................................................................................................ 14
To uncheck this setting, perform the following steps:................................................................................................................... 14
ProtoBase settlement and Salesware reporting ..................................................................................................................15
The basics .......................................................................................................................................................................................... 15
ProtoBase batches and subtotaling ..................................................................................................................................................... 15
Additional settlement options........................................................................................................................................................ 16
Report and selection comparisons options .................................................................................................................................... 17
Example: ....................................................................................................................................................................................... 17
ProtoBase offline transactions ...........................................................................................................................................17
Automated authorization when ProtoBase comes back online .......................................................................................................... 18
Example: ....................................................................................................................................................................................... 18
Manual authorization when ProtoBase comes back online ................................................................................................................ 19
TROUBLESHOOTING PROTOBASE................................................................................................... 19
General troubleshooting tips .................................................................................................................................................................... 19
Elavon contact information ...................................................................................................................................................................... 19
Technical support procedures ............................................................................................................................................19
Understanding basic ProtoBase transactions .......................................................................................................................................... 20
There are two processes that take place in credit card processing ................................................................................................ 20
Authorization process of credit card transactions – Flow of credit the card authorization ........................................................... 20
Authorization process flow ................................................................................................................................................21
Authorization flow ........................................................................................................................................................................ 21
Settlement process flow .....................................................................................................................................................22
Settlement/funding process of credit card batches ........................................................................................................................ 22
Rates/compliance .......................................................................................................................................................................... 23
3
ProtoBase credit card interface components and points of failure ....................................................................................................... 24
What is the reporting process In lieu of seller's not being able to print a Close Batch Report? .................................................... 25
Siriusware Inc. credit card interface system overview ........................................................................................................................... 25
Software directory structure...............................................................................................................................................25
ProtoBase TCP/IP gateway connectivity information .......................................................................................................26
ProtoBase NT service ........................................................................................................................................................26
To un-install the ProtoBase NT Service (from a command line): ................................................................................................. 27
To re-install the ProtoBase NT Service (from a command line): .................................................................................................. 27
System processes ...............................................................................................................................................................27
Understanding response messages ........................................................................................................................................................... 28
INSTALLING DIRECTNET CHARGE CARDS ..................................................................................... 28
DirectNet .INI settings............................................................................................................................................................................... 29
Example: ....................................................................................................................................................................................... 29
Layouts ....................................................................................................................................................................................................... 30
Security ....................................................................................................................................................................................................... 31
Licensing .................................................................................................................................................................................................... 31
Miscellaneous notes ................................................................................................................................................................................... 31
Example: ....................................................................................................................................................................................... 31
Important note on training mode ............................................................................................................................................................. 32
Working with DirectNet variable priced gift cards ................................................................................................................................ 32
Methods of payment ..........................................................................................................................................................32
Set up the following methods of payment in Salesware to process gift cards: .............................................................................. 32
Product setup .....................................................................................................................................................................34
Selling a Variable Priced Gift Card ...................................................................................................................................35
Procedures .......................................................................................................................................................................................... 35
INSTALLING INGENICO CHARGE CARDS ........................................................................................ 38
General notes ............................................................................................................................................................................................. 39
How Ingenico works with Salesware module .......................................................................................................................................... 39
How Ingenico works with SysManager ................................................................................................................................................... 40
How Ingenico works with Sales ................................................................................................................................................................ 40
Sales Host settings for E-Commerce module .......................................................................................................................................... 41
ww.dll .INI settings .................................................................................................................................................................................... 42
web.config settings ..................................................................................................................................................................................... 42
INSTALLING MONERIS/TENDER RETAIL/VERSAPAY CARDS ....................................................... 42
4
Setting up charge card processing in Canada ......................................................................................................................................... 43
Summary............................................................................................................................................................................43
Details ................................................................................................................................................................................43
Terminology ......................................................................................................................................................................44
What the client needs to do to install Tender Retail/Moneris: .............................................................................................................. 44
Client duties: ......................................................................................................................................................................44
From Moneris: ............................................................................................................................................................................... 44
Installation ................................................................................................................................................................................................. 44
Initial installation issues ....................................................................................................................................................44
Installation steps ................................................................................................................................................................45
Setting up Moneris Card and Chip credit card solution ........................................................................................................................ 47
Installation steps ................................................................................................................................................................47
Testing suggestions ............................................................................................................................................................52
MOTO setup ......................................................................................................................................................................52
INSTALLING PAYMENT EXPRESS ..................................................................................................... 52
ADDITIONAL INFORMATION .............................................................................................................. 52
No Luhn Check .......................................................................................................................................................................................... 52
Reporting.................................................................................................................................................................................................... 53
CardWare Transactions By Operator/Salespoint ...............................................................................................................53
Individual Card Search Report ..........................................................................................................................................53
Batch Detail Report ...........................................................................................................................................................53
Pinpads ....................................................................................................................................................................................................... 53
Setting up TenderRetail Card and Chip credit card solution (card not present) ................................................................53
Introduction ........................................................................................................................................................................................ 54
Setting up a salespoint as CNP .......................................................................................................................................................... 55
Setting up E-Commerce module as CNP ........................................................................................................................................... 57
Setting up SysManager ...................................................................................................................................................................... 58
Setting up TenderRetail Card and Chip credit card solution (card present) ......................................................................59
Installation steps................................................................................................................................................................................. 59
Setup .................................................................................................................................................................................................. 60
Example: ....................................................................................................................................................................................... 63
Setting up Moneris Card and Chip credit card solution for Kiosk .....................................................................................66
Installation steps................................................................................................................................................................................. 66
Setup .................................................................................................................................................................................................. 66
5
Introduction
The Charge Cards module in Salesware supports five systems: ProtoBase, DirectNET, Ingenico, Tender
Retail/Moneris and Payment Express. It also supports EZCharge cards, which are similar to In-House Cards items
except that the guest’s credit card is charged instead of having an amount subtracted from an in-house debit card.
This section describes how to install and configure these systems. The vast majority of Siriusware clients use
ProtoBase, so detailed configuration directions are provided for ProtoBase only; installation of the other Charge
Card systems follow the steps provided for ProtoBase, modifying where necessary (as explained in the
DirectNET, Ingenico or Tender Retail/Moneris section below). If you chose to install support for Salesware
Charge Cards module when you were installing the core Salesware modules (see Installation of core Salesware
modules), .INI setting were written into your Sales32c.INI file, depending on which radio button you
selected.
This document uses the following terminology:
1. Authorization – The process of verifying that the cardholder has sufficient credit left to pay for the
transaction. This does not actually put the money in your bank. It does allocate the money from the
person’s credit for seven days, though.
2. Settlement – The process of collecting the money from all of your authorizations.
3. Issuer – This is the bank from which the cardholder receives his card.
4. Acquirer – A bank that has a business relationship with a merchant and receives all credit card
transactions from that merchant; the acquirer gets the money and deposits it into the merchant’s bank.
5. Processor – A company that handles credit card transactions and batches for acquirers (e.g., PaymentTech,
Moneris, 5th/3rd, Vital, etc.).
6. Integration – Siriusware® Inc. codes to a single spec and the product with which Salesware integrates
translates the single format that we send to the format required for any given number of processors (e.g.,
Tender Retail Merchant Connect [a.k.a., CreditCheq], Elavon ProtoBase, etc.).
Installing and using ProtoBase charge cards
General notes
Follow this list of “to-do’s” to begin your implementation of ProtoBase. More specific information is given in
Pre-install instructions.
1. Contact your processing bank and tell them you’re switching to “high-speed ProtoBase” or let the new
processing bank you choose know that you’ll be using high-speed ProtoBase – they may have to create
new merchant IDs for this. You’ll need up to three merchant IDs – one for Retail sales, one for F&B and
one for E-Commerce sales (MOTO).
2. Once you have the merchant IDs, complete the MVP form twice – once for each merchant ID – and also
complete the other two attached documents.
3. Fax all the completed paperwork to Elavon (ProtoBase’s parent company), 727-431-4411.
4. It takes Elavon about ten - twelve business days to build and test your new merchant files.
5. Elavon contacts you to schedule the remote implementation. It takes about two hours and happens over the
phone and with VNC.
6. Elavon bills you for their products after the implementation has been completed.
6
Please observe the following when installing ProtoBase:
1. Always change the default administrative log-in/pw (don’t use pbadmin/pbadmin).
• pbadm32 usually runs on the ProtoBase Server, but you don’t want everyone in the organization
running it from there. Use RealVu instead, which runs remotely from other Computers but provides
much of the same information.
• What are the typical reasons why totals don’t match in Salesware and pbadm32 (clients should check
this when they close out each day)?
• Someone added a transaction in pbadm32
• Salespoint times out – transaction went through but Salespoint thinks it didn’t, so CC is used
again. Change the timeout value with the ProtobaseTimeout .INI setting.
2. Any network using ProtoBase is protected by a firewall.
3. The key technology behind ProtoBase is the “soft-trans module,” which interfaces between client
networks and the various credit card processors.
4. It is important that your merchant file is correct. The primary merchant types are:
• Retail
• Food Service (allows tipping)
• MOTO – Mail Order Telephone Order (E-Commerce module)
Note: If your merchant type is wrong, you may be paying too much for each transaction.
5. The cost of each transaction ultimately depends on how much risk the credit card companies are taking.
The more information collected about the credit card and user, the less risk to the credit card company, so
the less they charge for a transaction. If clients have risky practices, they are downgraded, so they pay
more per transaction. You definitely need to do address verification in E-Commerce module.
6. When you void a transaction, it prevents it from being settled (versus a refund).
Pre-install instructions
Scheduling the installation of ProtoBase with Elavon
1. It is your responsibility to ensure ProtoBase is installed at your site prior to the Salesware implementation.
2. You should have already received your ProtoBase forms from your Siriusware salesperson and been cc’d
on an e-mail to Elavon initiating the order. If not, please contact your salesperson.
3. Submit your ProtoBase forms as soon as possible. Our experience is that it can take up to four weeks after
submission before Elavon schedules an installation. Please follow the ProtoBase MVP instructions
carefully or delays occur.
4. A specific reminder: if changing from dialup to high speed, you must call your processing bank.
5. If your Siriusware Inc. installation is closer than four weeks away, we advise you to pay Elavon to
expedite ($100/MID for 3-5 day service; $300/MID for 48 hour service). You must do this when you
submit your forms.
7
6. Once your forms are processed, Elavon schedules installation of and training for the ProtoBase system
with you. Please schedule this prior to the Salesware implementation. Elavon needs to know:
• Date and time of install. Remind them to schedule training, also (about 1.5 hours).
• Name of onsite contact and phone number.
• Name and address of person who receives the modem and welcome packet.
• IP address, username and password for your ProtoBase PC. This is explained in Elavon’s welcome
packet.
7. Elavon tells you the ticket number for the installation; please take note of it for future reference.
8. For the status of an order, the best contact is [email protected] When you receive the notification
that your order has been received by Elavon, they ask you to use this e-mail for status reports.
Setting up your hardware and network prior to the ProtoBase installation date:
On the ProtoBase PC:
1.
2.
3.
4.
5.
6.
Configure the PC with the static IP address that you provided to Elavon.
Ensure the PC connects with the Internet.
Install the latest Windows SP and critical updates.
Install WinZip.
Install PCAnywhere, Terminal Services or Remote Desktop Connection.
If using a firewall on your network, be sure port 443 is open to allow outgoing traffic. Port 443 does not
need to be open to allow ingoing traffic.
See the Salesware System Architecture and Specifications document for a diagram showing how the ProtoBase
server integrates with the rest of the Salesware installation.
ProtoBase installation
ProtoBase installation is normally performed by ProtoBase technicians. This section provides a brief overview of
the installation process and components.
ProtoBase is installed on a dedicated computer with a static IP address. It is usually installed at the root of the C:
drive:
Configuring ProtoBase for Salesware
Once ProtoBase is installed, you need to configure your salespoints to “talk” to ProtoBase. This is accomplished
by:
1. Inserting the appropriate settings from ProtoBase into each salespoint.
2. Inserting the IP address of the ProtoBase computer into the local Sales32c.INI files.
3. Creating payment types for credit cards.
8
Configuring the salespoint credit card settings
You set the terminal ID for ProtoBase in either SysManager or Sales. In SysManager, go to Activities > System
Lists > Salespoints and edit each salespoint. From the Salespoint Configuration dialog, click the Credit Cards
tab.
In Sales, go to Tools > Credit Cards > General Setup. The Credit Cards Setup dialog is displayed.
9
Enter the appropriate code (typically three or four characters) in the Credit Card Terminal field (in SysManager,
this field is called Terminal No). The value in Credit Card Terminal cannot be more than four characters and
must be alphanumeric. Be sure to also enter the appropriate Merchant ID # for each salespoint (this sole purpose
for this field is to print the Merchant ID # number on a Credit Card Receipt layout with that field specified). The
client “makes up” the Credit Card Terminal code, which can be any combination of three or four alphanumeric
characters. The Credit Card Terminal (i.e., RET for Retail) is set up at the time of installation. The terminal is
tied to an industry for the salespoint – Retail (usually RET), restaurant/bar/tipping (usually REST) and card not
present (usually MOTO).
Set an “assumed approval” amount for each salespoint. If ProtoBase is offline for some reason, this is the amount
that the system assumes is approved. See ProtoBase offline transactions for a complete description of how
Salesware handles transactions when ProtoBase goes offline and how Salesware recovers after ProtoBase comes
back online.
If a card is being charged for an amount that is over the “assumed approval” amount and ProtoBase is offline, the
operator is prompted to call to get a voice authorization. Once the operator receives the voice authorization, she
needs to type it into the prompt in Sales that is waiting for the voice authorization entry.
When setting this limit keep in mind the amount you are willing to lose if a card that was assumed to be good was
declined once it was forwarded for a real authorization. Also, please ensure that your operators have access to the
phone numbers and information they need for voice authorizations.
10
Inserting the IP address of the ProtoBase server
Enter the IP address of the ProtoBase computer in the Sales32c.INI file on all salespoints. This must be done
in the local Sales32c.INI file – not within the global .INI in SysManager > Preferences > Miscellaneous
> Global INI. Browse to the Sales32c.INI file. The default location of this file is
C:\ProgramData\Siriusware\Sales\Sales32c.INI, but you can also get to it from Windows Start
> All Programs > Siriusware > Settings. In the [Server] section there is an entry for Protobase=. Enter
the IP address of the ProtoBase server followed by the port (default is 4209). If the IP address for the ProtoBase
server is set in the SiteDefaults.INI file, this setting is automatically assigned when you install Sales on a
salespoint. See Installing Pool Service for more information. Make sure that the CreditCardSales setting is
set to TRUE. Without this set to TRUE, cards are not processed for authorizations when used for payment. This
setting can also be automatically assigned when you install Sales. See Installing Sales for more information.
11
Configure payment types
You use SysManager > Activities > Financial Lists > Payment Types to configure payment types for each type
of card you accept. With the Sales Point Type tab you can also limit what types of payments are available per
salespoint type if necessary (This is one of the few remaining uses for the Salesware 3.x salespoint type
functionality accessible from SysManager > Preferences > Sales Point Types – there is no other way to
implement this functionality.)
The Process Via is set to ProtoBase. The Card Type is set according to the following table:
Card Type field abbreviation
Card type
AMEX
American Express
CTBL
Carte Blanche
DINR
Diners Club
DISC
Discover
ENRT
En Route
JCB
Japan Credit Bureau
MACH
Master Charge
VISA
Visa
PRIV
Not implemented yet
DBTW
Debitware (In-House Cards module) – See the document Salesware InHouse Cards
Please use the BIN ranges (Acct Range) described in the following table. Most clients probably don’t need/want
the JCB or BankCard entries. The table has the card, BIN ranges and the acceptable lengths of the card number.
Acceptable lengths are provided for informational purposes only. They are handled automatically by Salesware;
you do not need to configure them manually in Salesware module.
Card
BIN range(s)
Acceptable lengths of the card number
American Express
340000-349999 370000379999
15
Visa
400000-499999
13 or 16
MasterCard
510000-559999
16
12
MasterCard (due to
the new
MasterCard/Diners
Club alliance in North
America)
360000-369999
14
Discover Card
601100-601199 650000-650999 16
Diners Club
300000-305999 380000389999
14
Japan Credit Bureau
300000-399999
16
Japan Credit Bureau
180000-180099 213100-213199 15
BankCard
560000-561999
16
You can also enter a Payment Type Group for each payment type configured. This is used on reports to subtotal
payment types configured with the same group number together. For example, Visa, MasterCard, Discover Card
and American Express are all in group 3. The Cash Drawer Report shows the total for each payment type and it
totals all payment types included in group 3 together so that you can see your total for these credit cards.
Sort By impacts how the operator sees the payment types sorted on the Finalize dialog in Sales (first by the
Group number, and then by the Sort By number). Even though credit cards are the most common form of
payment next to cash, you do not need to sort these payment types to the top of the list. When using a credit card
for payment in Sales, there is no need to select the payment type or even click the Finalize button. Simply swipe
the card and the system selects the appropriate payment type based on the card number swiped.
13
Disabling unique identifier protocol from PBAdmin in version 6.01
When ProtoBase version 6.01 is installed, it has a new security protocol (set up by default) that causes ProtoBase
to swap out card numbers for a unique identifier. Salesware module requires this to be unchecked. If not
corrected, this error message appears as, “Unable to set up payment” in Sales because it doesn’t get a card
number.
To uncheck this setting, perform the following steps:
1. In PBAdmin, select Setup > Location Information.
2. For each of the Locations in the dropdown on the General Setup tab:
3. Go to the Settings tab and ensure that the Unique ID in Lieu of Accnt # in API check box is unchecked.
14
4. Exit from the dialog, click OK to the warning, and then go back and uncheck this setting for another
Location.
ProtoBase settlement and Salesware reporting
The basics
Credit card payments made at a Siriusware salespoint are passed to ProtoBase for authorization from a credit card
processor. Processors include companies such as Payment Tech, Vital, Moneris (Canadian E-Commerce only),
etc.
The settlement (deposit) of credit card transactions happens within ProtoBase via the PBAdmin or RealVu
applications or within ProtoBase’s web product, WebVu. Settlement is a manual process, but is very easy. It
requires the operator to enter the Deposit Criteria, which is typically just the current date and click a Deposit
Selected or Deposit All button.
ProtoBase batches and subtotaling
ProtoBase assigns the same batch number to all transactions deposited at the same time. It is possible to get a
breakdown within the single large batch based on either Siriusware salespoint name or Siriusware operator name.
15
By default, Siriusware Inc. provides the salespoint name to ProtoBase. The Siriusware salespoint name is
inserted into the ProtoBase cashier ID field. Thus, by default, within a single ProtoBase batch the individual
transactions and subtotals per Siriusware salespoint may be viewed.
Instead of using the Siriusware salespoint name for grouping transactions within a ProtoBase batch (default
functionality), the Siriusware operator name may be sent into ProtoBase as the cashier ID. The individual credit
card transactions and subtotals would then be viewed by Siriusware operator name instead of Siriusware
salespoint name within ProtoBase batches.
To specify sending in the Siriusware operator name instead of the salespoint name, a Sales .INI setting must be
in place. It is recommended that this setting be inserted in the <defaults> section of the global .INI
(SysManager > Preferences > Miscellaneous > Global INI tab) so that all salespoints follow this setting. (The
same setting needs to be removed from the local .INI file or from the global group sections in order to make the
global default setting take effect.) The global .INI is discussed in detail in the Salesware .INI Settings
Reference document.
[Preferences]
SettleByOperator=TRUE
Sending in the Siriusware salespoint name or Siriusware operator name is a decision that must be made by you –
specifically, by your accounting department, as this is the department that typically shoulders the responsibility
for credit card activity and reconciliation. If a client typically reports by operator, then sending in the operator
name to ProtoBase as the cashier ID might make sense. If a client typically reports by salespoint or salespoint
group, then sending in the salespoint name to ProtoBase as the cashier ID might make more sense. Again – this
decision must be made by the client.
Note: In the past, Cardware (former name of Charge Cards module) batches were always reported by salespoint,
so if you have used Cardware in the past, there may be more of a comfort level with reporting by salespoint name
rather than operator name – thus the reason for the default setting of using salespoint name as the ProtoBase
cashier ID.
Additional settlement options
Credit Card transactions in ProtoBase may be settled by Transaction Date or by Business Date:
1. The Transaction Date in ProtoBase is the date that the card was authorized.
2. The Business Date in ProtoBase corresponds to the “sale date” in Sales. Sale date may be altered via the
set carryover functionality in Siriusware software.
Another option to use in determining what transactions to settle is terminal ID, which is set per salespoint in the
Sales > Tools > Credit Cards > General Setup menu. One possibility is to give all salespoints within a given
business area the same terminal ID (for example, tickets could be TIX; ski school could be SS, etc.). You can
then settle by business date (sale date) and terminal ID, which would allow you to settle all transactions for the
venue at one time.
16
Report and selection comparisons options
Various Siriusware reports can be run via ReportManager to compare with the credit card transaction information
from ProtoBase.
Example:
If using the ProtoBase terminal ID to represent an operational venue, Siriusware reports such as the Daily
Summary Report can be run via the salespoint group selection to compare to the settlement information.
PBAdmin Selection
Siriusware Designation
Card Type
Payment Type
Business Date
Sale Date
Transaction Date
Date Card was Authorized
Terminal
Credit Card Terminal (in Tools > Credit Cards >
General Setup)
Cashier ID
Salespoint Name or Operator
ProtoBase offline transactions
This section describes how Salesware module handles the situation when ProtoBase goes offline and when it
comes back online.
17
When ProtoBase goes offline, you cannot receive payment. You cannot receive payment without authorization,
but authorizations do occur once ProtoBase is online again. This process can be automated or manual. The
following sections describe the differences.
Automated authorization when ProtoBase comes back online
You can use the ForwardAuthOnReconnect .INI setting to automatically cause the salespoint to seek
authorization of all stored credit card transactions upon reconnection with ProtoBase.
[Preferences]
ForwardAuthOnReconnect=TRUE
This setting causes the forwarding of all offline ProtoBase credit card transactions when ProtoBase comes back
online. This setting causes the operator to be prompted when ProtoBase is back online, allowing them to select
whether or not to forward the offline transactions at the end of the finalize process. The default setting is FALSE.
Example:
If you're offline and collect ten credit card transactions, and then ProtoBase comes back online, all ten
transactions automatically get sent for authorization if the operator clicks OK at the prompt. The operator is given
the choice in order to accommodate the situation where there is a long line of customers and the operator probably
does not want to stop selling while the outstanding transactions process.
Warning: Each transaction can take up to two minutes to process, so the authorization process could take quite a
bit of time depending on the amount of stored transactions.
If the operator clicks OK at the prompt, authorizations are sent and come back – good or declined – and credit
card receipts come spitting out of the receipt printer.
Note: Credit card receipts don’t automatically print when using ProtoBase. After the transactions process, the
Processed Off-line Transactions dialog comes up. From there you can choose to print the receipts. Cardware,
Siriusware’s earlier credit cards product, does automatically print the receipts, but any other credit card module
behaves this way.
When ProtoBase is offline and an approval is assumed (the amount depends on the amount of the “assumed
approval” set for each salespoint), a regular credit card receipt prints (see previous note), but without an approval
code (look for AP: on the credit card receipt and you see that it does not contain a real approval code). When
ProtoBase is back online, these “assumed approval” sales are authorized and a new credit card receipt prints with
the real authorization number (there is an entry next to AP: on the receipt) or the word Decline is printed on the
receipt if the transaction was not authorized.
18
Your operators might think that something “crazy” is happening because they said OK to a prompt to forward
offline credit card sales and suddenly the receipt printer started printing (see previous note) – but this is expected
functionality. The operator simply needs to match up the credit card receipts with real approvals with those
receipts that contain no approval, but have the guest signature.
Manual authorization when ProtoBase comes back online
If the operator clicks NO to the message described in the previous section or if you do not want the authorizations
to go out automatically, you can perform them manually. This can be done at the salespoint through the Tools >
Credit Cards > Process Off-line button. When that button is pressed, the transactions are sent out for
authorization.
You do not see offline transactions that have not been processed in PBAdmin − but they are stored in the local
cc_trans table.
Troubleshooting ProtoBase
This appendix presents materials that Siriusware Inc. has obtained from Elavon, makers of ProtoBase. They are
useful for troubleshooting issues you may be having with ProtoBase.
General troubleshooting tips
The following are general notes about ProtoBase:
•
•
•
•
•
After a “hard shutdown” you use a batch file to delete startup files. Contact Siriusware Technical Support
for more information about this script.
What are the typical reasons why totals don’t match in Salesware and pbadm32 (you should check this
when you close out each day)?
Someone added a transaction in pbadm32.
Salespoint timed out – Transaction went through but the salespoint thinks it didn’t, so credit card is used
again. Change the timeout value set with the ProtobaseTimeout .INI setting.
The best way to troubleshoot a ProtoBase server that is not working is to look in Task Manager. If there
is a problem with the server, you see lots of processes stacking up.
Elavon contact information
Technical support procedures
Elavon technical assistance is available to you 24 hours a day, 7 days a week for all authorization related
problems. If you experience technical issues, contact the Elavon Client Services department at: 1-877-732-1799.
Please provide the following information to the representative to help expedite the resolution time:
19
1.
2.
3.
4.
Your name and your contact phone number
Name and location of the site experiencing problems
If this problem is widespread or localized
The nature of the problem
• Authorization
• Settlement
• Both authorization and settlement
• Functionality
5. How long the site has been experiencing the problem
6. The frequency of the problem (how often it is happening)
7. Any steps that have been taken to correct the problem
Please let the representative know of any issues or problems, such as internal network outages or POS problems
that may affect the credit card processing.
Please e-mail any files or information you have gathered from the site to the ProtoBase Client Services mailbox:
[email protected]
Note: When sending files to the Client Services mailbox, it is suggested that you follow up with your
representative to let them know you have sent data.
Understanding basic ProtoBase transactions
There are two processes that take place in credit card processing
1. Authorization
• Verifies that the card is valid
• Verifies that the customer has enough credit
• Provides the merchant with good-faith that the transaction is funded if settlement is completed
• Puts a hold on the cardholders open-to-buy for the amount of the transaction
2. Settlement
• Begins the funding process for the merchant
• If settlement is never initiated, the merchant does not get funded and the hold on the open-to-buy goes
away within 14-30 days
• Transactions are assessed a fee for processing services
Authorization process of credit card transactions – Flow of credit the card authorization
1. Salespoint
2. Third-party-processor
• Host
• Network
• Switch
• Sometimes thought of as the bank
20
3. Card Association
• Visa and MasterCard - Separate entities, set rules and regulations for the processing of credit cards.
These rules apply to the consumer, the merchant and the issuing banks.
• Made up of member banks
4. Issuing Bank
• Are members of card associations
• Issue credit cards to consumers with the card association logo/brand
Authorization process flow
Authorization flow
1. Card is swiped at the salespoint.
2. Transaction is transmitted to third-party processor.
3. Third-party processor looks at the BIN number – Bank Identification Number (first six digits of card) that
identifies the card association and issuing bank – and forwards the transaction to the appropriate card
association or company.
4. Card association looks at the BIN number further to determine who the issuer of the card is, and then
forwards it to that issuer.
5. The issuer receives the transaction and looks up that card in their database. If the card account has enough
funds and is authorized, the issuer puts a hold on their open-to-buy.
6. The issuer responds to the card association with either an authorization number or a decline message.
7. The card association forwards the response to the third-party processor.
8. The third-party processor forwards the response back to ProtoBase /salespoint.
9. ProtoBase /salespoint puts that transaction in a batch.
21
This process happens 100’s of times throughout the day. The batch then needs to be deposited so the merchant
can get funded for their goods and/or services.
In addition, there are two capture methods:
1. Terminal capture:
• Transactions stored in the salespoint or ProtoBase Server at the merchant’s location
• Costs the merchant less money due to communication cost, does not have to dial out for voids or
returns.
2. Host capture
• Transactions are stored at the third-party processor
• Cost more for the merchants because the TPP is managing their transactions
• Every must dial out to update the host
Settlement process flow
Settlement/funding process of credit card batches
1. Salespoint/ProtoBase
• Deposits the credit card batch to the third-party processor
2. Third-party processor
• Collects batches from all of their merchants and passes them to their back-end early in the morning
around 2 AM
3. Backend processor acquirer
• Sorts through all of the batches and creates an offload record containing transactions for all the
merchants sorted by card type
• Performs pre-qualification on the transactions to determine the rates associated with the transactions
• Funds the merchant based on the transactions pre-qualification
• Transmits the offload to the card association
22
4. Card association/interchange
• Sorts through the offload record and creates a batch of transactions for each issuing bank
• Performs interchange where it scrutinizes the transactions for compliance data looking for items such
as card-swipe, item detail, tax amount, etc.
• Transmits their batches to the issuing banks
5. Issuing Bank
• Makes credits and debits to card holders account
• Transmits electronic funds through ACH to card association minus interchange fee’s
6. Card association funds the acquiring bank minus the interchange fee’s
• Acquiring bank may bill the difference in interchange fee’s to merchant
Rates/compliance
Discount rate = Best rate a merchant can qualify for. This rate is based on:
1. Industry
• Level of risk involved in taking that transaction
• Retail module transactions contain card swipe data
• Signature is verified
• Card is present – Face-to-face transaction
2. Anticipated volume of transactions
• The more transactions the merchant processes the better rate they can expect to get assuming their
transactions are compliant
3. Downgrade – When the transaction does not meet the qualifications for compliance for that industry type.
Information such as card swipe and transaction detail is missing from the transaction. Batches must be
settled in a timely manner.
The overall authorization and settlement process is summarized in the following diagram:
23
ProtoBase credit card interface components and points of failure
The following diagram presents the entire ProtoBase interface. It is used to determine points of failure.
24
Front End From Interfaces (PMS / POS)
PbAdmin
PMS
Work
Station
PMS
Work
Station
POS
Work
Station
Siriusware PMS
Food /Bev POS
Retail POS
Internal
Client
Network
LAN
Routers
Switches
Hubs
Firewalls
Ethernet
POS
Work
Station
TCP/IP
Gateway
POLLING DIR
C:\pbase\
polling
~ETC\
HOSTS
SERVICES
PBADSET
PBFE
PBADMIN.INI
PBFE.INI
DB\PBADMAIN
PBADUSER
PBADLOCA
DBHIST\
PBAD[MMYY]
API\SETTLE\
PB[MKEY].IN
PBS[MKEY].IN
BATCH\SETTLE\
PB[MKEY].DAT
PBPUT##.DAT
Back End to Third Party Processors
MODEM
ProtoBase
SofTrans
PB
PBDIRECT
PBCOM
PBIPCOM
PBIPX25
PBDEV.DAT
PBTERM.DAT
PBPROC.DAT
PBSET##.DAT
PBMERC.DAT
Java Client
VPN
Software
VPN
Hardware
Device
PBBATCH.DAT
YYMMDDHH.H00
YYMMDDHH.B00
Internal
Client
Network
LAN
Routers
Switches
Hubs
Firewalls
Ethernet
Network
Carrier
Sprint
MCI
ATT
SBC
BrightHouse
Verizon
Internet
SDC Network
Edge
VPN
Concentrator
XTSS
Servers
SDC Network
Core
Third Party
Processors
Vital
Paymentech
First Horizon
First Data
Amex
Moneris
Global Pmnts
Gift Card Prc
SVS
Givex
ValueLink
Card
Associations
VISA / MC
Private Issue
Discover
Amex JCB
Diners Club
Carte Blance
Issuing Bank
Chase
CitiBank
BankOne
Bank of Am.
Capital One
ADNTSERV
Listening Port
REALVU
Target IP / Port
What is the reporting process In lieu of seller's not being able to print a Close Batch Report?
Using ProtoBase, closing the batch at the salespoint is optional. The station’s CC transactions are forwarded to
ProtoBase, regardless whether the batch is closed or not at the salespoint.
However, “closing the batch” is something a misnomer. No batch is closed by hitting a button. The only reason
to “close the batch” with ProtoBase is to get a list of the CC transactions for the logged in operator.
Note: If the previous day’s transactions have not been settled, they show on this list as well as the current day’s
transactions. This is a very common technical support call from those who use the Close Out button in Sales >
Tools and ProtoBase. The client calls and says the list doesn't agree with what the operator did today. The query
that runs to furnish the list is based on the currently open batch in ProtoBase.
If you are interested in retrieving a daily summary of a station’s CC activity, going to Sales > Tools > Credit
Cards > Close Batch gives you a brief printable report. Alternatively, you could run the Batch Detail Report in
ReportManager and get the same information, but it also includes card numbers and other sensitive CC
information.
Siriusware Inc. credit card interface system overview
ProtoBase utilizes the interfaces described in this section.
Software directory structure
•
•
ProtoBase
PbAdmin
c:\pbase\
c:\pbase\
25
•
•
•
•
•
•
•
•
•
•
PbAdmin Main Txn Database
PbAdmin History Database
PbAdmin Transaction Log
PbAdmin Settlement Log
PbAdmin Administrator Log
Elavon Merchant File
TCP/IP Gateway
TCP/IP Polling Directory
ProtoBase eXpress Client
Sun Microsystems Java Runtime
c:\pbase\db\
c:\pbase\dbhist\
c:\pbase\db\pbadmin.trn
c:\pbase\db\pbadmin.stl
c:\pbase\db\pbadmin.log
c:\pbase\pbmerc.dat
c:\pbase\
c:\pbase\polling\
c:\xtcp\
c:\program files\java\
Caution: The c:\pbase\db\ directory contains the main transaction database and may include live
transactions that have not been deposited yet. Always exercise extreme caution when in this directory. Never
delete any files without first consulting Elavon Technical Support.
ProtoBase TCP/IP gateway connectivity information
The ProtoBase TCP/IP gateway accepts connections on port 4209 of the IP address of the network interface.
The following system files may or may not be used with the TCP/IP gateway:
Directory/file
File entry
c:\windows\system32\drivers\etc\hosts
[interface ip]
c:\windows\system32\drivers\etc\services tcpGatePort1
tcpGateHost1
4209/tcp
ProtoBase NT service
The ProtoBase NT service automatically starts and stops the ProtoBase application’s processes upon system
startup and shutdown. The ProtoBase NT service can be manually stopped and started by performing the
following:
1.
2.
3.
4.
5.
Click START, and then click RUN. The RUN dialog appears.
On the RUN dialog, type services.msc, and then press Enter.
The Windows Services Applet appears.
Scroll down the list of system services to the ProtoBase NT Service.
Right-click on the ProtoBase NT Service and choose either Start or Stop
The ProtoBase NT service controls the ProtoBase application from the PBNTSRVC.INI file located in the
c:\pbase\ directory. The pbntsrvc.INI file is a text file and should contain the following entries:
;
26
;
c:\pbase\pbdirect.exe c:\pbase –q
c:\pbase\pbtsrv.exe ipaddress:4209 120 c:\pbase\polling
STOP c:\pbase\pbgatkil.exe 4209
Once this file has been modified, it must be re-installed. It is always a good idea to uninstall the file before
attempting to re-install it.
To un-install the ProtoBase NT Service (from a command line):
C:\pbase>pbntsrvc –remove
To re-install the ProtoBase NT Service (from a command line):
C:\pbase>pbntsrvc -install
The process must be started using the instructions above.
System processes
To check the status of the ProtoBase and TCP/IP gateway applications, you can view the processes running on the
system using the Task Manager applet. To open the Task Manager applet, right click on your task bar and select
the Task Manager option. Once Task Manager is running, click the Processes tab. The following processes is
started:
•
•
•
•
•
•
•
•
Pbdirect.exe
Pbntsrvc.exe
Pbtsrv.exe
Pbcom.exe
Pbipcom.exe
Pbipx25.exe
Xtcpservice.exe
Adntserv.exe
(ProtoBase)
(ProtoBase service controller)
(TCP/IP gateway)
(if ProtoBase is in DIAL mode)
(if ProtoBase is in IP high speed mode)
(if ProtoBase is in Frame/X.25 high speed mode)
(if ProtoBase eXpress Service is being used)
(if RealVu is being used)
Note: For pbcom.exe, pbipcom.exe and pbipx25.exe there may be multiple instances of these processes
depending on how many devices are configured on the system.
27
Understanding response messages
The lists in the following diagram are designed to help you understand where a response message may be coming
from. The lists do not contain all response messages that can be passed back; however, they are the more common
messages.
For a complete list of messages see ProtoBase Error Messages Addendum. Also see ProtoBase online help.
Installing DirectNet charge cards
The basic process for installing DirectNet charge cards is similar to installing ProtoBase, in terms of the basic
configuration steps that are performed in Salesware module. See Configuring ProtoBase for Salesware for the
salespoint credit card settings and payment types. In addition, the following sections call out the DirectNetspecific information of which you should be aware.
28
DirectNet .INI settings
For more information on these settings, see the Salesware .INI Settings Reference document.
Setting
.INI file
Section
Description
CheckAvailableFunds
Sales32c.INI Preferences
To enable balance inquiry for
DirectNet private label cards to
ensure sufficient funds prior to
finalizing the sale. Must be set to
TRUE.
CreditCardSales
Sales32c.INI Server
See the Salesware .INI Settings
Reference.
DirectNet
Sales32c.INI Server
The IP address and port of the
DirectNet server. Port is 3200.
Example:
DirectNet =
10.1.11.17:3200
DirectNetGiftCardTotals Sales32c.INI Preferences
Used to include the DirectNet gift
card amounts in the “other”
category for batch settlement.
Note: A DirectNet gift card is
specified by selecting PRIV as
the card type.
DirectNetValidate
Sales32c.INI Preferences
Specifies whether or not to use
DirectNet to validate passes (if
the pass number qualifies as a
DirectNet number). Default is
FALSE.
RangeX
Sales32c.INI DirectNet
Any card swiped on the
Validation dialog that falls into
these ranges is treated as a
DirectNet card. These ranges
must be fifteen digits in length.
Any number of ranges may be
set, but must be set in order −
e.g., Range1, Range2, Range3,
etc.
29
Note: [Preferences]
DirectNetValidate=TRUE
must be set.
FrontCard=TRUE
Sales32c.INI DirectNetLi
nk
If FALSE, creates a non-front
card account (allows DirectNet
account creation without
associating a credit card with it).
IP
Sales32c.INI DirectNetLi
nk
IP address of the DirectNet nontransactional API server. If IP
setting is present, a file called
DN_Link.dbf is created and
holds information about
DirectNet accounts that need to
be created through the DirectNet
non-transactional API. This
process keys off a field in a
template (t_newdnact) (which
can be filled in SysManager) if
the swipe_no field has been
filled in.
Password
Sales32c.INI DirectNetLi
nk
Sales32c.INI DirectNetLi
nk
Password that accesses DirectNet
StartupCCEZ
Sales32c.INI Server
See the Salesware .INI Settings
Reference
Timeout
Sales32c.INI DirectNetLi
nk
Sales32c.INI DirectNetLi
nk
Timeout in call to DirectNet
Port
UserName
Port for DirectNet nontransactional API
Log-in name that accesses
DirectNet
Layouts
The table below describes the fields available to print for layouts.
Table name
Description
ccauth.dbf,
operators.dbf,
sales_pt.dbf
Tables that are available for CC receipts. In ccauth.dbf there is
a field called prtmsg that is used.
30
Security
The following security setting is used with DirectNet. See the Salesware User and Ticketing Guide for Beginning
Users for a detailed description of security settings and security roles in Salesware module.
SysManager - Menu/Preferences - DirectNet Interface = Allows the operator access to DirectNet interface
setup info.
Licensing
SysManager > Preferences > Sales Point Licenses > CC column = The number of salespoints licensed to use
DirectNet
Miscellaneous notes
1. After installation, it is necessary to go to Sales > Tools > Diagnostics > Reset Max. Keys before trying a
credit card transaction. If you don’t do this, Sales gives a message that DirectNet is offline.
2. If you use repeat terminal IDs under the same merchant #, you are not able to settle batches (but repeat
terminal IDs under different merchant #s are OK).
Example:
term ID=0102, store ID=0001, merch ID=000021001401
term ID=0102, store ID=0001, merch ID=000021001402
3. Use of Sales32c.INI:
[Preferences]
CheckAvailableFunds=TRUE
DirectNetGiftcardTotals=TRUE
[Server]
CreditCardSales=TRUE
StartupCCEZ=TRUE
DirectNet=x.x.x.x:3200
[TRAINING]
CreditCardSales=FALSE
StartupCCEZ=FALSE
Directnet=0.0.0.0:3200
31
4. You need to close the batch from within Sales (like CreditCheq, but not like ProtoBase, which uses
PBAdmin). Do this via Sales > Tools > Credit Cards > Close Batch.
5. DirectNet private label cards work via the Priv payment type.
6. Gift card balances are available without a swipe via (see the Salesware .INI Settings Reference):
[Interface]
MainButtonX=GCB
7. Batches must be closed daily/per operator from each salespoint – otherwise, batches span multiple
operators and eventually, if they sit long enough (greater than 24 hours), the rate/fee increases.
8. You must reset MaxKeys on an existing salespoint – resets the batch # field before use.
Important note on training mode
If you do not specify otherwise, the live mode server settings for DirectNet flow into training. If you finalize a
credit card sale in training, it charges the account and it increments the batch number, which causes problems. As
a precaution, always add Directnet=0.0.0.0:3200 to the training section of Sales32c.INI.
Working with DirectNet variable priced gift cards
The following instructions outline the procedure for adding money to a gift card.
Methods of payment
When a Gift Card is sold at a Point-of-Sale (POS) the seller selects three forms of payment to process the Gift
Card. The payment type GIFT CARD places money on the Gift Card via DirectNet. The payment type
GCACTIVATE was created for accounting purposes so reports balance. The seller selects the last payment type
and is the method in which the guest is paying for the Gift Card (i.e., Cash, Credit, Check, etc.).
Set up the following methods of payment in Salesware to process gift cards:
1. GIFT CARD (modify existing payment type to settings below)
• Description: GIFT CARD
• Payment Type Group: 10
• Sort by: 2
• Process via: PosWare DirectNet
• Card Type: PRIV
• Acct Range: 601396 to 601397
32
2. GCACTIVATE
• Description: GCACTIVATE
• Payment Type Group: 10
• Sort by: 1
• Process via: Regular
33
Product setup
1. Create a, “Variable Gift Card” item and set Validation to None.
34
2. Select Direct Pricing
Note: There are no return gift card products. You can expire the existing gift card return products. (See
Returning a Gift Card.)
3. Continue to use the Variable Gift Card print product for printing gift cards GCVAR.
Selling a Variable Priced Gift Card
Procedures
1. Seller chooses Variable Priced Gift Card product.
2. Enter in the amount of dollars to put on the gift card on the New Line Item Price dialog box.
3. Select Set Price.
35
4. Click on the Message button.
5. Swipe the card to record the gift card number.
Note: In some cases this pops the manual entry for the gift card payment type. If the information is
correct, select OK, and then choose the GCACTIVATE payment.
6. If the Payment Type does not automatically pop, select Finalize.
7. You select three types of payment to process the gift card in this order:
• Select GIFT CARD
• Enter in the amount of the gift card in negative dollars. (-25.00) Payment box changes to PRIV #### (last four digits of Gift Card)
36
•
•
•
•
Choose GCACTIVATE.
Enter in the amount of the gift card (25.00).
Choose method by which guest is paying for gift card (Cash, Credit, Check, etc.).
Enter in the amount of the gift card (25.00).
37
•
•
•
•
Click OK on the three dialogs.
Press REPRINT to print two receipts if two don’t automatically print.
Guest signs one receipt, the other is for your backup.
Insert the Gift Card in the holder and give guest the receipt and their new Gift Card now loaded with
dollars.
Note: The guest should record their number in a safe place and save their receipt for backup.
Installing Ingenico charge cards
The basic process for installing Ingenico charge cards is similar to installing ProtoBase, in terms of the basic
configuration steps that are performed in Salesware module. See Configuring ProtoBase for Salesware and
modify as appropriate. In addition, the following sections call out the Ingenico-specific information of which you
should be aware.
38
General notes
1. You have to install PCEftpos software ( two pieces - EFTServer and EFTClient) on each salespoint (card
present transactions)
2. EFTPOS works on a dedicated modem, shared modem or argent line (DSL line with constant connection)
3. Pinpads are programmed from the bank and must connect without error to EFT software before testing in
Siriusware Inc. A pinpad, when plugged in, indicates on-screen whether it is communicating with the
client (via a comm port). Also, pinpad operation can be tested in EFTclient by going to the EFT client
control panel and hitting the Logon button. If Log-on is successful, then the pinpad can connect to the
bank and get authorizations. This is verified first before trying a transaction is Sales.
4. EFTClient holds merchant and terminal ID information.
5. Pinpad is programmed with merchant and terminal ID at the bank – be certain its settings match the
settings in the EFTClient.
6. Run client diagnostics to troubleshoot setup of the EFTPos system.
7. You have to purchase and install OCV server software for E-Commerce module on the “OSC Server”
(card-not-present transactions).
8. All debit cards can now be processed via EFTPOS − PC-EFTPOS now only parses out track 1 information
(e.g., cardholder name) if the track 1 is encoded properly.
How Ingenico works with Salesware module
1. The operator clicks the Finalize button and selects the payment type (Visa, Master Card, American
Express, bank card, etc.).
2. The operator receives a message for the guest to swipe his/her card.
3. The guest swipes a credit or debit card into the terminal (pinpad).
4. The operator receives a, “select account” message.
5. The guest selects Account Type, which is basically a bank account (checking) or credit.
6. The operator may or may not receive a prompt for guest to enter his PIN based on account type selected
and the guest may or may not need to enter PIN based on account type selected.
7. If Checking was selected, then the operator receives a prompt for the guest to enter his PIN (same
message appears on the pinpad).
8. If the guest selected Credit, the operator is prompted to, “check signature” and must say OK prior to the
transaction completion.
9. There are no Sales > Tools > Credit Cards > General Setup configurations in Salesware software except
for the Assume Approvals if Invoice Amount <= $ (terminal IDs, etc., doesn’t matter in the Salesware
setup – all that is set up in the PCEftpos software).
10. Pinpads are usually programmed to auto-settle once a day at a specific time. This configuration is set up
by your bank. Manual once-per-day settlement can happen through Sales > Tools > Credit Cards >
Close Batch (which really just accesses the PCEftpos software – so settlement can also be manually done
directly through that software). Only one settlement can be done in a 24-hour period (either manual or
automatic).
39
How Ingenico works with SysManager
Configure credit card payment types to process via Ingenico. See Configuring ProtoBase for Salesware for more
information on how this is done for Charge Cards module in general.
Bank Cards can use the card type PRIV (although it doesn’t really matter).
This uses the Salesware Credit Card layout in SysManager > Preferences > Miscellaneous.
How Ingenico works with Sales
Add the following .INI setting.
[Preferences]
PCEftpos=TRUE
Does not work with MOTO=TRUE (you get a message).
PCEftpos software must be running for everything to work. Some sample screen captures of what this looks like:
40
You can access PCEftpos software configuration from the task tray (red or green depending on server
connection).
Sales Host settings for E-Commerce module
[Preferences]
OCV=TRUE
MOTO=TRUE
[Server]
OCV=127.0.0.1:3005
[Salespoint]
Interface=Web
Call center salespoints all talk to an OCV Server. The server has to have the OCV server software installed and
one supported pinpad installed. The hardware on the server requires two comm. ports – one for the pinpad and
one for the modem. From one pinpad, many “virtual” pinpads can be installed (corresponding to each salespoint
that needs to process). Setup in Salesware module can include offline processing, but there is no override if the
Assume Approvals if Invoice Amount <= $ is exceeded. Account ID is the Salesware terminal ID and Client ID
is the Salesware merchant ID. Settlement is handled by the bank.
41
ww.dll .INI settings
ww_system.INI
[Server]
AccountID=0
OCV=127.0.0.1:3005
ccTerminalID=12345678
To integrate with Sales Host utility for the second part of E-Commerce module credit card processing: Added
OCV=TRUE and MOTO=TRUE to [Preferences] section of Sales32c.INI file; added OCV=< IP
address and port of OCV server> to [Server] section of Sales32c.INI file; in Sales Host >
Tools > Credit Cards > General Setup: Merchant ID Selector set to 00, Merchant ID set to 12345678
(must agree with TerminalID registry setting for ww.dll), Credit Card Terminal set to 0 (must agree with
AccountID registry setting for ww.dll).
Note: Merchant ID and Merchant ID Selector may need to be set up for the Sales Host salespoint in
SysManager > Activities > System Lists > Salespoints > Salespoint Configuration Form > Credit Cards tab
if they are greyed out in Sales.
web.config settings
Use device type of 17 for credit card processing.
Merchant or Account ID setting can be added that overrides the setting in the ww.dll registry (important for
being able to process web transactions done through different installs of the pages with a different merchant
number):


Installing Moneris/Tender Retail/VersaPay cards
For more information about installation and configuration, contact Siriusware Technical Support. The following
is also a useful link to the Siriusware Knowledge Base (http://google.siriusware.com):
http://portal.siriusware.com/docs/kb-pdf/IT/servers_and_ports_2009_july_24.pdf
42
For details on how to migrate to the TCP/IP version of Tender Retail/Moneris from an older dial-up version, see
http://portal.siriusware.com/docs/kb-pdf/Installation_and_updates/moneris_2009_March_23.pdf.
Note: Tender Retail’s product name is Merchant Connect, but it is also referred to as CreditCheq in this
documentation and in the Salesware interface.
Because most Siriusware clients use ProtoBase, the documentation regarding use of Salesware’s Charge Card
module is most complete for ProtoBase. Many of the features documented there are used with the other supported
credit card systems as well. See Installing and using ProtoBase Charge Cards.
Setting up charge card processing in Canada
Summary
Salesware users in Canada use Moneris for all credit/debit processing via Salesware module, but the methods or
gateways, vary somewhat.
For in-person transactions in Canada, Salesware is certified via a “gateway” processor named Tender Retail,
which communicates between Salesware and Moneris. All Salesware credit card transactions with a guest or
visitor presently flow through Tender Retail. Tender Retail’s product name is Merchant Connect, but it is also
referred to as CreditCheq in this documentation and in the Salesware interface.
For online transactions, you still use Moneris, but via the Elavon “gateway,” using Elavon’s ProtoBase product.
This is because Salesware is certified through Elavon to process E-Commerce module transactions. All Salesware
sales captured online flow through ProtoBase.
Details
Salesware module acts as the front-end for credit/debit processing for Canadian clients. Salesware uses Tender
Retail/Moneris for card present (swiped) transactions with credit and debit cards and ProtoBase/Moneris for
credit card not present (manually entered through E-Commerce module) transactions. PIN debit cards are not
supported through E-Commerce module.
Salesware module takes the initial information, encrypts it, stores the encrypted information and sends it to
Tender Retail for “card present” transactions or ProtoBase for “card not present” transactions. Tender Retail and
ProtoBase are software modules that configure the information in the correct format for the processor, Moneris, to
then interface with the issuing bank, the bank that issued the card. The issuing bank authorizes or declines the
transaction and Moneris sends back an authorization or a declined message to TenderRetail or ProtoBase, as the
case may be.
Tender Retail software is installed automatically during the Salesware salespoint installation and communicates
directly with Moneris from each salespoint. Every salespoint must have a pin pad (currently the Ingenico
i3070/7800 v. 6.27 Pinpad). ProtoBase, on the other hand, uses a central ProtoBase server that the web salespoint
43
(Sales Host) and the Salesware ww.dll communicate with; the ProtoBase server then communicates with
Moneris. No PIN pad is necessary with the ProtoBase setup because debit cards are not supported.
Note: TenderRetail PaymentTech libraries are present and functioning against a TenderRetail/PaymentTech
pinpad.
Terminology
The following terminology is useful for understanding how the Tender Retail/Moneris solution works:
1. Issuer – This is the bank from which the cardholder receives his card.
2. Acquirer – A bank that has a business relationship with a merchant and receives all credit card
transactions from that merchant; the acquirer gets the money and deposits it into the merchant’s bank.
3. Processor – A company that handles credit card transactions and batches for acquirers (e.g., PaymentTech,
Moneris, 5th/3rd, Vital, etc.).
4. Integration – Salesware codes to a single specification and the product with which Salesware integrates
translates the single format that Salesware sends to the format required for any given number of
processors (e.g., Tender Retail Merchant Connect/CreditCheq, Elavon ProtoBase, etc.).
What the client needs to do to install Tender Retail/Moneris:
Client duties:
From Moneris:
1. Merchant ID
2. ECR numbers – A unique debit ECR and a unique credit ECR is required for each “card present”
salespoint, and a unique credit ECR is required for each MOTO (call center - card not present) salespoint
3. Ingenico PinSmart devices
4. Contact: Client should already have a contact, but if not, George Smith (604) 658-2055
[email protected]
Tender Retail .dll’s are installed with the Sales install and nothing is needed directly from Tender Retail.
Contact: Mike Loftus (416) 498-1200 x22 [email protected] if there are any problems.
ProtoBase requires a separate process, as described in Installing and using ProtoBase Charge Cards.
Installation
Initial installation issues
In the following installation steps you are instructed to add the following setting to your Sales32c.INI file.
44
[Preferences]
CreditCheq=TRUE
If you selected the CreditCheq radio button when you were running the Sales installer, this .INI setting was
already added to the .INI file.
Installation steps
1. In SysManager, make sure all required charge card payment types are set up with number ranges, Process
via CreditCheq and the correct Card Type.
2. Create a Debit Card payment type (Interac cards) with a number range from 000000 to 999999, Process
Via CreditCheq, Card Type PRIV and check Debit Card.
45
3. Do not specify a CC layout in SysManager > Preferences > Miscellaneous. The layout is taken care of
by the Tender Retail install files.
4. Connect the PinSmart device to power and the salespoint serial port. The display shows a version number
and other numbers.
5. Ensure that the computer keyboard is configured for English if a keyboard swipe is being used for charge
card swiping. A French keyboard configuration puts ? for a separator instead of ^ and makes the swipe
unreadable by the software.
Note: The keyboard swipe (or external mag swipe unit) processes charge cards faster than if the PinSmart
swipe is used.
6. For each salespoint ensure that the following entries are in the Sales32c.INI file or Global .INI:
[Preferences]
CreditCheq=TRUE
CreditCheqLineFeeds=n
where n is the number of line feeds between merchant and customer receipts and after the second receipt.
In the Sales32c System.INI ensure the following settings are present:
[Server] CreditCardSales=TRUE
TenderRetailLib=Moneris
CCtagFile=C:\Moneris\cctag.config
46
Setting up Moneris Card and Chip credit card solution
Siriusware Inc. currently supports Verifone vx810 and Ingenico 3070 pinpad.
•
•
Verifone vx810 terminal
Ingenico 3070 terminal
Installation steps
1. Install USB driver for pinpad
• Ingenico 3070 pinpad
a. Download and run CP210xVCPINstaller.exe for 3070 terminal driver.
b. Plug in pinpad.
•
Verifone Vx810 pinpad
a. Download to computer.
b. Insert pinpad.
c. When prompted by Windows to install drivers, select VXUART.inf file.
2. Verify which COM port that has pinpad installed.
a. Open Device Manager
b. Select Ports (COM & LPT)
c. Make note of which COM port pinpad is installed.
3. Copy c:\Program Files\Siriusware\Sales\tenderretail\moneris file into
c:\moneris.
4. If performing a re-install, delete multi.INI and cctag.INI file in c:\Windows.
5. Run c:\moneris\cctagp1.exe as an administrator
6. Open the Config file (cctag.3070 for the 3070 pinpad or
cctag.vx810.66008510.28103767.tips for the vx810 pinpad.)
7. Setup
a. Modify the Authorization Terminal with the ECR number that is unique to the pinpad.
b. Modify the IP Address to point to the Moneris processing server. (Typically, it is
ipgate.moneris.com.)
c. Modify the Merchant ID for the client that is being installed.
47
8. Access the Devices tab.
48
a. Modify the Pinpad Port number to match the port number retrieved in Step number 2 listed
above.
b. Set up Tips if required (None for no tips or Credit and Debit Card inc. Pre-Auth if tip
prompting is required).
9. Select Accepted Card Types and Floor Limits for each card. Check the Authorize Off Line and Do
SAF check boxes if offline processing is required.
10. Select the Printer/Header tab and set up the Credit Card Receipt Header. The highlighted check box is
for tips.
11. Save the file under a different name via Menu > File > Save As. Usually this is saved in
c:\moneris\cctag.config.
12. Go to Menu > Tools > Create EMV Files. This takes approximately thirty seconds on a slow computer
so be patient. If you get an error, most likely you are not running ccragp1.exe as an administrator.
13. Exit the software.
14. Run c:\moneris\testcdcs.exe
15. Click Browse CCTAG button.
49
16. Select the cctag.config files saved in step 11 listed above.
17. Click the Initialize CDCA button. This may take a few seconds to initialize.
18. Test the Computer – Pinpad connection by pressing the Swipe Card button in the Administration pinpad.
50
a. After pressing the button, the pinpad asks the user to swipe their card. If this message does not
display, it means that the Computer – Pinpad link is bad. Verify that the pinpad is set up as a USB,
verify that the driver is installed, and then verify that the COM port number is correct (See Step 8
listed above).
b. Cancel out the swipe card.
19. Click the Pinpad Init button located below the Swipe Card button.
a. The pinpad displays the message, “Downloading.” This process may take a minute so please be
patient.
b. If this does not work, check the ECR number, IP Address and the Merchant ID that were entered
in Step 7 listed above.
20. Once you have finished installing the pinpad, remove the testcdca.exe program after using it to set
up the pinpad.
51
Testing suggestions
The easiest way to do a test of your system is to do a small sale (e.g., $1.00), press Save and charge the sale to a
live card (don’t press Finalize or you are not able to reverse the charge through the Sales interface, although you
could still cancel the charge by calling Moneris). You can then recall the sale and select Tools > Actions >
Reverse Payment to reverse the charge. You can also test connectivity by charging to a debit card and entering
the wrong PIN which results in an, “Incorrect PIN” response from Moneris if the connection is set up properly.
MOTO setup
With Moneris you have to have separate credit ECR numbers for each of your MOTO (card not present)
salespoints. For example, Reservations salespoints that accept “card not present”. If you don’t, the settlement
process goes spectacularly bad (although you don’t really know that anything bad is happening, because on the
Salesware side of things everything looks perfectly fine). It is possible to be missing funds because only one
salespoint using a shared MOTO ECR “wins” the game of settlement. Also, regarding settlement, here are the
options:
1. Pinpad/Card Present must be settled manually per salespoint.
2. MOTO/Card Not Present must be settled manually per salespoint.
3. E-Commerce module is usually set up to be a scheduled settlement by Moneris.
To configure a salespoint for MOTO transactions, in [Preferences] set MOTO=TRUE in Sales32c.INI,
enter the credit ECR number in both Auxiliary Terminal Info fields 1 and 6 and check the Swiper Missing
check box on the Devices > PINPad tab.
Installing Payment Express
For information on installing and using Payment Express, please contact Siriusware Technical Support.
Additional information
No Luhn Check
A No Luhn Check, check box is present on the General tab of the Payment Type dialog. This is used for credit
cards, such as China Union Pay, which do not include a checksum digit in their card numbers. Sales, bypasses the
Luhn Credit Card Check if No Luhn Check is checked in the General tab of the payment type.
52
Reporting
CardWare Transactions By Operator/Salespoint
A new credit card report, CardWare Transactions By Operator/Salespoint is now available. To run the report the
operator must have the security setting, ReportManager - Reports/CardWare - Transactions By OP/SP
assigned to his/her role. Report criteria are Transaction Begin Date, Transaction End Date,
Operator/Operator Group and Salespoint/Salespoint Group. Instead of using normal Credit Card Report
criteria to find relevant CC batches for the user to check off for printing. It just prints the CC transactions that
meet the report criteria (date range, operator or salespoint) regardless of batch number. This allows clients to
research CC transactions which, for a variety of reasons, never have batch numbers assigned to them.
Individual Card Search Report
Salesware’s Individual Card Search Report in ReportManager to look up transactional information by cardholder
name or credit card number.
Batch Detail Report
The Batch Detail Report can also be utilized to get a summary report of credit card totals by salespoint/operator.
Pinpads
Setting up TenderRetail Card and Chip credit card solution (card not present)
Siriusware currently supports the Verifone vx810, IPP320 and K800 pinpad (for Kiosks only) through
TenderRetail. This document describes installation for the Vx810, and IPP320 in card not present scenarios. For
the K800 pinpad, please see Setting up Moneris Card and Chip credit card solution for Kiosk.
53
Verifone vx810 terminal
Note: Software versions matter! Please ensure your pinpad is installed with the appropriate version. For:
•
•
•
Vx810 – XPI 3.11
iPP320 – CPX 9.04
K800 – 1.04H
Introduction
There are two parts to the VersaPay/PaymentTech credit card processing system:
1. Card Present (CP)
• This means that the card is physically present during the purchase.
• Uses a pinpad to swipe/insert card.
2. Card Not Present ( CNP , MOTO)
• The card is not physically there during purchase.
• Used primarily for E-Commerce module purchases and phone orders.
• Does not require a pinpad to process.
• Orbital is the processing system to process CNP transactions
• For CNP stations (i.e., no pinpad), in the Sales32c.INI set:
[Preferences]
MOTO=TRUE
54
Note: This following details setting up the CNP scenario and Sales Host use. For details on CP setup see Setting
up TenderRetail Card and Chip credit card solution (card present).
Setting up a salespoint as CNP
1. Extract zip file to c:\ Orbital.zip.
2. Create two new environment variables:
• PAYMENTECH_HOME=C:\Orbital
• PAYMENTECH_LOGDIR=C:\Orbital\Logs
3. Control Panel > System ( or search of edit the system Environment Variables in windows 7)
55
4. Copy the below section into c:\program
files\siriusware\sales\sales32c_system.INI:
[VersaPay]
; given by paymentech/versapay
MerchantID=000010163768
TerminalID=001
BIN=000002
; setup for canadian currency
CurrencyCode=124
CurrencyExponent=2
; setup for us currency
;CurrencyCode=840
;CurrencyExponent=2
;user name and password, setup by paymentech/versapay
OrbitalConnectionUserName=
Pass=
56
; ComPort the pinpad is connected to.
Port=1
5. You need to modify MerchantID, TerminalID, OrbitalUserName, Pass and Port:
• MerchantID/TerminalID, unique identifier for the client supplied by Versapay
• OrbitalUserName/Pass is the log-in credentials from Versapay
• Port is the com port number that the pinpad is connected to.
• Uncomment the US currency portion and comment the Canadian currency portion if installing for a
US client.
6. For MOTO stations (i.e., no pinpad) set the Sales32c.INI to:
[Preferences]
MOTO=TRUE
7. Disable credit card receipt printing in Sales for stations that have pinpads.
8. Below is a screen capture of what the pinpad looks like. It has a base with a built in receipt printer.
Setting up E-Commerce module as CNP
1. Modify CCDeviceType to 19 (for Versapay).
57

<add key="CCDeviceType" value="19"/>
2. Add the following section to ww_system.INI (refer to salespoint setup above for what to change. The
only difference is ww_system.INI has no Port setting).
[VersaPay]
; given by paymentech/versapay
MerchantID=000010163768
TerminalID=001
BIN=000002
; setup for canadian currency
CurrencyCode=124
CurrencyExponent=2
; setup for us currency
;CurrencyCode=840
;CurrencyExponent=2
;user name and password, setup by paymentech/versapay
OrbitalConnectionUserName=
Pass=
Setting up SysManager
Change Payment Type > Process Via to VersaPay for all credit cards.
58
Setting up TenderRetail Card and Chip credit card solution (card present)
Siriusware currently supports the Verifone vx810, IPP320 through TenderRetail. This document describes
installation for the Vx810 and IPP320 in card present scenarios.
Note: Software versions matter! Please ensure your pinpad is installed with the appropriate version. For:
•
•
Vx810 – XPI 3.11
iPP320 – CPX 9.04
Installation steps
1. Install USB driver for pinpad (i.e.,Verifone Vx810’s pinpad).
• Download VXUART.inf onto PC.
• Insert pinpad.
• When windows asks for drivers to install, select the VXUART.inf file
Vx810_USB_Driver_Installation.Doc.
2. Verify COM port pinpad is installed in.
• Open Device Manager.
• Select Ports (COM & LPT).
• Note on which comport pinpad is installed.
3. For the Vx810:
59
•
Copy c:\program files\siriusware\sales\tenderretail\paymentech software
into c:\paymentech.
4. For the iPP320:
• Copy c:\program files\siriusware\sales\tenderretail\paymentech_iPP320
software into c:\paymentech_iPP320.
5. If doing a reinstall delete multi.INI and cctag.INI file in c:\windows.
6. Run c:\paymentech\cctagp1.exe as administrator (or C:\paymentech_iPP320\cctagp1).
7. Open config file (cctag.vx810.66008510.28103767.tips for vx810).
Note: TenderRetail usually sets up appropriate config file. Please review and ensure the unique pinpad ID.
Note: If installing for the first time Steps 6 and 7 are optional.
Setup
1.
2.
3.
4.
Review and modify the Authorization Terminal with the ECR number that’s unique to a pinpad
Review the IP Address to point to the TenderRetail processing server.
Review Merchant ID for the client that is being installed.
Go to the Devices tab
60
5. Modify PINPad Port number to match port number that was noted as outlined in the installation steps
above.
6. Set up tips if required. (None for no tips, Credit and Debit Card inc. Pre-Auth if tips prompting is
required.)
7. Select Card Types and Floor Limits for each card on the Card Types tab.
8. Check the Authorize Off Line and Do SAF check boxes if offline processing is required.
61
9. Select Printer/Header tab and set up Credit Card Receipt Header. The for tips check the Print Tip Row
and Print Non-Authorized Tip check boxes.
62
10. Save the file under a different name via Menu (File > Save As). Usually saved in
c:\paymentech\cctag.config
11. Go into Menu (Tools > Create EMV Files) This takes about thirty seconds for a slow computer. If you
receive an error, you are not running cctagp1.exe as administrator.
12. Exit software.
13. Create System Environment Variable for appropriate pinpad. To set up environment variables go to >
System > Environment Variables.
Example:
Vx810
•
•
PaymenTech_home=C:\paymentech
PaymenTech_LOGDIR=C:\paymentech\Logs
iPP320
•
•
PaymenTech_home=C:\paymentech_iPP320
PaymenTech_LOGDIR=C:\paymentech_iPP320\Logs
63
14. Run c:\paymentech\testcdca.exe.
15. Click Browse CCTAG button.
16. Select the cctag.config file.
17. Click the Initialize CDCA button. This takes a few seconds.
18. Test the PC-Pinpad connection by pressing the Swipe Card Button in the Administration pinpad.
64
19. After pressing the button, the pinpad asks the user to swipe the card. If it doesn’t, that means that the PC >
Pinpad link is bad. Verify pinpad is set up as USB. Verify driver installed. Verify COM port number is
correct.
20. Cancel out of the Swipe Card.
21. Click the Pinpad Init button, below the Swipe Card button.
22. The pinpad now displays the message, “Downloading”. This process takes a minute or so. If this doesn’t
work, check the ECR number, IP Address and Merchant ID.
23. Set up Sales .INI files
24. Under the Sales32c_system.INI, [Server] section add:
TenderRetailLib=paymentech
CCTagFile=c:\paymentech\cctag.config
Under the Sales32c.INI, [Preferences] section, set:
CreditCheq=TRUE
65
25. Set up credit cards CreditCheq to process credit cards in SysManager. (Activities > Financial List >
Payment Types).
26. Once you have finished installing the pinpad, remove the testcdca.exe program after using it to set
up the pinpad.
Setting up Moneris Card and Chip credit card solution for Kiosk
Note: Siriusware currently supports the K800 pinpad for Kiosk use.
Note: Make sure software installed on K800 Pinpad is 1.04h
Installation steps
1. Make sure c_Sales_42.0.2X is installed and is the Sales32c TenderRetail version of Sales.
2. Open up directory: C:\Program Files\Siriusware\Sales\TenderRetail (if on 64-bit
Program Files (x86).
3. Copy Moneris_K800 folder.
4. Paste Moneris_K800 folder on C:\ drive (C:\Moneris_K800).
5. If doing a reinstall delete multi.INI and cctag.INI file in c:\windows.
6. Run c:\moneris_K800\cctagp1.exe as administrator.
7. Open config file (cctag.vx810.66008510.28103767.tips for vx810).
Setup
1. Modify the Authorization Terminal with the ECR number that’s unique to a pinpad.
2. Modify the IP Address to point to the Moneris processing server. Typically it’s ipgate.moneris.com.
3. Modify Merchant ID for the client installing the pinpad.
66
4. Go to the Devices tab.
67
5.
6.
7.
8.
9.
Modify PINPad Port number to match the com port to which the pinpad is installed.
None for Prompt for Tip.
Ensure EMV Supported is selected for EMV Mode.
Select the Card Types tab.
Choose the Accepted Card Types and Floor Limits for each card. Be sure to disable Authorize Off
Line if it is currently selected.
68
10. Select Printer/Header tab and set up Credit Card Receipt Header. The highlighted check box is for NonAuthorized Tips.
69
11. Save the file under a different name via Menu (File > Save As). Save as cctag.config in the
c:\moneris_K800\ folder.
12. Go into Menu (Tools > Create EMV Files). This can takes about thirty seconds for a slow computer. If
you receive an error, you are not running cctagp1.exe as administrator.
13. Exit the software.
14. Run c:\moneris_K800\testcdca.exe
15. Click the Browse CCTAG button.
70
16. Select the cctag.config file..
17. Click the Initialize CDCA button. Expect this to take a few seconds.
18. Test the PC-pinpad Connection by pressing the Swipe Card button in the Administration pinpad.
71
19. After pressing the button, the pinpad asks the user to swipe the card. If this does not happen, it means that
the PC- pinpad link is bad. Verify pinpad is set up as USB. Verify the driver installed. Verify that the
COM port number is correct.
20. Cancel out of the swipe card.
21. Click the PinPad Init button, below the Swipe Card button.
22. The pinpad now displays the message, “Downloading”. This process takes a minute or so. If this doesn’t
work, check the ECR number, IP Address and Merchant ID.
23. Set up Sales .INI files
24. Under the Sales32c_system.INI, [Server] section add:
TenderRetailLib=Moneris_K800
iCCTagFile=c:\moneris_K800\cctag.config
25. Under the Sales32c.INI, [Preferences] section, set:
CreditCheq=TRUE
72
26. Set up credit cards CreditCheq to process credit cards in SysManager. (Activities > Financial List >
Payment Types)
27. Once you have finished installing the pinpad, remove the testcdca.exe program after using it to set
up the pinpad.
73

Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Related manuals

Download PDF

User manual | Salesware Charge Cards

Related manuals