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.

error_outline
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 Type Field 0723
F = First Payment to Establish Credential on file
Field 0738 Field
0712 and 0190
Field
0713
and
0714
Field 0047
position 5
Field
0054
Initiated
by
Reason
COF Established
Sale(02)
Single MOTO
F Not Present 1 A 01 Cardholder Unscheduled
Sale (02) - Recurring F Not Present 2 9 01 Cardholder Recurring
Sale (02) - Installment F Not Present 3 Installment
Number
and Count
9 01 Cardholder Installment
Auth Only (01)
Single MOTO
F Not Present 1 A 01 Cardholder Unscheduled
Auth Only (01)
Recurring
F Not Present 2 9 01 Cardholder Recurring
Auth Only (01)
Installment
F Not Present 3 Installment
Number/Count
9 01 Cardholder Installment
Zero Dollar Auth Only (01)
Unscheduled
F Not Present 1 A 01 Cardholder Unscheduled
Zero Dollar Auth Only (01)
Recurring
F Not Present 2 9 01 Cardholder Recurring
Zero Dollar Auth Only (01)
Installment
F Not Present 3 Installment
Number/Count
9 01 Cardholder Installment

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 Type Field 0723
S=Subsequent Payment
U = Unscheduled Payment
Field 0738 Field 0712
and 0190
Field 0713
and 0714
Field 0047
position 5
Field 0054 Initiated
by
Reason
COF Used
Auth Only (01)
Single MOTO
U Value from Original Transaction Response 1 A 01 Cardholder Unscheduled
Sale (02)
Single MOTO
U Value from Original Transaction Response 1 A 01 Cardholder Unscheduled
Sale (02)
Recurring
S Value from Original Transaction 2 9 01 Merchant Recurring
Sale (02)
Installment
S Value from Original Transaction Response 3 Installment Number/Count 9 01 Merchant Installment
Auth Only (01)
Single MOTO
S Value from Original Transaction Response 1 A 01 Merchant Unscheduled
Auth Only (01)
Recurring
S Value from Original Transaction Response 2 9 01 Merchant Recurring
Auth Only (01)
Installment
S Value from Original Transaction Response 3 Installment Number/Count 9 01 Merchant Installment

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 Type Field 0723
S=Subsequent Payment
Field 0738 Field 0712
and 0190
Field 0047
position 5
Field 0054 Initiated
by
Reason
COF Used
Incremental Auth (75) S Value from Original Transaction Response 1 4 01 Merchant Unscheduled

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 Type Field 0723
S=Subsequent Payment
U=Unscheduled Payment
Field 0738 Field 0712
and 0190
Field 0047
position 5
Field 0054 Initiated
by
Reason
COF Used
Return (09) S Value from Original Transaction Response 1 A 01 Merchant Unscheduled
Return (09) U Value from Original Transaction Response 1 A 01 Cardholder Unscheduled

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 Type Field 0723
F=First Payment to Establish Credential on File
S=Subsequent Payment
U=Unscheduled Payment
Field 0738 Field 0047
position 5
Field 0054 Initiated
by
Reason
COF Used
Prior Authorization (07) Same as initial Authorization Only (01) Value from Original Transaction Response Same as initial Authorization Only (01) 01 Merchant Same 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 Type Field 0723 Field 0738 Field 0712
and 0190
Field 0713
and 0714
Field Field 0047
position 5
Field 0054 Initiated
by
Reason
COF Used
Full Reversal (61), Partial Reversal (76), Void Sale (11), Void Return (17) Same as Original Value from Original Transaction Response Same as Original Same as Original 01 Same as Original Same 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 Type Field 0723
F=First Payment to Establish Credential on File
Field 0738 Field 0712
and 0190
Field 0713
and 0714
Field Field 0047
position 5
Field 0054 Initiated
by
Reason
COF Used
Sale (02)
eCommerce
F Not present 7 A 01 Cardholder Unscheduled
Auth Only (01)
eCommerce
F Not present 7 A 01 Cardholder Unscheduled
Sale (02)
eCommerce
F Not Present 7 9 01 Cardholder Recurring
Auth Only (01)
eCommerce
F Not Present 7 9 01 Cardholder Recurring
Sale (02)
eCommerce
F Not Present 7 Installment Number
and Count Installment
9 01 Cardholder Installment
Auth Only (01)
eCommerce
F Not Present 7 Installment Number
and Count
9 01 Cardholder Installment
Sale (02)
eCommerce 3DS Authenticated
F Not Present 5 A 01 Cardholder Unscheduled
Auth Only (01)
eCommerce 3DS Authenticated
F Not Present 5 9 01 Cardholder Unscheduled
Sale (02)
eCommerce 3DS Authenticated – Recurring
F Not Present 5 9 01 Cardholder Recurring
Auth Only (01)
eCommerce 3DS Authenticated - Recurring
F Not Present 5 9 01 Cardholder Recurring
Sale (02)
eCommerce 3DS Authenticated – Installment
F Not Present 5 Installment Number
and Count
9 01 Cardholder Installment
Auth Only (01)
eCommerce 3DS Authenticate - Installment
F Not Present 5 Installment Number
and Count
9 01 Cardholder Installment
Sale (02) - eCommerce
3DS Non-Authenticated
F Not Present 6 A 01 Cardholder Unscheduled
Auth Only (01)
eCommerce Non-Authenticated
F Not Present 6 A 01 Cardholder Unscheduled
Sale (02)
eCommerce 3DS Non-Authenticated - Recurring
F Not Present 6 9 01 Cardholder Recurring
Sale (02)
eCommerce 3DS Non-Authenticated – Installment
F Not Present 6 Installment Number
and Count
9 01 Cardholder Installment
Auth Only (01)
eCommerce Non-Authenticated
Installment
F Not Present 6 Installment Number
and Count
9 01 Cardholder Installment
Zero Dollar Auth Only (01)
eCommerce – Unscheduled
F Not Present 7 A 01 Cardholder Unscheduled
Zero Dollar Auth Only (01)
eCommerce – Recurring
F Not Present 7 9 01 Cardholder Recurring
Zero Dollar Auth Only
(010 – eCommerce - Installment )
F Not Present 7 Installment Number
and Count
9 01 Cardholder Installment

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 Type Field 0723
S=Subsequent Payment
U=Unscheduled Payment
Field 0738 Field 0712
and 0190
Field 0713
and 0714
Field 0305 Field 0047
position 5
Field 0054 Initiated
by
Reason
COF Used
Sale (02) – eCommerce U Value from Original Transaction Response 7 A 01 Cardholder Unscheduled
Auth Only (01)
eCommerce
U Value from Original Transaction Response 7 A 01 Cardholder Unscheduled
Sale (02)
eCommerce
S Value from Original Transaction Response 7 A 01 Merchant Unscheduled
Auth Only (01)
eCommerce
S Value from Original Transaction Response 7 A 01 Merchant Unscheduled
Sale (02)
eCommerce – Recurring
S Value from Original Transaction Response 7 9 01 Merchant Recurring
Auth Only (01) eCommerce
Recurring
S Value from Original Transaction Response 7 9 01 Merchant Recurring
Sale (02)
eCommerce – Installment
S Value from Original Transaction Response 7 Installment Number
and Count
9 01 Merchant Installment
Auth Only (01)
eCommerce Installment
S Value from Original Transaction Response 7 Installment Number
and Count
9 01 Merchant Installment

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 Type Field 0723
S=Subsequent Payment
Field 0738 Field 0712
and 0190
Field 0047
position 5
Field 0054 Initiated
by
Reason
COF Used
Incremental Auth (75) S Value from Original Transaction Response 7 4 01 Merchant Unscheduled

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 Type Field 0723
S=Subsequent Payment
U=Unscheduled Payment
Field 0738 Field 0712
and 0190
Field 0047
position 5
Field 0054 Initiated
by
Reason
COF Used
Return (09) S Value from Original Transaction Response 7 A 01 Merchant Unscheduled
Return (09) U Value from Original Transaction Response 7 A 01 Cardholder Unscheduled

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 Type Field 0723
F=First Payment to Establish Credential on File
S=Subsequent Payment
U=Unscheduled Payment
U=Unscheduled Payment
Field 0738 Field 0047
position 5
Field 0054 Initiated
by
Reason
COF Used
Prior Authorization (07) Same as initial Authorization Only (01) Value from Original Transaction Response Same as initial Authorization Only (01) 01 Merchant Same 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 Type Field 0723
F=First Payment to Establish Credential on FileS=Subsequent Payment
Field 0738 Field 0712 and 0190 Field 0047
position 5
Field 0054 Initiated
by
Reason
COF Used
Full Reversal (61), Partial Reversal (76), Void Sale (11), Void Return (17) Same as Original Value from Original Transaction Response Same as Original Same as Original 01 Same as Original Same 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.

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