When a pass that has been configured as a Direct-To-Lift pass is scanned using a ScanMan scanner, SalesEZ application writes the auto-sale request information into the ww_sales table. Normally the auto-sale would be billed to a predefined account (determined from the pass table). If there is no predefined account defined and the auto-sale’s price is non-zero, then the auto-sale is processed as a Direct-To-Lift charge. SalesEZ application looks up the related guest and mailing address records for the pass and makes a note of the cc_swipe and zip fields. It then generates a new ww_sales record with all the charge information in an XML structure inside the sale_text column. After this, SalesEZ application is done and processing is handed off to Sales. A Direct-To-Lift validation thus generates an auto-sale transaction and a ww_sales record.

 

Note: Instead of making the guest wait in line until an authorization is received for the credit card, SalesEZ application always assumes that the credit card on file is good and scans the pass as “good.” If the credit card is subsequently declined for any reason (expired, reported lost/stolen, etc.) the pass is voided and subsequent scans of the pass scan as “bad.” Similarly, if the credit card information for the guest is missing, the pass is voided and scans as “bad” on subsequent scans.

 

Sales Host utility then attempts to get an authorization using the credit card associated with the guest who owns the pass. If the authorization attempt fails, the pass is voided and the record is put into the “error” state. The record can be re-processed and if the authorization succeeds, the pass is un-voided. All Direct-To-Lift authorization attempts are recorded in the cc_trans table. Any record with a status of 3 means that the authorization attempt was unsuccessful.

 

Note: You must be running Sales Host utility for processing to occur.

 

Note: At this time, Direct-To-Lift functionality works with two Charge Cards systems: DirectNet and ProtoBase.

 

The Direct to Lift pass is scanned by ScanMan. The SalesEZ looks up the guest the guest record and hands the process to SalesHost for credit card authorization.

The ScanMan response will be GOOD in the case of all first scans so that the quest is not held up waiting for credit card authorization. If the charge is declined, the pass will be voided and all subsequent scans will be BAD. A failed authorization can be reprocessed and, if successful, the pass will be un-voided.