ORS Credit Card Deposits

ORS provides a payment option for credit card deposits made for reservations, typically at the time of booking. This deposit information transfers to OPERA PMS and appears on the property reservation. If a reservation is canceled in ORS, however, the deposit is not automatically refunded to the guest; it must be manually refunded.

Note: For deposits to be uploaded from PMS to ORS, certain configuration settings must be applied from within PMS. See PMS to ORS Deposit Upload Configuration in Reservation Deposits and Cancellations.

Some properties might not have an online credit card interface available, due to their remote location or other circumstances. In these cases, properties using ORS need another interface to credit card companies for deposits and refunds transmissions. OPERA can accommodate those needs by providing batch processing and uploads/downloads with the payment solution iVeri Interface. See more information in the section below called Extraction of Credit Card Deposits and Refunds with iVeri Interface.

Notes:

To better control the processing of deposits and cancellations, certain restrictions are available that can be placed on bookers. Bookers must have the user permission of CASHIERING > DEPOSIT AMOUNT OVERRIDE to override the deposit mount. See Reservation Deposits and Cancellations for more information.

ORS credit card deposits functionality does not operate identical to OPERA PMS credit card deposits functionality. More features will be available for ORS in future releases.

In ORS, the following application settings and system configuration must be adjusted before credit card deposit processing is available.

Prior Setup

It is assumed that deposit and cancellation rules have already been set up for each property. Refer to Deposit Rule Configuration and Cancellation Rule Configuration.

Applications Settings

The following applications settings must be activated.

Global > Reservations > Functions > CREDIT CARD DEPOSIT PAYMENT = Y. When this function is activated, the OPP_MHT3 add-on license will be activated. This activates Cross Posting functionality in the ORS environment. The license is internal and not visible to the user.

Global > Reservations > Parameters > CANCEL WITH DEPOSIT = Y. Activate this parameter if you want users to have the right to cancel reservations, even if a deposit has already been paid. As mentioned previously, the refund must be handled manually.

Global > Cashiering > Functions > DEPOSIT HANDLING = Y. Activate this function for deposit handling.

Global > Cashiering > Functions > CANCELLATION HANDLING = Y. Activate this function for cancellation handling.

Global > Cashiering > Parameters > BYPASS CASHIER LOGIN = Y. Activate this parameter if you want users designated as cashiers to only have to log in as cashiers once, as opposed to logging in every time they handle credit card deposits.

Configuration

• The printer should be configured for the workstation for GST FOLIO printer task. Configure at least one report in the group Deposit Receipt. This will provide a documented receipt for the deposit. Select Setup- > Report Setup > Report Groups > Deposit Receipt group. Use the sample_deprecpt.rdf to customize your deposit receipt. For more information, refer to Customizable Reports for details.
• The Credit Card Interface add-on license has to be entered for each property. Select Configuration > Setup > License Codes > IFC > Add-on License. Refer to Add-on License.
• Configure the credit card interface. Select Setup > Property Interfaces > Credit Card Interfaces > General Parameters and enter the information. The property URL field needs to be configured properly and the setup should pass the test for correct connectivity to the credit card interface. Refer to General Parameters.
• If specific credit card functionality needs to be set up, select Setup > Property Interfaces > Credit Card Interfaces > Functionality Setup. Refer to Credit Cards Functionality Setup.
• Create cashier IDs and configure the cashiering criteria for that ID. Select Configuration > Cashiering > Cashiers. See Cashier Setup.
• Once cashier IDs are set up, assign an ID to a specific user. All reservation agents who have permission to post deposits need to have their unique Cashier ID entered here. Select User Configuration > Users. The Users screen appears. Highlight an existing user and select Edit, or select New to create a new user. On the Edit Users or New Users screen, select an ID from the Cashier ID LOV for that user. The ID will also help identify user activity. Refer to Edit Users.
• Configure credit cards and attach them to transaction codes. Select Cashiering > Payment Types. Refer to Payment Types.
• Credit Card transaction codes should be configured for Electronic Fund Transfer [EFT].) Select Cashiering > Codes > Transaction Codes. On the Transactions screen, select the EFT option button. Refer to Transaction Codes.
• Exchange Codes should have the Exchange Cash check box checked for that Currency Code's Exchange Code, which will be used in the reservation. Select Cashiering > Foreign Currency. Refer to Exchange Codes.

Credit Card Deposit Processing

You can make a credit card deposit on a new or existing reservation. At the Reservation screen (Sales Screen > New or Lookup > Availability > Rate Code > Reservation Type), you can begin making a credit card deposit by selecting the Options button.  The Reservation Options screen appears. Select the Deposit/CXL button to open the Deposit Cancellation screen.

• On the Deposit Cancellation screen, select the Payment button to make a credit card deposit.
• Upon selecting the Payment button, the Reservation Deposit Payments screen appears. The default amount of the payment, if it is already set up, will display as the Deposit Due amount. This amount can be accepted or changed. If no deposit amount exists, select the New button to create a new amount.
• When the correct amount has been entered on the Reservation Deposit Payments screen, select the OK button. The credit deposit will be authorized. If authorization is successful, the transaction will be settled and payment will be received. The settlement screen appears with details of the transaction and the Successful message. The report and receipt are automatically generated. The paid deposit and financial transaction details will display on the Reservation Deposits screen. The user can reprint the receipt, or view the transaction. The OXI interface will transfer this transaction to the OPERA PMS system.

For more detailed information on the Reservation Deposits screen, refer to Reservation Deposits and Cancellations.

Extraction of Credit Card Deposits and Refunds with iVeri Interface

iVeri Interface provides an interface to credit card companies. OPERA can integrate the iVeri Interface with properties and ORS to extract batch credit card and refunds data (in a flat file) on a daily basis. The functionality includes:

• Extract all Reservations with Deposit Requests for Authorization and Settlement.
• Process all CANCELLED reservations which are entitled to a Refund (as per cancellation rules).
• Process all CANCELLED reservations for which a cancellation fee needs to be raised (as per the Cancellation Rules).
• Process all Reservations for which a Manual Authorization Code has been received.

General Overview

Where Property Name appears, this is the name of the property doing the extraction.

• In application settings, activate (Y) the General > Parameter > CC DEPOSIT EXTRACTION FOR IVERI INTERFACE. This parameter enables the functionality to extract Credit Card Deposits/Refunds into an iVeri Interface Fix Format. Do not switch on the parameter if iVeri Interface is not being used.
• Configure Resort Udfs for BATCH_LIVE_APPLICATION_ID and BATCH_USN and BATCH_TEST_APPLICATION_ID.
• For the background processor called CREDITCARDEXTRACT, nightly, this procedure will extract Credit Card related deposits out of the system and upload them into Property Name_Upload_Header and Property Name_Upload_Detail tables with NEW status.
• Cancellation in the system will also upload refund data into the same table, with refund transaction codes, with NEW status.
• Procedure written by Property Name will read the data out of these tables and upload it as a Flat file for Credit Card approval. This procedure marks the status as READ in Property Name_upload_header table.
• Once transaction will be approved/failed then the procedure written by Property Name will call EXTRACT.BATCHRESULT API and based on result related payment information will be uploaded in the OPERA system. This process also updates property_upload_header table's status column as a RESPONSE for that batch.

Sample Tables

PROPERTY_UPLOAD_HEADER

Column Name	Data Type	Comment
header_id	number	Sequence Number
trx_date	date	truncated sysdate
record_type	varchar2(2)	Always 00
Version	varchar2(3)	Always 001
bank_code	varchar2(2)	Always 01
merchant_usn	varchar2(10)	RESORT_UDF - BATCH_USN
file_processing_date	varchar2(8)	Always sysdate
application_id	varchar2(36)	RESORT_UDF - BATCH_LIVE_APPLICATION_ID
merchant_name	varchar2(20)	RESORT CODE
Status	varchar2(10)	NEW/READ/RESPONSE

PROPERTY_UPLOAD_DETAIL

Column Name	Data Type	Comment
header_id	number	Foreign key to SProperty_Upload_Header Table
trx_id	number	Unique for the Transaction coming from property_upload_trx_seq
merchant_reference	varchar2(32) )	INV-resv_name_id- resv_deposit_schedule_id- 01/02
merchant_terminal	varchar2(8)	Four Zeros'0000'
transaction_code	varchar2(2)	01-Sale/02-Refund/03- Authorization/04- AuthReversal
purchase_date	varchar2(8)	Arrival Date - Sale Cancel Date  - Refund
purchase_time	varchar2(4)	Arrival Time - Sale Cancel Time - Refund
Amount	varchar2(10)	Deposit Amount
Ccnumber	varchar2(20)	Encrypted CC#
cc_start_date	varchar2(6)	Hard Coded Sysdate-365
cc_expiry_date	varchar2(6)	CC Expiry Date
authorisation_code	varchar2(6)	For Refund this is INV- resv_name_id- resv_deposit_schedule_id for Deposit schedule ID
budget_period	varchar2(2)	Always 00
org_merchant_reference	varchar2(32)	For Refund this is INV- resv_name_id- resv_deposit_schedule_id- 01
result_status	varchar2(3)	0 for Ok else check the Appendix.
transation_status	varchar2(5)
Cycle_Number	varchar2(6)
Trace_Number	varchar2(6)
Reconciliation_Status	varchar2(5)

SAMPLE PROPERTY EXTRACT API Details

This procedure called by external interface to populate result of the Authorization.

Procedure Batch_Result(in_header_id in property_upload_detail.header_id%type,
in_trx_id	in property_upload_detail.trx_id%type,
in_result_status	in property_upload_detail.result_status%type,
in_transation_status	in property_upload_detail.transation_status%type,
in_cycle_number	in property_upload_detail.cycle_number%type,
in_trace_number	in property_upload_detail.trace_number%type,
in_recon_status	in property_upload_detail.reconciliation_status%type,
in_authorisation_code	in property_upload_detail.authorisation_code%type,
in_transaction_code	in property_upload_detail.transaction_code%type)

This procedure called by external interface to populate result of the Authorization based on merchant reference.

Procedure Batch_Result

(in_merchant_reference in property_upload_detail.merchant_reference%type,
in_result_status	in property_upload_detail.result_status%type,
in_transation_status	in property_upload_detail.transation_status%type,
in_cycle_number	in property_upload_detail.cycle_number%type,
in_trace_number	in property_upload_detail.trace_number%type,
in_recon_status	in property_upload_detail.reconciliation_status%type,
in_authorisation_code	in property_upload_detail.authorisation_code%type,
in_transaction_code	in property_upload_detail.transaction_code%type);