Lodging

Card Present Connect | Lodging is the solution for processing lodging transactions. lodging processing is based on the global standards established by the card schemes for reliable, scalable, and secure card-not-present transactions and contact and contactless EMV card-present transactions.

For information about tokenizing lodging payment card data, see Token Management Service (TMS) documentation.

Supported Card Types

These card types can be used to process lodging transactions:

• Mastercard
• Visa

PIN debit cards are supported in North America only and can be used to process sales transactions only. Other transaction types, such as refunds or pre-authorizations, are not supported on PIN debit cards.

Card-Present Transaction Risk Control Requirements

Card-present transactions carry lower risk than card-not-present transactions because the customer and payment card are physically present, which can result in lower transaction fees. However, acquirers must still apply standard risk-control measures. Acquirers must monitor transaction activity and manage fraud and disputes in accordance with payment network rules, including the Global Acquirer Risk Standards. They also must comply with these Visa risk compliance programs:

• Visa Fraud Monitoring Program
• Visa Dispute Monitoring Program

To meet risk control requirements, acquirers can use one of these options:

• Enable transaction and fraud monitoring tools.
• Ensure that their payment technology providers (PTPs) implement transaction and fraud monitoring tools.
• Deploy their own transaction and fraud monitoring tools.

Each option provides necessary fraud and risk controls for direct merchant relationships and for PTPs that do not operate their own monitoring solutions.

Lodging Transaction Scenarios

This section describes the lodging transaction scenarios supported by .

Check-In Transaction Scenario

Check-in is a crucial step in the guest's journey, and it sets the tone for their entire stay. A smooth and efficient check-in process can make a positive impression on guests and encourage them to return to your property.

The lodging check-in transaction workflow typically includes this sequence of events:

1. The guest arrives and presents their identification and reservation information.
2. The front desk staff verifies the guest's reservation.
3. The front desk staff collects the guest's payment card.
4. The front desk staff inserts, swipes, or taps the guest's payment card or enters the payment information manually into their payment system. The authorization request sent to the processor includes the lodging fields.
5. The processor sends an authorization request to the issuing bank.
6. The issuing bank approves the transaction and sends an authorization response to the processor.
7. The payment technology provider (PTP) sends the authorization response to the lodging's property management system (PMS).
8. The PMS updates the guest's reservation with the payment information and generates a receipt.
9. The front desk staff gives the guest a room key and receipt.

Incremental Authorization Scenario

An incremental transaction is an additional authorization that increases the original amount of a transaction. The final authorized total combines the amounts from the initial and the incremental authorizations.

This type of authorization is used to increase the total payment amount when the initial authorization is insufficient to cover the total cost of lodging and associated services.

Lodging transactions comprise these types of incremental authorizations:

• Initial authorization: Upon reservation or check-in, the guest's payment card is pre-authorized for an estimated amount based on the initial reservation details and potential additional charges. The lodging staff obtains explicit consent from the guest to process the incremental authorizations when charges exceed the initial authorization.
• Additional charges: As the guest's stay progresses and additional charges are incurred, such as dining, spa treatments, or minibar consumption, the initial pre-authorization might become insufficient to cover the total amount due for payment. To ensure adequate coverage for the guest's expenses, the lodging staff initiates an incremental authorization request for an additional amount.

For examples of scenarios in which an incremental authorization could be used, see Check-In Transaction Scenario and Check-Out Transaction Scenario.

Check-Out Transaction Scenario

The check-out process begins when the guest indicates that they are checking out of the lodging.

The lodging check-out transaction workflow typically includes this sequence of events:

1. The guest confirms they want to pay their bill using the stored payment method.
2. The lodging's system calculates the total amount due, including any remaining balance on the incremental authorization.
3. The lodging's payment system processes the transaction, communicating with the payment processor and the card issuer.
4. The lodging's payment system verifies the payment information, authorizes the transaction, and captures the funds.
5. The front desk staff gives the guest a paper receipt, which includes charges and payment information.
6. The lodging sends an electronic receipt or sends an email copy of the receipt to the guest (optional).

No-Show Transaction Scenario

A no-show occurs when a guest makes a reservation but does not check in or cancel the reservation. No-show transactions are determined by the lodging's disclosed and agreed-upon cancellation policy.

A lodging business can handle no-shows in several ways, including these options:

• Charging a no-show fee: This fee is charged to the guest's credit card if they do not cancel their reservation within a certain amount of time. The amount of the fee is typically based on the room rate and the length of the stay.
• Requiring a deposit: This is a payment that the guest is required to make upfront to secure their reservation. The deposit is typically refunded if the guest cancels their reservation by a certain date.

The no-show transaction workflow typically includes this sequence of events:

1. The guest makes a reservation online, by phone, or in person. At the time of booking, the guest provides their credit card information.
2. The lodging staff sends the guest a confirmation email or text message with the details of the reservation. The guest confirms their reservation by replying to the email or text message.
3. The guest does not check in or cancel their reservation by the time their reservation is scheduled to start, which is considered a no-show.
4. The lodging charges the guest a no-show fee using the same payment method the guest used to make the reservation. The amount of the fee is based on the lodging's no-show policy.

Lodging EMV and Card Data

You can request these payment services for lodging with EMV and card data:

• Authorization: standard and incremental
• Capture
• Stand-alone credit

This table shows the requirement for EMV tags using these categories:

• M: required
• P: prohibited
• O: optional
• C: conditional (send tag when it is present in card and terminal)

Lodging Transaction Descriptions

Use the lodging transaction descriptions listed in the tables to help you identify types of request messages for production transactions in the and in your transaction reports. Include the clientReferenceInformation.comments field with a transaction description value when you submit a request.

If you want to review your test environment result after you add the comments field, contact customer support.

This table lists the check-in transaction descriptions:

This table lists the incremental authorization transaction descriptions:

This table lists the check-out transaction descriptions:

There are no card-not-present transactions during the check-out procedure.

This table lists the no-show transaction descriptions:

This table lists the refund and credit transaction descriptions:

This table lists the error transaction descriptions: