eCommerce 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 cardholder-initiated stored credential transaction (COF) provides better visibility between the merchant and cardholder. The COF transaction category introduces Scheduled COF and Unscheduled COF transaction types. These types of transactions also update card brand rules, including merchant disclosure requirements.

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

  • Industry-specific (delayed, no-show, incremental).

  • Recurring billing and installment payments.

  • Cardholder-initiated stored credential transaction that does not occur on a fixed schedule.

Recurring billing makes use of COF and allows merchants to offer a recurring billing service to customers.

note

While Credential on File integrations are not third party processor specific, if a merchant changes third party processor with already established Credentials on File, it is advised that the merchant re-establish those Credentials on File with the new third party processor. 

Direct Marketing COF and Related Transaction Scenarios

Direct marketing COF transactions are indicated by fields 0712 (Charge description) and 0190 (eCommerce Indicator), 0738 (Recurring compliance data), 0054 (POS entry mode), and 0723 (Recurring payment status).

MOTO - Establish a Credential on File

Scenario

Cardholder and Merchant agree to establish a Credential on File and perform the initial MOTO authorization transaction. The COF may be used for future transactions initiated by the cardholder or merchant for the purchase of goods or services. This includes single purchases, recurring payments or installment payments.

Example

Cardholder makes a purchase over the phone and agrees to place their card on file with the merchant for future transactions.

Tran TypeField 0723
F = First Payment to Establish Credential on file
Field 0738Field
0712 and 0190
Field
0713
and
0714
Field 0047
position 5
Field
0054
Initiated
by
Reason
COF Established
Sale(02)
Single MOTO
FNot Present1A01CardholderUnscheduled
Sale (02) - RecurringFNot Present2901CardholderRecurring
Sale (02) - InstallmentFNot Present3Installment
Number
and Count
901CardholderInstallment
Auth Only (01)
Single MOTO
FNot Present1A01CardholderUnscheduled
Auth Only (01)
Recurring
FNot Present2901CardholderRecurring
Auth Only (01)
Installment
FNot Present3Installment
Number/Count
901CardholderInstallment
Zero-dollar Auth Only (01)
Unscheduled
FNot Present1A01CardholderUnscheduled
Zero-dollar Auth Only (01)
Recurring
FNot Present2901CardholderRecurring
Zero-dollar Auth Only (01)
Installment
FNot Present3Installment
Number/Count
901CardholderInstallment

MOTO - Use a Credential on File

Scenario

Cardholder or Merchant initiates a transaction using the established COF.

Example

Cardholder makes a single MOTO purchase using their existing COF.

Merchant initiates a recurring or installment payment using the existing COF based on an agreement with the cardholder.

Tran TypeField 0723
S=Subsequent Payment
U = Unscheduled Payment
Field 0738Field 0712
and 0190
Field 0713
and 0714
Field 0047
position 5
Field 0054Initiated
by
Reason
COF Used
Auth Only (01)
Single MOTO
UValue from Original Transaction Response1A01CardholderUnscheduled
Sale (02)
Single MOTO
UValue from Original Transaction Response1A01CardholderUnscheduled
Sale (02)
Recurring
SValue from Original Transaction2901MerchantRecurring
Sale (02)
Installment
SValue from Original Transaction Response3Installment Number/Count901MerchantInstallment
Auth Only (01)
Single MOTO
SValue from Original Transaction Response1A01MerchantUnscheduled
Auth Only (01)
Recurring
SValue from Original Transaction Response2901MerchantRecurring
Auth Only (01)
Installment
SValue from Original Transaction Response3Installment Number/Count901MerchantInstallment

Scenario

Merchant initiates an Incremental Authorization.

Example

Merchant requires an additional authorization amount for an item or service purchased, an incremental authorization is performed using the COF.

Tran TypeField 0723
S=Subsequent Payment
Field 0738Field 0712
and 0190
Field 0047
position 5
Field 0054Initiated
by
Reason
COF Used
Incremental Auth (75)SValue from Original Transaction Response1401MerchantUnscheduled

Scenario

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

Example

  • Cardholder cancels an item after purchase was made and an amount is to be refunded.

  • Merchant has overcharged for a previous item purchased or service provided.

Tran TypeField 0723
S=Subsequent Payment
U=Unscheduled Payment
Field 0738Field 0712
and 0190
Field 0047
position 5
Field 0054Initiated
by
Reason
COF Used
Return (09)SValue from Original Transaction Response1A01MerchantUnscheduled
Return (09)UValue from Original Transaction Response1A01CardholderUnscheduled

Scenario

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.

Tran TypeField 0723
F=First Payment to Establish Credential on File
S=Subsequent Payment
U=Unscheduled Payment
Field 0738Field 0047
position 5
Field 0054Initiated
by
Reason
COF Used
Prior Authorization (07)Same as initial Authorization Only (01)Value from Original Transaction ResponseSame as initial Authorization Only (01)01MerchantSame as Initial Authorization Only (01)

Scenario

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

Examples

  • 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.

Tran TypeField 0723Field 0738Field 0712
and 0190
Field 0713
and 0714
Field Field 0047
position 5
Field 0054Initiated
by
Reason
COF Used
Full Reversal (61), Partial Reversal (76), Void Sale (11), Void Return (17)Same as OriginalValue from Original Transaction ResponseSame as OriginalSame as Original01Same as OriginalSame as Original

eCommerce – Establish a COF

Scenario

Cardholder establishes a Credential on File on the Merchant’s website and performs the initial eCommerce authorization transaction. The COF may be used for future transactions initiated by the cardholder or merchant for the purchase of goods or services. This includes single purchases, recurring payments or installment payments.

Example

Cardholder makes a purchase on a website and agrees to place their card on file with the merchant for future transactions.

Tran TypeField 0723
F=First Payment to Establish Credential on File
Field 0738Field 0712
and 0190
Field 0713
and 0714
Field Field 0047
position 5
Field 0054Initiated
by
Reason
COF Used
Sale (02)
eCommerce
FNot present7A01CardholderUnscheduled
Auth Only (01)
eCommerce
FNot present7A01CardholderUnscheduled
Sale (02)
eCommerce
FNot Present7901CardholderRecurring
Auth Only (01)
eCommerce
FNot Present7901CardholderRecurring
Sale (02)
eCommerce
FNot Present7Installment Number
and Count Installment
901CardholderInstallment
Auth Only (01)
eCommerce
FNot Present7Installment Number
and Count
901CardholderInstallment
Sale (02)
eCommerce 3DS Authenticated
FNot Present5A01CardholderUnscheduled
Auth Only (01)
eCommerce 3DS Authenticated
FNot Present5901CardholderUnscheduled
Sale (02)
eCommerce 3DS Authenticated – Recurring
FNot Present5901CardholderRecurring
Auth Only (01)
eCommerce 3DS Authenticated - Recurring
FNot Present5901CardholderRecurring
Sale (02)
eCommerce 3DS Authenticated – Installment
FNot Present5Installment Number
and Count
901CardholderInstallment
Auth Only (01)
eCommerce 3DS Authenticate - Installment
FNot Present5Installment Number
and Count
901CardholderInstallment
Sale (02) - eCommerce
3DS Non-Authenticated
FNot Present6A01CardholderUnscheduled
Auth Only (01)
eCommerce Non-Authenticated
FNot Present6A01CardholderUnscheduled
Sale (02)
eCommerce 3DS Non-Authenticated - Recurring
FNot Present6901CardholderRecurring
Sale (02)
eCommerce 3DS Non-Authenticated – Installment
FNot Present6Installment Number
and Count
901CardholderInstallment
Auth Only (01)
eCommerce Non-Authenticated
Installment
FNot Present6Installment Number
and Count
901CardholderInstallment
Zero-dollar Auth Only (01)
eCommerce – Unscheduled
FNot Present7A01CardholderUnscheduled
Zero-dollar Auth Only (01)
eCommerce – Recurring
FNot Present7901CardholderRecurring
Zero-dollar Auth Only
(010 – eCommerce - Installment )
FNot Present7Installment Number
and Count
901CardholderInstallment

eCommerce - Use a Credential on File

Scenario

Cardholder or Merchant initiates a transaction using the established COF.

Examples

Cardholder makes a single eCommerce purchase using their existing COF.

Merchant initiates a recurring or installment payment using the existing COF based on an agreement with the cardholder.

Tran TypeField 0723
S=Subsequent Payment
U=Unscheduled Payment
Field 0738Field 0712
and 0190
Field 0713
and 0714
Field 0305Field 0047
position 5
Field 0054Initiated
by
Reason
COF Used
Sale (02) – eCommerceUValue from Original Transaction Response7A01CardholderUnscheduled
Auth Only (01)
eCommerce
UValue from Original Transaction Response7A01CardholderUnscheduled
Sale (02)
eCommerce
SValue from Original Transaction Response7A01MerchantUnscheduled
Auth Only (01)
eCommerce
SValue from Original Transaction Response7A01MerchantUnscheduled
Sale (02)
eCommerce – Recurring
SValue from Original Transaction Response7901MerchantRecurring
Auth Only (01) eCommerce
Recurring
SValue from Original Transaction Response7901MerchantRecurring
Sale (02)
eCommerce – Installment
SValue from Original Transaction Response7Installment Number
and Count
901MerchantInstallment
Auth Only (01)
eCommerce Installment
SValue from Original Transaction Response7Installment Number
and Count
901MerchantInstallment

Scenario

Merchant initiates an Incremental Authorization.

Example

Merchant requires an additional authorization amount for an item or service purchased, an incremental authorization is performed using the COF.

Tran TypeField 0723
S=Subsequent Payment
Field 0738Field 0712
and 0190
Field 0047
position 5
Field 0054Initiated
by
Reason
COF Used
Incremental Auth (75)SValue from Original Transaction Response7401MerchantUnscheduled

Scenario

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

Example

  • Cardholder cancels an item after purchase was made and an amount is to be refunded.

  • Merchant has overcharged for a previous item purchased or service provided.

Tran TypeField 0723
S=Subsequent Payment
U=Unscheduled Payment
Field 0738Field 0712
and 0190
Field 0047
position 5
Field 0054Initiated
by
Reason
COF Used
Return (09)SValue from Original Transaction Response7A01MerchantUnscheduled
Return (09)UValue from Original Transaction Response7A01CardholderUnscheduled

Scenario

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.

Tran TypeField 0723
F=First Payment to Establish Credential on File
S=Subsequent Payment
U=Unscheduled Payment
U=Unscheduled Payment
Field 0738Field 0047
position 5
Field 0054Initiated
by
Reason
COF Used
Prior Authorization (07)Same as initial Authorization Only (01)Value from Original Transaction ResponseSame as initial Authorization Only (01)01MerchantSame as initial Authorization Only (01)

Scenario

Merchant initiates a Reversal or Void of a previous COF transaction

Examples

  • 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.

Tran TypeField 0723
F=First Payment to Establish Credential on File
S=Subsequent Payment
Field 0738Field 0712 and 0190Field 0047
position 5
Field 0054Initiated
by
Reason
COF Used
Full Reversal (61), Partial Reversal (76), Void Sale (11), Void Return (17)Same as OriginalValue from Original Transaction ResponseSame as OriginalSame as Original01Same as OriginalSame as Original

POS Data Code - Field 0047 Position 5 – Cardholder Presence

Cardholder Present Value

  • 0 = Cardholder present

Cardholder Not Present Values

  • 1 = Cardholder not present (reason not specified)

  • 3 = Cardholder not present, telephone order

  • 4 = Cardholder not present, Industry Practice

  • 5 = Cardholder not present, e-Commerce

  • A = Cardholder not present, Standing Authorization - Unscheduled

  • 9 = Cardholder not present, Standing Authorization – Recurring or Installment

POS Entry Mode - Field 0054

Entry Mode of the Transaction

  • 01 = Manual/Key Entry

  • 05 = EMV

  • 07 = Contactless Chip Card

  • 80 = EMV fall back to swipe

  • 90 = Magnetic Stripe

  • 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 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

    • Possibly a different value from the request.

    • Merchant does not need to store this value.

important

When attempting to establish a COF, if a value is not returned in field 0738, the COF response was not established. The merchant must treat this and any future transactions for this card as non COF transactions. In this case, do not send 0723 and 0738 on those future transactions.