MASTER_40_Salesware_Installation_Guide

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.
For example, if you're offline and collect 10 credit card transactions and then ProtoBase comes back
online, all 10 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 2 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.
102