Charge Cards : Installing and using ProtoBase charge cards : General notes : ProtoBase offline transactions : Automated authorization when ProtoBase comes back online
 
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.
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.