Skip to main content

Fusebox

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. This transaction category introduces Scheduled 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.

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

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), 0739 (Credential on File - Initiation and Purpose Indicator), (0054 (POS entry mode), and 0723 (Recurring Payment Status).

MOTO - Establish a credential on file

Scenario
Cardholder and merchant agree to establish a COF 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.

Note: Values starting with F indicate cardholder-initiated transaction to establish a COF.

Sale (02) Single MOTO

  • Field 0723 - F (First payment to establish credential on file)
  • Field 0738 - Not present
  • Field 0739 - F101
  • Field 0712 and 0190 - 1
  • Field 0047 position 5 - A
  • Field 0054 - 01
  • Reason COF established - Unscheduled

Sale (02) Recurring

  • Field 0723 - F (First payment to establish credential on file)
  • Field 0738 - Not present
  • Field 0739 - F103
  • Field 0712 and 0190 - 2
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Reason COF established - Recurring

Sale (02) Installment

  • Field 0723 - F (First payment to establish credential on file)
  • Field 0738 - Not present
  • Field 0739 - F104
  • Field 0712 and 0190 - 3
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Reason COF established - Installment

Auth Only (01) Single MOTO

  • Field 0723 - F (First payment to establish credential on file)
  • Field 0738 - Not present
  • Field 0739 - F101
  • Field 0712 and 0190 - 1
  • Field 0047 position 5 - A
  • Field 0054 - 01
  • Reason COF established - Unscheduled

Auth Only (01) Recurring

  • Field 0723 - F (First payment to establish credential on file)
  • Field 0738 - Not present
  • Field 0739 - F103
  • Field 0712 and 0190 - 2
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Reason COF established - Recurring

Auth Only (01) Installment

  • Field 0723 - F (First payment to establish credential on file)
  • Field 0738 - Not present
  • Field 0739 - F104
  • Field 0712 and 0190 - 1
  • Field 0713 and 0714 - Installment Number/Count
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • 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 0739 - F101
  • Field 0712 and 0190 - 1
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • 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 0739 - F103
  • Field 0712 and 0190 - 3
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • 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 0739 - F104
  • Field 0712 and 0190 - 3
  • Field 0713 and 0714 - Installment Number/Count
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Reason COF established - 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.

Auth Only (01) Single MOTO

  • Field 0723 - U (Unscheduled Payment)
  • Field 0738 - Value from original transaction response
  • Field 0739 - C101
  • Field 0712 and 0190 - 1
  • Field 0047 position 5 - A
  • Field 0054 - 01
  • Reason COF established - Unscheduled

Sale (02) Single MOTO

  • Field 0723 - U (Unscheduled Payment)
  • Field 0738 - Value from original transaction response
  • Field 0739 - C101
  • Field 0712 and 0190 - 1
  • Field 0047 position 5 - A
  • Field 0054 - 01
  • Reason COF established - Unscheduled

Sale (02) Recurring

  • Field 0723 - S (Subsequent Payment)
  • Field 0738 - Value from original transaction response
  • Field 0739 - M101
  • Field 0712 and 0190 - 2
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Reason COF established - Recurring

Sale (02) Installment

  • Field 0723 - S (Subsequent Payment)
  • Field 0738 - Value from original transaction response
  • Field 0739 - M104
  • Field 0712 and 0190 - 3
  • Field 0713 and 0714- Installment Number/Count
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Reason COF established - Installment

Auth Only (01) Single MOTO

  • Field 0723 - S (Subsequent Payment)
  • Field 0738 - Value from original transaction response
  • Field 0739 - M101
  • Field 0712 and 0190 - 1
  • Field 0047 position 5 - A
  • Field 0054 - 01
  • Reason COF established - Unscheduled

Auth Only (01) Recurring

  • Field 0723 - S (Subsequent Payment)
  • Field 0738 - Value from original transaction response
  • Field 0739 - M102
  • Field 0712 and 0190 - 2
  • Field 0713 and 0714 2
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Reason COF established - Recurring

Auth Only (01) Installment

  • Field 0723 - S (Subsequent Payment)
  • Field 0738 - Value from original transaction response
  • Field 0739 - M104
  • Field 0712 and 0190 - 3
  • Field 0713 and 0714 - Installment Number/Count
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Reason COF established - Installment

Incremental Authorization (75)

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.

  • Field 0723 - S (Subsequent Payment)
  • Field 0738 - Value from original transaction response
  • Field 0739 - M101
  • Field 0712 and 0190 - 1
  • Field 0047 position 5 - 4
  • Field 0054 - 01
  • Reason COF established - Unscheduled

Return (09)

Scenario
Cardholder or merchant initiates a Return transaction using the established COF.

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

  • Field 0723 - S (Subsequent Payment)
  • Field 0738 - Value from original transaction response
  • Field 0739 - M101
  • Field 0740 -
  • Field 0712 and 0190 - 1
  • Field 0047 position 5 - A
  • Field 0054 - 01
  • Reason COF established - Unscheduled

Prior Authorization (07)

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.

  • Field 0723 - Same as initial Authorization Only (01)
  • Field 0738 - Value from original transaction response
  • Field 0739 - M101
  • Field 0047 position 5 - Same as initial Authorization (01)
  • Field 0054 - 01
  • Reason COF established - Same as Initial Authorization Only (01)

Reversal or Void

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 0739 - Same as Original
  • 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.

Note: Values starting with F indicate cardholder-initiated transaction to establish a COF.

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 0739 - F101
  • Field 0712 and 190 - 7
  • Field 0047 position 5 - A
  • Field 0054 - 01
  • Reason COF Used - Unscheduled

Auth Only (01) eCommerce

  • Field 0723 - F
  • Field 0738 - Not present
  • Field 0739 - F101
  • Field 0712 and 190 - 7
  • 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 0739 - F104
  • Field 0712 and 190 - 7
  • Field 0713 and 0714 - Installment Number/Count
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Reason COF Used - Installment

Auth Only (01) eCommerce

  • Field 0723 - F
  • Field 0738 - Not present
  • Field 0739 - F104
  • Field 0712 and 190 - 7
  • Field 0713 and 0714 - Installment Number/Count
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Reason COF Used - Installment

Sale (02) eCommerce

  • Field 0723 - F
  • Field 0738 - Not present
  • Field 0739 - F104
  • Field 0712 and 190 - 7
  • Field 0713 and 0714 - Installment Number/Count
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Reason COF Used - Installment

Auth Only (01) eCommerce

  • Field 0723 - F
  • Field 0738 - Not present
  • Field 0739 - F104
  • Field 0712 and 190 - 7
  • Field 0713 and 0714 - Installment Number/Count
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Reason COF Used - Installment

Sale (02) eCommerce 3DS Authenticated

  • Field 0723 - F
  • Field 0738 - Not present
  • Field 0739 - F101
  • Field 0712 and 190 - 5
  • Field 0047 position 5 - A
  • Field 0054 - 01
  • Reason COF Used - Unscheduled

Auth Only (01) eCommerce 3DS Authenticated

  • Field 0723 - F
  • Field 0738 - Not present
  • Field 0739 - F101
  • Field 0712 and 190 - 5
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Reason COF Used - Unscheduled

Sale (02) eCommerce 3DS Authenticated - Recurring

  • Field 0723 - F
  • Field 0738 - Not present
  • Field 0739 - F102
  • Field 0712 and 190 - 5
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Reason COF Used - Recurring

Auth Only (01) eCommerce 3DS Authenticated - Recurring

  • Field 0723 - F
  • Field 0738 - Not present
  • Field 0739 - F102
  • Field 0712 and 190 - 5
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Reason COF Used - Recurring

Sale (02) eCommerce 3DS Authenticated - Installment

  • Field 0723 - F
  • Field 0738 - Not present
  • Field 0739 - F104
  • Field 0712 and 190 - 5
  • Field 0713 and 0714 - Installment Number/Count
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Reason COF Used - Installment

Auth Only (01) eCommerce Authenticated Installment

  • Field 0723 - F
  • Field 0738 - Not present
  • Field 0739 - F104
  • Field 0712 and 190 - 5
  • Field 0713 and 0714 - Installment Number/Count
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Reason COF Used - Installment

Auth Only (01) eCommerce 3DS Authenticated - Installment

  • Field 0723 - F
  • Field 0738 - Not present
  • Field 0739 - F104
  • Field 0712 and 190 - 5
  • Field 0713 and 0714 - Installment Number/Count
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Reason COF Used - Installment

Sale (02) - eCommerce 3DS Non-Authenticated

  • Field 0723 - F
  • Field 0738 - Not present
  • Field 0739 - F101
  • Field 0712 and 190 - 6
  • Field 0047 position 5 - A
  • Field 0054 - 01
  • Reason COF Used - Unscheduled

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

  • Field 0723 - F
  • Field 0738 - Not present
  • Field 0739 - F104
  • Field 0712 and 190 - 6
  • Field 0713 and 0714 - Installment Number/Count
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Reason COF Used - Installment

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

  • Field 0723 - F
  • Field 0738 - Not present
  • Field 0739 - F101
  • Field 0712 and 190 - 7
  • Field 0047 position 5 - 9A
  • Field 0054 - 01
  • Reason COF Used - Unscheduled

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

  • Field 0723 - F
  • Field 0738 - Not present
  • Field 0739 - F102
  • Field 0712 and 190 - 7
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Reason COF Used - Recurring

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

  • Field 0723 - F
  • Field 0738 - Not present
  • Field 0739 - F104
  • Field 0712 and 190 - 7
  • Field 0713 and 0714 - Installment Number/Count
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • 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 0739 - C101
  • Field 0712 and 190 - 7
  • Field 305
  • Field 0047 position 5 - A
  • Field 0054 - 01
  • Reason COF Used - Unscheduled

Auth Only (01) eCommerce

  • Field 723 – U
  • Field 0738 - Value from original transaction response
  • Field 0739 - C101
  • Field 0712 and 190 - 7
  • Field 305
  • Field 0047 position 5 - A
  • Field 0054 - 01
  • Reason COF Used - Unscheduled

Sale Only (02) eCommerce

  • Field 723 – S
  • Field 0738 - Value from original transaction response
  • Field 0739 - C101
  • Field 0712 and 190 - 7
  • Field 305
  • Field 0047 position 5 - A
  • Field 0054 - 01
  • Reason COF Used - Unscheduled

Auth Only (02) eCommerce

  • Field 723 – S
  • Field 0738 - Value from original transaction response
  • Field 0739 - M101
  • Field 0712 and 190 - 7
  • Field 305
  • Field 0047 position 5 - A
  • Field 0054 - 01
  • Reason COF Used - Unscheduled

Sale Only (02) eCommerce

  • Field 723 – S
  • Field 0738 - Value from original transaction response
  • Field 0739 - M101
  • Field 0712 and 190 - 7
  • Field 305
  • Field 0047 position 5 - A
  • Field 0054 - 01
  • Reason COF Used - Unscheduled

Auth Only (01) eCommerce

  • Field 723 – S
  • Field 0738 - Value from original transaction response
  • Field 0739 - M101
  • Field 0712 and 190 - 7
  • Field 305
  • Field 0047 position 5 - A
  • Field 0054 - 01
  • Reason COF Used - Unscheduled

Sale (02) eCommerce - Recurring

  • Field 723 – S
  • Field 0738 - Value from original transaction response
  • Field 0739 - M102
  • Field 0712 and 190 - 7
  • Field 305
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Reason COF Used - Recurring

Sale (02) eCommerce - Installment

  • Field 723 – S
  • Field 0738 - Value from original transaction response
  • Field 0739 - M104
  • Field 0712 and 190 - 7
  • Field 713 and 0714 - Installment Number/Count
  • Field 305
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • Reason COF Used - Installment

Auth Only (01) eCommerce - Installment

  • Field 723 – S
  • Field 0738 - Value from original transaction response
  • Field 0739 - M104
  • Field 0712 and 190 - 7
  • Field 713 and 0714 - Installment Number/Count
  • Field 305
  • Field 0047 position 5 - 9
  • Field 0054 - 01
  • 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 0739 - M101
  • Field 0712 and 190 - 7
  • Field 0047 position 5 - 4
  • Field 0054 - 01
  • 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.

Merchant

Return (09)

  • Field 723 – S
  • Field 0738 - Value from original transaction response
  • Field 0739 - M101
  • Field 0712 and 190 - 7
  • Field 0047 position 5 - A
  • Field 0054 - 01
  • Reason COF Used - Unscheduled

Cardholder

Return (09)

  • Field 723 – U
  • Field 0738 - Value from original transaction response
  • Field 0739 - C101
  • Field 0712 and 190 - 7
  • Field 0047 position 5 - A
  • Field 0054 - 01
  • 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 0739 - M101
  • Field 0712 and 190 - Value from original transaction response
  • Field 0047 position 5 - Same as initial Authorization Only (01)
  • Field 0054 - 01
  • 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), Partial Reversal (76), Void Sale (11), Void Return (17)

  • Field 723 – Same as original
  • Field 0738 - Value from original transaction response
  • Field 0739 - Same as Original
  • Field 0712 and 190 - Same as Original
  • Field 0047 position 5 - Same as Original
  • Field 0054 - 01
  • Initiated by - Same as Original
  • Reason COF Used - Same as Original

Sale (02) eCommerce

  • Field 723 – U
  • Field 0738 - Value from original transaction response
  • Field 0739 - C101
  • Field 0712 and 190 - 7
  • Field 305
  • Field 0047 position 5 - A
  • Field 0054 - 01
  • 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 COF 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.

Credential on File Initiation and Purpose Indicator - Field 0739

This field indicates if cardholder or merchant initiated the COF transaction and for what purpose.

Valid values:
Initial card on file trans (First trans establishes COF)

  • F101 - Credential on File (ad hoc)
  • F102 - Standing order (variable amount and fixed frequency)
  • F103 - Subscription (fixed amount and frequency)
  • F104 - Installment

Cardholder initiated COF transactions (Cardholder uses established COF)

  • C101 - Credential on File (ad hoc)
  • C102 - Standing order (variable amount and fixed frequency)
  • C103 - Subscription (fixed amount and frequency)
  • C104 - Installment

Merchant initiated COF transactions (Merchant uses established COF)

  • M101 - Unscheduled Cred on File
  • M102 - Standing order (variable amount and fixed frequency)
  • M103 - Subscription (fixed amount and frequency)
  • M104 - Installment
  • M205 - Partial shipment
  • M206 - Related/delayed charge
  • M207 - No-show charge
  • M208 - Resubmission

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 transactions, that’s where 0723 = S or 0723 = U.

Request

API field/ValueDescription
0001,02Transaction type
0002,100.00Transaction amount
0003,412493XXXXXX9990Acct number
0004,1025Card exp date MMYY
0007,87954322Reference number
0047,1;0;0;0;2;0;1;0;0;1;1;0;2;4POS data code
0050,123CVV2/CVC2/CID Information
0054,01POS entry mode
0070,87654321Customer code. Merchant-assigned code to identify customer. Default to field 0007
0071,1Tax included indicator
0072,7.00<Tax amount
0109,00000003Terminal ID
0110,SDC88888Cashier ID
0115,010Transaction qualifier
0190,1eCommerce indicator
0647,1Partial auth acceptance
0700,33777Billing zip code
0701,8005Billing street address
0711,123125Shipping date MMDDYY
0712,1Charge description
0715,1234567Order number
0716,33777Ship to zip code
0717,COMPUTERItem 1 text
0720,123;1;100.00Item code 1
0723,FRecurring payment status. Req if establishing or using a COF
0732,PElectronic goods indicator
0739,F101COF Initiation and Purpose Indicator
8002,DEVTSTQALocation name
8006,DEVTSTChain code

Response

API field/ValueDescription
0001,02Transaction type
0002,100.00Transaction amount
0003,************9990Acct number
0004,1025Card exp date MMYY
0006,CV1064Authorization code
0007,10016551Reference number
0009,001Host batch number
0030,1Online indicator
0032,090617Auth trans date MMDDYY
0033,095130Auth trans time HHMMSS
0034,VAuth characteristics indicator
0035,4928Validation code
0036,117262949890813Transaction identifier
0037,4Authorizer
0040,UCompliance data
0043,100382System trace audit number
0047,1;0;0;0;2;0;1;0;0;1;1;0;2;4POS data code
0049,ACard product result code
0050,***CVV2/CVC2/CID Information
0054,01POS entry mode
0056,1CVV2/CVC2/CID presence indicator
0070,87654321Customer code. Merchant-assigned code to identify customer. Default to field 0007
0071,1Tax included indicator
0072,7.00Tax amount
0109,00000003Terminal ID
0110,SDC88888Cashier ID
0112,400Processor ID
0115,010Transaction qualifier
0125,919095130Retrieval reference number
0126,0Track indicator
0129,1Compliance data
0130,100.00Total auth amt
0140,USDMerchant currency code
0190,1eCommerce indicator
0632,100.00Account balance
0647,1Partial auth acceptance
0651,0000000Auxiliary TPP reversal data
0700,33777Billing zip code
0701,8005 Serena DriveBilling street address
0711,123125Shipping date MMDDYY
0712,1Charge description
0715,1234567Order number
0716,33777Ship to zip code
0717,COMPUTERItem 1 text
0720,123;1;100.00Item code 1
0723,FRecurring pymnt status. Req if establishing or using a COF
0732,PElectronic goods indicator
0738,922328A0180827103630602035VERecurring compliance data. Req in request if using a COF. Retain response when establishing a COF
0739,F101COF Initiation and Purpose Indicator
1000,VICard type
1001,VISACard name
1003,0000Elavon gateway response code
1004,APPROVALHost response message
1005,0017340008024792213374Merchant number
1008,************9990Masked account number
1009,AAHost response code
1010,COMPLETEElavon response msg
1012,0007Elavon batch number
1015,XHost AVS result code
1020,YGateway AVS response field
1200,0000AAIssuer network info
4747,010100Third party interface POS data code
7007,1117262498908589Fusebox transaction identifier
8002,DEVTSTQALocation name
8006,DEVTSTChain code

Using a credential on file

This example request shows 0723 = S which represents using a credential on file.

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

Request

API field/ValueDescription
0001,02Transaction type
0002,100.00Transaction amount
0003,4724XXXXXXXX9990Acct number
0004,1025Card exp date MMYY
0007,87954322Reference number
0047,1;0;0;0;2;0;1;0;0;1;1;0;2;4POS data code
0050,123CVV2/CVC2/CID Information
0054,01POS entry mode
0070,87654321Customer code. Merchant-assigned code to identify customer. Default to field 0007
0071,1Tax included indicator
0072,7.00Tax amount
0109,00000003Terminal ID
0110,SDC88888Cashier ID
0115,010Transaction qualifier
0190,1eCommerce indicator
0647,1Partial auth acceptance
0700,33777Billing zip code
0701,8005 Serena DriveBilling street address
0711,123125Shipping date MMDDYY
0712,1Charge description
0715,1234567Order number
0716,33777Ship to zip code
0717,COMPUTERItem 1 text
0720,123;1;100.00Item code 1
0723,SRecurring payment status. Required if establishing or using a COF
0739,C101COF Initiation and Purpose Indicator
0732,PElectronic goods indicator
8002,DEVTSTQALocation name
8006,DEVTSTChain code

Response

API field/ValueDescription
0001,02Transaction type
0002,100.00Transaction amount
0003,************9990Acct number
0004,1025Card exp date MMYY
0006,CV1064Authorization code
0007,10016551Reference number
0009,001Host batch number
0030,1Online indicator
0032,090617Auth trans date MMDDYY
0033,095130Auth trans time HHMMSS
0034,VAuth characteristics indicator
0035,4928Validation code
0036,117262949890813Transaction identifier
0037,4Authorizer
0040,UCompliance data
0043,100382System trace audit number
0047,1;0;0;0;2;0;1;0;0;1;1;0;2;4POS data code
0049,ACard product result code
0050,***CVV2/CVC2/CID Information
0054,01POS entry mode
0056,1CVV2/CVC2/CID presence indicator
0070,87654321Customer code. Merchant-assigned code to identify customer. Default to field 0007
0071,1Tax included indicator
0072,7.00Tax amount
0109,00000003Terminal ID
0110,SDC88888Cashier ID
0112,400Processor ID
0115,010Transaction qualifier
0125,919095130Retrieval reference number
0126,0Track indicator
0129,1Compliance data
0130,100.00Total auth amt
0140,USDMerchant currency code
0190,1eCommerce indicator
0632,100.00Account balance
0647,1Partial auth acceptance
0651,0000000Auxiliary TPP reversal data
0700,33777Billing zip code
0701,8005 Serena DriveBilling street address
0711,123125Shipping date MMDDYY
0712,1Charge description
0715,1234567Order number
0716,33777Ship to zip code
0717,COMPUTERItem 1 text
0720,123;1;100.00Item code 1
0723,SRecurring payment status. Required if establishing or using a COF
0732,PElectronic goods indicator
0738,922328A0180827103630602035VERecurring compliance data. Req in request if using a COF. Retain response when establishing a COF
0739,C101COF Initiation and Purpose Indicator
1000,VICard type
1001,VISACard name
1003,0000Elavon gateway response code
1004,APPROVALHost response message
1005,0017340008024792213374Merchant number
1008,************9990Masked account number
1009,AAHost response code
1010,COMPLETEElavon response msg
1012,0007Elavon batch number
1015,XHost AVS result code
1020,YGateway AVS response field
1200,0000AAIssuer network info
4747,010100Third party interface POS data code
7007,1117262498908589Fusebox transaction identifier
8002,DEVTSTQALocation name
8006,DEVTSTChain code

ON THIS PAGE

Elavon downloads and stores cookies on your device when you visit our website. We use these cookies to better understand and improve your browsing experience by identifying most visited pages, personalising content, and measuring site performance.

Cookie Settings