Credential on File Transactions

Credential on file transactions occur when a cardholder gives express permission to the merchant to store their payment credentials for use on a future purchase.

The COF transaction category introduces two transaction types:

• Scheduled COF
• Unscheduled COF

These types of transactions also update card brand rules, including merchant disclosure requirements.

The stored credential transaction category covers all COF transactions, including:

• Cardholder-initiated stored credential transactions - no fixed schedule
• Industry Specific (delayed, no-show, incremental)

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

Scenarios Establishing a Credential on File

Auth Only (01) - Check In

Cardholder and Merchant agree to establish a Credential on File at a hotel and perform the initial authorization transaction. The COF may be used for future transactions initiated by the cardholder or merchant for payment of lodging stays or hotel services.

Example: Cardholder checks into a hotel and agrees to place their card on file for future transactions. Use the following fields for check in.

• Field 0723 - F (First Payment to Establish Credential on file)
• Field 0738 - Not Present
• Field 0305 - 1
• Field 0047 position 5 - 0
• Field 0054 - As entered
• Initiated by - Cardholder
• Reason COF Used - Unscheduled

Sale (02)

Cardholder and Merchant agree to establish a Credential on File while making a reservation and perform the initial sale transaction. The COF may be used for future transactions initiated by the cardholder or merchant for payment of lodging stays or hotel services.

Example: Cardholder makes an advanced deposit, express service arrangement, or assured reservation for a hotel stay and agrees to place their card on file for future transactions.

Sale (02) - Advanced Deposit

• Field 0723 - F (First Payment to Establish Credential on file)
• Field 0738 - Not Present
• Field 0305 - 3
• Field 0047 position 5 - 4
• Field 0054 - As entered
• Initiated by - Cardholder
• Reason COF Used - Unscheduled

Sale (02) - Express Service

• Field 0723 - F (First Payment to Establish Credential on file)
• Field 0738 - Not Present
• Field 0305 - 5
• Field 0047 position 5 - 4
• Field 0054 - As entered
• Initiated by - Cardholder
• Reason COF Used - Unscheduled

Sale (02) - Assured Reservation

• Field 0723 - F (First Payment to Establish Credential on file)
• Field 0738 - Not Present
• Field 0305 - 6
• Field 0047 position 5 - 4
• Field 0054 - As entered
• Initiated by - Cardholder
• Reason COF Used - Unscheduled

Zero-dollar Auth Only (01)

• Field 0723 - F (First Payment to Establish Credential on file)
• Field 0738 - Not Present
• Field 0305 - 1
• Field 0047 position 5 - 4
• Field 0054 - As entered
• Initiated by - Cardholder
• Reason COF Used - Unscheduled

Scenarios Using a Credential on File

Guest arrives at the hotel and agrees to use their COF to check into the hotel.

Auth Only (01) - Check In

• Field 0723 - S (Subsequent Payment)
• Field 0738 - Value from Original Transaction Response
• Field 0305 - 1
• Field 0047 position 5 - 4
• Field 0054 - 01
• Initiated by - Merchant
• Reason COF Used - Unscheduled

Auth Only (01) - Check In

• Field 0723 - U (Unscheduled Payment)
• Field 0738 - Value from Original Transaction Response
• Field 0305 - 1
• Field 0047 position 5 - 4
• Field 0054 - 01
• Initiated by - Cardholder
• Reason COF Used - Unscheduled

Advanced Deposit, Express Service, Assured Reservation

Cardholder or Merchant initiates a transaction for an advanced deposit, express service arrangement or assured reservation using the established COF

Example: Cardholder makes an advanced deposit, express service arrangement or assured reservation for a hotel stay using their established COF. Merchant requires a payment for an advanced deposit, express service arrangement or assured reservation, a transaction is performed using the cardholder’s COF.

Sale (02) - Adv Deposit

• Field 0723 - S (Subsequent Payment)
• Field 0738 - Value from Original Transaction Response
• Field 0305 - 3
• Field 0047 position 5 - 4
• Field 0054 - 01
• Initiated by - Merchant
• Reason COF Used - Unscheduled

Sale (02) - Adv Deposit

• Field 0723 - U (Unscheduled Payment)
• Field 0738 - Value from Original Transaction Response
• Field 0305 - 3
• Field 0047 position 5 - 4
• Field 0054 - 01
• Initiated by - Cardholder
• Reason COF Used - Unscheduled

Sale (02) - Express Service

• Field 0723 - S (Subsequent Payment)
• Field 0738 - Value from Original Transaction Response
• Field 0305 - 5
• Field 0047 position 5 - 4
• Field 0054 - 01
• Initiated by - Merchant
• Reason COF Used - Unscheduled

Sale (02) - Express Service

• Field 0723 - U (Unscheduled Payment)
• Field 0738 - Value from Original Transaction Response
• Field 0305 - 5
• Field 0047 position 5 - 4
• Field 0054 - 01
• Initiated by - Cardholder
• Reason COF Used - Unscheduled

Sale (02) - Assured Reservation

• Field 0723 - S (Subsequent Payment)
• Field 0738 - Value from Original Transaction Response
• Field 0305 - 6
• Field 0047 position 5 - 4
• Field 0054 - 01
• Initiated by - Merchant
• Reason COF Used - Unscheduled

Sale (02) - Assured Reservation

• Field 0723 - U (Unscheduled Payment)
• Field 0738 - Value from Original Transaction Response
• Field 0305 - 6
• Field 0047 position 5 - 4
• Field 0054 - 01
• Initiated by - Cardholder
• Reason COF Used - Unscheduled

Sale (02) - No Show

Merchant initiates a transaction for a No Show charge.

Example: The card holder did not appear for their hotel reservation, and the merchant performs a transaction using the established COF.

• Field 0723 - S (Subsequent Payment)
• Field 0738 - Value from Original Transaction Response
• Field 0305 - 2
• Field 0047 position 5 - 4
• Field 0054 - 01
• Initiated by - Merchant
• Reason COF Used - Unscheduled

Sale (02) - Delayed Charge

Merchant initiates a transaction for a Delayed charge.

Example: The cardholder owes an amount after check out for additional charges, the merchant performs a transaction using the COF.

• Field 0723 - S (Subsequent Payment)
• Field 0738 - Value from Original Transaction Response
• Field 0305 - 4
• Field 0047 position 5 - 4
• Field 0054 - 01
• Initiated by - Merchant
• Reason COF Used - Unscheduled

Incremental Auth (75)

Merchant initiates an incremental Authorization.

Example: Merchant requires an additional authorization amount for the lodging stay or incidental charges, an incremental authorization is performed using the COF.

• Field 0723 - S (Subsequent Payment)
• Field 0738 - Value from Original Transaction Response
• Field 0305 - 1
• Field 0047 position 5 - 4
• Field 0054 - 01
• Initiated by - Merchant
• Reason COF Used - Unscheduled

Return (09)

Cardholder or Merchant initiates a Return Transaction using the established COF.

Example: Merchant has overcharged for a previous lodging stay and needs to refund the cardholder.

• Field 0723 - S (Subsequent Payment)
• Field 0738 - Value from Original Transaction Response
• Field 0305 - 1
• Field 0047 position 5 - 4
• Field 0054 - 01
• Initiated by - Merchant
• Reason COF Used - Unscheduled

Example: Cardholder cancels portion of a lodging stay and an amount is to be refunded.

• Field 0723 - U (Unscheduled Payment)
• Field 0738 - Value from Original Transaction Response
• Field 0305 - 1
• Field 0047 position 5 - 4
• Field 0054 - 01
• Initiated by - Cardholder
• Reason COF Used - Unscheduled

Prior Authorization (07)

Merchant initiates a Prior Authorization to complete a previous COF authorization only transaction.

Example: Merchant needs to submit a prior authorization for a COF transaction as part of their End of Day process and initiate settlement.

• Field 0723 - Same as initial Authorization Only (01)
• Field 0738 - Value from Original Transaction Response
• Field 0047 position 5 - Same as initial Authorization Only (01)
• Field 0054 - 01
• Initiated by - Merchant
• Reason COF Used - Same as initial Authorization Only (01)

Voids and Reversals

Merchant initiates a Reversal or Void of a previous COF transaction.

Example: Merchant needs to cancel a previous transaction, a void or full reversal is performed. Merchant has over-charged on previous authorization transaction, a partial reversal is performed.

• Transaction Type - Full Reversal (61), Partial Reversal (76), Void Sale (11), Void Return (17)
• Field 0723 - Same as original
• Field 0738 - Value from Original Transaction Response
• Field 0305 - Same as original
• Field 0047 position 5 - 4
• Field 0054 - 01
• Initiated by - Same as original
• Reason COF Used - Same as original

POS Data Code - FIELD 0047 POSITION 5 – Cardholder Presence

• Cardholder Present Value
  0 = Cardholder present

Cardholder Not Present Value

• Value 1 - Cardholder not present (reason not specified)

• Value 2 - Cardholder not present, mail order

• Value 3 - Cardholder not present, telephone order

• Value 4 - Cardholder not present, Industry Practice

• Value 5 - Cardholder not present, eCommerce

• Value A - Cardholder not present, Standing Authorization Unscheduled

• Value 9 - Cardholder not present, Standing Authorization Recurring or Installment

POS Entry Mode - Field 0054

• Value 01 - Manual/Key Entry

• Value 05 - EMV

• Value 07 - Contactless Chip Card

• Value 80 - EMV fall back to swipe|

• Value 90 - Magnetic Stripe

• Value 91- - Contactless Mag Stripe

Compliance Data Value - Field 0738

• This field contains the compliance data required to process Credential on File transactions. The value is returned in the API response of the transaction that established the COF. This value must be retained by the merchant POS.

• The stored value must be provided on in the API request by the POS on all transactions using the COF.

When Establishing a COF

• API Request – Not Present

• API Response – Compliance Data Value - Merchant POS must retain for all transactions using a COF

When Using a COF

• API Request

Compliance Data Value retained from field 0738 of the Original Authorization Transaction Response when the COF was Established.

• API Response

• Compliance Data Value is possibly a different value from the request.

• Merchant does not need to store this value.