Server Management and System Options
The Server Management page displays a list of available system options as well as a list of all current account administrators.
More information regarding account privileges (including Account Admins) can be found on the FasCard Admin Site - User Accounts page.
The System options page is where the user designates what the machine will accept as payment, which credit cards will display on the reader, as well as authorization amounts for credit cards.
|When checked, all the readers will enable coins features.|
|Accepts Credit Cards for Adding Value||When checked, all readers will allow customers to use credit cards when adding value to their account.|
|Accepts Credit Cards for Machine Starts||When checked, all readers will allow customers to use credit cards to start the machines|
|Accept Apple Pay*||When checked, all readers will accept Apple Pay|
|Accept Android Pay*||When checked, all readers will accept Android Pay|
|Allow Loyalty||When checked, all readers will allow loyalty program, accumulating points or redeeming points.|
|Enable Location Groups||When checked, enables Location Group features. See FasCard Admin Site - Location Groups for more information.|
|CCI Support||Enabling this check box grants CCI technical support access to system. Without this option enabled, access is restricted to users granted "Website Privileges" on the User Accounts page.|
|Service Type||This field indicates the gateway service used by the FasCard account.|
Authorization Mode - This option allows an owner to choose which type of Authorization to use for their system.
**Note** Does not apply to "Add Value" transactions using a credit card.
This field indicates the pre-authorization hold amount that will be used when credit cards are processed in the "Pre-Authorization Only" mode (see above)
This field is only displayed when the "Test and Trust" Authorization mode is selected. This field is the maximum amount that the customer can spend in a set of transactions.
|Max Daily Auth Amount||This field indicates the maximum amount that may be authorized per credit card per day. This is set to $200.00 by default. If this is set to $0.00, credit cards transactions will not process.|
|Offline Auth Amount|
This field indicates the maximum amount to permit a customer to charge with a credit card when the satellite is offline. The satellite will attempt to charge the total amount of all customer transactions processed while offline - this depends upon availability of funds on the credit card and is subject to denial for standard reasons. These are delayed authorization attempts that will only attempt to process when the satellite is online again.
Utilizing the Offline Authorization feature by configuring the 'Offline Auth Amount' field to a non-zero amount is performed at the operator's discretion and risk. Card Concepts Inc. is not liable for charges that are declined or otherwise fail to process once satellite connectivity is restored.
This field is where a surcharge or a discount amount can be set (by the Owner).
|Idle Time Minutes||This field indicates the amount of time that the system will wait after a card is last used before it reconciles the actual transaction amount for an individual credit card.|
|Time Zone||This field indicates the time zone that will be indicated in the timestamp of individual credit card transactions.|
|Transaction Cut-Off Time||This is the time that designates the end of one business day and the start of the next. This should be set to match the time that Authorize.net is configured to use. Typically this is configured by CCI support- this field should only be changed under the supervision of CCI support.|
|Save||Click this button to save any changes made on this page.|
It's important to keep in mind when configuring 'Idle Time Minutes' that transactions that are captured after the 'Transaction Cut-Off Time' will be not be picked up by the gateway provider (Authorize.net) until the next business day.
This section of the page lists the name and email address of all of the admin users that are configured for the system. These users have full access to the system. As a best practice for secure systems, it is recommended to keep this list to a minimum to prevent unauthorized changes to the system.