This wizard is used to set up your copy of Panorama with your merchant account information. You’ll find this wizard in the Preferences submenu of the Wizard menu.
Configuring Merchant Information
Click the Configure button to open the Merchant Information dialog (you can also choose Configure from the Account menu).
This dialog allows you to configure six options:
License (ProVUE) - If you’ve purchased the Panorama/Authorize.Net interface, enter the license code here. If you haven’t purchased yet, leave this field blank to use demo mode. In demo mode the software will only work for processing test transactions (see Test Mode, below). (Click here to purchase your gateway license.)
API Login ID - This is the permanent ID that Panorama uses to access your merchant account. See API Login ID / Transaction Key to learn how obtain your ID.
Transaction Key - This key is used in combination with the API Login ID to access your merchant account. Unlike the API Login ID, however, the Transaction Key is not permanent. In fact, you can generate a new Transaction Key at any time (see API Login ID / Transaction Key). When you generate a new Transaction Key, the old key becomes invalid (either immediately or within 24 hours). This helps you prevent unauthorized access to your merchant account. For example, suppose an employee that had access to your merchant account leaves the company. Even if they had copied the merchant certificate (see below), they will not be able to access the merchant account once the transaction key is changed. (Of course you’ll need to update this dialog any time you change the transaction key, and also generate and copy new certificates if other computers are processing charges, see below.)
Default Currency - This specifies the currency that will be used if no currency is specified in an individual transaction. The default is US Dollars.
Test Mode - If this option is checked, transactions will not be submitted to the merchant gateway. Instead, any transaction with using the following cards will be “approved”: 370000000000002, 6011000000000012, 5424000000000015 or 4007000000027. To cause the system to generate a specific error, submit a transaction with the card number 4222222222222. The system will return the response reason code equal to the amount of the submitted transaction. For example, to test response reason code number 27, a test transaction would be submitted with the credit card number, “4222222222222,” and the amount, “27.00.”
Note that this option is independent of the Test Mode setting on the Authorize.Net web site. To process actual live transactions requires three settings:
* In your settings on the Authorize.Net web site, Test Mode must be turned Off (the default is On for new accounts).
* The Test Mode option must be turned Off in this dialog.
* A valid ProVUE license code must be entered in this dialog.
Allow Credits (Refunds) - If this option is turned off, Panorama will not allow refund transactions to be passed to the merchant gateway. You may want to disable this option for low level employees, so that only supervisors can issue credits.
Setting Up a Password
Whether you set up a password or not, Panorama uses a secure encryption algorithm to protect the information you enter into the Merchant Information dialog. However, if you don’t set up a password, anyone with physical access to your computer will be able to access your sensitive configuration information. Click on the Password button to set up a password (or change the password, if already set). Once you set a password, you will be prompted to enter the password any time you press the Configure button (however, if you have entered the password in the last five minutes, Panorama will not require you to enter it again).
Using Certificates to Configure Multiple Computers
So far we’ve assumed that only one computer will be used for processing credit card transactions. If more than one computer will be processing transactions, each one will need to be configured. One way to do that is to physically go to each computer and configure it using the Merchant Information dialog. However, in some situations this is inconvenient or impossible. For these situations Panorama provides a certificate system that allows the configuration to be distributed without revealing any sensitive configuration information.
The first step is to set up a “master” computer using the Merchant Information dialog as described earlier on this page. Then you have three choices for creating and distributing a certificate:
1) Drag the certificate icon to an e-mail program or text editor.
2) Hold down the Control key and click on the certificate icon to copy the certificate to the clipboard.
3) Choose Copy Certificate from the Certificate menu.
Once you’ve got the certificate in text form, you can transmit it to wherever it needs to go. You can send it to any staff member that is trusted to process credit cards. When the staff member receives the certificate, he or she can simply drag and drop it onto the Authorize.Net wizard on their computer. Alternately, they can copy the certificate onto the clipboard and use the Paste Certificate command from the Certificate menu (it’s not necessary to copy only the certificate itself -- Panorama will automatically extract the certificate data from any extraneous text, so usually the receiving staff member could simply press Command-A Command-C in their e-mail program, then go to the Authorize.Net wizard and paste Command-V.
Issuing New Certificates
Suppose an employee authorized to process credit card transactions leaves the company, or a computer containing a certificate is lost or stolen. When an event like this happens, you should immediately obtain a new Transaction Key (see above). Enter the new transaction key on your main computer, then distribute new certificates to all authorized users. The old certificates will no longer allow access to the merchant gateway system.
Issuing Different Certificates
If you have multiple staff members, they don’t all have to have the same certificate. For example, some might receive a certificate that allows them to process credits (refunds), while others can only process new transactions. Simply set up the options you want in the Merchant Information dialog, then generate and distribute the certificates.