MASTER_40_Salesware_Installation_Guide

More documents

Recommendations

Info

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
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. ProtoBase questions Is Cardware fully CISP compliant? Is data encrypted on the server? The term “Cardware” refers to Siriusware's own credit card processing software. Cardware was built for use in versions 3.2 – 3.4, and is not considered 100% CISP compliant. While some clients are still using Cardware, it is being phased out, and its functionality is now being provided by ProtoBase. ProtoBase offers a CISP compliant solution for both 3.4 and 4.0 users, and all credit card related data is encrypted in both Siriusware and ProtoBase applications. Who provides training for the new interface? Siriusware? Southern DataCom? What is covered by each? Training on ProtoBase applications is done by Southern DataCom. The training is usually done shortly after ProtoBase is installed. Siriusware provides assistance with setting up the necessary settings in Sales and SysManager, as well as basic information on Siriusware credit card/payment reporting. Are calls placed to Southern Datacom for technician support responded to immediately or do we have to wait for a return call? What is the response time? Southern DataCom’s technical support is similar to Siriusware’s in that emergency situations move to the front of the queue and are responded to immediately. Non-emergency calls may be responded to with a return call. I recommend calling Southern DataCom directly to inquire about their technical support process. Their number is 877.732.1799. For more information about troubleshooting 103
Page 1 and 2:
Salesware Installation Guide SALESW
Page 3 and 4:
Siriusware examined the worst probl
Page 5 and 6:
files associated with each module,
Page 7 and 8:
ports.INI file PDF documentation se
Page 9 and 10:
Note: If you want to install SQL Se
Page 11 and 12:
Note: If SQL Server Management Stud
Page 13 and 14:
The SQL service pack level is liste
Page 15 and 16:
Verifying mixed mode authentication
Page 17 and 18:
If Windows only was selected, you n
Page 19 and 20:
If Windows Authentication mode was
Page 21 and 22:
7. You are presented with the follo
Page 23 and 24:
10. You are presented with the foll
Page 25 and 26:
13. You are presented with the foll
Page 27 and 28:
• Writes shared information to th
Page 29 and 30:
7. When CommonFiles is finished ins
Page 31 and 32:
Page 33 and 34:
7. After PoolManager installation b
Page 35 and 36:
After PoolManager is installed, you
Page 37 and 38:
Page 39 and 40:
7. After SysManager installation be
Page 41 and 42:
directly from the \SiriusFS\Install
Page 43 and 44:
Page 45 and 46:
You can launch ReportManager from t
Page 47 and 48:
Page 49 and 50:
Page 51 and 52: 8. When the Sales installation comp
Page 53 and 54: The next screen can prompt you in o
Page 55 and 56: Note: The directions provided in th
Page 57 and 58: 4. You should see the following scr
Page 59 and 60: 8. Right-click on the user sirius a
Page 61 and 62: 11. The SQL Server Login Properties
Page 63 and 64: 13. You are prompted to confirm the
Page 65 and 66: 3. Right-click on Databases and sel
Page 67 and 68: 8. Click OK. Now your database is a
Page 69 and 70: 12. Click OK. Your database is now
Page 71 and 72: Note: Much of the information you a
Page 73 and 74: 9. The Attach Database - (LOCAL) di
Page 75 and 76: 13. Right-click on the user sirius
Page 77 and 78: The training database is now in pla
Page 79 and 80: Note: The training database must re
Page 81 and 82: 10. You should see the following di
Page 83 and 84: 12. Right-click on the user sirius
Page 85 and 86: some processors that have “execut
Page 87 and 88: 5. Click the radio button for Turn
Page 89 and 90: Uninstalling Salesware There are tw
Page 91 and 92: • Food service (allows tipping)
Page 93 and 94: ProtoBase Installation ProtoBase in
Page 95 and 96: Enter the appropriate code (typical
Page 97 and 98: You use SysManager > Activities > F
Page 99 and 100: ProtoBase settlement and Salesware
Page 101: Report and selection comparisons op
Page 105 and 106: can also be utilized to get a summa
Page 107 and 108: Can the batches be transmitted whil
Page 109 and 110: Password Sales32c.INI DirectNetLink
Page 111 and 112: 1. The operator clicks the Finalize
Page 113 and 114: [Preferences] OCV=TRUE MOTO=TRUE [S
Page 115 and 116: 2. From Moneris: Merchant ID; ECR n
Page 117 and 118: • Host: Processing bank. Is usual
Page 119 and 120: • Default Language: Specify the l
Page 121 and 122: 1. Set up from SysManager. See To s
show all

MASTER_40_Salesware_Installation_Guide

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?