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.

Sale (02) Single MOTO

  • Field 0723 - F (First Payment to Establish Credential on file)
  • Field 0738 - Not Present
  • Field 0712 and 0190 - 1
  • Field 0713 and 0714
  • Field 0047 position 5 - A
  • Field 0054 - 01
  • Initiated by - Cardholder
  • Reason COF Established - Unscheduled

Sale (02) Recurring

  • Field 0723 - F (First Payment to Establish Credential on file)
  • Field 0738 - Not Present
  • Field 0712 and 0190 - 2
  • Field 0713 and 0714
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Initiated by - Cardholder
  • Reason COF Established - Recurring

Sale (02) Installment

  • Field 0723 - F (First Payment to Establish Credential on file)
  • Field 0738 - Not Present
  • Field 0712 and 0190 - 3
  • Field 0713 and 0714 - Installment Number and Count
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Initiated by - Cardholder
  • Reason COF Established - Installment

Auth Only (01) Single MOTO

  • Field 0723 - F (First Payment to Establish Credential on file)
  • Field 0738 - Not Present
  • Field 0712 and 0190 - 1
  • Field 0713 and 0714
  • Field 0047 position 5 - A
  • Field 0054 - 01
  • Initiated by - Cardholder
  • Reason COF Established - Unscheduled

Auth Only (01) Recurring

  • Field 0723 - F (First Payment to Establish Credential on file)
  • Field 0738 - Not Present
  • Field 0712 and 0190 - 2
  • Field 0713 and 0714
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Initiated by - Cardholder
  • Reason COF Established - Recurring

Auth Only (01) Installment

  • Field 0723 - F (First Payment to Establish Credential on file)
  • Field 0738 - Not Present
  • Field 0712 and 0190 - 1
  • Field 0713 and 0714
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Initiated by - Cardholder
  • Reason COF Established - Installment

Zero-dollar Auth Only (01) Unscheduled

  • Field 0723 - F (First Payment to Establish Credential on file)
  • Field 0738 - Not Present
  • Field 0712 and 0190 - 1
  • Field 0713 and 0714
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Initiated by - Cardholder
  • Reason COF Established - Unscheduled

Zero-dollar Auth Only (01) Recurring

  • Field 0723 - F (First Payment to Establish Credential on file)
  • Field 0738 - Not Present
  • Field 0712 and 0190 - 3
  • Field 0713 and 0714 - Installment Number/Count
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Initiated by - Cardholder
  • Reason COF Established - Recurring

Zero-dollar Auth Only (01) Installment

  • Field 0723 - F (First Payment to Establish Credential on file)
  • Field 0738 - Not Present
  • Field 0712 and 0190 - 3
  • Field 0713 and 0714 - Installment Number/Count
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Initiated by - Cardholder
  • Reason COF Established - Installment

The example below shows 723 = F which establishes a Credential on File. In the response you will see 738 with a value that must be retained for any subsequent Credential on File transactions where 723 = S or 723 = U.

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.

Auth Only (01) Single MOTO

  • Field 0723 - U (Unscheduled Payment)
  • Field 0738 - Value from Original Transaction Response
  • Field 0712 and 0190 - 1
  • Field 0713 and 0714
  • Field 0047 position 5 - A
  • Field 0054 - 01
  • Initiated by - Cardholder
  • Reason COF Established - Unscheduled

Sale (02) Single MOTO

  • Field 0723 - U (Unscheduled Payment)
  • Field 0738 - Value from Original Transaction Response
  • Field 0712 and 0190 - 1
  • Field 0713 and 0714
  • Field 0047 position 5 - A
  • Field 0054 - 01
  • Initiated by - Cardholder
  • Reason COF Established - Unscheduled

Sale (02) Recurring

  • Field 0723 - S (Subsequent Payment)
  • Field 0738 - Value from Original Transaction Response
  • Field 0712 and 0190 - 2
  • Field 0713 and 0714
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Initiated by - Merchant
  • Reason COF Established - Recurring

Sale (02) Installment

  • Field 0723 - S (Subsequent Payment)
  • Field 0738 - Value from Original Transaction Response
  • Field 0712 and 0190 - 3
  • Field 0713 and 0714 Installment Number/Count
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Initiated by - Merchant
  • Reason COF Established - Installment

Auth Only (01) Single MOTO

  • Field 0723 - S (Subsequent Payment)
  • Field 0738 - Value from Original Transaction Response
  • Field 0712 and 0190 - 1
  • Field 0713 and 0714
  • Field 0047 position 5 - A
  • Field 0054 - 01
  • Initiated by - Merchant
  • Reason COF Established - Unscheduled

Auth Only (01) Recurring

  • Field 0723 - S (Subsequent Payment)
  • Field 0738 - Value from Original Transaction Response
  • Field 0712 and 0190 - 2
  • Field 0713 and 0714 2
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Initiated by - Merchant
  • Reason COF Established - Recurring

Auth Only (01) Installment

  • Field 0723 - S (Subsequent Payment)
  • Field 0738 - Value from Original Transaction Response
  • Field 0712 and 0190 - 3
  • Field 0713 and 0714 - Installment Number/Count
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Initiated by - Merchant
  • Reason COF Established - 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.

Incremental Auth (75)

  • Field 0723 - S (Subsequent Payment)
  • Field 0738 - Value from Original Transaction Response
  • Field 0712 and 0190 - 1
  • Field 0047 position 5 - 4
  • Field 0054 - 01
  • Initiated by - Merchant
  • Reason COF Established - 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.

Return (09)

  • Field 0723 - S (Subsequent Payment)
  • Field 0738 - Value from Original Transaction Response
  • Field 0712 and 0190 - 1
  • Field 0047 position 5 - A
  • Field 0054 - 01
  • Initiated by - Merchant
  • Reason COF Established - Unscheduled

Return (09)

  • Field 0723 - U (Unscheduled Payment)
  • Field 0738 - Value from Original Transaction Response
  • Field 0712 and 0190 - 1
  • Field 0047 position 5 - A
  • Field 0054 - 01
  • Initiated by - Cardholder
  • Reason COF Established - 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.

Prior Authorization (07)

  • Field 0723 - Same as initial Authorization Only (01)
  • Field 0738 - Value from Original Transaction Response
  • Field 0047 position 5 - Same as initial Authorization (01)
  • Field 0054 - 01
  • Initiated by - Merchant
  • Reason COF Established - 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.

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 0712 and 190 - Same as Original
  • Field 0713 and 0714
  • Field 0047 position 5 - Same as Original
  • Field 0054 - 01
  • Initiated by - Same as Original
  • Reason COF Used - 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.

Sale (02) eCommerce

  • Field 0723 - F
  • Field 0738 - Not Present
  • Field 0712 and 190 - 7
  • Field 0713 and 0714
  • Field 0047 position 5 - A
  • Field 0054 - 01
  • Initiated by - Cardholder
  • Reason COF Used - Unscheduled

Auth Only (01) eCommerce

  • Field 0723 - F
  • Field 0738 - Not Present
  • Field 0712 and 190 - 7
  • Field 0713 and 0714
  • Field 0047 position 5 - A
  • Field 0054 - 01
  • Initiated by - Cardholder
  • Reason COF Used - Unscheduled

Sale (02) eCommerce

  • Field 0723 - F
  • Field 0738 - Not Present
  • Field 0712 and 190 - 7
  • Field 0713 and 0714 - Installment Number and Count
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Initiated by - Cardholder
  • Reason COF Used - Installment

Auth Only (01) eCommerce

  • Field 0723 - F
  • Field 0738 - Not Present
  • Field 0712 and 190 - 7
  • Field 0713 and 0714 - Installment Number and Count
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Initiated by - Cardholder
  • Reason COF Used - Installment

Sale (02) eCommerce

  • Field 0723 - F
  • Field 0738 - Not Present
  • Field 0712 and 190 - 7
  • Field 0713 and 0714 - Installment Number and Count Installment
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Initiated by - Cardholder
  • Reason COF Used - Installment

Auth Only (01) eCommere

  • Field 0723 - F
  • Field 0738 - Not Present
  • Field 0712 and 190 - 7
  • Field 0713 and 0714 - Installment Number and Count Installment
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Initiated by - Cardholder
  • Reason COF Used - Installment

Sale (02) eCommerce 3DS Authenticated

  • Field 0723 - F
  • Field 0738 - Not Present
  • Field 0712 and 190 - 5
  • Field 0713 and 0714
  • Field 0047 position 5 - A
  • Field 0054 - 01
  • Initiated by - Cardholder
  • Reason COF Used - Unscheduled

Auth Only (01) eCommerce 3DS Authenticated

  • Field 0723 - F
  • Field 0738 - Not Present
  • Field 0712 and 190 - 5
  • Field 0713 and 0714
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Initiated by - Cardholder
  • Reason COF Used - Unscheduled

Sale (02) eCommerce 3DS Authenticated - Recurring

  • Field 0723 - F
  • Field 0738 - Not Present
  • Field 0712 and 190 - 5
  • Field 0713 and 0714
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Initiated by - Cardholder
  • Reason COF Used - Recurring

Auth Only (01) eCommerce 3DS Authenticated - Recurring

  • Field 0723 - F
  • Field 0738 - Not Present
  • Field 0712 and 190 - 5
  • Field 0713 and 0714
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Initiated by - Cardholder
  • Reason COF Used - Recurring

Sale (02) eCommerce 3DS Authenticated - Installment

  • Field 0723 - F
  • Field 0738 - Not Present
  • Field 0712 and 190 - 5
  • Field 0713 and 0714 - Installment Number and Count
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Initiated by - Cardholder
  • Reason COF Used - Installment

Auth Only (01) eCommerce Authenticated Installment

  • Field 0723 - F
  • Field 0738 - Not Present
  • Field 0712 and 190 - 5
  • Field 0713 and 0714 - Installment Number and Count
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Initiated by - Cardholder
  • Reason COF Used - Installment

Auth Only (01) eCommerce 3DS Authenticate - Installment

  • Field 0723 - F
  • Field 0738 - Not Present
  • Field 0712 and 190 - 5
  • Field 0713 and 0714 - Installment Number and Count
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Initiated by - Cardholder
  • Reason COF Used - Installment

Sale (02) - eCommerce 3DS Non-Authenticated

  • Field 0723 - F
  • Field 0738 - Not Present
  • Field 0712 and 190 - 6
  • Field 0713 and 0714 -
  • Field 0047 position 5 - A
  • Field 0054 - 01
  • Initiated by - Cardholder
  • Reason COF Used - Unscheduled

Sale (02) - eCommerce 3DS Non-Authenticated - Installment

  • Field 0723 - F
  • Field 0738 - Not Present
  • Field 0712 and 190 - 6
  • Field 0713 and 0714 - Installment Number and Count
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Initiated by - Cardholder
  • Reason COF Used - Installment

Zero-dollar Auth Only (01) - eCommerce - Unscheduled

  • Field 0723 - F
  • Field 0738 - Not Present
  • Field 0712 and 190 - 7
  • Field 0713 and 0714
  • Field 0047 position 5 - 9A
  • Field 0054 - 01
  • Initiated by - Cardholder
  • Reason COF Used - Unscheduled

Zero-dollar Auth Only (01) - eCommerce - Recurring

  • Field 0723 - F
  • Field 0738 - Not Present
  • Field 0712 and 190 - 7
  • Field 0713 and 0714
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Initiated by - Cardholder
  • Reason COF Used - Recurring

Zero-dollar Auth Only (01) - eCommerce - Installment

  • Field 0723 - F
  • Field 0738 - Not Present
  • Field 0712 and 190 - 7
  • Field 0713 and 0714 Installment Number and Count
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Initiated by - Cardholder
  • Reason COF Used - 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.

Sale (02) eCommerce

  • Field 723 – U
  • Field 0738 - Value from Original Transaction Response
  • Field 0712 and 190 - 7
  • Field 713 and 0714
  • Field 305
  • Field 0047 position 5 - A
  • Field 0054 - 01
  • Intiated by - Cardholder
  • Reason COF Used - Unscheduled

Auth Only (01) eCommerce

  • Field 723 – U
  • Field 0738 - Value from Original Transaction Response
  • Field 0712 and 190 - 7
  • Field 713 and 0714
  • Field 305
  • Field 0047 posiiton 5 - A
  • Field 0054 - 01
  • Intiated by - Cardholder
  • Reason COF Used - Unscheduled

Sale Only (02) eCommerce

  • Field 723 – S
  • Field 0738 - Value from Original Transaction Response
  • Field 0712 and 190 - 7
  • Field 713 and 0714
  • Field 305
  • Field 0047 posiiton 5 - A
  • Field 0054 - 01
  • Intiated by - Cardholder
  • Reason COF Used - Unscheduled

Auth Only (02) eCommerce

  • Field 723 – S
  • Field 0738 - Value from Original Transaction Response
  • Field 0712 and 190 - 7
  • Field 713 and 0714
  • Field 305
  • Field 0047 position 5 - A
  • Field 0054 - 01
  • Intiated by - Merchant
  • Reason COF Used - Unscheduled

Sale Only (02) eCommerce

  • Field 723 – S
  • Field 0738 - Value from Original Transaction Response
  • Field 0712 and 190 - 7
  • Field 713 and 0714
  • Field 305
  • Field 0047 position 5 - A
  • Field 0054 - 01
  • Intiated by - Merchant
  • Reason COF Used - Unscheduled

Auth Only (01) eCommerce

  • Field 723 – S
  • Field 0738 - Value from Original Transaction Response
  • Field 0712 and 190 - 7
  • Field 713 and 0714
  • Field 305
  • Field 0047 position 5 - A
  • Field 0054 - 01
  • Intiated by - Merchant
  • Reason COF Used - Unscheduled

Sale (02) eCommerce - Recurring

  • Field 723 – S
  • Field 0738 - Value from Original Transaction Response
  • Field 0712 and 190 - 7
  • Field 713 and 0714
  • Field 305
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Intiated by - Merchant
  • Reason COF Used - Recurring

Sale (02) eCommerce - Installment

  • Field 723 – S
  • Field 0738 - Value from Original Transaction Response
  • Field 0712 and 190 - 7
  • Field 713 and 0714 - Installment Number and Count
  • Field 305
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Intiated by - Merchant
  • Reason COF Used - Installment

Auth Only (01) eCommerce - Installment

  • Field 723 – S
  • Field 0738 - Value from Original Transaction Response
  • Field 0712 and 190 - 7
  • Field 713 and 0714 - Installment Number and Count
  • Field 305
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Intiated by - Merchant
  • Reason COF Used - 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.

Incremental Auth (75)

  • Field 723 – S
  • Field 0738 - Value from Original Transaction Response
  • Field 0712 and 190 - 7
  • Field 0047 position 5 - 4
  • Field 0054 - 01
  • Intiated by - Merchant
  • Reason COF Used - 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.

Return (09)

  • Field 723 – S
  • Field 0738 - Value from Original Transaction Response
  • Field 0712 and 190 - 7
  • Field 0047 position 5 - A
  • Field 0054 - 01
  • Intiated by - Merchant
  • Reason COF Used - Unscheduled

Return (09)

  • Field 723 – U
  • Field 0738 - Value from Original Transaction Response
  • Field 0712 and 190 - 7
  • Field 0047 position 5 - A
  • Field 0054 - 01
  • Intiated by - Cardholder
  • Reason COF Used - 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.

Prior Authorization (07)

  • Field 723 – U
  • Field 0738 - Same as initial Authorization Only (01)
  • Field 0712 and 190 - Value from Original Transaction Response
  • Field 0047 position 5 - Same as initial Authorization Only (01)
  • Field 0054 - 01
  • Intiated by - Merchant
  • Reason COF Used - 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.

Full Reversal (61), Partical Reversal (76), Void Sale (11), Void Return (17)

  • Field 723 – Same as Original
  • Field 0738 - Value from Original Transaction Response
  • Field 0712 and 190 - Same as Original
  • Field 0047 position 5 - Same as Original
  • Field 0054 - 01
  • Intiated by - Same as Original
  • Reason COF Used - Same as Original

Sale (02) eCommerce

  • Field 723 – U
  • Field 0738 - Value from Original Transaction Response
  • Field 0712 and 190 - 7
  • Field 713 and 0714
  • Field 305
  • Field 0047 position 5 - A
  • Field 0054 - 01
  • Intiated by - Cardholder
  • Reason COF Used - Unscheduled

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.

Examples

Establish Credential on File

This example request shows 723 = F which represents establishing a Credential on File.

In the response, you’ll see 738 with a value that must be retained for any subsequent COF transitions, that’s where 723 = S or 723 = U.

Request

0001,02<– Transaction type –>
0002,100.00<– Transaction amount –>
0003,412493XXXXXX9990<– Acct number –>
0004,1025<– Card exp date MMYY –>
0007,87954322<– Reference number –>
0047,1;0;0;0;2;0;1;0;0;1;1;0;2;4<– POS data code –>
0050,123<– CVV2/CVC2/CID Information –>
0054,01<– POS entry mode –>
0070,87654321<– Customer code. Merchant-assigned code to identify customer. Default to field 7 –>
0071,1<– Tax included indicator –>
0072,7.00< – Tax amount –>
0109,00000003<– Terminal ID –>
0110,SDC88888<– Cashier ID –>
0115,010<– Transaction qualifier –>
0190,1<– eCommerce indicator –>
0647,1<– Partial auth acceptance –>
0700,33777<– Billing zip code –>
0701,8005 Serena Drive<– Billing street address –>
0711,123125<– Shipping date MMDDYY –>
0712,1<– Charge description –>
0715,1234567<– Order number –>
0716,33777<– Ship to zip code –>
0717,COMPUTER<– Item 1 text –>
0720,123;1;100.00<– Item code 1 –>
0723,F<– Recurring payment status. Req if establishing or using a COF –>
0732,P<– Electronic goods indicator –>
8002,DEVTSTQA<– Location name –>
8006,DEVTST<– Chain code –>

Response

0001,02<– Transaction type –>
0002,100.00<– Transaction amount –>
0003,************9990<– Acct number –>
0004,1025<– Card exp date MMYY –>
0006,CV1064<– Authorization code –>
0007,10016551<– Reference number –>
0009,001<– Host batch number –>
0030,1<– Online indicator –>
0032,090617<– Auth trans date MMDDYY –>
0033,095130<– Auth trans time HHMMSS –>
0034,V<– Auth characteristics indicator –>
0035,4928<– Validation code –>
0036,117262949890813<– Transaction identifier –>
0037,4<– Authorizer –>
0040,U<– Compliance data –>
0043,100382<– System trace audit number –>
0047,1;0;0;0;2;0;1;0;0;1;1;0;2;4<– POS data code –>
0049,A<– Card product result code –>
0050,***<– CVV2/CVC2/CID Information –>
0054,01<– POS entry mode –>
0056,1<– CVV2/CVC2/CID presence indicator –>
0070,87654321<– Customer code. Merchant-assigned code to identify customer. Default to field 7 –>
0071,1<– Tax included indicator –>
0072,7.00< – Tax amount –>
0109,00000003<– Terminal ID –>
0110,SDC88888<– Cashier ID –>
0112,400<– Processor ID –>
0115,010<– Transaction qualifier –>
0125,919095130<– Retrieval reference number –>
0126,0<– Track indicator –>
0129,1<– Compliance data –>
0130,100.00<– Total auth amt –>
0140,USD<– Merchant currency code –>
0190,1<– eCommerce indicator –>
0632,100.00<– Account balance –>
0647,1<– Partial auth acceptance –>
0651,0000000<– Auxiliary TPP Reversal Data –>
0700,33777<– Billing zip code –>
0701,8005 Serena Drive<– Billing street address –>
0711,123125<– Shipping date MMDDYY –>
0712,1<– Charge description –>
0715,1234567<– Order number –>
0716,33777<– Ship to zip code –>
0717,COMPUTER<– Item 1 text –>
0720,123;1;100.00<– Item code 1 –>
0723,F<– Recurring pymnt status. Req if establishing or using a COF –>
0732,P<– Electronic goods indicator –>
0738,922328A0180827103630602035VE<– Recurring compliance data. Req on input request if using a COF. Retain output response when establishing a COF –>
1000,VI<– Card type –>
1001,VISA<– Card name –>
1003,0000<– Elavon gateway response code –>
1004,APPROVAL<– Host response message –>
1005,0017340008024792213374<– Merchant number –>
1008,************9990<– Masked account number –>
1009,AA<– Host response code –>
1010,COMPLETE<– Elavon response msg –>
1012,0007<– Elavon batch number –>
1015,X<– Host AVS result code –>
1020,Y<– Gateway AVS response field –>
1200,0000AA<– Issuer network info –>
4747,010100<– Third party interface POS data code –>
7007,1117262498908589<– Fusebox transaction identifier –>
8002,DEVTSTQA<– Location name –>
8006,DEVTST<– Chain code –>

Using a Credential on File

This example request shows 723 = S which represents using a Credential on File.

In the response, you’ll see 738 with a value that must be retained for any subsequent COF transitions, that’s where 723 = S or 723 = U.

Request

0001,02<– Transaction type –>
0002,100.00<– Transaction amount –>
0003,4724XXXXXXXX9990<– Acct number –>
0004,1025<– Card exp date MMYY –>
0007,87954322<– Reference number –>
0047,1;0;0;0;2;0;1;0;0;1;1;0;2;4<– POS data code –>
0050,123<– CVV2/CVC2/CID Information –>
0054,01<– POS entry mode –>
0070,87654321<– Customer code. Merchant-assigned code to identify customer. Default to field 7 –>
0071,1<– Tax included indicator –>
0072,7.00< – Tax amount –>
0109,00000003<– Terminal ID –>
0110,SDC88888<– Cashier ID –>
0115,010<– Transaction qualifier –>
0190,1<– eCommerce indicator –>
0647,1<– Partial auth acceptance –>
0700,33777<– Billing zip code –>
0701,8005 Serena Drive<– Billing street address –>
0711,123125<– Shipping date MMDDYY –>
0712,1<– Charge description –>
0715,1234567<– Order number –>
0716,33777<– Ship to zip code –>
0717,COMPUTER<– Item 1 text –>
0720,123;1;100.00<– Item code 1 –>
0723,F<– Recurring payment status. Req if establishing or using a COF –>
0732,P<– Electronic goods indicator –>
8002,DEVTSTQA<– Location name –>
8006,DEVTST<– Chain code –>

Response

0001,02<– Transaction type –>
0002,100.00<– Transaction amount –>
0003,************9990<– Acct number –>
0004,1025<– Card exp date MMYY –>
0006,CV1064<– Authorization code –>
0007,10016551<– Reference number –>
0009,001<– Host batch number –>
0030,1<– Online indicator –>
0032,090617<– Auth trans date MMDDYY –>
0033,095130<– Auth trans time HHMMSS –>
0034,V<– Auth characteristics indicator –>
0035,4928<– Validation code –>
0036,117262949890813<– Transaction identifier –>
0037,4<– Authorizer –>
0040,U<– Compliance data –>
0043,100382<– System trace audit number –>
0047,1;0;0;0;2;0;1;0;0;1;1;0;2;4<– POS data code –>
0049,A<– Card product result code –>
0050,***<– CVV2/CVC2/CID Information –>
0054,01<– POS entry mode –>
0056,1<– CVV2/CVC2/CID presence indicator –>
0070,87654321<– Customer code. Merchant-assigned code to identify customer. Default to field 7 –>
0071,1<– Tax included indicator –>
0072,7.00< – Tax amount –>
0109,00000003<– Terminal ID –>
0110,SDC88888<– Cashier ID –>
0112,400<– Processor ID –>
0115,010<– Transaction qualifier –>
0125,919095130<– Retrieval reference number –>
0126,0<– Track indicator –>
0129,1<– Compliance data –>
0130,100.00<– Total auth amt –>
0140,USD<– Merchant currency code –>
0190,1<– eCommerce indicator –>
0632,100.00<– Account balance –>
0647,1<– Partial auth acceptance –>
0651,0000000<– Auxiliary TPP Reversal Data –>
0700,33777<– Billing zip code –>
0701,8005 Serena Drive<– Billing street address –>
0711,123125<– Shipping date MMDDYY –>
0712,1<– Charge description –>
0715,1234567<– Order number –>
0716,33777<– Ship to zip code –>
0717,COMPUTER<– Item 1 text –>
0720,123;1;100.00<– Item code 1 –>
0723,F<– Recurring pymnt status. Req if establishing or using a COF –>
0732,P<– Electronic goods indicator –>
0738,922328A0180827103630602035VE<– Recurring compliance data. Req on input request if using a COF. Retain output response when establishing a COF –>
1000,VI<– Card type –>
1001,VISA<– Card name –>
1003,0000<– Elavon gateway response code –>
1004,APPROVAL<– Host response message –>
1005,0017340008024792213374<– Merchant number –>
1008,************9990<– Masked account number –>
1009,AA<– Host response code –>
1010,COMPLETE<– Elavon response msg –>
1012,0007<– Elavon batch number –>
1015,X<– Host AVS result code –>
1020,Y<– Gateway AVS response field –>
1200,0000AA<– Issuer network info –>
4747,010100<– Third party interface POS data code –>
7007,1117262498908589<– Fusebox transaction identifier –>
8002,DEVTSTQA<– Location name –>
8006,DEVTST<– Chain code –>

Use COF - Unscheduled

This example request shows 723 = F which represents establishing a Credential on File.

In the response, you’ll see 738 with a value that must be retained for any subsequent COF transitions, that’s where 723 = S or 723 = U.