Open the Portico Schema site
Portico Developer Guide
Lodging
Special Processing Rules > Industries > Lodging
The Lodging data is supplied as an extension on existing transactions listed in this document and the schema documentation. Support for Lodging is provided by the LodgingDataType elements and its sub-elements.

The following are some typical use cases for Lodging:

Check In

Upon Check-In, the merchant may use a CreditAuth transaction to authorize the card and reserve the funds.  If all that is needed at check-in is to validate the card, a CreditAccountVerify can be used.  If the final amount of the stay is known, a CreditSale can be used.

Check Out

Upon Check-Out, the merchant closes out a CreditAuth by using the CreditAddToBatch transaction (if the Check-In used a CreditAuth that has not yet been added to a batch). Otherwise, a CreditSale can be run. or the original authorized amount can be reduced using a CreditTxnEdit transaction. The transaction request must include the GatewayTxnID from the Check-In authorization transaction, and optionally the amount of the transaction. 

 

Incremental Authorization for the Lodging Industry

Use the CreditIncrementalAuth transaction to increase the authorized amount on a credit card. Incremental authorization in the lodging industry is typically used for extended duration and extra charges added to a customer's stay. 

 

Single Stay

 

Advance Deposit

Note:  For American Express, see also Amex Special Programs.

Additional Charge

No Show

Note:  For American Express, see also Amex Special Programs.

Delayed Charges

The check-in date is the initial authorization date and the stay duration is one day.

The valid stay duration is from 1 to 99 days.

Extra Charges

Lodging merchants may specify which types of Extra Charges were incurred during a stay.  These charges must be sent in the appropriate fields for the authorization platform.

Amex Special Programs

The AdvancedDepositType data block is used for American Express cards only.