Credential on File Transactions

Lodging credential on file transactions are indicated by Fields 0305, 0738, 0054, and 0723.

Scenarios Establishing a Credential on File

Scenario Field 0305 Value Field 0738 Value Field 0054 Value Field 0723 Value
Lodging Advanced Deposit – Card Not Present 3 = Advanced Deposit API Request - Not Present
API Response – Compliance Data Value (Merchant PMS must retain for COF transactions)
01 = Manual/Key Entry F = First Payment
Establishes Credential on File
Lodging Check in - Card Present
1 = Normal Lodging API Request - Not Present
API Response – Compliance Data Value (Merchant PMS must retain for COF transactions)
Entry Mode of the Card Present Transaction
01 = Manual/Key Entry
05 = EMV
07 = Contactless Chip Card
80 = EMV fall back to swipe
90 = Magnetic Stripe
91 = Contactless Mag Stripe
F = First Payment
Establishes Credential on File

Scenarios Using a Credential on File

Scenario Field 0305 Value Field 0738 Value Field 0054 Value Field 0723 Value
Lodging Incremental Authorization 1 = Normal Lodging
API Request - Compliance Data Value retained from field 0738 of the Original Authorization Transaction Response
API Response – Not Present
01 = Manual Entry/Key Entry S = Subsequent Payment Using Credential on File
Lodging Check in 1 = Normal Lodging
API Request - Compliance Data Value retained from field 0738 of the Original Authorization Transaction Response
API Response – Not Present
01 = Manual Entry/Key Entry S = Subsequent Payment
Using Credential on File
Lodging Extended Stay 1 = Normal Lodging
API Request - Compliance Data Value retained from field 0738 of the Original Authorization Transaction Response
API Response – Not Present
01 = Manual Entry/Key Entry S = Subsequent Payment
Payment Using Credential on File
Lodging Advanced Deposit 3 = Normal Lodging
API Request - Compliance Data Value retained from field 0738 of the Original Authorization Transaction Response
API Response – Not Present
01 = Manual Entry/Key Entry S = Subsequent
Payment Using Credential on File
Lodging No Show Charge 2 = No Show
API Request - Compliance Data Value retained from field 0738 of the Original Authorization Transaction Response
API Response – Not Present
01 = Manual Entry U = Unscheduled Payment/Purchase
Using Credential on File
Lodging Delayed Charge (Post Stay Charges) - Using Credential on File 4 = Delayed Charge API Request - Compliance Data Value retained from field 0738 of the Original Authorization Transaction Response
API Response – Not Present
01 = Manual Entry U = Unscheduled Payment/Purchase
Using Credentials on File

error_outline
important
  • There is a potential issue that lodging merchants supporting stored credentials on file for use in rewards or loyalty programs need to be aware of.

  • The issue can occur if the card number data is being obtained from a card present transaction (at a front desk terminal for example), and the cardholder is using an on phone payment application such as Apple Pay, Google Pay or Samsung Pay.

  • The card data used in this scenario is typically a onetime use token and cannot be used for future transactions beyond the card holder’s stay at the hotel and therefore would not be of use within a rewards program for transactions performed at a later date.