Structure of Log Files

Groups: All   Processing   Status   Debug  

Available Log Files for All-groups:


Log Files for All-groups:


cards-realtime.sts.authorization.log   
Added On:  08/14/14
Level:  Trace
Category:  cards-realtime.authorization
Status:  Active
Group:  processing
File Name:  cards-realtime.sts.authorization.log
Resource:  $app-home/jboss-7.4.0/standalone/log/processing/cards-realtime.sts.authorization.log
Legacy File Name:  
Сontains information about the processor's incoming requests and outgoing responses (STS)
Request Fields [Show Info]

ACTION_CODE, ADDR1, AUTH_REFERENCE, BUSINESS_TYPE, CHARGE_TRANSACTION_FK, CITY, EMAIL_ADDR, FIRST_NAME, ID, LAST_NAME, MERCHANT_ACCOUNT_CODE, MERCHANT_NUMBER, PHONE1, POINTS_AMOUNT, POS_ENTRY_MODE, RETAIL_TRANSACTION_CYCLE_FK, STATE, TERMINAL_ID, TICKET, TIP_AMOUNT, TRANS_TYPE, TRANSACTION_AMOUNT, TRANSACTION_ID, ZIP
Name Description
ACTION_CODE The Action_Code tells what type of transaction you are sending.

Reffer to the STS Provider's Specification for more detailes.
ADDR1 Cardholder's street address.
AUTH_REFERENCE Authorization number returned when response code = 00. Use this number for follow-on requests such as Void or Add Tip.
BUSINESS_TYPE R = Retail/Other;
F = Restaurant.
Default is R.
CHARGE_TRANSACTION_FK Reference to the entity that represents real-time financial transaction.
CITY Cardholder's City.
EMAIL_ADDR Cardholder's email address.
FIRST_NAME Cardholder's first name.
This field will have one space in it if the name is not in the database.
ID Identifier of the object used for references; auto-incremented integer value.
LAST_NAME Cardholder's last name.
This field will have one space in it if the name is not in the database.
MERCHANT_ACCOUNT_CODE Code of Merchant Account to which instance of this object is attributed to.
Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
MERCHANT_NUMBER Merchant number assigned by processor or MSP.
PHONE1 Cardholder's primary phone number.
POINTS_AMOUNT The amount of points of loyalty, present on card.

No Decimals implied.
Required for Action Codes 03 and 04.

Example: 20000 = 20 thousand.
POS_ENTRY_MODE S = Swiped;
M = Manual.

Required except for Action Code 12 (Totals Inquiry).
RETAIL_TRANSACTION_CYCLE_FK Reference to the entity that represents a group of real-time transactions which must be settled together.
STATE Cardholder's State or Provence.
TERMINAL_ID Terminal ID assigned by processor or MSP.
TICKET Ticket or invoice number from your system.
TIP_AMOUNT The amount of given tips.
Decimal number is required.

Example: $200.00.
TRANS_TYPE Default is N.

N = Non-loyalty;
L = Loyalty.

NA for transactions that don’t include a Points amount.
TRANSACTION_AMOUNT The amount of transaction.
Required for Action Codes 01, 02, 06, 07, 08 and 11.
Decimal number is required.

Example: $200.00.
TRANSACTION_ID This number is populated by the POS system (you) and is echoed back to you in the host response.
ZIP Cardholder's postal code.
Response Fields [Show Info]

ACTION_CODE, ADDR1, AMOUNT_BALANCE, APPROVED_AMOUNT, AUTH_REFERENCE, BUSINESS_TYPE, CHARGE_TRANSACTION_FK, CITY, EMAIL_ADDR, FIRST_NAME, ID, LAST_NAME, LIFE_POINTS_BALANCE, MERCHANT_ACCOUNT_CODE, MERCHANT_NUMBER, MISC_MESSAGE, PHONE1, POINTS_AMOUNT, POINTS_BALANCE, POS_ENTRY_MODE, RESPONSE_CODE, RESPONSE_TEXT, RETAIL_TRANSACTION_CYCLE_FK, STATE, TERMINAL_ID, TICKET, TIP_AMOUNT, TRANS_DATE_TIME, TRANS_TYPE, TRANSACTION_AMOUNT, TRANSACTION_ID, ZIP
Name Description
ACTION_CODE The Action_Code tells what type of transaction you are sending.

Reffer to the STS Provider's Specification for more detailes.
ADDR1 Cardholder's street address.
AMOUNT_BALANCE This value is the remaining balance.
APPROVED_AMOUNT Amount approved (Can be less than requested amount – partial approval.)
This field only appears in response to action code 19 transactions.
AUTH_REFERENCE Authorization number returned when response code = 00. Use this number for follow-on requests such as Void or Add Tip.
BUSINESS_TYPE R = Retail/Other;
F = Restaurant.
Default is R.
CHARGE_TRANSACTION_FK Reference to the entity that represents real-time financial transaction.
CITY Cardholder's City.
EMAIL_ADDR Cardholder's email address.
FIRST_NAME Cardholder's first name.
This field will have one space in it if the name is not in the database.
ID Identifier of the object used for references; auto-incremented integer value.
LAST_NAME Cardholder's last name.
This field will have one space in it if the name is not in the database.
LIFE_POINTS_BALANCE No implied decimal.
Only returned for loyalty transaction requests. Required for loyalty requests.

Example: 200 = two hundred.
MERCHANT_ACCOUNT_CODE Code of Merchant Account to which instance of this object is attributed to.
Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
MERCHANT_NUMBER Merchant number assigned by processor or MSP.
MISC_MESSAGE This field can be used to give the merchant additional messages to display on receipts, etc. i.e. a Rewards Message.
PHONE1 Cardholder's primary phone number.
POINTS_AMOUNT The amount of points of loyalty, present on card.

No Decimals implied.
Required for Action Codes 03 and 04.

Example: 20000 = 20 thousand.
POINTS_BALANCE No implied decimal.
Only returned for loyalty transaction requests. Required for loyalty requests.

Example: 200 = two hundred.
POS_ENTRY_MODE S = Swiped;
M = Manual.

Required except for Action Code 12 (Totals Inquiry).
RESPONSE_CODE Each two digit response code maps to a specific response, i.e.

00 = Approved/Captured.
01 = Decline/Error
RESPONSE_TEXT Text associated with the transaction approval or decline Response_Code.
RETAIL_TRANSACTION_CYCLE_FK Reference to the entity that represents a group of real-time transactions which must be settled together.
STATE Cardholder's State or Provence.
TERMINAL_ID Terminal ID assigned by processor or MSP.
TICKET Ticket or invoice number from your system.
TIP_AMOUNT The amount of given tips.
Decimal number is required.

Example: $200.00.
TRANS_DATE_TIME Fixed date (month, day, year) and time (hour, minute, second) of transaction.

MMDDYYhhmmss.
TRANS_TYPE Default is N.

N = Non-loyalty;
L = Loyalty.

NA for transactions that don’t include a Points amount.
TRANSACTION_AMOUNT The amount of transaction.
Required for Action Codes 01, 02, 06, 07, 08 and 11.
Decimal number is required.

Example: $200.00.
TRANSACTION_ID This number is populated by the POS system (you) and is echoed back to you in the host response.
ZIP Cardholder's postal code.
cards-realtime.mwe.authorization.log   
Added On:  09/26/14
Level:  Trace
Category:  cards-realtime.authorization
Status:  Active
Group:  processing
File Name:  cards-realtime.mwe.authorization.log
Resource:  $app-home/jboss-7.4.0/standalone/log/processing/cards-realtime.mwe.authorization.log
Legacy File Name:  
Сontains information about the processor's incoming requests and outgoing responses (MWE)
Request Fields [Show Info]

API_KEY, AUTH_CODE, AUTH_MESSAGE, AUTH_SETTLED_DATE, CAPTURE_AMOUNT, CARD_ID, CHARGE_TRANSACTION_FK, CUSTOM1, CUSTOM2, CUSTOM3, CUSTOMER_ADDRESS, CUSTOMER_CITY, CUSTOMER_COUNTRY, CUSTOMER_EMAIL, CUSTOMER_PHONE, CUSTOMER_POST_CODE, CUSTOMER_STATE, HASH, ID, MERCHANT_ACCOUNT_CODE, MERCHANT_UUID, METHOD, PAYMENT_CARD_NAME, REFUND_AMOUNT, RETAIL_TRANSACTION_CYCLE_FK, TRANSACTION_AMOUNT, TRANSACTION_CURRENCY, TRANSACTION_ID_REQUEST, TRANSACTION_PRODUCT, TRANSACTION_REFERENCE_ID
Name Description
API_KEY The value of this parameter is assigned to you by Merchant Warrior.
AUTH_CODE This field contain the upstream provider response data.
AUTH_MESSAGE Contains additional text information about the transaction.
AUTH_SETTLED_DATE This field contain the upstream provider response data.
CAPTURE_AMOUNT The amount of the capture.
CARD_ID A unique alphanumeric string returned by addCard, used to identify a specific card.
CHARGE_TRANSACTION_FK Reference to the entity that represents real-time financial transaction.
CUSTOM1 Freeform field. Returned as <custom1> in the XML response.
CUSTOM2 Freeform field. Returned as <custom2> in the XML response.
CUSTOM3 Freeform field. Returned as <custom3> in the XML response.
CUSTOMER_ADDRESS Customer's postal address.
CUSTOMER_CITY City of the customer's postal address.
CUSTOMER_COUNTRY Country of the customer's postal address.
CUSTOMER_EMAIL Customer's email address.
CUSTOMER_PHONE Customer's phone number.
CUSTOMER_POST_CODE Post code of the customer's postal address.
CUSTOMER_STATE State of the customer's postal address.
HASH The verifica1on hash is a combination of the MD5 of your API Passphrase, and specific parameters sent in the transaction.
ID Identifier of the object used for references; auto-incremented integer value.
MERCHANT_ACCOUNT_CODE Code of Merchant Account to which instance of this object is attributed to.
Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
MERCHANT_UUID The value of this parameter is assigned to you by Merchant Warrior.
METHOD This is case sensitive.
PAYMENT_CARD_NAME This must contain at the very least a space and no less than two characters. Only alphanumeric characters, hyphens, spaces and full stops are allowed.
REFUND_AMOUNT The amount of the refund.
RETAIL_TRANSACTION_CYCLE_FK Reference to the entity that represents a group of real-time transactions which must be settled together.
TRANSACTION_AMOUNT The amount of the transaction.
TRANSACTION_CURRENCY Currency in which the transaction is done.
TRANSACTION_ID_REQUEST An optional element that contains a unique user defined ID to identify the transaction. The Transaction ID will be returned in the Authorization Gateway response.

TRANSACTION_PRODUCT A product (or sale) description. This field’s primary purpose is to help the transaction be identfiable for reporting and accouning purposes.
TRANSACTION_REFERENCE_ID This is merchant’s unique reference ID for a transaction sent to Merchant Warrior. The main purpose of this ID is to verify the transaction via queryCard method in the event a valid response is not received.
Response Fields [Show Info]

API_KEY, AUTH_CODE, AUTH_MESSAGE, AUTH_RESPONSE_CODE, AUTH_SETTLED_DATE, CAPTURE_AMOUNT, CARD_ID, CHARGE_TRANSACTION_FK, CUSTOM1, CUSTOM2, CUSTOM3, CUSTOMER_ADDRESS, CUSTOMER_CITY, CUSTOMER_COUNTRY, CUSTOMER_EMAIL, CUSTOMER_PHONE, CUSTOMER_POST_CODE, CUSTOMER_STATE, HASH, ID, MERCHANT_ACCOUNT_CODE, MERCHANT_UUID, METHOD, PAYMENT_CARD_NAME, RECEIPT_NO, REFUND_AMOUNT, RESPONSE_CODE, RESPONSE_MESSAGE, RETAIL_TRANSACTION_CYCLE_FK, TRANSACTION_AMOUNT, TRANSACTION_CURRENCY, TRANSACTION_ID_REQUEST, TRANSACTION_ID_RESPONSE, TRANSACTION_PRODUCT, TRANSACTION_REFERENCE_ID
Name Description
API_KEY The value of this parameter is assigned to you by Merchant Warrior.
AUTH_CODE This field contain the upstream provider response data.
AUTH_MESSAGE Contains additional text information about the transaction.
AUTH_RESPONSE_CODE This field contain the upstream provider response data.
AUTH_SETTLED_DATE This field contain the upstream provider response data.
CAPTURE_AMOUNT The amount of the capture.
CARD_ID A unique alphanumeric string returned by addCard, used to identify a specific card.
CHARGE_TRANSACTION_FK Reference to the entity that represents real-time financial transaction.
CUSTOM1 Freeform field. Returned as <custom1> in the XML response.
CUSTOM2 Freeform field. Returned as <custom2> in the XML response.
CUSTOM3 Freeform field. Returned as <custom3> in the XML response.
CUSTOMER_ADDRESS Customer's postal address.
CUSTOMER_CITY City of the customer's postal address.
CUSTOMER_COUNTRY Country of the customer's postal address.
CUSTOMER_EMAIL Customer's email address.
CUSTOMER_PHONE Customer's phone number.
CUSTOMER_POST_CODE Post code of the customer's postal address.
CUSTOMER_STATE State of the customer's postal address.
HASH The verifica1on hash is a combination of the MD5 of your API Passphrase, and specific parameters sent in the transaction.
ID Identifier of the object used for references; auto-incremented integer value.
MERCHANT_ACCOUNT_CODE Code of Merchant Account to which instance of this object is attributed to.
Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
MERCHANT_UUID The value of this parameter is assigned to you by Merchant Warrior.
METHOD This is case sensitive.
PAYMENT_CARD_NAME This must contain at the very least a space and no less than two characters. Only alphanumeric characters, hyphens, spaces and full stops are allowed.
RECEIPT_NO
REFUND_AMOUNT The amount of the refund.
RESPONSE_CODE Contains a numeric bit that indicates one or many response messages.
RESPONSE_MESSAGE Contains text response to the transaction.
RETAIL_TRANSACTION_CYCLE_FK Reference to the entity that represents a group of real-time transactions which must be settled together.
TRANSACTION_AMOUNT The amount of the transaction.
TRANSACTION_CURRENCY Currency in which the transaction is done.
TRANSACTION_ID_REQUEST An optional element that contains a unique user defined ID to identify the transaction. The Transaction ID will be returned in the Authorization Gateway response.

TRANSACTION_ID_RESPONSE The <transactionID> returned for the initial transaction.
TRANSACTION_PRODUCT A product (or sale) description. This field’s primary purpose is to help the transaction be identfiable for reporting and accouning purposes.
TRANSACTION_REFERENCE_ID This is merchant’s unique reference ID for a transaction sent to Merchant Warrior. The main purpose of this ID is to verify the transaction via queryCard method in the event a valid response is not received.
HibernateDataService.log   
Added On:  10/20/14
Level:  Info
Category:  iapp.services.HibernateDataService
Status:  Active
Group:  status
File Name:  HibernateDataService.log
Resource:  $app-home/jboss-7.4.0/standalone/log/statistics/HibernateDataService.log
Legacy File Name:  hibernate-slow-queries.log
Сontains information about hibernate queries that took more than one second to execute.
HTTPFormGatesDebug.log   
Added On:  10/20/14
Level:  Debug
Category:  atlas.gates.HTTPFormGatesDebug
Status:  Active
Group:  debug
File Name:  HTTPFormGatesDebug.log
Resource:  $app-home/jboss-7.4.0/standalone/log/debug/HTTPFormGatesDebug.log
Legacy File Name:  http-gates.log
Contains information about incoming requests and outgoing responses of unicharge-api, including corresponding sensitive data.
reports.log   
Added On:  10/20/14
Level:  Debug
Category:  iapp.report
Status:  Active
Group:  status
File Name:  reports.log
Legacy File Name:  reports-access.log
Сontains specific information related to reports (parameters of the report generation, time when the report was generated, report generation issues, etc).
useraccess.log   
Added On:  10/20/14
Level:  Info
Category:  iapp.services.IappLoginModule
Status:  Active
Group:  status
File Name:  useraccess.log
Legacy File Name:  user-access.log
Сontains information about users' authentication to the system (was the login successful or not, issues that occurred while logging in, etc).
cards-realtime.vantiv-tandem.authorization.log   
Added On:  10/20/14
Level:  Trace
Category:  cards-realtime.authorization
Status:  Active
Group:  processing
File Name:  cards-realtime.vantiv-tandem.authorization.log
Resource:  $app-home/jboss-7.4.0/standalone/log/processing/cards-realtime.vantiv-tandem.authorization.log
Legacy File Name:  cards-realtime.vantiv.authorization.log
Сontains information about the processor's incoming requests and outgoing responses (vantiv-tandem)
Request Fields [Show Info]

, BIT03, BIT04, BIT07, BIT105, BIT106, BIT107, BIT109, BIT11, BIT110, BIT111, BIT112, BIT115, BIT12, BIT133, BIT134, BIT135, BIT136, BIT137, BIT22, BIT25, BIT32, BIT41, BIT42, BIT43, BIT60, BIT63, BIT65, BIT67, BIT70, BIT90, CHARGE_TRANSACTION_FK, G001, G009, G014, G015, G021, G023, IS_DEBIT_TRANSACTION, MERCHANT_ACCOUNT_CODE, MESSAGE_TYPE_IDENTIFIER, NETWORK_ROUTING, RETAIL_TRANSACTION_CYCLE_FK
Name Description
Clerk Number.

This eight-digit field appears in all controller requests that represent in-lane transactions. It identifies the employee associated with the transaction. If not applicable, the field should be zero filled.
BIT03 Processing Code.

May appear in the following message types:

  • 0100 and 0110 - Authorization request and response
  • 0200 and 0210 - Financial request and response
  • 0220 and 0230 - Financial request and response
  • 0400 - Unsolicited Reversal request (this is the Processing code of the original that is being reversed. The original processing code was ISO Format. This code will be its equivalent value in TPS format.)
  • 0410 - Reversal response
  • 0500 - Reconciliation request

Consists of three two-digit sub fields that indicate how the transaction specified by the message type affects the customer’s related account(s).

Note: The authorization service can update the "From" and "To" account information. The operating rules for the authorization service may require the terminal device to print the account information on the receipt.
BIT04 Transaction Amount.

This field may appear in the following message types:

  • 0100 Authorization request
  • 0110 Authorization response
  • 0200 Financial request
  • 0220 Financial request
  • 0400 Unsolicited Reversal Request

The nine-digit transaction amount field represents the monetary value associated with the cardholder’s authorization, debit, or credit transaction request. The amount is entered in the terminal as a seven-digit number and is always right justified and zero filled. This field does not include cash back.

  • For authorization reversals this field must contain the approved amount authorized from the original transaction.
  • For timeout scenarios where the approved amount is not known, populate this field with the original amount requested in the timed-out transaction.
  • For AVS verification only (Processing code 514000) request, this field must be zero filled.
  • For MasterCard and Discover Account Status Inquiry transactions this field must be zero-filled.
  • For Visa Product Eligibility Inquiry transactions this field must be zero-filled.
  • For EBT WIC purchases, this represents the amount of the transaction BEFORE any coupons or discounts are applied.
BIT07 Transmission Date and Time.

The transmission date and time field may appear in the following message types:
  • 0100 Check and financial authorization request (controller)
  • 0100 Partial reversal
  • 0110 Authorization response
  • 0200 Financial request (controller)
  • 0210 Financial response
  • 0220 Credit card prior authorization
  • 0400 Reversal (void) request (controller)
  • 0410 Reversal (void) response

In the host capture terminal messages this field represents the date and time that the transaction was processed by the host.
In the host capture controller messages this is the date/time at which the controller transmitted the transaction to the Tandem Online System. It is set by the controller.
In a 0400 reversal message, the date and time apply to the reversal/void request itself, not the original transaction.

The ten-digit field is in MMDDYYhhmm format, with the time portion expressed in 24-hour (military) notation. For example, 1114971346 represents Nov. 14, 1997, at 1:46 P.M.
BIT105 Contains several fields:
  • Additional Response Data/CVV2/AVS Result Code;
  • Payment Service Indicator;
  • Transaction Identifier Banknet/POSA SAF Ref. Num.;
  • VISA Validation Code.

Refer to the specification of the processor for more information.
BIT106 Cardholder Identification (AVS).

This 29-character field must appear in the 0100 authorization request or 0200 financial transaction request message when the Bit Map Type is 05, 06, 25, or 26. It contains the data used for address verification.

The field contains two data subfields:
The first 20 positions are the cardholder’s address data, left justified and space filled; the last nine positions contain the ZIP code. If the ZIP code is present, it must be either five or nine characters in length, left justified and padded with spaces if only five characters.
BIT107 Point-of-Service Device Capability Code.

This two-character field must appear in the following messages:

  • 0100 authorization request
  • 0200 financial request
  • 0220 financial request
  • 0400 reversal request

The field contains two subfields that indicate the type of POS device used and the device’s ability to read encoded data.
BIT109 P.O. Number/Customer Code.

This twenty-character field contains the purchase order number applicable to a financial transaction or the customer code associated with a purchase card. It is required in the following message types:

  • 0100 credit authorization only (Bit Map Type 21 or 25)
  • 0200 and 0220 credit card requests (Bit Map Types 21–26)
  • 0200 VISA POS check conversion request (Bit Map Type 16)
  • 0400 VISA POS check conversion request (Bit Map Type 16)
  • 0100 check verification/guarantee request (Bit Map Type 32)
  • 0200 check conversion request (Bit Map Type 32)

The field is optional in the 0200 financial request for a private-label (Bit Map Type 07) or fuel (Bit Map Type 09) sale.
BIT11 System Trace Audit Number (STAN).

The in-store controller creates this six-digit number at transaction time to uniquely identify the transaction. This field appears in every message type supported by the Tandem Online System and the instore controller.
BIT110 Tax Amount.

This nine-digit field appears in 0100 authorization requests and 0200 financial requests that apply to corporate or purchase credit cards.

It contains the dollar amount of tax included in the transaction, in the format 999999999. Sending a value of all 9’s (999999999) in the request message indicates that this is a non-taxable transaction. Sending a value of all 8’s (888888888) in the request message indicates that this is a tax-exempt transaction.

Note: For non-corporate/purchase cards, this data element can be sent as all zeroes.
BIT111 Additional Data, Private EBT.

This 15-byte field is conditional in the 0200 financial message. Present only when the processing code indicates an EBT transaction, it contains the voucher number required for clearing EBT voice authorizations.
BIT112 Card Sequence Number.

The three-digit card sequence number field is conditional in the 0200 financial request message when the processing code indicates an EBT transaction. The field is required only if the card has a generation number and the card was not swiped.

The card sequence number distinguishes between separate cards with the same primary account number.
BIT115 Trace Data 1.

In the host capture terminal message set, this 16-character field must appear in the 0800 (Bit Map Type 02) and 0810 (Bit Map Type 94) network management request and response when processing the line management test function (echo test).

The field is included in all controller messages as an echo field for the controller’s use.
The Tandem Online System echoes the data exactly as it was received.
BIT12 Local Transaction Date.

The six-digit transaction date appears in all request messages handled by the in-store controller; it indicates the date (MMDDYY) on which the transaction occurred at the point of sale.

In 0400 reversal/void requests, this field represents the transaction being voided; see 07 Transmission Date/Time.
In a Gift Card Completion message the Local Transaction Date must be populated with the Local Transaction Date received in the Gift Card Preauth approval message.
In an Unsolicited Reversal the Local Transaction Date must be populated with the Local Transaction Date received in the original Authorization request message.
BIT133 POSA Network ID.

This four-byte field defines the POSA network used to authorize the POSA transaction. This field must appear in all POSA transactions. POSA networks are:

  • “SWAY” Safeway
  • “INCM” InComm
  • “PRES” PreSolutions
  • “SVSG” Stored Value Systems
  • “VALU” ValueLink
  • “ “ Non POSA card (spaces)

If the merchant is processing POSA cards, but the point-of-sale system is unable to determine the POSA Network, then that merchant can only successfully process for a single POSA network. In this case, the POSA Network ID field must be set up at the point of sale to always indicate the merchant’s selected network (e.g. SWAY). The value should either be hard-coded into the system or set as a parameter. If the merchant also sells their own gift cards via non-POSA networks, then the BIN range(s) for the merchant’s gift cards must be registered with Vantiv, LLC (Tandem Onlines) for processing.

Notes: Merchants that do not participate in POSA need to fill the POSA Network ID field with spaces.
Contact Vantiv, LLC for current supported networks.

BIT134 POSA UPC Data.

This twenty-byte field contains the POSA scanned UPC (bar code data) on the card used to authorize the POSA prepaid transaction.
This field must appear in all POSA prepaid transactions
BIT135 POSA Stand-In indicator.

This one-byte field is used to indicate a POSA store and forward transaction request due to a merchant stand-in condition. Applicable to POSA activation and reload SAF transaction requests only. Use a value of “Y”, if the POS device has timed out or the host responds with response code “001” or “795” and load the POSA SAF reference number into field 136 of the request message. The POSA SAF Reference Number is returned in field 105.3 of every POSA response message, and should be retained for use in any SAF retransmission request.

When setting the POSA Stand-In indicator to “N”, the POSA SAF reference number must be initialized to spaces.
This field must appear in any POSA activation or reload SAF requests when the transaction is queued for re-transmission by the POS device.
BIT136 POSA SAF Reference Number.

This twelve-byte field contains a unique number generated by the host for each POSA prepaid transaction.

The host returns this value on every POSA prepaid transaction that is approved or declined (see field 105.3 – Transaction Identifier). In a Store-and-Forward scenario, where the transaction is queued for retransmission by the POS device this field contains the POSA SAF reference number of the original Activation/Reload transaction in the POSA prepaid request message. If a POSA device time out occurs no POSA SAF Reference Number is available then set the POSA SAF Reference Number to spaces and the POSA Stand-In Indicator (field 135) to a value of “Y”.
BIT137 Replacement Amount.

In a partial authorization reversal, the Replacement Amount reflects the corrected total amount of the authorization for the transaction. For a partial reversal, the Transaction Amount field must contain the original amount authorized. The host subtracts the Replacement Amount from the Transaction Amount to determine the amount being reversed. For timeout reversals, and for other cases where the original authorization is to be fully reversed, the replacement amount must be zero.

The replacement amount must not be equal to or greater than the transaction amount. Partial reversals are currently only supported for VISA and MasterCard payment types.
BIT22 Point-of-Service Entry Mode.

The three-digit POS entry mode field must appear in the following messages:

  • 0100 Authorization request
  • 0200 Financial request
  • 0220 Financial request

Contains two subfields that indicate the method used to enter the primary account number (PAN) and whether the POS terminal allows entry of personal identification numbers (PINs).
BIT25 Point-of-Service Condition Code.

The ten-digit POS condition code field must appear in the following messages:
  • 0100 Authorization request
  • 0200 Financial request
  • 0220 Financial request
  • 0400 Unsolicited reversal request

Contains four subfields that, together, identify the kind of terminal and indicate whether the customer and/or the customer’s credit card were present at the time of the transaction.
BIT32 Acquiring Institution Identification Code.

This four-digit field must appear in the following message types:

  • 0100 Authorization request
  • 0200 Financial request
  • 0220 Financial request
  • 0400 Reversal request
  • 0500 Reconciliation request
  • 0800 Network management request

The code (referred to in the Tandem Online Systems as the Bank ID) identifies the acquiring institution (i.e., merchant bank, merchant grouping, or merchants’ hierarchy) for the associated Card Acceptor ID Code (the Tandem Online Systems Merchant Number).
BIT41 Card Acceptor Terminal Identification.

The three-digit card acceptor terminal ID code (referred to as the Terminal ID in the Tandem Online System) identifies the terminal at the merchant (card acceptor) location at which the transaction was entered.
This field must appear in all transaction request messages.
BIT42 Card Acceptor Identification Code.

The 12-digit card acceptor ID code (referred to as the Merchant ID in the Tandem Online System) must appear in all transaction request messages. This field, in conjunction with the acquiring institution identification code (Field 32), uniquely identifies the merchant in the Tandem Online System.
BIT43 Lane Number.

This three-digit field appears in the following controller message types:

  • 0100 Authorization request
  • 0200 Financial request
  • 0220 Financial request
  • 0400 Reversal (void) request

It identifies the cashier location at which the transaction occurred.

Note: Of the 3 digit lane number only the right most two bytes are used. Lane numbers must be within the range of 01 to 99.
BIT60 Cash Back Amount.

This nine-digit field appears in the 0100 authorization and 0200 financial request messages. It represents the amount of money being given back to the cardholder. The entered amount can be up to seven digits; in the message it must be right-justified and padded with zeros to the full nine positions. This amount should not be included in the transaction amount field.

For AVS verification only (Processing code 514000) request, this field must be zero filled.
BIT63 Contains several fields:

  • Invoice/Folio Number.

  • This six-digit field appears in the 0200 and 0220 financial messages for those transactions (usually designated for specific card types) that use the extended prompts option. The field is required when settling American Express retail transactions. If the message also includes the P.O. Number/Customer Code field (bit 109), this field is ignored unless bit 109 is space-filled.

  • Item Code (from one to five)

  • These four-digit fields appear in the 0200 and 0220 financial messages for those transactions (usually designated for specific card types) that use the extended prompts option. These fields are used to cross reference a table in the Tandem Online Systems database that designates the type of merchandise purchased. Required when settling American Express retail transactions.
    BIT65 Authorization Identification Response.

    This six-character field appears in the following messages:
    • 0110 Authorization response (controller)
    • 0200 EBT voice authorization/voucher clear request
    • 0220 Financial request (prior authorized sale transactions) (controller)
    • 0210 Financial response (controller)
    • 0230 Financial response (controller)
    • 0410 Reversal response (controller)

    The auth ID response contains an authorization number assigned to the transaction by the authorizing institution. In all host capture terminal messages but the EBT voice-auth request, this data is in bit 38.
    BIT67 Extended Payment Code.

    The two-digit extended payment code field appears in the 0200 and 0220 financial request message. It pertains specifically to JCB transactions where the consumer can specify the number of installment payments they wish to make for each purchase.
    BIT70 Network Management Information Code.

    All request message types support the following codes:
    • 000 = Default (no key change required)
    • 101 = Key change requested
    • 900-999 = Log transaction as given error.

    The Tandem Online System will record this transaction as an error transaction with the given code and the error server name as ‘SLHBAS’.

    Full reversals support the following value:
  • 400 = Suspected Fraud

  • In addition, message type 0800 supports the following values:
    • 360 = Terminal validation
    • 380 = FleetOne Batch Close
    BIT90 Original Data Elements.

    This eight-character field must appear in 0400 reversals and the nine-character field must appear in 0100 authorization reversal request messages. It contains the retrieval reference number from the original transaction response, and helps identify the original transaction for reversal processing.
    For timeout reversals where the original transaction's retrieval reference number is not known, populate this field with zeroes.
    CHARGE_TRANSACTION_FK Reference to the entity that represents real-time financial transaction.
    G001 Merchant Reference Data.

    Used in settlement to uniquely identify a merchant’s transaction. The Merchant Reference Number can be present in any 0100, 0200, or 0220 authorization request transaction.

    The Draft locator ID field is a unique value assigned by the POS device for each transaction.
    The Merchant reference number should be a unique value assigned by the POS device for each transaction.
    G009 Optional Processing Indicators.

    It is a series of codes that identify terminal capability, terminal environment. Refer to the specification of the processor for more information.
    G014 Original Authorization Retrieval Reference Number.

    Provides a way to send an original authorization retrieval reference number.

    This field should be used when sending a 0220 force post. It should also be used with all full and partial reversals. This enables the Host to retrieve the original authorization information (if still available) to supplement settlement data.

    Note: Must be numeric. Any invalid data will be ignored by the host.
    G015 Additional Amounts Request.

    This 20-byte field contains information — up to six amount sets.

    The presence of this group is mandatory and indicates to the host this is an IIAS transaction request.
    The presence of G015 is optional in an EBT WIC authorization request transaction.

    IIAS transaction request:
    Amount type 4S must be present. The sum of the additional amount type fields must not exceed the total healthcare amount (4S). Any amount type can only appear once.

    EBT WIC transaction request:
    Only a single amount type 52 can be present in an EBT WIC authorization request transaction.

    Refer to the specification of the processor for more information.
    G021 Fee Data.

    Use this group to send convenience fee data. Please refer to card association regulations for details regarding fee usage.

    Convenience fees can be sent in a single transaction (Fee Type = 1) or in two transactions (Fee Types 2 and 3).

  • For a single convenience fee transaction (Fee Type 1):
  • put the fee in the Fee Amount field of this group and also include it with the Transaction Amount.

  • For a two-step convenience fee transaction:
  • 1. The first transaction must have Fee Type = 2 and Fee Amount = zero.
    2. The second transaction must have Fee Type = 3 and both Transaction Amount and Fee Amount containing the convenience fee.

    VISA CPS/Debit tax fees must be sent in a two-step transaction (Fee Types 2 and 3).
  • For a two-step VISA CPS/Debit tax transaction convenience fee transaction:
  • 1. The first transaction must have Fee Type = 2 and Fee Amount = zero.
    2. The second transaction must have Fee Type = 3 and both Transaction Amount and Fee Amount containing the convenience fee.

  • VISA limits the convenience fee amount for CPS/Debit Tax fee payment transactions, it is recommended to verify the fee limits and other terms during the merchant registration process.
  • G023 Restaurant Tip Amount.

    Used in conjunction with a sale or adjustment message to log the tip amount received. The cents portion is the last two positions, and the decimal point is implied.

    Must be numeric. Invalid data will result in a declined transaction. This group is ignored if the merchant is not configured on the host as Restaurant industry.
    IS_DEBIT_TRANSACTION Indicates whether the processed transaction is debit type.
    MERCHANT_ACCOUNT_CODE Code of Merchant Account to which instance of this object is attributed to.
    Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
    The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
    MESSAGE_TYPE_IDENTIFIER Appears in every message type supported by the Tandem Online Systems host capture message set.

    The first two digits identify the class of the message (authorization, financial, reversal, and so on); the last two digits represent the message function (request or response).
    NETWORK_ROUTING Сan be used to route the transaction through the front-end communications network (for example, CompuServe’s Routing Identifier – CRI). It appears in all messages, but is ignored by the Tandem Online System.
    RETAIL_TRANSACTION_CYCLE_FK Reference to the entity that represents a group of real-time transactions which must be settled together.
    Response Fields [Show Info]

    , APPROVED_AMOUNT, BIT_MAP_TYPE, BIT03, BIT04, BIT04_AMOUNT, BIT07, BIT105, BIT105_AVS_RESULT_CODE, BIT105_PAYMENT_SERVICE_INDICATOR, BIT105_TRANSACTION_IDENTIFIER, BIT105_VISA_VALIDATION_CODE, BIT106, BIT107, BIT109, BIT11, BIT110, BIT111, BIT112, BIT12, BIT120_BATCH_NUMBER, BIT120_CARD_TYPE, BIT120_DEMO_MERCHANT_FLAG, BIT123_ERROR_TEXT, BIT123_RESPONSE_CODE, BIT124_WORKING_KEY, BIT128_ADDITIONAL_AMOUNTS, BIT13, BIT133, BIT134, BIT135, BIT136, BIT137, BIT22, BIT25, BIT32, BIT37_RETRIEVAL_REFERENCE_NUMBER, BIT41, BIT42, BIT43, BIT60, BIT63, BIT65, BIT65_AUTHORIZATION_IDENTIFICATION_RESPONSE, BIT67, BIT70, BIT90, CHARGE_TRANSACTION_FK, G001, G009, G014, G015, G021, G023, IS_DEBIT_TRANSACTION, IS_REVERSAL_APPLIED, MERCHANT_ACCOUNT_CODE, MESSAGE_TYPE_IDENTIFIER, NETWORK_ROUTING, R001, R006, R007, R008, R009, R999, RETAIL_TRANSACTION_CYCLE_FK
    Name Description
    Clerk Number.

    This eight-digit field appears in all controller requests that represent in-lane transactions. It identifies the employee associated with the transaction. If not applicable, the field should be zero filled.
    APPROVED_AMOUNT Approved amount of the transaction.
    BIT_MAP_TYPE Used in conjunction with the Message Type Identifier to determine which data elements are in the message being transmitted.
    BIT03 Processing Code.

    May appear in the following message types:

    • 0100 and 0110 - Authorization request and response
    • 0200 and 0210 - Financial request and response
    • 0220 and 0230 - Financial request and response
    • 0400 - Unsolicited Reversal request (this is the Processing code of the original that is being reversed. The original processing code was ISO Format. This code will be its equivalent value in TPS format.)
    • 0410 - Reversal response
    • 0500 - Reconciliation request

    Consists of three two-digit sub fields that indicate how the transaction specified by the message type affects the customer’s related account(s).

    Note: The authorization service can update the "From" and "To" account information. The operating rules for the authorization service may require the terminal device to print the account information on the receipt.
    BIT04 Transaction Amount.

    This field may appear in the following message types:

    • 0100 Authorization request
    • 0110 Authorization response
    • 0200 Financial request
    • 0220 Financial request
    • 0400 Unsolicited Reversal Request

    The nine-digit transaction amount field represents the monetary value associated with the cardholder’s authorization, debit, or credit transaction request. The amount is entered in the terminal as a seven-digit number and is always right justified and zero filled. This field does not include cash back.

    • For authorization reversals this field must contain the approved amount authorized from the original transaction.
    • For timeout scenarios where the approved amount is not known, populate this field with the original amount requested in the timed-out transaction.
    • For AVS verification only (Processing code 514000) request, this field must be zero filled.
    • For MasterCard and Discover Account Status Inquiry transactions this field must be zero-filled.
    • For Visa Product Eligibility Inquiry transactions this field must be zero-filled.
    • For EBT WIC purchases, this represents the amount of the transaction BEFORE any coupons or discounts are applied.
    BIT04_AMOUNT Amount.

    This field may appear in the following message types:

    • 0100 Authorization request
    • 0110 Authorization response
    • 0200 Financial request
    • 0220 Financial request
    • 0400 Unsolicited Reversal Request

    The nine-digit transaction amount field represents the monetary value associated with the cardholder’s authorization, debit, or credit transaction request. The amount is entered in the terminal as a seven-digit number and is always right justified and zero filled. This field does not include cash back.
    BIT07 Transmission Date and Time.

    The transmission date and time field may appear in the following message types:
    • 0100 Check and financial authorization request (controller)
    • 0100 Partial reversal
    • 0110 Authorization response
    • 0200 Financial request (controller)
    • 0210 Financial response
    • 0220 Credit card prior authorization
    • 0400 Reversal (void) request (controller)
    • 0410 Reversal (void) response

    In the host capture terminal messages this field represents the date and time that the transaction was processed by the host.
    In the host capture controller messages this is the date/time at which the controller transmitted the transaction to the Tandem Online System. It is set by the controller.
    In a 0400 reversal message, the date and time apply to the reversal/void request itself, not the original transaction.

    The ten-digit field is in MMDDYYhhmm format, with the time portion expressed in 24-hour (military) notation. For example, 1114971346 represents Nov. 14, 1997, at 1:46 P.M.
    BIT105 Contains several fields:
    • Additional Response Data/CVV2/AVS Result Code;
    • Payment Service Indicator;
    • Transaction Identifier Banknet/POSA SAF Ref. Num.;
    • VISA Validation Code.

    Refer to the specification of the processor for more information.
    BIT105_AVS_RESULT_CODE AVS Result Code.

    The field contains the CVV2 and address verification (AVS) result codes. Used for transactions where CVV2 and/or AVS was requested, it provides an additional indication that the card is being used by the person to which it was issued.

    The first character is the CVV2 result code, the second character is the AVS result code (space when the transaction does not qualify for AVS). Visa and MasterCard return CVV2/CVC2 response codes. The following tables list the CVV2 and AVS result codes.

    AVS RESULT CODE (POSITION 2)

    • A - Address Matches, ZIP does not
    • E - Error
    • G - International issuer not participating in AVS
    • N - Neither address nor ZIP matches
    • R - Retry, system unavailable or timed out
    • U - Issuer is unavailable
    • Y - Address and ZIP both match
    • Z - ZIP matches, address does not
    BIT105_PAYMENT_SERVICE_INDICATOR Payment Service Indicator.

    This single-character field must appear in the following message types:
    • 0100 EFT partial reversal request
    • 0110 Authorization response
    • 0220 Financial request (Bit Map Type 04, 24)
    • 0210 Financial response
    • 0230 Financial response
    • 0410 Reversal response

    For VISA, the field contains a code that indicates whether the authorization qualifies for PS 2000 processing. ‘N’ = not PS2000 qualified; other values are as documented by VISA.
    For MasterCard, the field contains a CVC (card validation character) compliance flag, used internally by the Tandem Online System.
    BIT105_TRANSACTION_IDENTIFIER Transaction Identifier Banknet/POSA SAF Ref. Num.

    (VISA)/Banknet Data (MC)/POSA SAF Reference Number This 15-character field must appear in the following message types:

    • 0100 EFT partial reversal request
    • 0110 Authorization response
    • 0220 Financial request (Bit Map Type 04, 24)
    • 0210 Financial response
    • 0230 Financial response
    • 0410 Reversal response

    The field will contain information provided by the authorizer.
    • For VISA CPS implementation, it is a unique identifier used to link together all related transactions authorized and cleared through VISANet. If the Payment Service Indicator (bit 105.2) is ‘A’ and this field is not all zeros, it may be printed on receipts to facilitate retrieval requests but is not required. The printing of the Transaction ID is required for e-Сommerce Transaction Receipts.
    • For POSA Prepaid, the field contains the POSA SAF Reference Number uniquely assigned by the host. This value occupies the first twelve positions left-justified space filled. The POS device should use this value to populate POSA SAF Reference Number (field 136) when sending a POSA SAF Activation/Reload transaction request message. POSA SAF requests also require that the POSA Stand-In Indicator (Field 135) be set to a value of “Y” in the transaction request message.
    • For 'MasterCard values, please, refer o the specification of the processor for more information.
    BIT105_VISA_VALIDATION_CODE VISA Validation Code.

    This four-character field must appear in the following message types:
    • 0100 EFT partial reversal request
    • 0110 Authorization response
    • 0220 Financial request (Bit Map Type 04, 24)
    • 0210 Financial response
    • 0230 Financial response
    • 0410 Reversal response

    For VISA transactions, the code in the field is used to determine the accuracy of the authorization data. It is generated by VISA using a VISA-proprietary algorithm based on the following request and response data fields.

    Primary Account Number Authorization Identification Response
    Transaction Amount Response Code
    Merchant Type Payment Service Indicator
    POS Entry Mode Code (positions 1-2) Transaction Identifier

    For MasterCard transactions, this field contains the Banknet date.
    BIT106 Cardholder Identification (AVS).

    This 29-character field must appear in the 0100 authorization request or 0200 financial transaction request message when the Bit Map Type is 05, 06, 25, or 26. It contains the data used for address verification.

    The field contains two data subfields:
    The first 20 positions are the cardholder’s address data, left justified and space filled; the last nine positions contain the ZIP code. If the ZIP code is present, it must be either five or nine characters in length, left justified and padded with spaces if only five characters.
    BIT107 Point-of-Service Device Capability Code.

    This two-character field must appear in the following messages:

    • 0100 authorization request
    • 0200 financial request
    • 0220 financial request
    • 0400 reversal request

    The field contains two subfields that indicate the type of POS device used and the device’s ability to read encoded data.
    BIT109 P.O. Number/Customer Code.

    This twenty-character field contains the purchase order number applicable to a financial transaction or the customer code associated with a purchase card. It is required in the following message types:

    • 0100 credit authorization only (Bit Map Type 21 or 25)
    • 0200 and 0220 credit card requests (Bit Map Types 21–26)
    • 0200 VISA POS check conversion request (Bit Map Type 16)
    • 0400 VISA POS check conversion request (Bit Map Type 16)
    • 0100 check verification/guarantee request (Bit Map Type 32)
    • 0200 check conversion request (Bit Map Type 32)

    The field is optional in the 0200 financial request for a private-label (Bit Map Type 07) or fuel (Bit Map Type 09) sale.
    BIT11 System Trace Audit Number (STAN).

    The in-store controller creates this six-digit number at transaction time to uniquely identify the transaction. This field appears in every message type supported by the Tandem Online System and the instore controller.
    BIT110 Tax Amount.

    This nine-digit field appears in 0100 authorization requests and 0200 financial requests that apply to corporate or purchase credit cards.

    It contains the dollar amount of tax included in the transaction, in the format 999999999. Sending a value of all 9’s (999999999) in the request message indicates that this is a non-taxable transaction. Sending a value of all 8’s (888888888) in the request message indicates that this is a tax-exempt transaction.

    Note: For non-corporate/purchase cards, this data element can be sent as all zeroes.
    BIT111 Additional Data, Private EBT.

    This 15-byte field is conditional in the 0200 financial message. Present only when the processing code indicates an EBT transaction, it contains the voucher number required for clearing EBT voice authorizations.
    BIT112 Card Sequence Number.

    The three-digit card sequence number field is conditional in the 0200 financial request message when the processing code indicates an EBT transaction. The field is required only if the card has a generation number and the card was not swiped.

    The card sequence number distinguishes between separate cards with the same primary account number.
    BIT12 Local Transaction Date.

    The six-digit transaction date appears in all request messages handled by the in-store controller; it indicates the date (MMDDYY) on which the transaction occurred at the point of sale.

    In 0400 reversal/void requests, this field represents the transaction being voided; see 07 Transmission Date/Time.
    In a Gift Card Completion message the Local Transaction Date must be populated with the Local Transaction Date received in the Gift Card Preauth approval message.
    In an Unsolicited Reversal the Local Transaction Date must be populated with the Local Transaction Date received in the original Authorization request message.
    BIT120_BATCH_NUMBER Julian Day/Batch Number.

    This six-digit field appears in the 0210 and 0230 financial response and 0410 reversal response messages. It indicates under which batch the EFT transaction was captured at the host. The field contains the three-digit Julian day when the batch was opened and the three-digit batch number. (The batch number increases by one whenever a batch is released and resets to one for each Julian day). The field does not appear if Bit Map Type is 99.
    BIT120_CARD_TYPE Network Mnemonic/Card Type.

    This field serves one of two purposes, depending on the transaction type.

    The two- to four-character Card Type appears in the 0110 purchase/corporate card, check verification/guarantee authorization responses, 0210/0230 credit, check conversion responses, and 0410 reversal response messages for credit transactions and check conversion reversals.
    The value is controlled by the in-store application and the Tandem Online System (BIN table).

    The third character, when present, indicates the card category.

    • L (Business-to-Business settlement match edits eligible card),
    • B (Business),
    • R (Corporate), and
    • S (Purchase)

    are the VISA purchase-card categories;

  • S is the MasterCard purchase-card category.

  • The fourth character, if present, is the authorization source indicator returned by Visa. The code is left justified with the remainder of the field space filled.

    Example of network switch value for payment type DB is “MAES“, for payment type EB is “EWA1”.
    BIT120_DEMO_MERCHANT_FLAG Demo Merchant Flag.

    This single-character field appears in the 0210 and 0230 financial response and 0410 reversal response messages. It indicates whether or not the terminal is being operated in demonstration or production mode. Does not appear if Bit Map Type is 99.
    • ‘Y’ = Demo mode;
    • ‘N’ = Production mode
    BIT123_ERROR_TEXT Error Text.

    This 20-character field must appear in all response messages when the Bit Map Type is 99 (i.e., error responses). The field indicates an error condition; the text is displayed on the POS terminal.
    BIT123_RESPONSE_CODE Response Code.

    The three-digit response code must appear in all response messages when the Bit Map Type is 99 (i.e., error responses). In the case of the 0330 file update response (Bit Map Types 81 and 89), both approval and error messages include the response code. This field is used to further define the cause of a decline or error response, and is displayed in the scroll area of the terminal.

    POSA Prepaid Transactions
    When error response code values of “001” or “795” is received, the POS device should place the transaction on a store-and-forward (SAF) queue for retransmission. SAF request messages must have the POSA-Stand-In indicator (Field 135) to “Y” and include the POSA SAF Reference Number (Field 136) of the original transaction when available.

    The POSA SAF Reference Number is provided in field 105.3 of the response message. A POS device time-out should be treated the same as receiving a “001” response code except that the POSA SAF Reference Number should be set to spaces. If SAF queuing is used, the POS should use parameters to determine number of retries and retry interval.
    BIT124_WORKING_KEY Working Key.

    The 16-character working key appears in all response messages. It is not used when DUKPT encryption is employed.

    The field will contain blanks if the host does not require a key exchange. If the field does not contain blanks, the terminal uses this working key for future debit/EBT transaction processing.
    BIT128_ADDITIONAL_AMOUNTS Additional Amounts.

    This 20-byte field contains information — up to six amounts and related account data — for which specific data elements are not defined. It is used in 0110, for Premier Issue Mass Transaction, EBT and used in 0210 for EBT, POSA Prepaid and Gift Card responses, where it contains balance information.
    BIT13 Local Transaction Time.

    The six-digit transaction time appears in all request messages handled by the in-store controller; it indicates the time (hhmmss) at which the transaction occurred at the point of sale.

    In 0400 reversal/void requests, this field represents the transaction being voided; see 07 Transmission Date/Time.
    In a Gift Card Completion message the Local Transaction Time must be populated with the Local Transaction Time received in the Gift Card Preauth approval message.
    In a Unsolicited Reversal the Local Transaction Time must be populated with the Local Transaction Time received in the original Authorization request message.
    BIT133 POSA Network ID.

    This four-byte field defines the POSA network used to authorize the POSA transaction. This field must appear in all POSA transactions. POSA networks are:

    • “SWAY” Safeway
    • “INCM” InComm
    • “PRES” PreSolutions
    • “SVSG” Stored Value Systems
    • “VALU” ValueLink
    • “ “ Non POSA card (spaces)

    If the merchant is processing POSA cards, but the point-of-sale system is unable to determine the POSA Network, then that merchant can only successfully process for a single POSA network. In this case, the POSA Network ID field must be set up at the point of sale to always indicate the merchant’s selected network (e.g. SWAY). The value should either be hard-coded into the system or set as a parameter. If the merchant also sells their own gift cards via non-POSA networks, then the BIN range(s) for the merchant’s gift cards must be registered with Vantiv, LLC (Tandem Onlines) for processing.

    Notes: Merchants that do not participate in POSA need to fill the POSA Network ID field with spaces.
    Contact Vantiv, LLC for current supported networks.

    BIT134 POSA UPC Data.

    This twenty-byte field contains the POSA scanned UPC (bar code data) on the card used to authorize the POSA prepaid transaction.
    This field must appear in all POSA prepaid transactions
    BIT135 POSA Stand-In indicator.

    This one-byte field is used to indicate a POSA store and forward transaction request due to a merchant stand-in condition. Applicable to POSA activation and reload SAF transaction requests only. Use a value of “Y”, if the POS device has timed out or the host responds with response code “001” or “795” and load the POSA SAF reference number into field 136 of the request message. The POSA SAF Reference Number is returned in field 105.3 of every POSA response message, and should be retained for use in any SAF retransmission request.

    When setting the POSA Stand-In indicator to “N”, the POSA SAF reference number must be initialized to spaces.
    This field must appear in any POSA activation or reload SAF requests when the transaction is queued for re-transmission by the POS device.
    BIT136 POSA SAF Reference Number.

    This twelve-byte field contains a unique number generated by the host for each POSA prepaid transaction.

    The host returns this value on every POSA prepaid transaction that is approved or declined (see field 105.3 – Transaction Identifier). In a Store-and-Forward scenario, where the transaction is queued for retransmission by the POS device this field contains the POSA SAF reference number of the original Activation/Reload transaction in the POSA prepaid request message. If a POSA device time out occurs no POSA SAF Reference Number is available then set the POSA SAF Reference Number to spaces and the POSA Stand-In Indicator (field 135) to a value of “Y”.
    BIT137 Replacement Amount.

    In a partial authorization reversal, the Replacement Amount reflects the corrected total amount of the authorization for the transaction. For a partial reversal, the Transaction Amount field must contain the original amount authorized. The host subtracts the Replacement Amount from the Transaction Amount to determine the amount being reversed. For timeout reversals, and for other cases where the original authorization is to be fully reversed, the replacement amount must be zero.

    The replacement amount must not be equal to or greater than the transaction amount. Partial reversals are currently only supported for VISA and MasterCard payment types.
    BIT22 Point-of-Service Entry Mode.

    The three-digit POS entry mode field must appear in the following messages:

    • 0100 Authorization request
    • 0200 Financial request
    • 0220 Financial request

    Contains two subfields that indicate the method used to enter the primary account number (PAN) and whether the POS terminal allows entry of personal identification numbers (PINs).
    BIT25 Point-of-Service Condition Code.

    The ten-digit POS condition code field must appear in the following messages:
    • 0100 Authorization request
    • 0200 Financial request
    • 0220 Financial request
    • 0400 Unsolicited reversal request

    Contains four subfields that, together, identify the kind of terminal and indicate whether the customer and/or the customer’s credit card were present at the time of the transaction.
    BIT32 Acquiring Institution Identification Code.

    This four-digit field must appear in the following message types:

    • 0100 Authorization request
    • 0200 Financial request
    • 0220 Financial request
    • 0400 Reversal request
    • 0500 Reconciliation request
    • 0800 Network management request

    The code (referred to in the Tandem Online Systems as the Bank ID) identifies the acquiring institution (i.e., merchant bank, merchant grouping, or merchants’ hierarchy) for the associated Card Acceptor ID Code (the Tandem Online Systems Merchant Number).
    BIT37_RETRIEVAL_REFERENCE_NUMBER Retrieval Reference Number.

    This eight-digit must appear in the following message types:

    • 0110 Check auth response
    • 0210 Financial response
    • 0230 Financial response
    • 0410 Reversal response

    The retrieval reference number is used to identify and track the original transaction. The field is conditional; it is present in the message only when the Bit Map Type is not 99.
    BIT41 Card Acceptor Terminal Identification.

    The three-digit card acceptor terminal ID code (referred to as the Terminal ID in the Tandem Online System) identifies the terminal at the merchant (card acceptor) location at which the transaction was entered.
    This field must appear in all transaction request messages.
    BIT42 Card Acceptor Identification Code.

    The 12-digit card acceptor ID code (referred to as the Merchant ID in the Tandem Online System) must appear in all transaction request messages. This field, in conjunction with the acquiring institution identification code (Field 32), uniquely identifies the merchant in the Tandem Online System.
    BIT43 Lane Number.

    This three-digit field appears in the following controller message types:

    • 0100 Authorization request
    • 0200 Financial request
    • 0220 Financial request
    • 0400 Reversal (void) request

    It identifies the cashier location at which the transaction occurred.

    Note: Of the 3 digit lane number only the right most two bytes are used. Lane numbers must be within the range of 01 to 99.
    BIT60 Cash Back Amount.

    This nine-digit field appears in the 0100 authorization and 0200 financial request messages. It represents the amount of money being given back to the cardholder. The entered amount can be up to seven digits; in the message it must be right-justified and padded with zeros to the full nine positions. This amount should not be included in the transaction amount field.

    For AVS verification only (Processing code 514000) request, this field must be zero filled.
    BIT63 Contains several fields:

  • Invoice/Folio Number.

  • This six-digit field appears in the 0200 and 0220 financial messages for those transactions (usually designated for specific card types) that use the extended prompts option. The field is required when settling American Express retail transactions. If the message also includes the P.O. Number/Customer Code field (bit 109), this field is ignored unless bit 109 is space-filled.

  • Item Code (from one to five)

  • These four-digit fields appear in the 0200 and 0220 financial messages for those transactions (usually designated for specific card types) that use the extended prompts option. These fields are used to cross reference a table in the Tandem Online Systems database that designates the type of merchandise purchased. Required when settling American Express retail transactions.
    BIT65 Authorization Identification Response.

    This six-character field appears in the following messages:
    • 0110 Authorization response (controller)
    • 0200 EBT voice authorization/voucher clear request
    • 0220 Financial request (prior authorized sale transactions) (controller)
    • 0210 Financial response (controller)
    • 0230 Financial response (controller)
    • 0410 Reversal response (controller)

    The auth ID response contains an authorization number assigned to the transaction by the authorizing institution. In all host capture terminal messages but the EBT voice-auth request, this data is in bit 38.
    BIT65_AUTHORIZATION_IDENTIFICATION_RESPONSE Authorization Identification Response.

    This six-character field appears in the following messages:

    • 0110 Authorization response (controller)
    • 0200 EBT voice authorization/voucher clear request
    • 0220 Financial request (prior authorized sale transactions) (controller)
    • 0210 Financial response (controller)
    • 0230 Financial response (controller)
    • 0410 Reversal response (controller)

    The auth ID response contains an authorization number assigned to the transaction by the authorizing institution. In all host capture terminal messages but the EBT voice-auth request, this data is in bit 38.
    BIT67 Extended Payment Code.

    The two-digit extended payment code field appears in the 0200 and 0220 financial request message. It pertains specifically to JCB transactions where the consumer can specify the number of installment payments they wish to make for each purchase.
    BIT70 Network Management Information Code.

    All request message types support the following codes:
    • 000 = Default (no key change required)
    • 101 = Key change requested
    • 900-999 = Log transaction as given error.

    The Tandem Online System will record this transaction as an error transaction with the given code and the error server name as ‘SLHBAS’.

    Full reversals support the following value:
  • 400 = Suspected Fraud

  • In addition, message type 0800 supports the following values:
    • 360 = Terminal validation
    • 380 = FleetOne Batch Close
    BIT90 Original Data Elements.

    This eight-character field must appear in 0400 reversals and the nine-character field must appear in 0100 authorization reversal request messages. It contains the retrieval reference number from the original transaction response, and helps identify the original transaction for reversal processing.
    For timeout reversals where the original transaction's retrieval reference number is not known, populate this field with zeroes.
    CHARGE_TRANSACTION_FK Reference to the entity that represents real-time financial transaction.
    G001 Merchant Reference Data.

    Used in settlement to uniquely identify a merchant’s transaction. The Merchant Reference Number can be present in any 0100, 0200, or 0220 authorization request transaction.

    The Draft locator ID field is a unique value assigned by the POS device for each transaction.
    The Merchant reference number should be a unique value assigned by the POS device for each transaction.
    G009 Optional Processing Indicators.

    It is a series of codes that identify terminal capability, terminal environment. Refer to the specification of the processor for more information.
    G014 Original Authorization Retrieval Reference Number.

    Provides a way to send an original authorization retrieval reference number.

    This field should be used when sending a 0220 force post. It should also be used with all full and partial reversals. This enables the Host to retrieve the original authorization information (if still available) to supplement settlement data.

    Note: Must be numeric. Any invalid data will be ignored by the host.
    G015 Additional Amounts Request.

    This 20-byte field contains information — up to six amount sets.

    The presence of this group is mandatory and indicates to the host this is an IIAS transaction request.
    The presence of G015 is optional in an EBT WIC authorization request transaction.

    IIAS transaction request:
    Amount type 4S must be present. The sum of the additional amount type fields must not exceed the total healthcare amount (4S). Any amount type can only appear once.

    EBT WIC transaction request:
    Only a single amount type 52 can be present in an EBT WIC authorization request transaction.

    Refer to the specification of the processor for more information.
    G021 Fee Data.

    Use this group to send convenience fee data. Please refer to card association regulations for details regarding fee usage.

    Convenience fees can be sent in a single transaction (Fee Type = 1) or in two transactions (Fee Types 2 and 3).

  • For a single convenience fee transaction (Fee Type 1):
  • put the fee in the Fee Amount field of this group and also include it with the Transaction Amount.

  • For a two-step convenience fee transaction:
  • 1. The first transaction must have Fee Type = 2 and Fee Amount = zero.
    2. The second transaction must have Fee Type = 3 and both Transaction Amount and Fee Amount containing the convenience fee.

    VISA CPS/Debit tax fees must be sent in a two-step transaction (Fee Types 2 and 3).
  • For a two-step VISA CPS/Debit tax transaction convenience fee transaction:
  • 1. The first transaction must have Fee Type = 2 and Fee Amount = zero.
    2. The second transaction must have Fee Type = 3 and both Transaction Amount and Fee Amount containing the convenience fee.

  • VISA limits the convenience fee amount for CPS/Debit Tax fee payment transactions, it is recommended to verify the fee limits and other terms during the merchant registration process.
  • G023 Restaurant Tip Amount.

    Used in conjunction with a sale or adjustment message to log the tip amount received. The cents portion is the last two positions, and the decimal point is implied.

    Must be numeric. Invalid data will result in a declined transaction. This group is ignored if the merchant is not configured on the host as Restaurant industry.
    IS_DEBIT_TRANSACTION Indicates whether the processed transaction is debit type.
    IS_REVERSAL_APPLIED Indicates whether the original transactions was already reversed.
    MERCHANT_ACCOUNT_CODE Code of Merchant Account to which instance of this object is attributed to.
    Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
    The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
    MESSAGE_TYPE_IDENTIFIER Appears in every message type supported by the Tandem Online Systems host capture message set.

    The first two digits identify the class of the message (authorization, financial, reversal, and so on); the last two digits represent the message function (request or response).
    NETWORK_ROUTING Сan be used to route the transaction through the front-end communications network (for example, CompuServe’s Routing Identifier – CRI). It appears in all messages, but is ignored by the Tandem Online System.
    R001 eCommerce VISA Authentication Result.

    Used to indicate the result of an eCommerce VISA transaction that requested authentication. This response is only applicable to VISA transactions when G002 is sent in the request message.

    Notes:
    Non-U.S. acquired transactions that occur on cards issued in the U.S. region can receive a CAVV result code values of 7,8,9, or A.
    V.I.P. will reject a transaction with Reject Reason Code 0193 (invalid value) when an issuer returns the response message with the value C or D.

    R006 Card-Level Results.

    The field contains a two-character code created by Visa during the authorization process. Refer to the specification of processor for more information.
    R007 Additional Amounts.

    This 20-byte field contains information — up to four amount sets. This group is returned when the transaction has been partially approved and on balance inquiries. Refer to the specification of processor for more information.
    R008 Original Authorization Retrieval Reference Number.

    This group is used to respond with the retrieval reference number of the authorization transaction. To request this group to be returned the sixth byte of G009 (Optional Processing Indicators) on authorization request has to be set to “Y”.
    R009 AMEX Transaction Identifier/Discover Network Reference ID.

    Used to pass the AMEX Transaction Identifier/Discover Network Reference ID. This response group is returned on approvals or declines when G009 position 4 in request is set to "Y" and the American Express transaction was sent to American Express for authorization, or when G009 position 9 in request is set to "Y" and the Discover transaction was sent to Discover for authorization.
    R999 Error Group Data Response.

    This group response is applicable to any transaction that sends group data in a request message and is determined by the host that it is invalid.

    Note: A value of “00” in the group field indicates group level error no specific field.

    Used to indicate any errors found by the host when processing authorization requests that contain any optional group data. Refer to the specification of processor for more information.
    RETAIL_TRANSACTION_CYCLE_FK Reference to the entity that represents a group of real-time transactions which must be settled together.
    cards-realtime.vantiv-tandem.settlement.log   
    Added On:  10/20/14
    Level:  Trace
    Category:  cards-realtime.settlement
    Status:  Active
    Group:  processing
    File Name:  cards-realtime.vantiv-tandem.settlement.log
    Resource:  $app-home/jboss-7.4.0/standalone/log/processing/cards-realtime.vantiv-tandem.settlement.log
    Legacy File Name:  cards-realtime.vantiv.settlement.log
    Сontains information about the processor's incoming requests and outgoing responses (vantiv-tandem)
    cards-realtime.elavon.authorization.log   
    Added On:  10/20/14
    Level:  Trace
    Category:  cards-realtime.authorization
    Status:  Active
    Group:  processing
    File Name:  cards-realtime.elavon.authorization.log
    Resource:  $app-home/jboss-7.4.0/standalone/log/processing/cards-realtime.elavon.authorization.log
    Legacy File Name:  
    Сontains information about the processor's incoming requests and outgoing responses (elavon)
    Request Fields [Show Info]

    ACCOUNT_SOURCE, AMOUNT, AUTH_REFERENCE_NBR, AVS_INDICATOR, BANK_NBR, CHARGE_TRANSACTION_FK, CUSTOM_DATA, FORCE_APPROVAL, FORMAT_CODE, FORMAT_ONE, FORMAT_THREE, FORMAT_TWO, MARKET_SEGMENT, MERCHANT_ACCOUNT_CODE, PARTIAL_AUTH_IND, REG_KEY, RESPONSE_CODE, RETAIL_TRANSACTION_CYCLE_FK, STREET, TERMINAL_NBR, TRACE_NBR, TRANSACTION_CODE, VENDOR_ID, ZIP
    Name Description
    ACCOUNT_SOURCE This value is used to facilitate transaction routing on Elavon.

    0 = Manually entered transaction originated at a device capable of reading track 1 or 2
    1 = Inquiry originated at a track 1 magnetic stripe reading device (capable of reading track 1 or 2 data)
    2 = Inquiry originated at a track 2 magnetic stripe reading device
    3 = Inquiry originated at a Proximity payment reading device
    4 = Inquiry originated at a MICR device
    AMOUNT Total amount of the transactions including discount and tax. The transaction amount in the cardholder’s currency in 9(10)v99 format.
    AUTH_REFERENCE_NBR Authorization reference number.
    AVS_INDICATOR Address Verification Service indicator.
    BANK_NBR This six digit fixed length value is assigned by Elavon.

    The bank identification number is used to uniquely identify the financial institution to Elavon.
    CHARGE_TRANSACTION_FK Reference to the entity that represents real-time financial transaction.
    CUSTOM_DATA This field is used to pass additional data for specific industries and/or market segments.
    FORCE_APPROVAL This field is used when reversal contains Approval Code from original transaction.
    FORMAT_CODE This is a unique code that is used by the Merchant to denote the specific parsing rules for the merchant defined data that is contained in the Format Data field.

    The Format Code field is used to denote different parsing structure for this field, if necessary.

    000 = ECS Data – Format A
    001 = ECS Data – Format B
    002 = ECS Enhanced Transaction Data
    003 = POS Logistics – Equipment Data
    004 = POS Logistics – Statistics Data
    FORMAT_ONE This is a unique code that is used by the Merchant to denote the specific parsing rules for the merchant defined data that is contained in the Format Data field.

    This field contains information in first type of format.
    FORMAT_THREE This is a unique code that is used by the Merchant to denote the specific parsing rules for the merchant defined data that is contained in the Format Data field.

    This field contains information in third type of format.
    FORMAT_TWO This is a unique code that is used by the Merchant to denote the specific parsing rules for the merchant defined data that is contained in the Format Data field.

    This field contains information in second type of format.
    MARKET_SEGMENT Indicates transaction industry.
    MERCHANT_ACCOUNT_CODE Code of Merchant Account to which instance of this object is attributed to.
    Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
    The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
    PARTIAL_AUTH_IND This value is used to indicate if the POS is capable of performing partial authorizations.

    0 = Indicates that the POS is not capable of Partial Authorizations
    1 = Indicates that the POS is capable of Partial Authorizations
    2 = Indicates that the POS is capable of Partial Authorizations and is a Visa Aggregator
    REG_KEY Required in all Scripts sent to the Elavon Host for processing and will be sent as a HTTP Header Field in the Post request.

    Note: The Registration Key should be sent as an HTTP Header field.

    The NOVA_PORTAL_FAKE_KEY is only used to send transactions to the Elavon development host and cannot be used to send traffic to production hosts. A production Registration Key will be assigned by the Certification Department after certification is complete and is 20 characters long.
    RESPONSE_CODE Gateway generated response code.
    RETAIL_TRANSACTION_CYCLE_FK Reference to the entity that represents a group of real-time transactions which must be settled together.
    STREET The Merchant’s Street Address.
    TERMINAL_NBR This sixteen digit fixed length value is assigned by Elavon.

    The terminal identification number is used to uniquely identify the Merchant and their financial institution to Elavon. The Terminal ID consists of two parts and is assigned by Elavon for each POS device.
    TRACE_NBR This value is used as a message reference number identify the transaction request and is returned in all authorization response messages. It is sent to the host on reversal and void messages when applicable.
    TRANSACTION_CODE This value is used to uniquely identify the type of transaction that is being submitted to Elavon. Refer to the provider's specification for more information.
    VENDOR_ID This value is assigned by the Vendor Certification Department of ELAVON.

    This number is an alphanumeric value and should be capitalized. All Vendor Certification Device Types are value of "Z".
    ZIP The Merchant’s postal or zip code.
    Response Fields [Show Info]

    ACCOUNT_BALANCE, ACCOUNT_SOURCE, AMEX_CAP_CODE, AMOUNT, APPROVAL_CODE, AUTH_RESPONSE, AUTH_SOURCE, AUTHORIZED_AMOUNT, AVS_INDICATOR, AVS_RESPONSE_CODE, BANK_NBR, CAP_CODE, CHARGE_TRANSACTION_FK, CUSTOM_DATA, CVV2_RESPONSE, FORCE_APPROVAL, FORMAT_CODE, FORMAT_ONE, FORMAT_THREE, FORMAT_TWO, MARKET_SEGMENT, MERCHANT_ACCOUNT_CODE, MSDI, PARTIAL_AUTH_IND, PS2000_DATA, REFERENCE_NBR, REG_KEY, RESPONSE_CODE, RETAIL_TRANSACTION_CYCLE_FK, STREET, TERMINAL_NBR, TRACE_NBR, TRANS_DATE, TRANS_TIME, TRANSACTION_CODE, VENDOR_ID, ZIP
    Name Description
    ACCOUNT_BALANCE For Credit and Debit cards, if present this value indicates the remaining balance for a pre-paid account. For EBT transactions, if present this value indicates the remaining Food Stamp balance. For Gift Card transactions, if present this value indicates the remaining Gift Card balance on the account. Refer to the specification of the provider for more information.
    ACCOUNT_SOURCE This value is used to facilitate transaction routing on Elavon.

    0 = Manually entered transaction originated at a device capable of reading track 1 or 2
    1 = Inquiry originated at a track 1 magnetic stripe reading device (capable of reading track 1 or 2 data)
    2 = Inquiry originated at a track 2 magnetic stripe reading device
    3 = Inquiry originated at a Proximity payment reading device
    4 = Inquiry originated at a MICR device
    AMEX_CAP_CODE This is the American Express Capture Code field and is returned during a credit card authorization response. It determines the capture option allowed for the American Express Card in the Split Dial environment, where the POS is accessing Amex directly for Authorization processing of Amex Cards.

    0 = Do not process
    1 = Allow authorizations but do not capture in Settlement file
    2 = Allow authorizations and capture in settlement file for processing
    AMOUNT Total amount of the transactions including discount and tax. The transaction amount in the cardholder’s currency in 9(10)v99 format.
    APPROVAL_CODE This field contains the Approval Code for an approved transaction.
    Note: If the Response Code on the auth. is not equal to "AA" or “AP” the contents of this field are ignored.
    AUTH_RESPONSE This field contains the 16 character response display message. This field is used by the POS device to display the authorization results.
    AUTH_SOURCE This value is used to indicate the source for the authorization response. The values in this response message are subject to additions.

    For On-Line transactions, the codes are supplied by the Issuer and are returned by Elavon in the response message for all on line approvals
    For Off-Line transactions, this is a one character field in the list below contains the Authorization Source code:

    9 = No Authorization Source Code. This is used for non-authorized transactions, such as Credit Card Returns
    E = Off-Line Approval. This is used when the approval code is manually entered, such as on a Referral or Force Transaction
    6 = Off-Line approval, POS generated the approval.
    AUTHORIZED_AMOUNT This value is used to indicate the authorized amount of the transaction (excluding adjustments).
    AVS_INDICATOR Address Verification Service indicator.
    AVS_RESPONSE_CODE This value contains the address verification response code returned in response message as a result of an AVS Request. It is also a required value for a terminal-based settlement, if returned in the authorization response.
    BANK_NBR This six digit fixed length value is assigned by Elavon.

    The bank identification number is used to uniquely identify the financial institution to Elavon.
    CAP_CODE This field is used to indicate to the POS which transactions should be captured in the local Shadow file.

    0 = Do not Capture – Authorization Only
    1 = Capture Transaction in Shadow File (EDC)
    2 = Capture Transaction in Shadow File (EDC)

    This value is used for Debit Returns to indicate that the Debit Purchase is in the current batch.
    CHARGE_TRANSACTION_FK Reference to the entity that represents real-time financial transaction.
    CUSTOM_DATA This field is used to pass additional data for specific industries and/or market segments.
    CVV2_RESPONSE This value contains the Card verification response code returned in Authorization Response. It is also a required value for a terminal-based settlement message, if returned in the authorization response.

    M = Match
    N = No match
    P = Not Processed
    S = Issuer indicates that CVV2 data should be present on the card, but the merchant has indicated that the CVV2 data is not present on the card (Visa Only)
    U = Issuer not certified or registered to process card verification
    FORCE_APPROVAL This field is used when reversal contains Approval Code from original transaction.
    FORMAT_CODE This is a unique code that is used by the Merchant to denote the specific parsing rules for the merchant defined data that is contained in the Format Data field.

    The Format Code field is used to denote different parsing structure for this field, if necessary.

    000 = ECS Data – Format A
    001 = ECS Data – Format B
    002 = ECS Enhanced Transaction Data
    003 = POS Logistics – Equipment Data
    004 = POS Logistics – Statistics Data
    FORMAT_ONE This is a unique code that is used by the Merchant to denote the specific parsing rules for the merchant defined data that is contained in the Format Data field.

    This field contains information in first type of format.
    FORMAT_THREE This is a unique code that is used by the Merchant to denote the specific parsing rules for the merchant defined data that is contained in the Format Data field.

    This field contains information in third type of format.
    FORMAT_TWO This is a unique code that is used by the Merchant to denote the specific parsing rules for the merchant defined data that is contained in the Format Data field.

    This field contains information in second type of format.
    MARKET_SEGMENT Indicates transaction industry.
    MERCHANT_ACCOUNT_CODE Code of Merchant Account to which instance of this object is attributed to.
    Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
    The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
    MSDI The Market Specific Data Indicator value.

    Space = Not Specified
    A = Auto Rental
    B = Bill Payment
    E = Visa Aggregator
    G = MasterCard Payment Gateway
    H = Hotel Edits
    J = Business to Business
    M = HealthCare (Auto Substantiation)
    N = Not Applicable (Failed Edits)
    T = Transit (Auto Substantiation)
    I = Internet PIN 31
    PARTIAL_AUTH_IND This value is used to indicate if the POS is capable of performing partial authorizations.

    0 = Indicates that the POS is not capable of Partial Authorizations
    1 = Indicates that the POS is capable of Partial Authorizations
    2 = Indicates that the POS is capable of Partial Authorizations and is a Visa Aggregator
    PS2000_DATA This data will be as received during the original authorization processing. It will not be present for off line transactions. This is a “retain and return” value for terminal-based settlement messages.
    REFERENCE_NBR Beginning Transaction reference number.
    REG_KEY Required in all Scripts sent to the Elavon Host for processing and will be sent as a HTTP Header Field in the Post request.

    Note: The Registration Key should be sent as an HTTP Header field.

    The NOVA_PORTAL_FAKE_KEY is only used to send transactions to the Elavon development host and cannot be used to send traffic to production hosts. A production Registration Key will be assigned by the Certification Department after certification is complete and is 20 characters long.
    RESPONSE_CODE Gateway generated response code.
    RETAIL_TRANSACTION_CYCLE_FK Reference to the entity that represents a group of real-time transactions which must be settled together.
    STREET The Merchant’s Street Address.
    TERMINAL_NBR This sixteen digit fixed length value is assigned by Elavon.

    The terminal identification number is used to uniquely identify the Merchant and their financial institution to Elavon. The Terminal ID consists of two parts and is assigned by Elavon for each POS device.
    TRACE_NBR This value is used as a message reference number identify the transaction request and is returned in all authorization response messages. It is sent to the host on reversal and void messages when applicable.
    TRANS_DATE The actual date of the transaction.
    TRANS_TIME The actual time of the transaction.
    TRANSACTION_CODE This value is used to uniquely identify the type of transaction that is being submitted to Elavon. Refer to the provider's specification for more information.
    VENDOR_ID This value is assigned by the Vendor Certification Department of ELAVON.

    This number is an alphanumeric value and should be capitalized. All Vendor Certification Device Types are value of "Z".
    ZIP The Merchant’s postal or zip code.
    cards-realtime.elavon.settlement.log   
    Added On:  10/20/14
    Level:  Trace
    Category:  cards-realtime.settlement
    Status:  Active
    Group:  processing
    File Name:  cards-realtime.elavon.settlement.log
    Resource:  $app-home/jboss-7.4.0/standalone/log/processing/cards-realtime.elavon.settlement.log
    Legacy File Name:  
    Сontains information about the processor's incoming requests and outgoing responses (elavon)
    cards-realtime.elavon-viaconex4.authorization.log   
    Added On:  10/20/14
    Level:  Trace
    Category:  cards-realtime.authorization
    Status:  Active
    Group:  processing
    File Name:  cards-realtime.elavon-viaconex4.authorization.log
    Resource:  $app-home/jboss-7.4.0/standalone/log/processing/cards-realtime.elavon-viaconex4.authorization.log
    Legacy File Name:  cards-realtime.elavon4.authorization.log
    Сontains information about the processor's incoming requests and outgoing responses (elavon-viaconex4)
    Request Fields [Show Info]

    ACCOUNT_ENTRY_MODE, ACCOUNT_TYPE, APPLICATION_ID, APPROVAL_CODE, CASHBACK_AMOUNT, CHARGE_TRANSACTION_FK, CUSTOMER_CODE, CVV2_INDICATOR, DYNAMIC_DBA_NAME, ECOMMERCE_INDICATOR, GIFT_LOYALTY_TRANSACTION_CODE, INSTALLMENT_COUNT, INSTALLMENT_NUMBER, INVOICE_NUMBER, KEY_POINTER, MERCHANT_ACCOUNT_CODE, MERCHANT_REFERENCE_NBR, PARTIAL_AUTH_INDICATOR, POS_ENTRY_CAPABILITY, POSTAL_ZIP_CODE, PS2000_DATA, RECURRING_PAYMENT_TYPE, REQUEST, RESPONSE_CODE, RETAIL_TRANSACTION_CYCLE_FK, SALES_TAX, SHIPPING_DATE, STREET_ADDRESS, SURCHARGE_AMOUNT, TENDER_TYPE, TERMINAL_ID, TRACE_NUMBER, TRANSACTION_AMOUNT, TRANSACTION_CODE, TRANSACTION_REFERENCE_NBR, UCAF_INDICATOR, VOUCHER_CLEAR_NBR
    Name Description
    ACCOUNT_ENTRY_MODE This value is used to identify the method used to enter the Account Data for the transaction. Refer to the specification of the provider for more information.
    ACCOUNT_TYPE This value is used to facilitate transaction routing on Elavon.

    0 = Default or primary account on file (In Canada this is only used for Flash Transactions)
    1 = Checking
    2 = Savings
    3 = Food Stamp
    4 = Cash Benefits
    APPLICATION_ID This field is used to indicate the type of POS device that is originating the transaction. These values are case sensitive and must be capitalized. Sample: HZ0000GC.
    APPROVAL_CODE This field contains the Approval Code for an approved transaction.

    Note: If the Response Code on the auth. is not equal to "AA" or “AP” the contents of this field are ignored.
    CASHBACK_AMOUNT This field is used to indicate the cashback amount applied to the transaction. This amount should be included in the Transaction Amount field.
    CHARGE_TRANSACTION_FK Reference to the entity that represents real-time financial transaction.
    CUSTOMER_CODE This value is used to identify the customer number for purchasing card transactions.
    CVV2_INDICATOR This value is used to indicate the presence of the CVV2 data on the Visa card. For non-Visa Cards, the value of “Present” should be used when CVC2 or CID data is present, or “Bypassed” when not present.

    0 = Bypassed
    1 = Present
    2 = Illegible
    9 = Not Present
    DYNAMIC_DBA_NAME This value allows the merchant to dynamically change the “Doing Business As” name on each transaction submitted to the host for authorization and settlement. The use of the dynamic DBA (dDBA) field is restricted by Elavon and requires prior approval to participate in the program. Values that are sent in this field by merchants that are not approved for use of this field will be ignored by the host prior to authorization and the value currently “on file” with Elavon will be used.
    ECOMMERCE_INDICATOR This indicates the method used to capture the cardholder’s information for an eCommerce or Internet transaction.

    1 = Secure Electronic Commerce Transaction that includes the 3-D Secure Authentication value. (5)
    2 = Non-Authenticated Security Transaction from a 3-D Secure capable merchant, and merchant attempted to authorize using 3-D Secure. Transaction Does Not Include 3-D Secure authentication value. (6)
    3 = Non-Authenticated Security Transaction w/o Merchant Certificate i.e., Channel Encrypted (7)
    4 = Non-Authenticated Security Transaction at a SET Capable merchant (9)
    5 = Non-Secure Transaction (no encryption used) (8)
    GIFT_LOYALTY_TRANSACTION_CODE This character is used by the POS to uniquely identify the transaction to the gift card host. This value is required for both Gift Card and Loyalty reversal transactions.

    A unique value assigned by the POS to identify the gift card transaction.
    INSTALLMENT_COUNT This value is used to indicate the total number of payments for an installment transaction. For example, if the consumer is making payment 1 of 12, then this value should be set to “12”.
    INSTALLMENT_NUMBER This value is used to indicate the current payment number for an installment transaction. For example, if the consumer is making payment 1 of 12, then this value should be set to “1”.
    INVOICE_NUMBER This value is used to include the POS’s local transaction invoice or order number. This is a required value for Mail Order and Ecommerce transactions.
    KEY_POINTER This value is used to indicate which encryption methodology was used for US Debit transactions (POS to Elavon) and which key to use for the next transaction (Elavon to POS).

    D = Single-DES DUKPT
    T = Triple-DES DUKPT
    P = PIN Less Debit Purchase
    MERCHANT_ACCOUNT_CODE Code of Merchant Account to which instance of this object is attributed to.
    Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
    The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
    MERCHANT_REFERENCE_NBR This value contains the merchant assigned reference number for this transaction. If this value is not present, then Elavon will generate this number for backend use.
    PARTIAL_AUTH_INDICATOR This value is used to indicate if the POS is capable of performing partial authorizations.

    0 = Indicates that the POS is not capable of Partial Authorizations.
    1 = Indicates that the POS is capable of Partial Authorizations.
    2 = Indicates that the POS is capable of Partial Authorizations and is a Visa Aggregator.
    POS_ENTRY_CAPABILITY This value is used to identify the account entry capabilities on the POS device originating the transaction. Refer to the specification of the provider for more information.
    POSTAL_ZIP_CODE This value is used to indicate the cardholder’s Postal or ZIP Code.
    PS2000_DATA This data will be as received during the original authorization processing. It will not be present for off line transactions. This is a “retain and return” value for terminal-based settlement messages. Refer to the specification of the provider for more information.
    RECURRING_PAYMENT_TYPE This field is used to identify the type of recurring transaction that is being submitted for authorization.

  • A Recurring Transaction is a transaction in which a cardholder allows a merchant to charge their card for recurring goods or services for a mutually agreed-upon payment amount (variable or set) and for a specified length of time. The merchant must obtain written permission to bill a cardholder on a recurring basis. Subsequent permission must be obtained when the agreement is renewed.

  • Recurring transactions have a defined billing cycle and are in effect as long as the contract between the merchant and the cardholder is in good standing. Recurring payments include charges for Utilities, membership fees, subscriptions, insurance premiums, tuition, etc.
  • An Installment Transaction is a transaction in which a cardholder allows a merchant permission to charge their card for a single purchase of goods or services on a pre-determined payment schedule. The merchant must obtain permission to bill the cardholder in an arrangement in which a single purchase of goods/service is divided into two or more payments. Subsequent permission must be obtained when the agreement is modified.

  • Installment transactions have a defined transaction amount, billing cycle, and a total number of payments, which equal the full amount for the original agreed upon purchase. Installment payments include charges for loan payments, car purchase, furniture stores, etc.
  • A Carne Bill Payment Transaction is a Brazilian transaction in which a cardholder enters into an agreement and signs a contract with the Merchant to make regular monthly payments using a domestic Brazilian Debit Card for a current purchase. The cardholder then agrees to return to the store each month and present a domestic Brazilian Debit Card to make a payment according to the terms of the contract.
  • REQUEST Type of request.
    RESPONSE_CODE This value is a 2 character code indicating the authorization response status. An approval is always indicated with an ‘AA’ or ‘AP’ code, all other codes indicate a non-approval.

    AA = Approved Transaction (Authorizations and Reversals)
    AP = Approved Transaction for a Partial Amount
    NC = Decline (Pick Up Card)
    ND = Decline (Hard or Soft)
    NF = Decline (Record Not Found)
    NR = Decline (Referral Message)
    N7 = Decline (For CVV2 Only)
    NL = Decline (Loyalty/Gift Error)
    00-99 = Decline (Additional Gift Card Declined)
    RETAIL_TRANSACTION_CYCLE_FK Reference to the entity that represents a group of real-time transactions which must be settled together.
    SALES_TAX This is the actual sales tax amount applied to this transaction. Consumer or Merchant tax exempt transactions can enter a single zero to properly reflect a tax exempt transaction.
    SHIPPING_DATE The value is the date that the consumer’s goods were shipped. This value is the “Transaction Date” for direct marketing and ecommerce transactions.

    Shipping Date in MMDDYYYY format.
    STREET_ADDRESS This value is used to identify the cardholder’s street address.
    SURCHARGE_AMOUNT This field is used to indicate the amount of the surcharge applied to the transaction. This amount should be included in the Transaction Amount field.
    TENDER_TYPE The value is used to identify the payment method use to activate or reload a gift card.

    0 = Cash
    1 = Credit Card
    2 = Debit Card
    3 = Check
    9 = Unknown
    TERMINAL_ID The terminal identification number is used to uniquely identify the Merchant and their financial institution to Elavon. The Terminal ID consists of two parts and is assigned by Elavon for each POS device.
    TRACE_NUMBER This value is used as a message reference number identify the transaction request and is returned in all authorization response messages. It is sent to the host on reversal and void messages when applicable.
    TRANSACTION_AMOUNT This is the actual amount of the transaction. The maximum transaction amounts supported are currently $9,999,999.99 for Visa and MasterCard, and $99,999.99 all others card associations.

    For Terminal-Based Settlement messages, this value will contain the total amount of the transaction in the Merchant’s currency, including any Tips (for restaurant transactions).
    For Canadian Debit Authorization Response messages, this field is zero filled and right justified to 12 characters.
    TRANSACTION_CODE This value is used to uniquely identify the type of transaction that is being submitted to Elavon. Refer to the specification of the provider for more information.
    TRANSACTION_REFERENCE_NBR The Transaction Reference Number is returned in the authorization response message and is used on void and reversal transactions, when available. This number is assigned by Elavon.
    UCAF_INDICATOR This value identifies the means in which the transaction was processed between the cardholder and the merchant for a SecureCode authentication transaction.

    0 = UCAF data collection is not supported by the Merchant
    1 = UCAF data collection is supported by merchant but not populated
    2 = UCAF data collection is supported by merchant, and UCAF data must be present
    VOUCHER_CLEAR_NBR The Voucher Number from an EBT sales slip, used for Voucher Clear Food Stamp transactions.
    The 15 digit Voucher Clear Number from the Merchant’s EBT Food Stamp sales slip.
    Response Fields [Show Info]

    ACCOUNT_BALANCE1, ACCOUNT_BALANCE2, ACCOUNT_ENTRY_MODE, ACCOUNT_TYPE, AMEX_CAPTURE_CODE, APPLICATION_ID, APPROVAL_CODE, AUTHORIZATION_DATE, AUTHORIZATION_RESPONSE, AUTHORIZATION_SOURCE, AUTHORIZATION_TIME, AUTHORIZED_AMOUNT, AVS_RESPONSE, CAPTURE_CODE, CASHBACK_AMOUNT, CHARGE_TRANSACTION_FK, CUSTOMER_CODE, CVV2_INDICATOR, CVV2_RESPONSE, DEBIT_EBT_NETWORK_ID, DEBIT_EBT_SETTLEMENT_DATE, DYNAMIC_DBA_NAME, ECOMMERCE_INDICATOR, GIFT_LOYALTY_TRANSACTION_CODE, INSTALLMENT_COUNT, INSTALLMENT_NUMBER, INVOICE_NUMBER, ISSUER_RESPONSE_CODE, KEY_POINTER, MEMBER_NAME, MERCHANT_ACCOUNT_CODE, MERCHANT_REFERENCE_NBR, MSDI, PARTIAL_AUTH_INDICATOR, POINTS_ADDED, POINTS_CANCELED, POS_ENTRY_CAPABILITY, POSTAL_ZIP_CODE, PRE_AUTH_REFERENCE_NUMBER, PS2000_DATA, RECEIPT_MESSAGE, RECURRING_PAYMENT_TYPE, REFERENCE_NUMBER, REQUEST, RESPONSE_CODE, RETAIL_TRANSACTION_CYCLE_FK, SALES_TAX, SHIPPING_DATE, STREET_ADDRESS, SURCHARGE_AMOUNT, TENDER_TYPE, TERMINAL_ID, TRACE_NUMBER, TRANSACTION_AMOUNT, TRANSACTION_CODE, TRANSACTION_REFERENCE_NBR,
    Name Description
    ACCOUNT_BALANCE1 For Credit and Debit cards, if present this value indicates the remaining balance for a pre-paid account. For EBT transactions, if present this value indicates the remaining Food Stamp balance. For Gift Card transactions, if present this value indicates the remaining Gift Card balance on the account. Refer to the specification of the provider for more information.
    ACCOUNT_BALANCE2 For Credit and Debit cards, if present this value indicates the remaining Gift Card Balance on the account.
    For EBT transactions, if present this value indicates the remaining Cash Benefit balance.
    For Gift Card transactions, if present this value indicates the remaining Loyalty points on the account.
    ACCOUNT_ENTRY_MODE This value is used to identify the method used to enter the Account Data for the transaction. Refer to the specification of the provider for more information.
    ACCOUNT_TYPE This value is used to facilitate transaction routing on Elavon.

    0 = Default or primary account on file (In Canada this is only used for Flash Transactions)
    1 = Checking
    2 = Savings
    3 = Food Stamp
    4 = Cash Benefits
    AMEX_CAPTURE_CODE This is the American Express Capture Code field and is returned during a credit card authorization response. It determines the capture option allowed for the American Express Card in the Split Dial environment, where the POS is accessing Amex directly for Authorization processing of Amex Cards.

    0 = Do not process
    1 = Allow authorizations but do not capture in Settlement file
    2 = Allow authorizations and capture in settlement file for processing
    APPLICATION_ID This field is used to indicate the type of POS device that is originating the transaction. These values are case sensitive and must be capitalized. Sample: HZ0000GC.
    APPROVAL_CODE This field contains the Approval Code for an approved transaction.

    Note: If the Response Code on the auth. is not equal to "AA" or “AP” the contents of this field are ignored.
    AUTHORIZATION_DATE This value is the date which the transaction was authorized. For offline transactions, this value should be set to the date when the transaction occurs.
    AUTHORIZATION_RESPONSE This field contains the 16 character response display message. This field is used by the POS device to display the authorization results.
    AUTHORIZATION_SOURCE This value is used to indicate the source for the authorization response. The values in this response message are subject to additions.

    For On-Line transactions, the codes are supplied by the Issuer and are returned by Elavon in the response message for all on line approvals.

    For Off-Line transactions, this is a one character field in the table below contains the Authorization Source code:

    9 = No Authorization Source Code. This is used for non-authorized transactions, such as Credit Card Returns
    E = Off-Line Approval. This is used when the approval code is manually entered, such as on a Referral or Force Transaction
    6 = Off-Line approval, POS generated the approval.
    AUTHORIZATION_TIME This value is the time which the transaction was authorized. For offline transactions, this value should be set to the time when the transaction occurs.
    AUTHORIZED_AMOUNT This value is used to identify the total authorized amount for the authorization request. If the Partial authorization flag is enabled, this amount may be less than the requested amount.
    AVS_RESPONSE This value contains the address verification response code returned in response message as a result of an AVS Request. It is also a required value for a terminal-based settlement, if returned in the authorization response. Refer to the specification of the provider for more information.
    CAPTURE_CODE This field is used to indicate to the POS which transactions should be captured in the local Shadow file.

    0 = Do not Capture – Authorization Only
    1 = Capture Transaction in Shadow File (EDC)
    2 = Capture Transaction in Shadow File (EDC). This value is used for Debit Returns to indicate that the Debit Purchase is in the current batch.
    CASHBACK_AMOUNT This field is used to indicate the cashback amount applied to the transaction. This amount should be included in the Transaction Amount field.
    CHARGE_TRANSACTION_FK Reference to the entity that represents real-time financial transaction.
    CUSTOMER_CODE This value is used to identify the customer number for purchasing card transactions.
    CVV2_INDICATOR This value is used to indicate the presence of the CVV2 data on the Visa card. For non-Visa Cards, the value of “Present” should be used when CVC2 or CID data is present, or “Bypassed” when not present.

    0 = Bypassed
    1 = Present
    2 = Illegible
    9 = Not Present
    CVV2_RESPONSE This value contains the Card verification response code returned in Authorization Response. It is also a required value for a terminal-based settlement message, if returned in the authorization response.

    M = Match
    N = No match
    P = Not Processed
    S = Issuer indicates that CVV2 data should be present on the card, but the merchant has indicated that the CVV2 data is not present on the card (Visa Only)
    U = Issuer not certified or registered to process card verification.
    DEBIT_EBT_NETWORK_ID This value is used to indicate the Debit Network that the transaction was routed through for authorization. It may also be used on the Debit Purchase and PINLess Purchase transaction to indicate the preferred Debit Network routing ID for authorization. Refer to the specification of the provider for more information.
    DEBIT_EBT_SETTLEMENT_DATE This value is the debit switch settlement date in MMDD format.
    DYNAMIC_DBA_NAME This value allows the merchant to dynamically change the “Doing Business As” name on each transaction submitted to the host for authorization and settlement. The use of the dynamic DBA (dDBA) field is restricted by Elavon and requires prior approval to participate in the program. Values that are sent in this field by merchants that are not approved for use of this field will be ignored by the host prior to authorization and the value currently “on file” with Elavon will be used.
    ECOMMERCE_INDICATOR This indicates the method used to capture the cardholder’s information for an eCommerce or Internet transaction.

    1 = Secure Electronic Commerce Transaction that includes the 3-D Secure Authentication value. (5)
    2 = Non-Authenticated Security Transaction from a 3-D Secure capable merchant, and merchant attempted to authorize using 3-D Secure. Transaction Does Not Include 3-D Secure authentication value. (6)
    3 = Non-Authenticated Security Transaction w/o Merchant Certificate i.e., Channel Encrypted (7)
    4 = Non-Authenticated Security Transaction at a SET Capable merchant (9)
    5 = Non-Secure Transaction (no encryption used) (8)
    GIFT_LOYALTY_TRANSACTION_CODE This character is used by the POS to uniquely identify the transaction to the gift card host. This value is required for both Gift Card and Loyalty reversal transactions.

    A unique value assigned by the POS to identify the gift card transaction.
    INSTALLMENT_COUNT This value is used to indicate the total number of payments for an installment transaction. For example, if the consumer is making payment 1 of 12, then this value should be set to “12”.
    INSTALLMENT_NUMBER This value is used to indicate the current payment number for an installment transaction. For example, if the consumer is making payment 1 of 12, then this value should be set to “1”.
    INVOICE_NUMBER This value is used to include the POS’s local transaction invoice or order number. This is a required value for Mail Order and Ecommerce transactions.
    ISSUER_RESPONSE_CODE This value is the original Issuer response as returned during the authorization attempt.
    KEY_POINTER This value is used to indicate which encryption methodology was used for US Debit transactions (POS to Elavon) and which key to use for the next transaction (Elavon to POS).

    D = Single-DES DUKPT
    T = Triple-DES DUKPT
    P = PIN Less Debit Purchase
    MEMBER_NAME The Member name associated with the gift or loyalty card transaction, if available.
    MERCHANT_ACCOUNT_CODE Code of Merchant Account to which instance of this object is attributed to.
    Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
    The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
    MERCHANT_REFERENCE_NBR This value contains the merchant assigned reference number for this transaction. If this value is not present, then Elavon will generate this number for backend use.
    MSDI The Market Specific Data Indicator value.

    0 = Returned if the data was not presented in authorization
    1 = Returned if the data passed the Hotel Edits (H)
    2 = Returned if the data failed Edits (N)
    3 = Healthcare / Auto-Substantiation (M)
    4 = Transit / Auto-Substantiation (T)
    5 = Returned if the data passed the Visa Aggregator edits (E)
    6 = Returned if the data passed the Auto Rental edits (A)
    7 = Returned if the data passed the Bill Payment edits (B)
    8 = Returned if the data passed the MasterCard Payment Gateway edits (G)
    9 = Business to Business Invoice Payments (J)
    PARTIAL_AUTH_INDICATOR This value is used to indicate if the POS is capable of performing partial authorizations.

    0 = Indicates that the POS is not capable of Partial Authorizations.
    1 = Indicates that the POS is capable of Partial Authorizations.
    2 = Indicates that the POS is capable of Partial Authorizations and is a Visa Aggregator.
    POINTS_ADDED This value is used to indicate the number of points added to an account an account.
    POINTS_CANCELED This value is used to indicate the number of points to cancel from an account.
    POS_ENTRY_CAPABILITY This value is used to identify the account entry capabilities on the POS device originating the transaction. Refer to the specification of the provider for more information.
    POSTAL_ZIP_CODE This value is used to indicate the cardholder’s Postal or ZIP Code.
    PRE_AUTH_REFERENCE_NUMBER This is a Gift Card value used to identify the original pre-authorization request. This value is required to submit the post-authorization completion transaction message.
    PS2000_DATA This data will be as received during the original authorization processing. It will not be present for off line transactions. This is a “retain and return” value for terminal-based settlement messages. Refer to the specification of the provider for more information.
    RECEIPT_MESSAGE This field contains a custom message as retuned from the Gift Card host to be printed on the cardholder’s receipt.
    RECURRING_PAYMENT_TYPE This field is used to identify the type of recurring transaction that is being submitted for authorization.

  • A Recurring Transaction is a transaction in which a cardholder allows a merchant to charge their card for recurring goods or services for a mutually agreed-upon payment amount (variable or set) and for a specified length of time. The merchant must obtain written permission to bill a cardholder on a recurring basis. Subsequent permission must be obtained when the agreement is renewed.

  • Recurring transactions have a defined billing cycle and are in effect as long as the contract between the merchant and the cardholder is in good standing. Recurring payments include charges for Utilities, membership fees, subscriptions, insurance premiums, tuition, etc.
  • An Installment Transaction is a transaction in which a cardholder allows a merchant permission to charge their card for a single purchase of goods or services on a pre-determined payment schedule. The merchant must obtain permission to bill the cardholder in an arrangement in which a single purchase of goods/service is divided into two or more payments. Subsequent permission must be obtained when the agreement is modified.

  • Installment transactions have a defined transaction amount, billing cycle, and a total number of payments, which equal the full amount for the original agreed upon purchase. Installment payments include charges for loan payments, car purchase, furniture stores, etc.
  • A Carne Bill Payment Transaction is a Brazilian transaction in which a cardholder enters into an agreement and signs a contract with the Merchant to make regular monthly payments using a domestic Brazilian Debit Card for a current purchase. The cardholder then agrees to return to the store each month and present a domestic Brazilian Debit Card to make a payment according to the terms of the contract.
  • REFERENCE_NUMBER This value is a reference number assigned by Elavon and returned in the authorization response message.
    REQUEST Type of request.
    RESPONSE_CODE This value is a 2 character code indicating the authorization response status. An approval is always indicated with an ‘AA’ or ‘AP’ code, all other codes indicate a non-approval.

    AA = Approved Transaction (Authorizations and Reversals)
    AP = Approved Transaction for a Partial Amount
    NC = Decline (Pick Up Card)
    ND = Decline (Hard or Soft)
    NF = Decline (Record Not Found)
    NR = Decline (Referral Message)
    N7 = Decline (For CVV2 Only)
    NL = Decline (Loyalty/Gift Error)
    00-99 = Decline (Additional Gift Card Declined)
    RETAIL_TRANSACTION_CYCLE_FK Reference to the entity that represents a group of real-time transactions which must be settled together.
    SALES_TAX This is the actual sales tax amount applied to this transaction. Consumer or Merchant tax exempt transactions can enter a single zero to properly reflect a tax exempt transaction.
    SHIPPING_DATE The value is the date that the consumer’s goods were shipped. This value is the “Transaction Date” for direct marketing and ecommerce transactions.

    Shipping Date in MMDDYYYY format.
    STREET_ADDRESS This value is used to identify the cardholder’s street address.
    SURCHARGE_AMOUNT This field is used to indicate the amount of the surcharge applied to the transaction. This amount should be included in the Transaction Amount field.
    TENDER_TYPE The value is used to identify the payment method use to activate or reload a gift card.

    0 = Cash
    1 = Credit Card
    2 = Debit Card
    3 = Check
    9 = Unknown
    TERMINAL_ID The terminal identification number is used to uniquely identify the Merchant and their financial institution to Elavon. The Terminal ID consists of two parts and is assigned by Elavon for each POS device.
    TRACE_NUMBER This value is used as a message reference number identify the transaction request and is returned in all authorization response messages. It is sent to the host on reversal and void messages when applicable.
    TRANSACTION_AMOUNT This is the actual amount of the transaction. The maximum transaction amounts supported are currently $9,999,999.99 for Visa and MasterCard, and $99,999.99 all others card associations.

    For Terminal-Based Settlement messages, this value will contain the total amount of the transaction in the Merchant’s currency, including any Tips (for restaurant transactions).
    For Canadian Debit Authorization Response messages, this field is zero filled and right justified to 12 characters.
    TRANSACTION_CODE This value is used to uniquely identify the type of transaction that is being submitted to Elavon. Refer to the specification of the provider for more information.
    TRANSACTION_REFERENCE_NBR The Transaction Reference Number is returned in the authorization response message and is used on void and reversal transactions, when available. This number is assigned by Elavon.
    UCAF_INDICATOR This value identifies the means in which the transaction was processed between the cardholder and the merchant for a SecureCode authentication transaction.

    0 = UCAF data collection is not supported by the Merchant
    1 = UCAF data collection is supported by merchant but not populated
    2 = UCAF data collection is supported by merchant, and UCAF data must be present
    VOUCHER_CLEAR_NBR The Voucher Number from an EBT sales slip, used for Voucher Clear Food Stamp transactions.
    The 15 digit Voucher Clear Number from the Merchant’s EBT Food Stamp sales slip.
    cards-realtime.vantiv-lowell.authorization.log   
    Added On:  10/20/14
    Level:  Trace
    Category:  cards-realtime.authorization
    Status:  Active
    Group:  processing
    File Name:  cards-realtime.vantiv-lowell.authorization.log
    Resource:  $app-home/jboss-7.4.0/standalone/log/processing/cards-realtime.vantiv-lowell.authorization.log
    Legacy File Name:  cards-realtime.litle.authorization.log
    Сontains information about the processor's incoming requests and outgoing responses (vantiv-lowell)
    Request Fields [Show Info]

    ADDRESS_LINE1, AMOUNT, CAPABILITY, CARDHOLDER_ID, CHARGE_TRANSACTION_FK, CITY, CLINIC_OTHER_AMOUNT, CUSTOMER_ID, DENTAL_AMOUNT, EMAIL, ENTRY_MODE, LITLE_TOKEN, LITLE_TXN_ID, MERCHANT_ACCOUNT_CODE, MERCHANT_ID, NAME, ORDER_ID, ORDER_SOURCE, PAYPAGE_REGISTRATION_ID, PHONE, REPORT_GROUP, REQUEST_ID, RETAIL_TRANSACTION_CYCLE_FK, RX_AMOUNT, STATE, TERMINAL_ID, TOTAL_HEALTHCARE_AMOUNT, TRANSACTION_TYPE, TYPE, USER, VISION_AMOUNT, ZIP
    Name Description
    ADDRESS_LINE1 The elements addressLine1 defines the address information
    AMOUNT The amount element defines the amount of the transaction. Supply the value in cents without a decimal point.
    CAPABILITY The capability element is a required child of the pos element, which describes the capability of the point of sale terminal.
    CARDHOLDER_ID The cardholderId element is a required child of the pos element, which describes the method used for cardholder identification at the point of sale.
    CHARGE_TRANSACTION_FK Reference to the entity that represents real-time financial transaction.
    CITY The city element defines the customer’s city name
    CLINIC_OTHER_AMOUNT This value is used to submit the amount of all Clinical or other qualified medical expenses contained within this purchase.
    CUSTOMER_ID A value assigned by the merchant to identify the consumer.
    DENTAL_AMOUNT
    EMAIL The email element defines the email address of the customer
    ENTRY_MODE The entryMode element is a required child of the pos element, which describes the method used for card data entry at the point of sale.
    LITLE_TOKEN The litleToken element defines the value of the token. The system returns this value in XML responses when issuing new tokens to replace account numbers.
    LITLE_TXN_ID The litleTxnId element is used to identify transactions in the Litle system. The system returns this element in XML responses. You use it in various requests to reference the original transaction.
    MERCHANT_ACCOUNT_CODE Code of Merchant Account to which instance of this object is attributed to.
    Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
    The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
    MERCHANT_ID The merchantId element is used when you request an Account Update file. This value is a unique string used to identify the merchant within the Litle system.
    NAME The name element defines the customer name.
    ORDER_ID The orderId element defines a merchant-assigned value representing the order in the merchant’s system.
    ORDER_SOURCE The orderSource element defines the order entry source for the type of transaction.
    PAYPAGE_REGISTRATION_ID
    PHONE Defines the customers phone number.
    REPORT_GROUP Defines the merchant sub-group in the user interface where this transaction will be displayed.
    REQUEST_ID
    RETAIL_TRANSACTION_CYCLE_FK Reference to the entity that represents a group of real-time transactions which must be settled together.
    RX_AMOUNT
    STATE The state element defines the customer’s state name
    TERMINAL_ID
    TOTAL_HEALTHCARE_AMOUNT
    TRANSACTION_TYPE We use such values:
    C - Credit Transactions
    A - Authorization Transactions
    V - Void Transactions

    The Credit transaction enables you to refund money to a customer, even if the original transaction occurred outside of the Litle & Co. system.
    The Authorization transaction enables you to confirm that a customer has submitted a valid payment method with their order and has sufficient funds to purchase the goods or services they ordered.
    You use a Void transaction to cancel a transaction that occurred during the same business day.
    TYPE Defines the type of account used in the transaction.
    We use such values:
    VI -Visa Credit, Visa Debit,
    MC - MasterCard Credit, MasterCard Debit,
    AX - Amex,
    DI - Discover,
    DC - Dinners
    or empty
    USER The user element is a required child of the authentication element. It is a unique identifier of the user/merchant used to authenticate that the message is from a valid source.
    VISION_AMOUNT
    ZIP The ZIP element defines the customer’s postal code.
    Response Fields [Show Info]

    ADDRESS_LINE1, ADVANCED_AVS_RESULT, AMOUNT, AUTH_CODE, AUTHENTICATION_RESULT, AVS_RESULT, BIN, CAPABILITY, CARD_VALIDATION_RESULT, CARDHOLDER_ID, CHARGE_TRANSACTION_FK, CITY, CLINIC_OTHER_AMOUNT, CUSTOMER_ID, DENTAL_AMOUNT, EMAIL, ENTRY_MODE, LITLE_TOKEN, LITLE_TXN_ID, MERCHANT_ACCOUNT_CODE, MERCHANT_ID, MESSAGE, NAME, ORDER_ID, ORDER_SOURCE, PAYPAGE_REGISTRATION_ID, PHONE, POST_DATE, REPORT_GROUP, REQUEST_ID, RESPONSE, RESPONSE_TIME, RETAIL_TRANSACTION_CYCLE_FK, RX_AMOUNT, STATE, TERMINAL_ID, TOKEN_MESSAGE, TOKEN_RESPONSE_CODE, TOTAL_HEALTHCARE_AMOUNT, TRANSACTION_TYPE, TYPE, USER, VISION_AMOUNT, VOID_LITLE_TXN_ID, ZIP
    Name Description
    ADDRESS_LINE1 The elements addressLine1 defines the address information
    ADVANCED_AVS_RESULT
    AMOUNT The amount element defines the amount of the transaction. Supply the value in cents without a decimal point.
    AUTH_CODE The authCode element it specifies the authorization code from the associated Authorization transaction.
    AUTHENTICATION_RESULT The authenticationResult element defines the Visa CAVV Result code (from Verified by Visa).
    AVS_RESULT The avsResult defines the Address Verification response code returned by the networks.
    BIN The BIN element provides the 6-digit Bank (or Issuer) Identification Number of the Issuing Bank. The system returns this value in XML responses when issuing new tokens to replace Visa or MasterCard account numbers. For Discover and American Express cards, this element is empty.
    CAPABILITY The capability element is a required child of the pos element, which describes the capability of the point of sale terminal.
    CARD_VALIDATION_RESULT The cardValidationResult defines the Card Validation response code returned by the networks.
    CARDHOLDER_ID The cardholderId element is a required child of the pos element, which describes the method used for cardholder identification at the point of sale.
    CHARGE_TRANSACTION_FK Reference to the entity that represents real-time financial transaction.
    CITY The city element defines the customer’s city name
    CLINIC_OTHER_AMOUNT This value is used to submit the amount of all Clinical or other qualified medical expenses contained within this purchase.
    CUSTOMER_ID A value assigned by the merchant to identify the consumer.
    DENTAL_AMOUNT
    EMAIL The email element defines the email address of the customer
    ENTRY_MODE The entryMode element is a required child of the pos element, which describes the method used for card data entry at the point of sale.
    LITLE_TOKEN The litleToken element defines the value of the token. The system returns this value in XML responses when issuing new tokens to replace account numbers.
    LITLE_TXN_ID The litleTxnId element is used to identify transactions in the Litle system. The system returns this element in XML responses. You use it in various requests to reference the original transaction.
    MERCHANT_ACCOUNT_CODE Code of Merchant Account to which instance of this object is attributed to.
    Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
    The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
    MERCHANT_ID The merchantId element is used when you request an Account Update file. This value is a unique string used to identify the merchant within the Litle system.
    MESSAGE The message element provides a brief definition of the response code.
    NAME The name element defines the customer name.
    ORDER_ID The orderId element defines a merchant-assigned value representing the order in the merchant’s system.
    ORDER_SOURCE The orderSource element defines the order entry source for the type of transaction.
    PAYPAGE_REGISTRATION_ID
    PHONE Defines the customers phone number.
    POST_DATE The postDate element defines the date the transaction was posted. The format is YYYY-MM-DD. It occurs only in response to Online transactions.
    REPORT_GROUP Defines the merchant sub-group in the user interface where this transaction will be displayed.
    REQUEST_ID
    RESPONSE The response element contains a three digit numeric code which specifies either that the transaction is approved (000 code) or declined.
    RESPONSE_TIME The responseTime element provides a date/time stamp of the response. The format of the element is YYYY-MM-DDTHH:MM:SS.
    RETAIL_TRANSACTION_CYCLE_FK Reference to the entity that represents a group of real-time transactions which must be settled together.
    RX_AMOUNT
    STATE The state element defines the customer’s state name
    TERMINAL_ID
    TOKEN_MESSAGE The tokenMessage element contains a short, human-readable explanation of the tokenResponseCode.
    TOKEN_RESPONSE_CODE The tokenResponseCode element provides a 3-digit code indicating the results of a transaction involving the conversion or attempted conversion of an account number to a token.
    TOTAL_HEALTHCARE_AMOUNT
    TRANSACTION_TYPE We use such values:
    C - Credit Transactions
    A - Authorization Transactions
    V - Void Transactions

    The Credit transaction enables you to refund money to a customer, even if the original transaction occurred outside of the Litle & Co. system.
    The Authorization transaction enables you to confirm that a customer has submitted a valid payment method with their order and has sufficient funds to purchase the goods or services they ordered.
    You use a Void transaction to cancel a transaction that occurred during the same business day.
    TYPE Defines the type of account used in the transaction.
    We use such values:
    VI -Visa Credit, Visa Debit,
    MC - MasterCard Credit, MasterCard Debit,
    AX - Amex,
    DI - Discover,
    DC - Dinners
    or empty
    USER The user element is a required child of the authentication element. It is a unique identifier of the user/merchant used to authenticate that the message is from a valid source.
    VISION_AMOUNT
    VOID_LITLE_TXN_ID
    ZIP The ZIP element defines the customer’s postal code.
    tokenization.vantiv-lowell.log   
    Added On:  10/20/14
    Level:  Trace
    Category:  tokenization.authorization
    Status:  Active
    Group:  processing
    File Name:  tokenization.vantiv-lowell.log
    Resource:  $app-home/jboss-7.4.0/standalone/log/processing/tokenization.vantiv-lowell.log
    Legacy File Name:  tokenization.litle.authorization.log
    Сontains information about tokenization process (vantiv-lowell)
    Request Fields [Show Info]

    Name Description
    Response Fields [Show Info]

    Name Description
    cards-realtime.paymentech-orbital.authorization.log   
    Added On:  10/20/14
    Level:  Trace
    Category:  cards-realtime.authorization
    Status:  Active
    Group:  processing
    File Name:  cards-realtime.paymentech-orbital.authorization.log
    Resource:  $app-home/jboss-7.4.0/standalone/log/processing/cards-realtime.paymentech-orbital.authorization.log
    Legacy File Name:  cards-realtime.paymenttech.authorization.log
    Сontains information about the processor's incoming requests and outgoing responses (paymentech-orbital)
    Request Fields [Show Info]

    AMOUNT, AVS_ADDRESS1, AVS_CITY, AVS_NAME, AVS_STATE, AVS_ZIP, BIN, CARD_BRAND, CARD_PRESENT_IND, CC_CARD_VERIFY_PRESENCE_IND, CHARGE_TRANSACTION_FK, COMMENTS, CUSTOMER_NAME, DEBIT_BILLER_REFERENCE_NUMBER, INDUSTRY_TYPE, MERCHANT_ACCOUNT_CODE, MERCHANT_ID, ORDER_ID, PARTIAL_AUTH_IND, PCARD_DEST_ZIP, PCARD_ORDER_ID, RETAIL_TRANSACTION_CYCLE_FK, RETRY_TRACE, REVERSAL_RETRY_NUMBER, SHIPPING_REF, TAX_AMOUNT, TAX_IND, TERMINAL_ID, TRANS_TYPE, TX_REF_NUM
    Name Description
    AMOUNT The amount element defines the amount of the transaction. Supply the value in cents without a decimal point.
    AVS_ADDRESS1 Cardholder billing address line 1 (street).
    AVS_CITY Cardholder billing city.
    AVS_NAME Cardholder name.
    AVS_STATE Cardholder billing state code.
    AVS_ZIP Cardholder billing address ZIP (or postal) code.
    BIN Transaction Routing Definition.
    CARD_BRAND Credit card brand.
    CARD_PRESENT_IND Card Presence Identifier:

    Y – Card Present/Swiped
    N – Manually Entry

    CC_CARD_VERIFY_PRESENCE_IND Card Security Presence Indicator
    If a Card Verification Number for a manual entry transaction is attempted to be collected, this value needs to be passed for a Visa or Discover only those cards transaction:
    9 - Cardholder states data not available
    CHARGE_TRANSACTION_FK Reference to the entity that represents real-time financial transaction.
    COMMENTS Any additional comments on the transaction.
    CUSTOMER_NAME Name of the customer.
    DEBIT_BILLER_REFERENCE_NUMBER
    INDUSTRY_TYPE Defines the Industry type of the transaction:
    RE – Retail
    MERCHANT_ACCOUNT_CODE Code of Merchant Account to which instance of this object is attributed to.

    Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.

    The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
    MERCHANT_ID Gateway merchant account number assigned by Chase Paymentech
    ORDER_ID Merchant Defined Order Number/Invoice Number:
    Field defined and supplied by the auth originator, and echoed back in response.
    PARTIAL_AUTH_IND
    PCARD_DEST_ZIP
    PCARD_ORDER_ID
    RETAIL_TRANSACTION_CYCLE_FK Reference to the entity that represents a group of real-time transactions which must be settled together.
    RETRY_TRACE Defines the Trace Number used for Retry Logic.

    The Orbital Gateway offers functionality, referred to as “Retry Logic”, which allows a customer to retry a transaction without
    duplicating the original request.
    The result is any Client properly utilizing Retry Logic can reprocess transactions with an unknown result without:
    • Risk of double authorizing a transaction against a cardholder’s available balance.
    • Prevent duplicate more settlement items.
    REVERSAL_RETRY_NUMBER Allowed number of reversal retries.
    SHIPPING_REF Order shipping reference.
    TAX_AMOUNT Amount of tax.
    TAX_IND Tax indicator.
    TERMINAL_ID Merchant Terminal ID assigned by Chase Paymentech
    TRANS_TYPE Defines the transaction New Order Transaction Type:

    AC – Authorization and Capture
    R – Refund request
    TX_REF_NUM Gateway transaction reference number:
    A unique value for each transaction, which is required to Void any transaction
    Response Fields [Show Info]

    AMOUNT, APPROVAL_STATUS, AUTHORIZATION_CODE, AVS_ADDRESS1, AVS_CITY, AVS_NAME, AVS_RESP_CODE, AVS_STATE, AVS_ZIP, BIN, CARD_BRAND, CARD_PRESENT_IND, CC_CARD_VERIFY_PRESENCE_IND, CHARGE_TRANSACTION_FK, COMMENTS, CUSTOMER_NAME, CVV_RESP_CODE, DEBIT_BILLER_REFERENCE_NUMBER, FAULT_STRING, HOST_AVS_RESP_CODE, HOST_CVV_RESP_CODE, HOST_RESP_CODE, INDUSTRY_TYPE, LAST_RETRY_DATE, MERCHANT_ACCOUNT_CODE, MERCHANT_ID, ORDER_ID, PARTIAL_AUTH_IND, PARTIAL_AUTH_OCCURED, PCARD_DEST_ZIP, PCARD_ORDER_ID, PROC_STATUS, PROC_STATUS_MESSAGE, REDEEMED_AMOUNT, REMAINING_BALANCE, RESP_CODE, RESP_CODE_MESSAGE, RESP_DATE_TIME, RETAIL_TRANSACTION_CYCLE_FK, RETRY_ATTEMPT_COUNT, RETRY_TRACE, REVERSAL_RETRY_NUMBER, SHIPPING_REF, TAX_AMOUNT, TAX_IND, TERMINAL_ID, TRANS_TYPE, TX_REF_IDX, TX_REF_NUM
    Name Description
    AMOUNT The amount element defines the amount of the transaction. Supply the value in cents without a decimal point.
    APPROVAL_STATUS Approval Status:
    0 – Decline
    1 – Approved
    2 – Message/System Error
    AUTHORIZATION_CODE Issuer approval Code: Unique transactional level code issuer uses to show each request was approved
    AVS_ADDRESS1 Cardholder billing address line 1 (street).
    AVS_CITY Cardholder billing city.
    AVS_NAME Cardholder name.
    AVS_RESP_CODE Address verification request response
    AVS_STATE Cardholder billing state code.
    AVS_ZIP Cardholder billing address ZIP (or postal) code.
    BIN Transaction Routing Definition.
    CARD_BRAND Credit card brand.
    CARD_PRESENT_IND Card Presence Identifier:

    Y – Card Present/Swiped
    N – Manually Entry

    CC_CARD_VERIFY_PRESENCE_IND Card Security Presence Indicator
    If a Card Verification Number for a manual entry transaction is attempted to be collected, this value needs to be passed for a Visa or Discover only those cards transaction:
    9 - Cardholder states data not available
    CHARGE_TRANSACTION_FK Reference to the entity that represents real-time financial transaction.
    COMMENTS Any additional comments on the transaction.
    CUSTOMER_NAME Name of the customer.
    CVV_RESP_CODE Card verification number request response
    DEBIT_BILLER_REFERENCE_NUMBER
    FAULT_STRING An error message from a SOAP message can be carried inside a Fault element. If a Fault element is present, it will appear as a
    child element of the Body element. A Fault element can only appear once in a SOAP message.
    The Orbital Gateway SOAP Fault element has the following sub elements:
    -faultcode
    -faultstring

    Fault Code - For errors generated by the Orbital Gateway, this value will be ‘SOAP-ENV:Server’.
    HOST_AVS_RESP_CODE Actual host address verification response code:
    Exact address verification response sent by host authorization system by the gateway.
    HOST_CVV_RESP_CODE Actual host card verification response code:
    Exact card verification response sent by host authorization system by the gateway
    HOST_RESP_CODE Actual host response code:
    Exact response sent by host authorization system by the gateway.
    INDUSTRY_TYPE Defines the Industry type of the transaction:
    RE – Retail
    LAST_RETRY_DATE The Date / time in which the PREVIOUS transaction using the same retryTrace value was processed by gateway:
    Format – ‘YYYYMMDDhh[24]miss’
    MERCHANT_ACCOUNT_CODE Code of Merchant Account to which instance of this object is attributed to.

    Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.

    The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
    MERCHANT_ID Gateway merchant account number assigned by Chase Paymentech
    ORDER_ID Merchant Defined Order Number/Invoice Number:
    Field defined and supplied by the auth originator, and echoed back in response.
    PARTIAL_AUTH_IND
    PARTIAL_AUTH_OCCURED Indicates whether partial authorization occured.
    PCARD_DEST_ZIP
    PCARD_ORDER_ID
    PROC_STATUS Process Status:
    The first data set that should be checked to determine the result of a request. It is the only element that is returned in all response scenarios. It identifies whether transactions have successfully passed all of the Gateway edit checks.
    0 – Success
    All other values constitute an error condition and will be returned in a SOAPFault.
    PROC_STATUS_MESSAGE Response Text message
    If ProcStatus = 0, the ‘approvalStratus’ Message text is returned.
    REDEEMED_AMOUNT
    REMAINING_BALANCE Remaining balance of the credit card of the customer.
    RESP_CODE Response Code:
    Normalized authorization response code issued by the PNS host system, which identifies an approval (‘00’) or the reason for a decline or error.
    Value conditionally returned when procStatus = 0
    RESP_CODE_MESSAGE Response Text message
    RESP_DATE_TIME Date / time the transaction was processed by gateway:
    Format – ‘YYYYMMDDhh[24]miss’
    RETAIL_TRANSACTION_CYCLE_FK Reference to the entity that represents a group of real-time transactions which must be settled together.
    RETRY_ATTEMPT_COUNT Defines the number of times a Transaction Result has been returned:
    0 - First Response retryTrace
    1 or Greater means the Orbital Gateway has processed this request previously and is echoing back the response. The number represents the number of requests processed by the Gateway with the same retryTrace number.
    RETRY_TRACE Defines the Trace Number used for Retry Logic.

    The Orbital Gateway offers functionality, referred to as “Retry Logic”, which allows a customer to retry a transaction without
    duplicating the original request.
    The result is any Client properly utilizing Retry Logic can reprocess transactions with an unknown result without:
    • Risk of double authorizing a transaction against a cardholder’s available balance.
    • Prevent duplicate more settlement items.
    REVERSAL_RETRY_NUMBER Allowed number of reversal retries.
    SHIPPING_REF Order shipping reference.
    TAX_AMOUNT Amount of tax.
    TAX_IND Tax indicator.
    TERMINAL_ID Merchant Terminal ID assigned by Chase Paymentech
    TRANS_TYPE Defines the transaction New Order Transaction Type:

    AC – Authorization and Capture
    R – Refund request
    TX_REF_IDX Gateway transaction index:
    Will always return a ‘0’ value on original transaction and a ‘1’ on void responses.
    TX_REF_NUM Gateway transaction reference number:
    A unique value for each transaction, which is required to Void any transaction
    cards-realtime.paymentech-utf.authorization.log   
    Added On:  10/20/14
    Level:  Trace
    Category:  cards-realtime.authorization
    Status:  Active
    Group:  processing
    File Name:  cards-realtime.paymentech-utf.authorization.log
    Resource:  $app-home/jboss-7.4.0/standalone/log/processing/cards-realtime.paymentech-utf.authorization.log
    Legacy File Name:  cards-realtime.paymenttechutf.authorization.log
    Сontains information about the processor's incoming requests and outgoing responses (paymentech-utf)
    Request Fields [Show Info]

    AV_CARDHOLDER_STREET_ADDRESS, AV_CARDHOLDER_ZIP_CODE, AV_EXTENDED_CARDHOLDER_STREET_ADDRESS, CHARGE_TRANSACTION_FK, CLIENT_NUMBER, ENTRY_DATA_SOURCE, INDUSTRY_CARD_SEQUENCE_NUMBER, INDUSTRY_CARD_TOTAL_NUMBER, INDUSTRY_CASH_OUT_INDICATOR, INDUSTRY_CHARGE_DESCRIPTION, INDUSTRY_CODE, INDUSTRY_ECOMMERCE_GOODS_INDICATOR, INDUSTRY_ELECTRONIC_COMMERCE_INDICATOR, INDUSTRY_EMPLOYEE_NUMBER, INDUSTRY_INVOICE_NUMBER, INDUSTRY_ITEM_CODE, INDUSTRY_REFERENCE_CODE, INDUSTRY_SERVER_NUMBER, INDUSTRY_TIP_AMOUNT, INDUSTRY_TYPE_INDICATOR, LAST_RETRIEVAL_REFERENCE_NUMBER, MARKET_SPECIFIC_DATA_INDICATOR, MERCHANT_ACCOUNT_CODE, MERCHANT_NUMBER, MISC_AUTHORIZATION_CODE, MISC_CASH_BACK_AMOUNT, MISC_EBT_TYPE_CODE, MISC_RETRIEVAL_REFERENCE_NUMBER, PIN_CAPABILITY_CODE, PURCHASE_CUSTOMER_REFERENCE_NUMBER, PURCHASE_DESTINATION_ZIP, PURCHASE_LOCAL_TAX_FLAG, PURCHASE_SALES_TAX_AMOUNT, REQUEST_TOKEN_DATA, RETAIL_TRANSACTION_CYCLE_FK, SEQUENCE_NUMBER, SYSTEM_INDICATOR, TERMINAL_NUMBER, TRANSACTION_AMOUNT, TRANSACTION_CODE, TRANSACTION_SEQUENCE
    Name Description
    AV_CARDHOLDER_STREET_ADDRESS
    AV_CARDHOLDER_ZIP_CODE
    AV_EXTENDED_CARDHOLDER_STREET_ADDRESS
    CHARGE_TRANSACTION_FK Reference to the entity that represents real-time financial transaction.
    CLIENT_NUMBER
    ENTRY_DATA_SOURCE
    INDUSTRY_CARD_SEQUENCE_NUMBER
    INDUSTRY_CARD_TOTAL_NUMBER
    INDUSTRY_CASH_OUT_INDICATOR
    INDUSTRY_CHARGE_DESCRIPTION
    INDUSTRY_CODE
    INDUSTRY_ECOMMERCE_GOODS_INDICATOR
    INDUSTRY_ELECTRONIC_COMMERCE_INDICATOR
    INDUSTRY_EMPLOYEE_NUMBER
    INDUSTRY_INVOICE_NUMBER
    INDUSTRY_ITEM_CODE
    INDUSTRY_REFERENCE_CODE
    INDUSTRY_SERVER_NUMBER
    INDUSTRY_TIP_AMOUNT
    INDUSTRY_TYPE_INDICATOR
    LAST_RETRIEVAL_REFERENCE_NUMBER
    MARKET_SPECIFIC_DATA_INDICATOR
    MERCHANT_ACCOUNT_CODE Code of Merchant Account to which instance of this object is attributed to.
    Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
    The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
    MERCHANT_NUMBER
    MISC_AUTHORIZATION_CODE
    MISC_CASH_BACK_AMOUNT
    MISC_EBT_TYPE_CODE
    MISC_RETRIEVAL_REFERENCE_NUMBER
    PIN_CAPABILITY_CODE
    PURCHASE_CUSTOMER_REFERENCE_NUMBER
    PURCHASE_DESTINATION_ZIP
    PURCHASE_LOCAL_TAX_FLAG
    PURCHASE_SALES_TAX_AMOUNT
    REQUEST_TOKEN_DATA
    RETAIL_TRANSACTION_CYCLE_FK Reference to the entity that represents a group of real-time transactions which must be settled together.
    SEQUENCE_NUMBER
    SYSTEM_INDICATOR
    TERMINAL_NUMBER
    TRANSACTION_AMOUNT
    TRANSACTION_CODE
    TRANSACTION_SEQUENCE_FLAG
    Response Fields [Show Info]

    AV_CARDHOLDER_STREET_ADDRESS, AV_CARDHOLDER_ZIP_CODE, AV_EXTENDED_CARDHOLDER_STREET_ADDRESS, CHARGE_TRANSACTION_FK, CLIENT_NUMBER, ENTRY_DATA_SOURCE, IC_AUTHORIZATION_CHARACTERISTICS_INDICATOR, IC_MC_BANK_NET_DATE, IC_MC_BANK_NET_REFERENCE_NUMBER, IC_MC_CVC_ERROR_INDICATOR, IC_MC_CVC_STATUS_CHANGE, IC_MC_MAGNETIC_STRIPE_QUALITY_INDICATOR, IC_MC_MERCHANT_CATEGORY_CODE, IC_VISA_AUTHORIZATION_RESPONSE_CODE, IC_VISA_AVS_RESPONSE_CODE, IC_VISA_COMMERCIAL_CARD_TYPE, IC_VISA_MERCHANT_CATEGORY_CODE, IC_VISA_POS_ENTRY_MODE, IC_VISA_TOTAL_AUTHORIZATION_AMOUNT, IC_VISA_TRANSACTION_ID, IC_VISA_VALIDATION_CODE, INDUSTRY_CARD_SEQUENCE_NUMBER, INDUSTRY_CARD_TOTAL_NUMBER, INDUSTRY_CASH_OUT_INDICATOR, INDUSTRY_CHARGE_DESCRIPTION, INDUSTRY_CODE, INDUSTRY_ECOMMERCE_GOODS_INDICATOR, INDUSTRY_ELECTRONIC_COMMERCE_INDICATOR, INDUSTRY_EMPLOYEE_NUMBER, INDUSTRY_INVOICE_NUMBER, INDUSTRY_ITEM_CODE, INDUSTRY_REFERENCE_CODE, INDUSTRY_SERVER_NUMBER, INDUSTRY_TIP_AMOUNT, INDUSTRY_TYPE_INDICATOR, LAST_RETRIEVAL_REFERENCE_NUMBER, MARKET_SPEC
    Name Description
    AV_CARDHOLDER_STREET_ADDRESS
    AV_CARDHOLDER_ZIP_CODE
    AV_EXTENDED_CARDHOLDER_STREET_ADDRESS
    CHARGE_TRANSACTION_FK Reference to the entity that represents real-time financial transaction.
    CLIENT_NUMBER
    ENTRY_DATA_SOURCE
    IC_AUTHORIZATION_CHARACTERISTICS_INDICATOR
    IC_MC_BANK_NET_DATE
    IC_MC_BANK_NET_REFERENCE_NUMBER
    IC_MC_CVC_ERROR_INDICATOR
    IC_MC_CVC_STATUS_CHANGE
    IC_MC_MAGNETIC_STRIPE_QUALITY_INDICATOR
    IC_MC_MERCHANT_CATEGORY_CODE
    IC_VISA_AUTHORIZATION_RESPONSE_CODE
    IC_VISA_AVS_RESPONSE_CODE
    IC_VISA_COMMERCIAL_CARD_TYPE
    IC_VISA_MERCHANT_CATEGORY_CODE
    IC_VISA_POS_ENTRY_MODE
    IC_VISA_TOTAL_AUTHORIZATION_AMOUNT
    IC_VISA_TRANSACTION_ID
    IC_VISA_VALIDATION_CODE
    INDUSTRY_CARD_SEQUENCE_NUMBER
    INDUSTRY_CARD_TOTAL_NUMBER
    INDUSTRY_CASH_OUT_INDICATOR
    INDUSTRY_CHARGE_DESCRIPTION
    INDUSTRY_CODE
    INDUSTRY_ECOMMERCE_GOODS_INDICATOR
    INDUSTRY_ELECTRONIC_COMMERCE_INDICATOR
    INDUSTRY_EMPLOYEE_NUMBER
    INDUSTRY_INVOICE_NUMBER
    INDUSTRY_ITEM_CODE
    INDUSTRY_REFERENCE_CODE
    INDUSTRY_SERVER_NUMBER
    INDUSTRY_TIP_AMOUNT
    INDUSTRY_TYPE_INDICATOR
    LAST_RETRIEVAL_REFERENCE_NUMBER
    MARKET_SPECIFIC_DATA_INDICATOR
    MERCHANT_ACCOUNT_CODE Code of Merchant Account to which instance of this object is attributed to.
    Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
    The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
    MERCHANT_NUMBER
    MISC_AUTHORIZATION_CODE
    MISC_CASH_BACK_AMOUNT
    MISC_EBT_TYPE_CODE
    MISC_RETRIEVAL_REFERENCE_NUMBER
    PIN_CAPABILITY_CODE
    PURCHASE_CUSTOMER_REFERENCE_NUMBER
    PURCHASE_DESTINATION_ZIP
    PURCHASE_LOCAL_TAX_FLAG
    PURCHASE_SALES_TAX_AMOUNT
    REQUEST_TOKEN_DATA
    RESPONSE_ACTION_CODE
    RESPONSE_ADDRESS_VERIFICATION_CODE
    RESPONSE_AUTHORIZATION_ERROR_CODE
    RESPONSE_AUTHORIZATION_SOURCE
    RESPONSE_AUTHORIZING_NETWORK_ID
    RESPONSE_BATCH_NUMBER
    RESPONSE_BEGINNING_BALANCE
    RESPONSE_CARD_TYPE
    RESPONSE_CASH_AVAILABLE_BALANCE
    RESPONSE_CASH_BEGINNING_BALANCE
    RESPONSE_CASH_LEDGER_BALANCE
    RESPONSE_FS_AVAILABLE_BALANCE
    RESPONSE_FS_LEDGER_BALANCE
    RESPONSE_MESSAGE
    RESPONSE_RETRIEVAL_REFERENCE_NUMBER
    RESPONSE_TRACE_NUMBER
    RETAIL_TRANSACTION_CYCLE_FK Reference to the entity that represents a group of real-time transactions which must be settled together.
    SEQUENCE_NUMBER
    SYSTEM_INDICATOR
    TERMINAL_NUMBER
    TK_B1_CURRENT_BALANCE_AMOUNT
    TK_B3_PREVIOUS_BALANCE_AMOUNT
    TK_B4_APPROVED_AMOUNT
    TK_B5_CASH_OUT_AMOUNT
    TK_B6_AVAILABLE_BALANCE1_AMOUNT
    TK_B6_AVAILABLE_BALANCE1_CURRENCY_CODE
    TK_B7_AVAILABLE_BALANCE2_AMOUNT
    TK_B7_AVAILABLE_BALANCE2_CURRENCY_CODE
    TK_CV_RESPONSE_VALUE
    TK_ER_FAILED_TOKEN_INDICATOR
    TK_Q8_AUTHORIZATION_TYPE_CODE
    TK_Q8_AUTHORIZED_AMOUNT
    TK_Q8_CARD_TYPE
    TK_VB_CAVV_RESPONSE_DATA
    TK_VC_VISA_CARD_LEVEL_RESULTS_CODE
    TRANSACTION_AMOUNT
    TRANSACTION_CODE
    TRANSACTION_SEQUENCE_FLAG
    cards-realtime.firstdata-north.authorization.log   
    Added On:  10/20/14
    Level:  Trace
    Category:  cards-realtime.authorization
    Status:  Active
    Group:  processing
    File Name:  cards-realtime.firstdata-north.authorization.log
    Resource:  $app-home/jboss-7.4.0/standalone/log/processing/cards-realtime.firstdata-north.authorization.log
    Legacy File Name:  cards-realtime.firstdatanorth.authorization.log
    Сontains information about the processor's incoming requests and outgoing responses (firstdata-north)
    Request Fields [Show Info]

    BIT03_TRANSACTION_AMOUNT, BIT21_TABLE_DS, BIT21_TABLE_SD, BIT21_TABLE_VI, BIT21_TABLE14, BIT21_TABLE48, BIT21_TABLE53, BIT21_TABLE55, BIT21_TABLE60, BIT21_TABLE62, BIT21_TABLE66, BIT21_TABLE68, BIT21_TABLE69, BIT21_TABLE72, BIT22_APPROVAL_CODE, BIT29_POS_ENTRY_MODE, BIT30_POS_PIN_CAPABILITY, BIT31_POS_CONDITION_CODE, BIT36_DEBIT_ACCOUNT_TYPE, BIT37_LOCAL_DATE_TIME, BIT38_DEBIT_RECEIPT_NUMBER, BIT39_CASH_BACK_AMOUNT, BIT43_DEBIT_FUNCTION_CODE, BIT45_ADDRESS_VERIFICATION, CHARGE_TRANSACTION_FK, IS_REVERSAL, MERCHANT_ACCOUNT_CODE, MERCHANT_ID, RETAIL_TRANSACTION_CYCLE_FK, TRANSACTION_CODE
    Name Description
    BIT03_TRANSACTION_AMOUNT
    BIT21_TABLE_DS
    BIT21_TABLE_SD
    BIT21_TABLE_VI
    BIT21_TABLE14
    BIT21_TABLE48
    BIT21_TABLE53
    BIT21_TABLE55
    BIT21_TABLE60
    BIT21_TABLE62
    BIT21_TABLE66
    BIT21_TABLE68
    BIT21_TABLE69
    BIT21_TABLE72
    BIT22_APPROVAL_CODE
    BIT29_POS_ENTRY_MODE
    BIT30_POS_PIN_CAPABILITY
    BIT31_POS_CONDITION_CODE
    BIT36_DEBIT_ACCOUNT_TYPE
    BIT37_LOCAL_DATE_TIME
    BIT38_DEBIT_RECEIPT_NUMBER
    BIT39_CASH_BACK_AMOUNT
    BIT43_DEBIT_FUNCTION_CODE
    BIT45_ADDRESS_VERIFICATION
    CHARGE_TRANSACTION_FK Reference to the entity that represents real-time financial transaction.
    IS_REVERSAL
    MERCHANT_ACCOUNT_CODE Code of Merchant Account to which instance of this object is attributed to.
    Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
    The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
    MERCHANT_ID Merchant ID assigned by FirstData.
    RETAIL_TRANSACTION_CYCLE_FK Reference to the entity that represents a group of real-time transactions which must be settled together.
    TRANSACTION_CODE
    Response Fields [Show Info]

    APPROVAL_CODE, APPROVAL_DATE, AUTHORIZED_AMOUNT, AVS_RESPONSE_CODE, BALANCE1_ACCOUNT_TYPE, BALANCE1_AMOUNT, BALANCE1_AMOUNT_TYPE, BALANCE1_CURRENCY_TYPE, BALANCE1_SIGN, BALANCE2_ACCOUNT_TYPE, BALANCE2_AMOUNT, BALANCE2_AMOUNT_TYPE, BALANCE2_CURRENCY_TYPE, BALANCE2_SIGN, BALANCE3_ACCOUNT_TYPE, BALANCE3_AMOUNT, BALANCE3_AMOUNT_TYPE, BALANCE3_CURRENCY_TYPE, BALANCE3_SIGN, BALANCE4_ACCOUNT_TYPE, BALANCE4_AMOUNT, BALANCE4_AMOUNT_TYPE, BALANCE4_CURRENCY_TYPE, BALANCE4_SIGN, BALANCE5_ACCOUNT_TYPE, BALANCE5_AMOUNT, BALANCE5_AMOUNT_TYPE, BALANCE5_CURRENCY_TYPE, BALANCE5_SIGN, BALANCE6_ACCOUNT_TYPE, BALANCE6_AMOUNT, BALANCE6_AMOUNT_TYPE, BALANCE6_CURRENCY_TYPE, BALANCE6_SIGN, BIT03_TRANSACTION_AMOUNT, BIT21_TABLE_DS, BIT21_TABLE_DS_RESPONSE, BIT21_TABLE_SD, BIT21_TABLE_VI, BIT21_TABLE_VI_RESPONSE, BIT21_TABLE14, BIT21_TABLE14_RESPONSE, BIT21_TABLE48, BIT21_TABLE48_RESPONSE, BIT21_TABLE49_RESPONSE, BIT21_TABLE53, BIT21_TABLE53_RESPONSE, BIT21_TABLE55, BIT21_TABLE55_RESPONSE, BIT21_TABLE60, BIT21_TABLE62, BIT21_TABLE62_RE
    Name Description
    APPROVAL_CODE Authorization code returned by Provider that approved this transaction. In some instances might also be used to store response code returned by Provider when transaction declines.
    APPROVAL_DATE
    AUTHORIZED_AMOUNT The total authorized amount for the authorization request. If the Partial authorization flag is enabled, this amount may be less than the requested amount.
    AVS_RESPONSE_CODE Address Verification Response. One character code indicating the response of the Address Verification process.
    BALANCE1_ACCOUNT_TYPE
    BALANCE1_AMOUNT
    BALANCE1_AMOUNT_TYPE
    BALANCE1_CURRENCY_TYPE
    BALANCE1_SIGN
    BALANCE2_ACCOUNT_TYPE
    BALANCE2_AMOUNT
    BALANCE2_AMOUNT_TYPE
    BALANCE2_CURRENCY_TYPE
    BALANCE2_SIGN
    BALANCE3_ACCOUNT_TYPE
    BALANCE3_AMOUNT
    BALANCE3_AMOUNT_TYPE
    BALANCE3_CURRENCY_TYPE
    BALANCE3_SIGN
    BALANCE4_ACCOUNT_TYPE
    BALANCE4_AMOUNT
    BALANCE4_AMOUNT_TYPE
    BALANCE4_CURRENCY_TYPE
    BALANCE4_SIGN
    BALANCE5_ACCOUNT_TYPE
    BALANCE5_AMOUNT
    BALANCE5_AMOUNT_TYPE
    BALANCE5_CURRENCY_TYPE
    BALANCE5_SIGN
    BALANCE6_ACCOUNT_TYPE
    BALANCE6_AMOUNT
    BALANCE6_AMOUNT_TYPE
    BALANCE6_CURRENCY_TYPE
    BALANCE6_SIGN
    BIT03_TRANSACTION_AMOUNT
    BIT21_TABLE_DS
    BIT21_TABLE_DS_RESPONSE
    BIT21_TABLE_SD
    BIT21_TABLE_VI
    BIT21_TABLE_VI_RESPONSE
    BIT21_TABLE14
    BIT21_TABLE14_RESPONSE
    BIT21_TABLE48
    BIT21_TABLE48_RESPONSE
    BIT21_TABLE49_RESPONSE
    BIT21_TABLE53
    BIT21_TABLE53_RESPONSE
    BIT21_TABLE55
    BIT21_TABLE55_RESPONSE
    BIT21_TABLE60
    BIT21_TABLE62
    BIT21_TABLE62_RESPONSE
    BIT21_TABLE66
    BIT21_TABLE66_RESPONSE
    BIT21_TABLE68
    BIT21_TABLE68_RESPONSE
    BIT21_TABLE69
    BIT21_TABLE72
    BIT22_APPROVAL_CODE
    BIT29_POS_ENTRY_MODE
    BIT30_POS_PIN_CAPABILITY
    BIT31_POS_CONDITION_CODE
    BIT36_DEBIT_ACCOUNT_TYPE
    BIT37_LOCAL_DATE_TIME
    BIT38_DEBIT_RECEIPT_NUMBER
    BIT39_CASH_BACK_AMOUNT
    BIT43_DEBIT_FUNCTION_CODE
    BIT45_ADDRESS_VERIFICATION
    CAPTURE_FLAG
    CHARGE_TRANSACTION_FK Reference to the entity that represents real-time financial transaction.
    IS_REVERSAL
    MERCHANT_ACCOUNT_CODE Code of Merchant Account to which instance of this object is attributed to.
    Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
    The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
    RESPONSE_MESSAGE
    RETAIL_TRANSACTION_CYCLE_FK Reference to the entity that represents a group of real-time transactions which must be settled together.
    TRANSACTION_CODE
    cards-realtime.firstdata-compass.authorization.log   
    Added On:  10/20/14
    Level:  Trace
    Category:  cards-realtime.authorization
    Status:  Active
    Group:  processing
    File Name:  cards-realtime.firstdata-compass.authorization.log
    Resource:  $app-home/jboss-7.4.0/standalone/log/processing/cards-realtime.firstdata-compass.authorization.log
    Legacy File Name:  cards-realtime.firstdatacompass.authorization.log
    Сontains information about the processor's incoming requests and outgoing responses (firstdata-compass)
    Request Fields [Show Info]

    ACTION_CODE, ADDRESS_LINE1, AMOUNT, AUTHORIZATION_CODE, BILLER_REFERENCE_NUMBER, CARD_SECURITY_PRESENCE, CITY, CLIENT_REF, COUNTRY_CODE, DIVISION_NUMBER, ENCRYPTION_FLAG, LENGTH_INDICATOR, MERCHANT_ACCOUNT_CODE, MOP_REQUEST, NAME_TEXT, ORDER_NUMBER, PARTIAL_REDEMPTION_INDICATOR, POSTAL_CODE, RESPONSE_DATE, RETAIL_TRANSACTION_CYCLE_FK, STATE, TERMINAL_ID, TOKEN_TYPE, TPP_ID, TRACK_INDICATOR, TRANSACTION_TYPE
    Name Description
    ACTION_CODE This action tells First Data what service to perform on the transaction.

    We use:
    DR - Refund Auth Reversal (PINLess Debit)
    PR - Purchase Auth Reversal (PINLess Debit)
    AR - Authorization Reversal (Amex, MasterCard, Visa, Discover, JCB, GoogleCheckout, PayPal, ValueLink)
    RA - Refund Auth (PINLess Debit)
    PA - Purchase Auth (PINLess Debit)
    AU - Authorize (Credit Card, Alt Pay, ValueLink)
    ADDRESS_LINE1 Accountholder’s address information
    AMOUNT Amount of the authorization. 2 decimal implied. Minimum amount for all card types is $0.01 U.S. dollars* (or established international currency equivalent), but no greater than the established Transaction Division limit. The default is $99,999.99
    AUTHORIZATION_CODE Authorization code of the approved, original, authorized transaction. This field cannot be blank or the transaction will reject with Response Reason Code 262 (Authorization Code/Response Date Invalid).
    BILLER_REFERENCE_NUMBER Reference number the biller (merchant) uses on his system to identify this customer
    CARD_SECURITY_PRESENCE Used to validate the presence of a card security value.

    We use:
    1 – Value is present (DI, MC, MD, or VI)
    “ ” – Blank, indicator not sent (AX, MC, MD)
    CITY Accountholder’s city.
    CLIENT_REF Unique value, that identifies the transaction.

    This value is calculated by the gateway, according to the processor's specification rules. This value is taken into account by the processor on the communications layer.
    COUNTRY_CODE Accountholder’s country code.
    DIVISION_NUMBER Assigned and provided to merchant by First Data. First Data assigns a unique Division Number to process each international currency. A single Division Number can support different transaction types and methods of payment in the same currency.
    ENCRYPTION_FLAG Indicates transaction token status.
    Possible values:
    PAN – TransArmor token request (or on response if tokenization failure and PAN masked;
    TOK – TransArmor token supplied.

    LENGTH_INDICATOR Indicates the number of positions submitted for the following field
    MERCHANT_ACCOUNT_CODE Code of Merchant Account to which instance of this object is attributed to.
    Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
    The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
    MOP_REQUEST Method of Payment (MOP) defines the MOP associated with this transaction.
    NAME_TEXT Accountholder’s name (asterisk should precede last name).
    ORDER_NUMBER A value composed of any alpha, blank, digit, or punctuation combination that will be returned in the transaction response. This field will tie the merchant’s request to the First Data response.
    PARTIAL_REDEMPTION_INDICATOR Determines approval functionality for pre-paid/gift card authorizations.

    Valid values for American Express:
    Y – Transaction is not declined if authorization amount is greater than the current balance
    N – Transaction is declined if authorization amount is greater than the current balance

    Valid values for Discover:
    Y – The sale amount can be partially approved but the cash back amount cannot be partially approved.
    N – Merchant does not support partial authorization. Partial authorization not allowed for both sale amount and cash back amount.

    Valid values for Visa/MasterCard/MasterCard Diners:
    Y – Attempt a partial authorization if allowed for the account.
    N – Do not attempt a partial authorization.
    POSTAL_CODE Accountholder’s postal code.
    RESPONSE_DATE Date of approved, original, authorized transaction. YYMMDD format.
    Response date must be current or prior date or the transaction will reject with Response Reason Code 262 (Authorization Code/Response Date Invalid).
    RETAIL_TRANSACTION_CYCLE_FK Reference to the entity that represents a group of real-time transactions which must be settled together.
    STATE Accountholder’s state.
    TERMINAL_ID Terminal identification – code identifying the balancing features available to the POS from the Host.
    TOKEN_TYPE Merchant Specific Token Value issued by First Data.
    This Format record will be returned on all TransArmor submissions.
    TPP_ID Third Party Processor ID is mandatory on all Authorization requests submitted by Third Parties who have been issued one by First Data.

    If you were assigned a Third Party Processor ID, you are required to send this additional format record.
    If you were not assigned a Third Party Processor ID, this record should not be sent.
    TRACK_INDICATOR Track that was read.

    Valid values: 1 – Track 1 2 – Track 2
    TRANSACTION_TYPE Describes the circumstances under which the transaction takes place. Default space filled.

    We use:
    1 – MOTO Indicator – Single Transaction Mail/telephone order: designates a transaction where the cardholder is not present at a merchant location and consummates the sale via the phone or through the mail. The transaction is not for recurring services or product and does not include sales that are processed via an installment plan.
    2 – MOTO Indicator – Recurring Transaction: Designates a transaction that represents an arrangement between a cardholder and the merchant where transactions are going to occur on a periodic basis.
    3 – MOTO Indicator – Installment Payment: Designates a group of transactions that originated from a single purchase where the merchant agrees to bill the cardholder in installments.
    7 – ECI Indicator – Channel Encrypted Transaction: Designates a transaction between a cardholder and a merchant consummated via the Internet where the transaction includes the use of transaction encryption such as SSL, but authentication was not performed. The cardholder payment data was protected with a form of Internet security, such as SSL, but authentication was not performed.
    R – Retail Indicator – designates a transaction where the cardholder was present at a merchant location. If an “R” is sent for a transaction with a MOTO Merchant Category Code (MCC) the transaction will downgrade.
    Response Fields [Show Info]

    ACTION_CODE, ADDRESS_LINE1, AMOUNT, AUTHORIZATION_CODE, AVS_RESPONSE_CODE, BILLER_REFERENCE_NUMBER, CARD_SECURITY_PRESENCE, CAVV_RESPONSE_CODE, CITY, CLIENT_REF, COUNTRY_CODE, CSV_RESPONSE_CODE, CURRENT_BALANCE, DIVISION_NUMBER, ENCRYPTION_FLAG, FIRST_DATA_TOKEN_CODE, LENGTH_INDICATOR, MERCHANT_ACCOUNT_CODE, MOP_REQUEST, NAME_TEXT, ORDER_NUMBER, PARTIAL_REDEMPTION_INDICATOR, POSTAL_CODE, RECURRING_PAYMENT_ADVICE_CODE, REDEMPTION_AMOUNT, RESPONSE_DATE, RESPONSE_REASON_CODE, RETAIL_TRANSACTION_CYCLE_FK, STATE, SURCHARGE_AMOUNT, TERMINAL_ID, TOKEN_TYPE, TOTAL_AMOUNT, TPP_ID, TRACE_NUMBER, TRACK_INDICATOR, TRANSACTION_TYPE
    Name Description
    ACTION_CODE This action tells First Data what service to perform on the transaction.

    We use:
    DR - Refund Auth Reversal (PINLess Debit)
    PR - Purchase Auth Reversal (PINLess Debit)
    AR - Authorization Reversal (Amex, MasterCard, Visa, Discover, JCB, GoogleCheckout, PayPal, ValueLink)
    RA - Refund Auth (PINLess Debit)
    PA - Purchase Auth (PINLess Debit)
    AU - Authorize (Credit Card, Alt Pay, ValueLink)
    ADDRESS_LINE1 Accountholder’s address information
    AMOUNT Amount of the authorization. 2 decimal implied. Minimum amount for all card types is $0.01 U.S. dollars* (or established international currency equivalent), but no greater than the established Transaction Division limit. The default is $99,999.99
    AUTHORIZATION_CODE Authorization code of the approved, original, authorized transaction. This field cannot be blank or the transaction will reject with Response Reason Code 262 (Authorization Code/Response Date Invalid).
    AVS_RESPONSE_CODE Response to address verification request.
    BILLER_REFERENCE_NUMBER Reference number the biller (merchant) uses on his system to identify this customer
    CARD_SECURITY_PRESENCE Used to validate the presence of a card security value.

    We use:
    1 – Value is present (DI, MC, MD, or VI)
    “ ” – Blank, indicator not sent (AX, MC, MD)
    CAVV_RESPONSE_CODE This field will be populated for any Verified by Visa transaction.
    It is used during authorization processing to verify that authentication, or attempted authentication, was performed. The Issuer receives the authorization request and validates the CAVV and responds with a CAVV response code, as well as an approval or a decline of the authorization. If the CAVV does not match, the Issuer should decline the transaction.
    CITY Accountholder’s city.
    CLIENT_REF Unique value, that identifies the transaction.

    This value is calculated by the gateway, according to the processor's specification rules. This value is taken into account by the processor on the communications layer.
    COUNTRY_CODE Accountholder’s country code.
    CSV_RESPONSE_CODE Card Security Value Response Code returned by the card Issuer in response to a card security verification request.
    CURRENT_BALANCE Current Balance
    DIVISION_NUMBER Assigned and provided to merchant by First Data. First Data assigns a unique Division Number to process each international currency. A single Division Number can support different transaction types and methods of payment in the same currency.
    ENCRYPTION_FLAG Indicates transaction token status.
    Possible values:
    PAN – TransArmor token request (or on response if tokenization failure and PAN masked;
    TOK – TransArmor token supplied.

    FIRST_DATA_TOKEN_CODE The tokenized value of Account Number.
    LENGTH_INDICATOR Indicates the number of positions submitted for the following field
    MERCHANT_ACCOUNT_CODE Code of Merchant Account to which instance of this object is attributed to.
    Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
    The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
    MOP_REQUEST Method of Payment (MOP) defines the MOP associated with this transaction.
    NAME_TEXT Accountholder’s name (asterisk should precede last name).
    ORDER_NUMBER A value composed of any alpha, blank, digit, or punctuation combination that will be returned in the transaction response. This field will tie the merchant’s request to the First Data response.
    PARTIAL_REDEMPTION_INDICATOR Determines approval functionality for pre-paid/gift card authorizations.

    Valid values for American Express:
    Y – Transaction is not declined if authorization amount is greater than the current balance
    N – Transaction is declined if authorization amount is greater than the current balance

    Valid values for Discover:
    Y – The sale amount can be partially approved but the cash back amount cannot be partially approved.
    N – Merchant does not support partial authorization. Partial authorization not allowed for both sale amount and cash back amount.

    Valid values for Visa/MasterCard/MasterCard Diners:
    Y – Attempt a partial authorization if allowed for the account.
    N – Do not attempt a partial authorization.
    POSTAL_CODE Accountholder’s postal code.
    RECURRING_PAYMENT_ADVICE_CODE Field Recurring payment advice code (MasterCard/MasterCard Diners Only) has such valid values:
    01 – New account information available. Obtain new account information.
    02 – Try again later. Recycle transaction in 72 hours.
    03 – Do not try again. Obtain another type of payment from customer.
    21 – Do not try again. Issuer has blocked recurring payment transaction. Default space filled
    REDEMPTION_AMOUNT Approved amount. Partial authorization is done and redemption amount is returned if authorized amount > available balance.
    RESPONSE_DATE Date of approved, original, authorized transaction. YYMMDD format.
    Response date must be current or prior date or the transaction will reject with Response Reason Code 262 (Authorization Code/Response Date Invalid).
    RESPONSE_REASON_CODE Description of the response code
    RETAIL_TRANSACTION_CYCLE_FK Reference to the entity that represents a group of real-time transactions which must be settled together.
    STATE Accountholder’s state.
    SURCHARGE_AMOUNT Amount of surcharge
    TERMINAL_ID Terminal identification – code identifying the balancing features available to the POS from the Host.
    TOKEN_TYPE Merchant Specific Token Value issued by First Data.
    This Format record will be returned on all TransArmor submissions.
    TOTAL_AMOUNT Total transaction amount, including surcharge (if any)
    TPP_ID Third Party Processor ID is mandatory on all Authorization requests submitted by Third Parties who have been issued one by First Data.

    If you were assigned a Third Party Processor ID, you are required to send this additional format record.
    If you were not assigned a Third Party Processor ID, this record should not be sent.
    TRACE_NUMBER Trace number returned from debit vendor
    TRACK_INDICATOR Track that was read.

    Valid values: 1 – Track 1 2 – Track 2
    TRANSACTION_TYPE Describes the circumstances under which the transaction takes place. Default space filled.

    We use:
    1 – MOTO Indicator – Single Transaction Mail/telephone order: designates a transaction where the cardholder is not present at a merchant location and consummates the sale via the phone or through the mail. The transaction is not for recurring services or product and does not include sales that are processed via an installment plan.
    2 – MOTO Indicator – Recurring Transaction: Designates a transaction that represents an arrangement between a cardholder and the merchant where transactions are going to occur on a periodic basis.
    3 – MOTO Indicator – Installment Payment: Designates a group of transactions that originated from a single purchase where the merchant agrees to bill the cardholder in installments.
    7 – ECI Indicator – Channel Encrypted Transaction: Designates a transaction between a cardholder and a merchant consummated via the Internet where the transaction includes the use of transaction encryption such as SSL, but authentication was not performed. The cardholder payment data was protected with a form of Internet security, such as SSL, but authentication was not performed.
    R – Retail Indicator – designates a transaction where the cardholder was present at a merchant location. If an “R” is sent for a transaction with a MOTO Merchant Category Code (MCC) the transaction will downgrade.
    cards-realtime.firstdata-linkpoint.authorization.log   
    Added On:  10/20/14
    Level:  Trace
    Category:  cards-realtime.authorization
    Status:  Active
    Group:  processing
    File Name:  cards-realtime.firstdata-linkpoint.authorization.log
    Resource:  $app-home/jboss-7.4.0/standalone/log/processing/cards-realtime.firstdata-linkpoint.authorization.log
    Legacy File Name:  cards-realtime.firstdatalinkpoint.authorization.log
    Сontains information about the processor's incoming requests and outgoing responses (firstdata-linkpoint)
    Request Fields [Show Info]

    ADDRESS1, ADDRNUM, CARDEXPMONTH, CARDEXPYEAR, CHARGE_TRANSACTION_FK, CHARGETOTAL, CITY, COMPANY, CONFIGFILE, CVMINDICATOR, MERCHANT_ACCOUNT_CODE, NAME, OID, ORDERTYPE, PHONE, RETAIL_TRANSACTION_CYCLE_FK, STATE, TDATE, TERMINALTYPE, TRANSACTIONORIGIN, USERID, ZIP
    Name Description
    ADDRESS1 The first line of the customer's billing street address.
    ADDRNUM The numeric portion of the street address.
    CARDEXPMONTH The numeric expiration month of the credit card
    CARDEXPYEAR Expiration year of the credit card
    CHARGE_TRANSACTION_FK Reference to the entity that represents real-time financial transaction.
    CHARGETOTAL The total dollar amount of this transaction including subtotal, tax, and shipping
    CITY Billing city
    COMPANY Company name
    CONFIGFILE This field should contain the merchant store name or store number
    CVMINDICATOR Indicates whether the card code was supplied. We use such values:
    - provided
    - not_provided
    MERCHANT_ACCOUNT_CODE Code of Merchant Account to which instance of this object is attributed to.
    Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
    The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
    NAME Customer's name
    OID The order Id to be assigned to the transaction. For sale and pre-authorization transactions, this field must be unique. For void, credit and post-authorization transactions this field must be a valid Order Id from a prior Sale or pre-authorization transaction.
    ORDERTYPE The type of transaction. We use such values: Sale, Void, Credit
    PHONE Billing phone number. The number shouldn't contain dashes.
    RETAIL_TRANSACTION_CYCLE_FK Reference to the entity that represents a group of real-time transactions which must be settled together.
    STATE U.S. state of billing address. For international addresses, this field can be used for the province or territory
    TDATE This field is returned with every successful transaction. If you want to run a void or other transaction against an existing order ID, you may need to pass the Tdate field to identity the specific transaction you want to void.
    TERMINALTYPE The type of terminal that is sending the transaction. We use such value:
    - POS (for an electronic cash register or integrated POS system)
    TRANSACTIONORIGIN The source of the transaction. We use such values:
    Eci - if order was received via email or Internet
    MOTO - mail order/telephone order
    Retail - face to face
    USERID The userid field is an optional custom field to track customers.
    ZIP Billing ZIP or postal code.
    Response Fields [Show Info]

    CHARGE_TRANSACTION_FK, MERCHANT_ACCOUNT_CODE, RAPPROVED, RAUTHRESPONSE, RAVS, RCODE, RERROR, RETAIL_TRANSACTION_CYCLE_FK, RMESSAGE, RREF, RTDATE, RTIME
    Name Description
    CHARGE_TRANSACTION_FK Reference to the entity that represents real-time financial transaction.
    MERCHANT_ACCOUNT_CODE Code of Merchant Account to which instance of this object is attributed to.
    Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
    The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
    RAPPROVED The result of the transaction, which may be approved, declined, or blockedbecause of fraud.
    RAUTHRESPONSE Authentication results returned from Verified By Visa and MasterCard Secure Code.
    RAVS The Address Verification System response for the transaction.
    RCODE The approval code for the transaction
    RERROR Any error message associated with the transaction.
    RETAIL_TRANSACTION_CYCLE_FK Reference to the entity that represents a group of real-time transactions which must be settled together.
    RMESSAGE Any message returned by the processor
    RREF The reference number returned by the credit card processor.
    RTDATE A server time-date stamp for the transaction. Used to uniquely identify a specific transaction where one order number may apply to several individual transactions
    RTIME The time and date of the transaction server response.
    cards-realtime.firstdata-omaha.authorization.log   
    Added On:  10/20/14
    Level:  Trace
    Category:  cards-realtime.authorization
    Status:  Active
    Group:  processing
    File Name:  cards-realtime.firstdata-omaha.authorization.log
    Resource:  $app-home/jboss-7.4.0/standalone/log/processing/cards-realtime.firstdata-omaha.authorization.log
    Legacy File Name:  cards-realtime.firstdataomaha.authorization.log
    Сontains information about the processor's incoming requests and outgoing responses (firstdata-omaha)
    Request Fields [Show Info]

    AUTH_CHAR_INDICATOR_REQUEST, AUTHORIZATION_CODE, AVS_ADDRESS, AVS_RESPONSE_CODE, AVS_ZIP_CODE, BATCH_NUMBER, CARD_TYPE_INDICATOR, CARD_VERIFICATION_PRESENCE_INDICATOR, CARDHOLDER_SET_CERTIFICATE_SERIAL_NUMBER, CASH_BACK_AMOUNT, CHARGE_TRANSACTION_FK, CUSTOMER_CODE, DEVICE_ID, EBT_VOUCHER_NUMBER, FORMAT_CODE, INVOICE_NUMBER, ITEM_NUMBER, MERCHANT_ACCOUNT_CODE, MERCHANT_NUMBER, MERCHANT_SET_CERTIFICATE_SERIAL_NUMBER, ORDER_NUMBER, PARTIAL_AUTHORIZATION_INDICATOR, PHONE_MAIL_ORDER_FLAG, POS_DATA_CODES, PROTOCOL_TYPE, RETAIL_TRANSACTION_CYCLE_FK, REVISION_NUMBER, SHIP_TO_POSTAL_CODE, SURCHARGE, TAX_AMOUNT, TERMINAL_ID, TIP_AMOUNT, TOTAL_AMOUNT, TOTAL_AUTHORIZED_AMOUNT, TPP, TRANS_STAIN, TRANSACTION_CODE, TRANSACTION_IDENTIFIER, TRANSACTION_TYPE, WRITE_CONTROL_CHARACTER, XID
    Name Description
    AUTH_CHAR_INDICATOR_REQUEST Code identifying the type of transaction approval.
    AUTHORIZATION_CODE Numeric or alphanumeric code assigned to a transaction as verification that a transaction has been approved.
    AVS_ADDRESS Principal cardholder‘s address entered for address verification.
    AVS_RESPONSE_CODE Code indicating whether address verification was performed and the results.
    AVS_ZIP_CODE ZIP (or postal) code of principal cardholder‘s address entered for address verification.
    BATCH_NUMBER Number identifying the batch; assigned by the POS device.
    CARD_TYPE_INDICATOR Character indicating the type of card.
    CARD_VERIFICATION_PRESENCE_INDICATOR Character that indicates whether the CVV2/CVC2/CID value is included with message packet.
    CARDHOLDER_SET_CERTIFICATE_SERIAL_NUMBER Cardholder Secure Electronic Transaction Certificate Serial number.
    CASH_BACK_AMOUNT Dollar-and-cent amount ($$$.¢¢) of a debit/EBT cash back amount.
    CHARGE_TRANSACTION_FK Reference to the entity that represents real-time financial transaction.
    CUSTOMER_CODE Merchant-assigned code.
    DEVICE_ID Merchant-assigned code identifying the device at the merchant‘s location.
    EBT_VOUCHER_NUMBER Number from EBT Voucher Form.
    FORMAT_CODE Code indicating the type of format for the message to the Host.
    INVOICE_NUMBER Merchant-defined number.
    ITEM_NUMBER Number of the transaction in the batch; assigned by the POS.
    MERCHANT_ACCOUNT_CODE Code of Merchant Account to which instance of this object is attributed to.
    Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
    The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
    MERCHANT_NUMBER Number assigned by merchant‘s financial institution.
    MERCHANT_SET_CERTIFICATE_SERIAL_NUMBER Merchant Secure Electronic Transaction Certificate Serial number.
    ORDER_NUMBER Merchant-defined number identifying the purchase or service.
    PARTIAL_AUTHORIZATION_INDICATOR Value will be blank for Online Void.
    PHONE_MAIL_ORDER_FLAG Code identifying whether the transaction is mail order, phone order or electronic commerce.
    POS_DATA_CODES POS Codes for American Express Ticket Only (Tran Code 3) transaction. Contact American Express to determine how these values are generated and used for American Express.
    PROTOCOL_TYPE Character identifying which protocol rule the transaction follows; required field.
    RETAIL_TRANSACTION_CYCLE_FK Reference to the entity that represents a group of real-time transactions which must be settled together.
    REVISION_NUMBER Number identifying the number of revisions to a monetary transaction.
    SHIP_TO_POSTAL_CODE This is a mandatory field for supporting Amex Level 2 Transactions.
    SURCHARGE Dollar-and-cent amount ($$$.¢¢) of the charge that the cardholder paid the merchant for the ability to perform the transaction.
    TAX_AMOUNT Dollar-and-cent amount ($$$$$.¢¢) of tax for the purchase.
    TERMINAL_ID Code identifying the balancing features available to the POS from the Host.
    TIP_AMOUNT Dollar-and-cent amount ($$$.¢¢) of the tip given at the restaurant for the purchase.
    TOTAL_AMOUNT Total dollar-and-cent amount ($$$$$.¢¢) of the purchase.
    TOTAL_AUTHORIZED_AMOUNT Dollar-and-cent amount ($$$$$.¢¢) of the purchase.
    TPP If a First Data assigned TPP value is not available do not send this field with a default value.
    TRANS_STAIN A value used to define a merchant‘s security settings for SET.
    TRANSACTION_CODE Code identifying how the System will respond to the transaction request.
    TRANSACTION_IDENTIFIER Code generated by the card associations on the authorization; known as TID for Visa and BankNet Reference Number for MasterCard.
    TRANSACTION_TYPE Code identifying how the System will respond to the transaction request.
    WRITE_CONTROL_CHARACTER Character identifying the account number entry method and Host response protocol (single or multiple mode).
    XID A unique transaction identifier assigned to a SET Transaction.
    Response Fields [Show Info]

    ACTION_CODE, ADDITIONAL_RESPONSE_INDICATOR, APPROVED_AMOUNT, AUTH_CHAR_INDICATOR_REQUEST, AUTHORIZATION_CODE, AVS_ADDRESS, AVS_RESPONSE_CODE, AVS_ZIP_CODE, BALANCE_SIGN, BATCH_NUMBER, CARD_TYPE_INDICATOR, CARD_VERIFICATION_PRESENCE_INDICATOR, CARD_VERIFICATION_RESPONSE_CODE, CARDHOLDER_SET_CERTIFICATE_SERIAL_NUMBER, CASH_BACK_AMOUNT, CHARGE_TRANSACTION_FK, CUSTOMER_CODE, DEBIT_CARD_TYPE_NUMBER, DEBIT_NETWORK_NAME, DEVICE_ID, EBT_RESPONSE_CODE, EBT_VOUCHER_NUMBER, FORMAT_CODE, INVOICE_NUMBER, ITEM_NUMBER, MERCHANT_ACCOUNT_CODE, MERCHANT_NUMBER, MERCHANT_SET_CERTIFICATE_SERIAL_NUMBER, ORDER_NUMBER, PARTIAL_AUTHORIZATION_INDICATOR, PHONE_MAIL_ORDER_FLAG, POS_DATA_CODES, PROTOCOL_TYPE, REMAINING_BALANCE, REQUESTED_AMOUNT, RESPONSE_CODE, RESPONSE_TEXT, RETAIL_TRANSACTION_CYCLE_FK, REVISION_NUMBER, SURCHARGE, TAX_AMOUNT, TERMINAL_ID, TIP_AMOUNT, TOTAL_AMOUNT, TOTAL_AUTHORIZED_AMOUNT, TPP, TRANS_STAIN, TRANSACTION_CODE, TRANSACTION_IDENTIFIER, TRANSACTION_TYPE, WRITE_CONTROL_CHARACTER, XID
    Name Description
    ACTION_CODE Code indicating a Host response.
    ADDITIONAL_RESPONSE_INDICATOR Variable Length, 4 position Field. Positions 2 – 4 Reserved for Future Use. Position 1 Only – used in conjunction with Terminal ID Field. It will only be present in Credit Sale, Credit Auth only transactions for Retail industry.
    APPROVED_AMOUNT The amount approved if received Partial Sale / Auth, Action Code 3. Must support the PARTIAL AUTHORIZATION INDICATOR within transaction message Industry Specific Formats. If Partial Auth not accepted, this Amount must be the TOTAL AMOUNT of the void transaction to cancel the partially approved transaction.
    AUTH_CHAR_INDICATOR_REQUEST Code identifying the type of transaction approval.
    AUTHORIZATION_CODE Numeric or alphanumeric code assigned to a transaction as verification that a transaction has been approved.
    AVS_ADDRESS Principal cardholder‘s address entered for address verification.
    AVS_RESPONSE_CODE Code indicating whether address verification was performed and the results.
    AVS_ZIP_CODE ZIP (or postal) code of principal cardholder‘s address entered for address verification.
    BALANCE_SIGN If Positive balance position will contain a space Character If Balance is negative, field will contain a ―-―character.
    BATCH_NUMBER Number identifying the batch; assigned by the POS device.
    CARD_TYPE_INDICATOR Character indicating the type of card.
    CARD_VERIFICATION_PRESENCE_INDICATOR Character that indicates whether the CVV2/CVC2/CID value is included with message packet.
    CARD_VERIFICATION_RESPONSE_CODE The result from performing a CVC2/CVV2/CID check.
    CARDHOLDER_SET_CERTIFICATE_SERIAL_NUMBER Cardholder Secure Electronic Transaction Certificate Serial number.
    CASH_BACK_AMOUNT Dollar-and-cent amount ($$$.¢¢) of a debit/EBT cash back amount.
    CHARGE_TRANSACTION_FK Reference to the entity that represents real-time financial transaction.
    CUSTOMER_CODE Merchant-assigned code.
    DEBIT_CARD_TYPE_NUMBER The number of the debit network through which the debit card was processed.
    DEBIT_NETWORK_NAME The name of the network through which the debit card was processed.
    DEVICE_ID Merchant-assigned code identifying the device at the merchant‘s location.
    EBT_RESPONSE_CODE Code sent by Network that processed the transaction.
    EBT_VOUCHER_NUMBER Number from EBT Voucher Form.
    FORMAT_CODE Code indicating the type of format for the message to the Host.
    INVOICE_NUMBER Merchant-defined number.
    ITEM_NUMBER Number of the transaction in the batch; assigned by the POS.
    MERCHANT_ACCOUNT_CODE Code of Merchant Account to which instance of this object is attributed to.
    Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
    The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
    MERCHANT_NUMBER Number assigned by merchant‘s financial institution.
    MERCHANT_SET_CERTIFICATE_SERIAL_NUMBER Merchant Secure Electronic Transaction Certificate Serial number.
    ORDER_NUMBER Merchant-defined number identifying the purchase or service.
    PARTIAL_AUTHORIZATION_INDICATOR Value will be blank for Online Void.
    PHONE_MAIL_ORDER_FLAG Code identifying whether the transaction is mail order, phone order or electronic commerce.
    POS_DATA_CODES POS Codes for American Express Ticket Only (Tran Code 3) transaction. Contact American Express to determine how these values are generated and used for American Express.
    PROTOCOL_TYPE Character identifying which protocol rule the transaction follows; required field.
    REMAINING_BALANCE Right justified w/leading spaces when a Balance returned by issuer.
    Balance is returned by Issuer when Partial Auth Indicator is set to 1 in the online sale request. When Balance not returned by Issuer, The field will contain the constant value ―UNAVAILABLE‖ Left justified trailing spaces.
    REQUESTED_AMOUNT The Amount entered at POS to be authorized by Host.
    RESPONSE_CODE Value defining how the System responded to the transaction.
    RESPONSE_TEXT Message from the Host which appears on the POS device.
    RETAIL_TRANSACTION_CYCLE_FK Reference to the entity that represents a group of real-time transactions which must be settled together.
    REVISION_NUMBER Number identifying the number of revisions to a monetary transaction.
    SURCHARGE Dollar-and-cent amount ($$$.¢¢) of the charge that the cardholder paid the merchant for the ability to perform the transaction.
    TAX_AMOUNT Dollar-and-cent amount ($$$$$.¢¢) of tax for the purchase.
    TERMINAL_ID Code identifying the balancing features available to the POS from the Host.
    TIP_AMOUNT Dollar-and-cent amount ($$$.¢¢) of the tip given at the restaurant for the purchase.
    TOTAL_AMOUNT Total dollar-and-cent amount ($$$$$.¢¢) of the purchase.
    TOTAL_AUTHORIZED_AMOUNT Dollar-and-cent amount ($$$$$.¢¢) of the purchase.
    TPP If a First Data assigned TPP value is not available do not send this field with a default value.
    TRANS_STAIN A value used to define a merchant‘s security settings for SET.
    TRANSACTION_CODE Code identifying how the System will respond to the transaction request.
    TRANSACTION_IDENTIFIER Code generated by the card associations on the authorization; known as TID for Visa and BankNet Reference Number for MasterCard.
    TRANSACTION_TYPE Code identifying how the System will respond to the transaction request.
    WRITE_CONTROL_CHARACTER Character identifying the account number entry method and Host response protocol (single or multiple mode).
    XID A unique transaction identifier assigned to a SET Transaction.
    cards-realtime.globalpayments-east.authorization.log   
    Added On:  10/20/14
    Level:  Trace
    Category:  cards-realtime.authorization
    Status:  Active
    Group:  processing
    File Name:  cards-realtime.globalpayments-east.authorization.log
    Resource:  $app-home/jboss-7.4.0/standalone/log/processing/cards-realtime.globalpayments-east.authorization.log
    Legacy File Name:  cards-realtime.globalpayments.authorization.log
    Сontains information about the processor's incoming requests and outgoing responses (globalpayments-east)
    Request Fields [Show Info]

    BIT11, BIT12, BIT22, BIT25, BIT3, BIT30, BIT31, BIT32, BIT38, BIT4, BIT42, BIT44, BIT48, BIT54, BIT61, CHARGE_TRANSACTION_FK, MERCHANT_ACCOUNT_CODE, MESSAGE_TYPE, PROCESS_MODE, RETAIL_TRANSACTION_CYCLE_FK
    Name Description
    BIT11
    BIT12
    BIT22
    BIT25
    BIT3
    BIT30
    BIT31
    BIT32
    BIT38
    BIT4
    BIT42
    BIT44
    BIT48
    BIT54
    BIT61
    CHARGE_TRANSACTION_FK Reference to the entity that represents real-time financial transaction.
    MERCHANT_ACCOUNT_CODE Code of Merchant Account to which instance of this object is attributed to.
    Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
    The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
    MESSAGE_TYPE
    PROCESS_MODE
    RETAIL_TRANSACTION_CYCLE_FK Reference to the entity that represents a group of real-time transactions which must be settled together.
    Response Fields [Show Info]

    APPROVED_AMOUNT, BIT11, BIT12, BIT22, BIT25, BIT3, BIT30, BIT31, BIT31_ACQUIRER_REFERENCE_DATA, BIT31_AUTHORIZATION_SOURCE_CODE, BIT31_BALANCE_DATA, BIT31_MERCHANT_ADVICE_CODE, BIT31_PRODUCT_IDENTIFIER, BIT31_PROGRAM_IDENTIFIER, BIT31_RESPONSE_CODE, BIT31_SYSTEM_ADDRESS, BIT31_TRANSACTION_ID, BIT31_VALIDATION_CODE, BIT32, BIT38, BIT38_APPROVAL_CODE, BIT39_ACTION_CODE, BIT4, BIT42, BIT44, BIT44_BATCH_AMOUNT, BIT44_BATCH_NUMBER, BIT44_CASH_BENEFIT_BALANCE, BIT44_FOOD_STAMP_BALANCE, BIT44_ITEM, BIT44_VERBIAGE, BIT48, BIT48_ADDITIONAL_DATA, BIT48_AVS_RESULT_CODE, BIT48_CARD_VERIFICATION_RESULT, BIT48_CAVV_RESULT_CODE, BIT54, BIT61, BIT62_GLOBAL_PAYMENTS_DATA, CHARGE_TRANSACTION_FK, MERCHANT_ACCOUNT_CODE, MESSAGE_TYPE, PROCESS_MODE, RETAIL_TRANSACTION_CYCLE_FK
    Name Description
    APPROVED_AMOUNT Amount actually used. The merchant must tender the difference between the requested amount and the approved amount.
    BIT11
    BIT12
    BIT22
    BIT25
    BIT3
    BIT30
    BIT31
    BIT31_ACQUIRER_REFERENCE_DATA
    BIT31_AUTHORIZATION_SOURCE_CODE
    BIT31_BALANCE_DATA
    BIT31_MERCHANT_ADVICE_CODE
    BIT31_PRODUCT_IDENTIFIER
    BIT31_PROGRAM_IDENTIFIER
    BIT31_RESPONSE_CODE
    BIT31_SYSTEM_ADDRESS
    BIT31_TRANSACTION_ID
    BIT31_VALIDATION_CODE
    BIT32
    BIT38
    BIT38_APPROVAL_CODE
    BIT39_ACTION_CODE
    BIT4
    BIT42
    BIT44
    BIT44_BATCH_AMOUNT
    BIT44_BATCH_NUMBER
    BIT44_CASH_BENEFIT_BALANCE
    BIT44_FOOD_STAMP_BALANCE
    BIT44_ITEM
    BIT44_VERBIAGE
    BIT48
    BIT48_ADDITIONAL_DATA
    BIT48_AVS_RESULT_CODE
    BIT48_CARD_VERIFICATION_RESULT
    BIT48_CAVV_RESULT_CODE
    BIT54
    BIT61
    BIT62_GLOBAL_PAYMENTS_DATA
    CHARGE_TRANSACTION_FK Reference to the entity that represents real-time financial transaction.
    MERCHANT_ACCOUNT_CODE Code of Merchant Account to which instance of this object is attributed to.
    Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
    The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
    MESSAGE_TYPE
    PROCESS_MODE
    RETAIL_TRANSACTION_CYCLE_FK Reference to the entity that represents a group of real-time transactions which must be settled together.
    cards-realtime.tsys.authorization.log   
    Added On:  10/20/14
    Level:  Trace
    Category:  cards-realtime.authorization
    Status:  Active
    Group:  processing
    File Name:  cards-realtime.tsys.authorization.log
    Resource:  $app-home/jboss-7.4.0/standalone/log/processing/cards-realtime.tsys.authorization.log
    Legacy File Name:  
    Сontains information about the processor's incoming requests and outgoing responses (tsys)
    Request Fields [Show Info]

    , ACCOUNT_DATA_SOURCE, ACQUIRER_BIN, AGENT_BANK_NUMBER, AGENT_CHAIN_NUMBER, BATCH_NUMBER, CANCEL_DATA1, CANCEL_DATA2, CARD_ACCEPTOR_DATA, CARDHOLDER_ID_CODE, CHARGE_TRANSACTION_FK, CITY_CODE, INDUSTRY_CODE, MARKET_SPECIFIC_DATA, MERCHANT_ACCOUNT_CODE, MERCHANT_CATEGORY_CODE, MERCHANT_NUMBER, MERCHANT_SETTLEMENT_AGENT_NUMBER, RECORD_FORMAT, REQUESTED_ACI, RETAIL_TRANSACTION_CYCLE_FK, REVERSAL_TRANSACTION_ID, SECONDARY_AMOUNT, SHARING_GROUPS, STORE_NUMBER, TERMINAL_NUMBER, TIME_ZONE_DIFFERENTIAL, TRANSACTION_AMOUNT, TRANSACTION_CODE, TRANSACTION_SEQUENCE_NUMBER
    Name Description
    Identifies the merchant to a direct debit switch.

    This field must be supplied for all direct debit request transactions except for the Interlink Debit Cancel (Transaction Code 95). This number is provided by the signing member or processor.
    ACCOUNT_DATA_SOURCE Contains code identifying the source of the customer data entered in field:

    • D - Full magnetic stripe read and transmit, Track two
    • H - Full magnetic stripe read and transmit, Track one
    • T - Manually keyed, Track two capable
    • X - Manually keyed, Track one capable
    • @ - Manually keyed, terminal has no card reading capability
    ACQUIRER_BIN Contains a six-character numeric Visa assigned Bank Identification Number (BIN) issued by the merchant's member bank or processor. The Acquirer BIN identifies the member bank that signed the merchant using the POS application.
    AGENT_BANK_NUMBER Contains an agent number assigned by the signing member or processor. The number identifies an institution which signs merchants as an agent of a member. The member uses this number to identify the agent within TSYS Acquiring Solutions’ system.
    AGENT_CHAIN_NUMBER Contains a merchant chain identification number assigned by the signing member or processor. The member uses this number to identify the merchant chain within the TSYS Acquiring Solutions’ system.
    BATCH_NUMBER Contains a batch sequence number generated by the terminal. The number wraps from 999 to 001. This number is also transmitted as the data capture batch number. Batch numbers should not be repeated within five days.
    CANCEL_DATA1 The following sub-fields are required when performing an ATM or Debit Non-Confirm Authorization request, or when performing an Authorization Reversal request, a Debit Reversal/Cancel request, or a AFD Completion Advice message. For all other transaction types, this field should be submitted without data.

    Approval Code:
    Contains approval code returned in the original authorization response record. This is the authorization code for the completed AFD transaction, or the transaction to be either partially or completely reversed. For a debit non-confirm purchase or ATM authorization transactions, the approval code will be space filled.

    Local Transaction Date:
    Contains value reflecting the local transaction date returned in the original authorization response record for the AFD sale or the transaction to be canceled or reversed. For a debit non-confirm purchase or ATM authorization transactions, this field will contain the local transaction date.

    Local Transaction Time:
    Contains the local transaction time of the original authorization request for the AFD sale or the transaction to be either partially or fully reversed. The Local Transaction Time must be submitted in HHMMSS format. For a debit non-confirm purchase or ATM authorization transactions, this field will contain the local transaction time.

    Retrieval Reference Number:
    In AFD Completion Advice messages and reversal transactions, this field must contain Retrieval Reference Number returned in the original authorization response. For debit non-confirm purchase or ATM authorization transactions, this field contains two parts. The first four characters are a yddd date (Julian date) format. The last eight characters are a numeric transaction identification number.
    CANCEL_DATA2 The following sub-fields are required when requesting any of the following Authorization Transaction Codes: A3, A4, B1, B2, B3, B4, C1, C3, C4 and 5C. This field does not contain data for any other transaction types.

    System Trace Audit Number:
    Must contain the System Trace Audit Number returned in the confirmation data field of the debit authorization response record for the transaction to be canceled or reversed. For a debit non-confirm purchase transaction, this number uniquely.

    Network Identification Code:
    When returned in a debit authorization response message, this value designates the debit network through which the request was processed. When performing an Authorization Reversal, this field must contain the one-character Network Identification Code returned in the confirmation data field of the authorization response record for the item to be canceled or reversed. For a debit non-confirm or ATM authorization transactions, the network identification code field will be space-filled.
    CARD_ACCEPTOR_DATA The following sub-fields are required for direct debit transactions. For all other transactions, the following sub-fields should be configured as parameters within the POS system but need not necessarily contain data.

    The format of this 40-byte field is:

    “NNNNNNNNNNNNNNNNNNNNNNNNNLLLLLLLLLLLLLSS”
    where
    NNNN... 1-25 A/N Merchant Name
    LL.....LL 26-38 A/N Merchant City
    SS 39-40 A/N Merchant State

    For Direct Marketing merchants and preferred customer/passenger transport transactions, this field should contain a customer service phone number in XXX-XXXXXXX format.
    CARDHOLDER_ID_CODE Contains a code that specifies the method used to verify the identity the cardholder. The values can be used in conjunction with AVS and Recurring and Installment Requested ACI Indicators.

    • K - Personal Identification Number 32-character DUK/PT
    • M - Card Present: Unable to read Mag stripe, sending Address Verification Data
    • N - Card Not Present: Includes e-Commerce and Full Address Verification Data
    • Z - Cardholder Signature - Terminal has a PIN Pad
    • @ - Cardholder Signature - No PIN pad available
    CHARGE_TRANSACTION_FK Reference to the entity that represents real-time financial transaction.
    CITY_CODE Contains the code used to further identify the merchant location (ZIP Code).
    INDUSTRY_CODE Used to identify the industry type of the merchant submitting the authorization request.

    • R - Retail
    • D - Direct Marketing
    MARKET_SPECIFIC_DATA The following sub-fields contain market specific data for hotel and auto rental transactions. The market specific data sub-fields need not be supplied for incremental authorization or authorization reversal transactions.

    The format of this field is: “PIDD.”
    • P - Prestigious Indicator (This indicator is used by participants in Visa’s Prestigious Lodging Program)
    • I - Market Specific Data Identifier (The market specific data identifier is used to indicate which industry data is being submitted)
    • DD - Stay or Rental Duration (When the market specific data is supplied in an incremental transaction, this sub-field represents the number of additional days for the hotel stay or auto rental)

    • P - Non-participating properties should put a “space”
    • I - Bill Payment Transaction
    • DD - For Bill Payment this sub-field should be set to “00.”
    MERCHANT_ACCOUNT_CODE Code of Merchant Account to which instance of this object is attributed to.
    Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
    The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
    MERCHANT_CATEGORY_CODE Contains a number assigned by the signing member or processor to identify a merchant industry classification.

    This value is similar to the Standard Industry Code (SIC).
    MERCHANT_NUMBER Contains a unique number, assigned by the signing merchant’s bank or processor. Used to identify the merchant within the TSYS Acquiring Solutions system.
    MERCHANT_SETTLEMENT_AGENT_NUMBER Identifies the merchant settling agent. Provided by the signing member or processor.
    RECORD_FORMAT Identifies the message format with the TSYS Acquiring Solutions system.

    • D - Credit Card Authorization request messages (Groups I and III)
    • T - Debit/Electronic Benefits Transfer - EBT request messages (Groups I, II, and III)
    REQUESTED_ACI Contains the Requested Authorization Characteristics Indicator (ACI) used to identify an authorization request as potentially qualifying for CPS (Custom Payment Services) and MasterCard Merit programs. If a merchant chooses not to participate in CPS, the Requested ACI value should default to an “N.”
    Y - Device is CPS capable
    R - Recurring Payment. No AVS required
    N - Device is not CPS capable
    RETAIL_TRANSACTION_CYCLE_FK Reference to the entity that represents a group of real-time transactions which must be settled together.
    REVERSAL_TRANSACTION_ID When performing either an Incremental Authorization or Authorization Reversal request, this field must contain the Transaction Identifier returned in the original authorization response record. For all other transaction types, this field should be submitted without data.
    SECONDARY_AMOUNT Secondary amount associated with the transaction representing a cashback amount.

    This is a variable length field from zero to 12-character numeric in length. This field contains a secondary transaction amount related to the transaction type and industry indicated. The transaction amount is to be presented with an implied decimal point. For example, $.01 could be represented as 1, 01, or 001. The allowable number of significant digits, as well as the positioning of any implied decimal point, are dictated by the Currency Code designated. In the United States, the allowable number of significant characters is seven with an implied decimal point.
    In industries where cash back is permitted on purchase transactions, this field could contain a cash back amount.
    For Authorization Reversal transactions, this field must contain the final settlement amount for a partial reversal, and is not used for a full reversal.
    SHARING_GROUPS Contains a listing of direct debit and EBT networks that a POS device can access. Provided by the signing member or processor. The values must correspond to one of the Visa assigned direct debit network types. This data is part of the TSYS Acquiring Solutions direct debit data.
    STORE_NUMBER Contains a number assigned by the signing member, processor, or merchant to identify a specific merchant store within the TSYS Acquiring Solutions’ system.
    TERMINAL_NUMBER Contains a number assigned by the signing member, processor, or merchant to identify a unique terminal within a merchant location.

    Because the terminal number submitted in the authorization request is echoed back to the terminal in the authorization response, this field can additionally be used in controller-based environments to assist in the matching and routing of authorization request and response messages at the point of concentration.
    TIME_ZONE_DIFFERENTIAL Contains a code used to calculate the local time within the TSYS Acquiring Solutions authorization system.

    The differential is calculated by the signing member or processor, providing the standard local time zone differential from Greenwich Mean Time (GMT). The first character numeric specifies the direction of the differential and offset increment as well as whether daylight savings is observed, and the last two-character numeric specify the magnitude of the differential.
    For now, such values is used - 705, 706, 707, 708
    TRANSACTION_AMOUNT Contains the transaction amount to be authorized. The transaction amount is to be presented with implied decimal point.

    For all Authorization Reversal transactions, this field contains the Total Authorization Amount (the total of all previous authorizations performed for a particular transaction or associated with a single Transaction ID).
    TRANSACTION_CODE Contains a code identifying the type of authorization or function being requested.

    In conditions where an authorization request has been submitted to the host but no response was ever received, the transaction code should be converted to its corresponding “Repeat” value and resubmitted for authorization.

    • 54 - Standard Authorization Request
    • 56 - Used primarily in Direct Marketing, Mail, and Telephone Order Environments
    • 59 - Used to reverse a completed credit authorization prior to batch settlement
    • 93 - Standard Debit Authorization Request
    • 94 - Direct Debit: Purchase Return
    • 5A - Same as code '59', except the reversal is being submitted after batch settlement occurred
    • 5B - Bill Payment Transaction (Credit Card)
    • 9C - Debit transactions without a PIN
    • A3 - Automatic Reversal: Direct Debit Purchase
    • A4 - Automatic Reversal: Direct Debit Purchase Return
    TRANSACTION_SEQUENCE_NUMBER Contains a terminal-generated transaction sequence number to be submitted in all authorization request messages.

    This number is echoed back to the terminal for purposes of assisting in the matching of authorization request and response messages.
    This value must be in the range of 0001 - 9999 and is incremented on each authorization request message. This number is automatically incremented from 9999 to 0001.
    Response Fields [Show Info]

    , ACCOUNT_DATA_SOURCE, ACQUIRER_BIN, AGENT_BANK_NUMBER, AGENT_CHAIN_NUMBER, APPROVAL_CODE, AUTHORIZATION_RESPONSE_TEXT, AUTHORIZATION_SOURCE_CODE, AVS_RESULT_CODE, BATCH_NUMBER, CANCEL_DATA1, CANCEL_DATA2, CARD_ACCEPTOR_DATA, CARD_LEVEL_RESULTS, CARDHOLDER_ID_CODE, CAVV_RESULTS_CODE, CHARGE_TRANSACTION_FK, CITY_CODE, COMMERCIAL_CARD_RESPONSE_INDICATOR, FIRST_ACCOUNT_TYPE1, FIRST_ACCOUNT_TYPE2, FIRST_AMOUNT, FIRST_CURRENCY_CODE, FIRST_SIGN, FOURTH_ACCOUNT_TYPE1, FOURTH_ACCOUNT_TYPE2, FOURTH_AMOUNT, FOURTH_CURRENCY_CODE, FOURTH_SIGN, HOST_MESSAGE_IDENTIFIER, INDUSTRY_CODE, LOCAL_TRANSACTION_DATE, LOCAL_TRANSACTION_TIME, MARKET_DATA_IDENTIFIER, MARKET_SPECIFIC_DATA, MERCHANT_ACCOUNT_CODE, MERCHANT_CATEGORY_CODE, MERCHANT_NUMBER, MERCHANT_SETTLEMENT_AGENT_NUMBER, NETWORK_ID_CODE, RECORD_FORMAT, REQUESTED_ACI, RESPONSE_CODE, RETAIL_TRANSACTION_CYCLE_FK, RETRIEVAL_REFERENCE_NUMBER, RETURNED_ACI, REVERSAL_TRANSACTION_ID, SECOND_ACCOUNT_TYPE1, SECOND_ACCOUNT_TYPE2, SECOND_AMOUNT, SECOND_CURRENCY_CODE, SECOND_SIGN, SE
    Name Description
    Identifies the merchant to a direct debit switch.

    This field must be supplied for all direct debit request transactions except for the Interlink Debit Cancel (Transaction Code 95). This number is provided by the signing member or processor.
    ACCOUNT_DATA_SOURCE Contains code identifying the source of the customer data entered in field:

    • D - Full magnetic stripe read and transmit, Track two
    • H - Full magnetic stripe read and transmit, Track one
    • T - Manually keyed, Track two capable
    • X - Manually keyed, Track one capable
    • @ - Manually keyed, terminal has no card reading capability
    ACQUIRER_BIN Contains a six-character numeric Visa assigned Bank Identification Number (BIN) issued by the merchant's member bank or processor. The Acquirer BIN identifies the member bank that signed the merchant using the POS application.
    AGENT_BANK_NUMBER Contains an agent number assigned by the signing member or processor. The number identifies an institution which signs merchants as an agent of a member. The member uses this number to identify the agent within TSYS Acquiring Solutions’ system.
    AGENT_CHAIN_NUMBER Contains a merchant chain identification number assigned by the signing member or processor. The member uses this number to identify the merchant chain within the TSYS Acquiring Solutions’ system.
    APPROVAL_CODE Contains fixed approval code returned in the original authorization response record.

    This is the authorization code for the completed AFD transaction, or the transaction to be either partially or completely reversed. For a debit non-confirm purchase or ATM authorization transactions, the approval code will be space filled.
    AUTHORIZATION_RESPONSE_TEXT Contains a response or display text message. This message can be used by the terminal to display the authorization result. The display text must not be used to determine the nature of a response message.
    AUTHORIZATION_SOURCE_CODE Contains code indicating the source of the authorization code. The received code must be stored and resubmitted in the data capture settlement record.
    AVS_RESULT_CODE Contains the Address Verification Result Code. An Address Verification Result Code can provide additional information concerning the authentication of a particular transaction for which cardholder Address Verification was requested. An Address Verification result code of “0” is returned in the response message when no address verification has been requested. The value returned should be stored and submitted as part of the data capture settlement record.
    BATCH_NUMBER Contains a batch sequence number generated by the terminal. The number wraps from 999 to 001. This number is also transmitted as the data capture batch number. Batch numbers should not be repeated within five days.
    CANCEL_DATA1 The following sub-fields are required when performing an ATM or Debit Non-Confirm Authorization request, or when performing an Authorization Reversal request, a Debit Reversal/Cancel request, or a AFD Completion Advice message. For all other transaction types, this field should be submitted without data.

    Approval Code:
    Contains approval code returned in the original authorization response record. This is the authorization code for the completed AFD transaction, or the transaction to be either partially or completely reversed. For a debit non-confirm purchase or ATM authorization transactions, the approval code will be space filled.

    Local Transaction Date:
    Contains value reflecting the local transaction date returned in the original authorization response record for the AFD sale or the transaction to be canceled or reversed. For a debit non-confirm purchase or ATM authorization transactions, this field will contain the local transaction date.

    Local Transaction Time:
    Contains the local transaction time of the original authorization request for the AFD sale or the transaction to be either partially or fully reversed. The Local Transaction Time must be submitted in HHMMSS format. For a debit non-confirm purchase or ATM authorization transactions, this field will contain the local transaction time.

    Retrieval Reference Number:
    In AFD Completion Advice messages and reversal transactions, this field must contain Retrieval Reference Number returned in the original authorization response. For debit non-confirm purchase or ATM authorization transactions, this field contains two parts. The first four characters are a yddd date (Julian date) format. The last eight characters are a numeric transaction identification number.
    CANCEL_DATA2 The following sub-fields are required when requesting any of the following Authorization Transaction Codes: A3, A4, B1, B2, B3, B4, C1, C3, C4 and 5C. This field does not contain data for any other transaction types.

    System Trace Audit Number:
    Must contain the System Trace Audit Number returned in the confirmation data field of the debit authorization response record for the transaction to be canceled or reversed. For a debit non-confirm purchase transaction, this number uniquely.

    Network Identification Code:
    When returned in a debit authorization response message, this value designates the debit network through which the request was processed. When performing an Authorization Reversal, this field must contain the one-character Network Identification Code returned in the confirmation data field of the authorization response record for the item to be canceled or reversed. For a debit non-confirm or ATM authorization transactions, the network identification code field will be space-filled.
    CARD_ACCEPTOR_DATA The following sub-fields are required for direct debit transactions. For all other transactions, the following sub-fields should be configured as parameters within the POS system but need not necessarily contain data.

    The format of this 40-byte field is:

    “NNNNNNNNNNNNNNNNNNNNNNNNNLLLLLLLLLLLLLSS”
    where
    NNNN... 1-25 A/N Merchant Name
    LL.....LL 26-38 A/N Merchant City
    SS 39-40 A/N Merchant State

    For Direct Marketing merchants and preferred customer/passenger transport transactions, this field should contain a customer service phone number in XXX-XXXXXXX format.
    CARD_LEVEL_RESULTS Contains code created by Visa during the authorization process.

    Conditional in the response record. It will only be returned if the values are non-zero.
    CARDHOLDER_ID_CODE Contains a code that specifies the method used to verify the identity the cardholder. The values can be used in conjunction with AVS and Recurring and Installment Requested ACI Indicators.

    • K - Personal Identification Number 32-character DUK/PT
    • M - Card Present: Unable to read Mag stripe, sending Address Verification Data
    • N - Card Not Present: Includes e-Commerce and Full Address Verification Data
    • Z - Cardholder Signature - Terminal has a PIN Pad
    • @ - Cardholder Signature - No PIN pad available
    CAVV_RESULTS_CODE Indicates whether the authentication value submitted by the merchant can be validated by Visa or the issuer.
    CHARGE_TRANSACTION_FK Reference to the entity that represents real-time financial transaction.
    CITY_CODE Contains the code used to further identify the merchant location (ZIP Code).
    COMMERCIAL_CARD_RESPONSE_INDICATOR If the Commercial Card Request Indicator (this field is utilized to request that TSYS Acquiring Solutions systems return a value in the authorization response message identifying whether the card type being presented was a Commercial Card. This field is currently defaulted to 010, and is supported for Visa and MasterCard transactions only) was supplied in the authorization request, the host responds with one of the following response indicators identifying the card being processed.

    When a response indicator has been received indicating that the approved card is a Business, Corporate, or Purchasing Card, the POS device should prompt for addendum data elements as needed for settlement.
    FIRST_ACCOUNT_TYPE1 Contains identifiers for account types.
    FIRST_ACCOUNT_TYPE2 Contains identifiers for account types.
    FIRST_AMOUNT Contains any additional amounts related to the authorization request or response.
    FIRST_CURRENCY_CODE Contains currency code identifying the currency for the returned additional amount.
    FIRST_SIGN Indicates whether the amount is a debit or credit.
    FOURTH_ACCOUNT_TYPE1 Contains identifiers for account types.
    FOURTH_ACCOUNT_TYPE2 Contains identifiers for account types.
    FOURTH_AMOUNT Contains any additional amounts related to the authorization request or response.
    FOURTH_CURRENCY_CODE Contains currency code identifying the currency for the returned additional amount.
    FOURTH_SIGN Indicates whether the amount is a debit or credit.
    HOST_MESSAGE_IDENTIFIER Contains a unique host message identifier assigned by the authorizing system and returned in debit card response messages. Reserved for future use and will most likely contain spaces. This value must be recorded and submitted in the debit confirmation record.
    INDUSTRY_CODE Used to identify the industry type of the merchant submitting the authorization request.

    • R - Retail
    • D - Direct Marketing
    LOCAL_TRANSACTION_DATE Contains value reflecting the local transaction date (in MMDDYY format) returned in the original authorization response record for the AFD sale or the transaction to be canceled or reversed. For a debit non-confirm purchase or ATM authorization transactions, this field will contain the local transaction date.
    LOCAL_TRANSACTION_TIME Contains the local transaction time of the original authorization request for the AFD sale or the transaction to be either partially or fully reversed. The local transaction time must be submitted in HHMMSS format. For a debit non-confirm purchase or ATM authorization transactions, this field will contain the local transaction time.
    MARKET_DATA_IDENTIFIER Used to indicate which industry data is being submitted.

    When this sub-field is supplied in an incremental transaction, it should use the same value that was requested in the original authorization transaction.
    MARKET_SPECIFIC_DATA The following sub-fields contain market specific data for hotel and auto rental transactions. The market specific data sub-fields need not be supplied for incremental authorization or authorization reversal transactions.

    The format of this field is: “PIDD.”
    • P - Prestigious Indicator (This indicator is used by participants in Visa’s Prestigious Lodging Program)
    • I - Market Specific Data Identifier (The market specific data identifier is used to indicate which industry data is being submitted)
    • DD - Stay or Rental Duration (When the market specific data is supplied in an incremental transaction, this sub-field represents the number of additional days for the hotel stay or auto rental)

    • P - Non-participating properties should put a “space”
    • I - Bill Payment Transaction
    • DD - For Bill Payment this sub-field should be set to “00.”
    MERCHANT_ACCOUNT_CODE Code of Merchant Account to which instance of this object is attributed to.
    Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
    The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
    MERCHANT_CATEGORY_CODE Contains a number assigned by the signing member or processor to identify a merchant industry classification.

    This value is similar to the Standard Industry Code (SIC).
    MERCHANT_NUMBER Contains a unique number, assigned by the signing merchant’s bank or processor. Used to identify the merchant within the TSYS Acquiring Solutions system.
    MERCHANT_SETTLEMENT_AGENT_NUMBER Identifies the merchant settling agent. Provided by the signing member or processor.
    NETWORK_ID_CODE Contains a code that specifies the network to be used for transmission of the message and determines the program rules that apply to the transaction.
    RECORD_FORMAT Identifies the message format with the TSYS Acquiring Solutions system.

    • D - Credit Card Authorization request messages (Groups I and III)
    • T - Debit/Electronic Benefits Transfer - EBT request messages (Groups I, II, and III)
    REQUESTED_ACI Contains the Requested Authorization Characteristics Indicator (ACI) used to identify an authorization request as potentially qualifying for CPS (Custom Payment Services) and MasterCard Merit programs. If a merchant chooses not to participate in CPS, the Requested ACI value should default to an “N.”
    Y - Device is CPS capable
    R - Recurring Payment. No AVS required
    N - Device is not CPS capable
    RESPONSE_CODE Contains code identifying the type of authorization or function being requested.

    In conditions where an authorization request has been submitted to the host but no response was ever received, the transaction code should be converted to its corresponding “Repeat” value and resubmitted for authorization.
    RETAIL_TRANSACTION_CYCLE_FK Reference to the entity that represents a group of real-time transactions which must be settled together.
    RETRIEVAL_REFERENCE_NUMBER Contains value reflecting the transaction Retrieval Reference Number returned by the authorizing system.

    The POS system should record the retrieval reference number received in the original authorization response. The Retrieval Reference Number from the original response is required when submitting AFD Completion Advice messages and when submitting incremental authorizations, or authorization reversal requests that must be settled for direct debit transactions.
    RETURNED_ACI Contains the Returned Authorization Characteristics Indicator (ACI).
    Provides information concerning the transactions’ CPS qualification status. It is not recommended that the POS system attempt to interpret the meaning of this value. Instead, the POS system should extract whatever value is returned in this field and submit it in the data capture settlement record. The POS system should not interpret any relationship between this field and the presence of data in either the Transaction Identifier or Validation Code fields.
    REVERSAL_TRANSACTION_ID When performing either an Incremental Authorization or Authorization Reversal request, this field must contain the Transaction Identifier returned in the original authorization response record. For all other transaction types, this field should be submitted without data.
    SECOND_ACCOUNT_TYPE1 Contains identifiers for account types.
    SECOND_ACCOUNT_TYPE2 Contains identifiers for account types.
    SECOND_AMOUNT Contains any additional amounts related to the authorization request or response.
    SECOND_CURRENCY_CODE Contains currency code identifying the currency for the returned additional amount.
    SECOND_SIGN Indicates whether the amount is a debit or credit.
    SETTLEMENT_DATE Contains the transaction settlement date returned by the TSYS Acquiring Solutions authorization system and is submitted in MMDD format.
    SHARING_GROUPS Contains a listing of direct debit and EBT networks that a POS device can access. Provided by the signing member or processor. The values must correspond to one of the Visa assigned direct debit network types. This data is part of the TSYS Acquiring Solutions direct debit data.
    SPEND_QUALIFIED_INDICATOR Optionally sent by Visa in an autorization response message. The merchant's intercharge rate may be determined by spend qualified indicator. See the specification of the processor for more information.
    STORE_NUMBER Contains a number assigned by the signing member, processor, or merchant to identify a specific merchant store within the TSYS Acquiring Solutions’ system.
    SYSTEM_TRACE_AUDIT_NUMBER Must contain System Trace Audit Number returned in the confirmation data field of the debit authorization response record for the transaction to be canceled or reversed. For a debit non-confirm purchase transaction, this number uniquely identifies a cardholder transaction. The trace number remains unchanged for all messages throughout the life cycle of the transaction.
    TERMINAL_NUMBER Contains a number assigned by the signing member, processor, or merchant to identify a unique terminal within a merchant location.

    Because the terminal number submitted in the authorization request is echoed back to the terminal in the authorization response, this field can additionally be used in controller-based environments to assist in the matching and routing of authorization request and response messages at the point of concentration.
    THIRD_ACCOUNT_TYPE1 Contains identifiers for account types.
    THIRD_ACCOUNT_TYPE2 Contains identifiers for account types.
    THIRD_AMOUNT Contains any additional amounts related to the authorization request or response.
    THIRD_CURRENCY_CODE Contains currency code identifying the currency for the returned additional amount.
    THIRD_SIGN Indicates whether the amount is a debit or credit.
    TIME_ZONE_DIFFERENTIAL Contains a code used to calculate the local time within the TSYS Acquiring Solutions authorization system.

    The differential is calculated by the signing member or processor, providing the standard local time zone differential from Greenwich Mean Time (GMT). The first character numeric specifies the direction of the differential and offset increment as well as whether daylight savings is observed, and the last two-character numeric specify the magnitude of the differential.
    For now, such values is used - 705, 706, 707, 708
    TRANSACTION_AMOUNT Contains the transaction amount to be authorized. The transaction amount is to be presented with implied decimal point.

    For all Authorization Reversal transactions, this field contains the Total Authorization Amount (the total of all previous authorizations performed for a particular transaction or associated with a single Transaction ID).
    TRANSACTION_CODE Contains a code identifying the type of authorization or function being requested.

    In conditions where an authorization request has been submitted to the host but no response was ever received, the transaction code should be converted to its corresponding “Repeat” value and resubmitted for authorization.

    • 54 - Standard Authorization Request
    • 56 - Used primarily in Direct Marketing, Mail, and Telephone Order Environments
    • 59 - Used to reverse a completed credit authorization prior to batch settlement
    • 93 - Standard Debit Authorization Request
    • 94 - Direct Debit: Purchase Return
    • 5A - Same as code '59', except the reversal is being submitted after batch settlement occurred
    • 5B - Bill Payment Transaction (Credit Card)
    • 9C - Debit transactions without a PIN
    • A3 - Automatic Reversal: Direct Debit Purchase
    • A4 - Automatic Reversal: Direct Debit Purchase Return
    TRANSACTION_IDENTIFIER Contains a transaction identifier (Visa, American Express or Discover) or Reference Number (MasterCard). The POS device does not attempt to interpret the meaning of any data appearing in this field. Data returned in this field is recorded and submitted as part of the data capture settlement format.
    TRANSACTION_SEQUENCE_NUMBER Contains a terminal-generated transaction sequence number to be submitted in all authorization request messages.

    This number is echoed back to the terminal for purposes of assisting in the matching of authorization request and response messages.
    This value must be in the range of 0001 - 9999 and is incremented on each authorization request message. This number is automatically incremented from 9999 to 0001.
    VALIDATION_CODE Discover Usage:
    Used to indicate the magnetic stripe condition and the vulnerability for fraud in Discover Network Card Transactions.

    Non-Discover Usage:
    Can contain specific information generated by the card issuer. The POS device should not attempt to interpret the meaning of any data appearing in this field. Data returned in this field is recorded and submitted as part of the data capture settlement format.
    VERIFICATION_RESULT_CODE Contains the host returned CVV2/CVC2/CID result code.
    cards-realtime.authorizenet.authorization.log   
    Added On:  10/20/14
    Level:  Trace
    Category:  cards-realtime.authorization
    Status:  Active
    Group:  processing
    File Name:  cards-realtime.authorizenet.authorization.log
    Resource:  $app-home/jboss-7.4.0/standalone/log/processing/cards-realtime.authorizenet.authorization.log
    Legacy File Name:  
    Сontains information about the processor's incoming requests and outgoing responses (authorizenet)
    Request Fields [Show Info]

    ALLOW_PARTIAL_AUTH, AMOUNT, BILL_TO_ADDRESS
    Name Description
    ALLOW_PARTIAL_AUTH Indicates whether partial authorization is supported. Default is 'N'. Valid values = 'Y' or 'N'.
    AMOUNT The amount element defines the amount of the transaction. Supply the value in cents without a decimal point.
    BILL_TO_ADDRESS
    Response Fields [Show Info]

    APPROVED_AMOUNT, AUTH_CODE, AVS_RESULT_CODE, BALANCE_ON_CARD
    Name Description
    APPROVED_AMOUNT Amount actually used. The merchant must tender the difference between the requested amount and the approved amount.
    AUTH_CODE The authCode element specifies the authorization code from the associated Authorization or Sale transaction.
    AVS_RESULT_CODE Address verification result code.
    BALANCE_ON_CARD
    cards-realtime.ezidebit.authorization.log   
    Added On:  10/20/14
    Level:  Trace
    Category:  cards-realtime.authorization
    Status:  Active
    Group:  processing
    File Name:  cards-realtime.ezidebit.authorization.log
    Resource:  $app-home/jboss-7.4.0/standalone/log/processing/cards-realtime.ezidebit.authorization.log
    Legacy File Name:  
    Сontains information about the processor's incoming requests and outgoing responses (ezidebit)
    Request Fields [Show Info]

    CUSTOMER_NAME, DEBIT_DATE, EMAIL_ADDRESS, FIRST_NAME, LAST_NAME, MERCHANT_ACCOUNT_CODE, MOBILE_PHONE_NUMBER, NAME_ON_CREDIT_CARD, PAYMENT_AMOUNT_IN_CENTS, PAYMENT_ID, PAYMENT_REFERENCE, REFUND_AMOUNT_IN_CENTS, REFUND_BANK_RECEIPT_ID, RETAIL_TRANSACTION_CYCLE_FK, SMS_EXPIRED_CARD, SMS_FAILED_NOTIFICATION, SMS_PAYMENT_REMINDER, SUBMISSION_CL, YOUR_GENERAL_REFERENCE, YOUR_SYSTEM_REFERENCE
    Name Description
    CUSTOMER_NAME Name of the customer.
    DEBIT_DATE Date when the payment will be deducted from customer's bank account or credit card.
    EMAIL_ADDRESS Email address of the customer.
    FIRST_NAME First name of the customer.
    LAST_NAME Last name of the customer.
    MERCHANT_ACCOUNT_CODE Code of Merchant Account to which instance of this object is attributed to.
    Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
    The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
    MOBILE_PHONE_NUMBER Mobile phone number of the customer for discussing any processing issues.
    NAME_ON_CREDIT_CARD Name of the credit card holder, printed on the credit card.
    PAYMENT_AMOUNT_IN_CENTS The amount to debit from the customer in cents.
    PAYMENT_ID The unique transaction ID given to the original payment by Ezidebit.
    PAYMENT_REFERENCE Reference number of the transaction.
    REFUND_AMOUNT_IN_CENTS The amount that the refund is to be processed for. Must be less than or equal to the amount originally paid by the payer.
    REFUND_BANK_RECEIPT_ID Receipt Number issued by the Merchant Acquirer (bank) for this refund.
    RETAIL_TRANSACTION_CYCLE_FK Reference to the entity that represents a group of real-time transactions which must be settled together.
    SMS_EXPIRED_CARD Indicates whether SMS notification will be sent to the customer if his recorded credit card is due to expire. Optional.
    SMS_FAILED_NOTIFICATION Indicates whether SMS notification will be sent to the customer if his debit fails.
    SMS_PAYMENT_REMINDER Indicates whether SMS notification will be sent to the customer to remind him of upcoming scheduled debits. Optional.
    SUBMISSION_CL Enumeration of possible submission types.
    YOUR_GENERAL_REFERENCE A secondary unique reference for the customer. If no value is supplied for this field it will default to 'LastnameFirstnameYYYYmmDDhhMM'.
    YOUR_SYSTEM_REFERENCE A unique system identifier for the customer (e.g. GUID or your primary key).
    Response Fields [Show Info]

    BANK_RECEIPT_ID, BANK_RECEIPT_ID, BANK_RECEIPT_ID, CUSTOMER_NAME, CUSTOMER_REF, EMAIL_ADDRESS, ERROR, ERROR_MESSAGE, EXCHANGE_PAYMENT_ID, FIRST_NAME, LAST_NAME, MERCHANT_ACCOUNT_CODE, MOBILE_PHONE_NUMBER, NAME_ON_CREDIT_CARD, PAYMENT_AMOUNT_IN_CENTS, PAYMENT_REFERENCE, PAYMENT_RESULT, PAYMENT_RESULT_CODE, PAYMENT_RESULT_TEXT, RETAIL_TRANSACTION_CYCLE_FK, SMS_EXPIRED_CARD, SMS_FAILED_NOTIFICATION, SMS_PAYMENT_REMINDER, SUBMISSION_CL, YOUR_GENERAL_REFERENCE, YOUR_SYSTEM_REFERENCE
    Name Description
    BANK_RECEIPT_ID The Original Receipt Number issued by the Merchant Acquirer (bank) for this payment.
    BANK_RECEIPT_ID The Original Receipt Number issued by the Merchant Acquirer (bank) for this payment.
    BANK_RECEIPT_ID The Original Receipt Number issued by the Merchant Acquirer (bank) for this payment.
    CUSTOMER_NAME Name of the customer.
    CUSTOMER_REF Unique reference number stored in the Ezidebit database that corresponds to the customer.
    EMAIL_ADDRESS Email address of the customer.
    ERROR Code of the occured error.
    ERROR_MESSAGE Text message explaining the occured error.
    EXCHANGE_PAYMENT_ID Identifier for the payment within Ezidebit's own payment systems.
    FIRST_NAME First name of the customer.
    LAST_NAME Last name of the customer.
    MERCHANT_ACCOUNT_CODE Code of Merchant Account to which instance of this object is attributed to.
    Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
    The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
    MOBILE_PHONE_NUMBER Mobile phone number of the customer for discussing any processing issues.
    NAME_ON_CREDIT_CARD Name of the credit card holder, printed on the credit card.
    PAYMENT_AMOUNT_IN_CENTS The amount to debit from the customer in cents.
    PAYMENT_REFERENCE Reference number of the transaction.
    PAYMENT_RESULT Result of the processed payment of the customer.
    PAYMENT_RESULT_CODE Gateway generated result code of the processed payment.
    PAYMENT_RESULT_TEXT Gateway generated result text message of the processed payment.
    RETAIL_TRANSACTION_CYCLE_FK Reference to the entity that represents a group of real-time transactions which must be settled together.
    SMS_EXPIRED_CARD Indicates whether SMS notification will be sent to the customer if his recorded credit card is due to expire. Optional.
    SMS_FAILED_NOTIFICATION Indicates whether SMS notification will be sent to the customer if his debit fails.
    SMS_PAYMENT_REMINDER Indicates whether SMS notification will be sent to the customer to remind him of upcoming scheduled debits. Optional.
    SUBMISSION_CL Enumeration of possible submission types.
    YOUR_GENERAL_REFERENCE A secondary unique reference for the customer. If no value is supplied for this field it will default to 'LastnameFirstnameYYYYmmDDhhMM'.
    YOUR_SYSTEM_REFERENCE A unique system identifier for the customer (e.g. GUID or your primary key).
    cards-realtime.nmi.authorization.log   
    Added On:  10/20/14
    Level:  Trace
    Category:  cards-realtime.authorization
    Status:  Active
    Group:  processing
    File Name:  cards-realtime.nmi.authorization.log
    Resource:  $app-home/jboss-7.4.0/standalone/log/processing/cards-realtime.nmi.authorization.log
    Legacy File Name:  
    Сontains information about the processor's incoming requests and outgoing responses (nmi)
    Request Fields [Show Info]

    ADDRESS1, AMOUNT, CHARGE_TRANSACTION_FK, CITY, COUNTRY, DESCRIPTOR, DESCRIPTOR_PHONE, EMAIL, FIRSTNAME, LASTNAME, MERCHANT_ACCOUNT_CODE, ORDERDESCRIPTION, ORDERID, PHONE, PONUMBER, PROCESSOR_ID, RETAIL_TRANSACTION_CYCLE_FK, SHIPPING, SHIPPING_ADDRESS1, SHIPPING_CITY, SHIPPING_COUNTRY, SHIPPING_FIRSTNAME, SHIPPING_LASTNAME, SHIPPING_STATE, SHIPPING_ZIP, STATE, TAX, TRANSACTIONID, TYPE, ZIP
    Name Description
    ADDRESS1 The first line of the merchant's street address.
    AMOUNT The amount element defines the amount of the transaction. Supply the value in cents without a decimal point.
    CHARGE_TRANSACTION_FK Reference to the entity that represents real-time financial transaction.
    CITY City of the mailing address.
    COUNTRY
    DESCRIPTOR
    DESCRIPTOR_PHONE
    EMAIL
    FIRSTNAME
    LASTNAME
    MERCHANT_ACCOUNT_CODE Code of Merchant Account to which instance of this object is attributed to.
    Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
    The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
    ORDERDESCRIPTION
    ORDERID
    PHONE
    PONUMBER
    PROCESSOR_ID
    RETAIL_TRANSACTION_CYCLE_FK Reference to the entity that represents a group of real-time transactions which must be settled together.
    SHIPPING
    SHIPPING_ADDRESS1
    SHIPPING_CITY
    SHIPPING_COUNTRY
    SHIPPING_FIRSTNAME
    SHIPPING_LASTNAME
    SHIPPING_STATE
    SHIPPING_ZIP
    STATE
    TAX
    TRANSACTIONID
    TYPE
    ZIP ZIP or postal code of the mailing address.
    Response Fields [Show Info]

    ADDRESS1, AMOUNT, AUTHCODE, AVSRESPONSE, CHARGE_TRANSACTION_FK, CITY, COUNTRY, CVVRESPONSE, DESCRIPTOR, DESCRIPTOR_PHONE, EMAIL, FIRSTNAME, LASTNAME, MERCHANT_ACCOUNT_CODE, ORDERDESCRIPTION, ORDERID, PHONE, PONUMBER, PROCESSOR_ID, RESPONSE, RESPONSECODE, RESPONSETEXT, RETAIL_TRANSACTION_CYCLE_FK, SHIPPING, SHIPPING_ADDRESS1, SHIPPING_CITY, SHIPPING_COUNTRY, SHIPPING_FIRSTNAME, SHIPPING_LASTNAME, SHIPPING_STATE, SHIPPING_ZIP, STATE, TAX, TRANSACTIONID, TYPE, ZIP
    Name Description
    ADDRESS1 The first line of the merchant's street address.
    AMOUNT The amount element defines the amount of the transaction. Supply the value in cents without a decimal point.
    AUTHCODE The authCode element specifies the authorization code from the associated Authorization or Sale transaction.
    AVSRESPONSE address verification response code returned in response message as a result of an AVS Request. It is also a required value for a terminal-based settlement, if returned in the authorization response.
    CHARGE_TRANSACTION_FK Reference to the entity that represents real-time financial transaction.
    CITY City of the mailing address.
    COUNTRY
    CVVRESPONSE
    DESCRIPTOR
    DESCRIPTOR_PHONE
    EMAIL
    FIRSTNAME
    LASTNAME
    MERCHANT_ACCOUNT_CODE Code of Merchant Account to which instance of this object is attributed to.
    Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
    The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
    ORDERDESCRIPTION
    ORDERID
    PHONE
    PONUMBER
    PROCESSOR_ID
    RESPONSE
    RESPONSECODE
    RESPONSETEXT
    RETAIL_TRANSACTION_CYCLE_FK Reference to the entity that represents a group of real-time transactions which must be settled together.
    SHIPPING
    SHIPPING_ADDRESS1
    SHIPPING_CITY
    SHIPPING_COUNTRY
    SHIPPING_FIRSTNAME
    SHIPPING_LASTNAME
    SHIPPING_STATE
    SHIPPING_ZIP
    STATE
    TAX
    TRANSACTIONID
    TYPE
    ZIP ZIP or postal code of the mailing address.
    cards-realtime.firstdata-buypass.authorization.log   
    Added On:  10/20/14
    Level:  Trace
    Category:  cards-realtime.authorization
    Status:  Active
    Group:  processing
    File Name:  cards-realtime.firstdata-buypass.authorization.log
    Resource:  $app-home/jboss-7.4.0/standalone/log/processing/cards-realtime.firstdata-buypass.authorization.log
    Legacy File Name:  
    Сontains information about the processor's incoming requests and outgoing responses (firstdata-buypass)
    Request Fields [Show Info]

    Name Description
    Response Fields [Show Info]

    Name Description
    fraud.subuno.log   
    Added On:  12/04/14
    Level:  Info
    Category:  fraud.subuno
    Status:  Active
    Group:  processing
    File Name:  fraud.subuno.log
    Legacy File Name:  
    Сontains information about fraud tracking (subuno)
    Request Fields [Show Info]

    , BILL_CITY, BILL_COUNTRY, BILL_STATE, BILL_STREET1, BILL_ZIP, CHARGE_TRANSACTION_FK, COMPANY, CUSTOMER_NAME, EMAIL, IP_ADDR, MERCHANT_ACCOUNT_CODE, PHONE, PRICE, SHIP_CITY, SHIP_NAME, SHIP_STATE, SHIP_STREET1, SHIP_ZIP, SOURCE, TID
    Name Description
    BILL_CITY
    BILL_COUNTRY
    BILL_STATE
    BILL_STREET1
    BILL_ZIP
    CHARGE_TRANSACTION_FK Reference to the entity that represents real-time financial transaction.
    COMPANY Company name.
    CUSTOMER_NAME
    EMAIL
    IP_ADDR
    MERCHANT_ACCOUNT_CODE Code of Merchant Account to which instance of this object is attributed to.
    Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
    The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
    PHONE
    PRICE
    SHIP_CITY
    SHIP_NAME
    SHIP_STATE
    SHIP_STREET1
    SHIP_ZIP
    SOURCE
    TID
    Response Fields [Show Info]

    , ACTION, AVS_RESPONSE, BILL_CITY, BILL_COUNTRY, BILL_STATE, BILL_STREET1, BILL_ZIP, CHARGE_TRANSACTION_FK, COMPANY, CUSTOMER_NAME, CVV_RESPONSE, EMAIL, IP_ADDR, MERCHANT_ACCOUNT_CODE, PHONE, PRICE, REF_CODE, SHIP_CITY, SHIP_NAME, SHIP_STATE, SHIP_STREET1, SHIP_ZIP, SOURCE, TID
    Name Description
    ACTION
    AVS_RESPONSE The Response Code to the Address Verification Service.
    BILL_CITY
    BILL_COUNTRY
    BILL_STATE
    BILL_STREET1
    BILL_ZIP
    CHARGE_TRANSACTION_FK Reference to the entity that represents real-time financial transaction.
    COMPANY Company name.
    CUSTOMER_NAME
    CVV_RESPONSE
    EMAIL
    IP_ADDR
    MERCHANT_ACCOUNT_CODE Code of Merchant Account to which instance of this object is attributed to.
    Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
    The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
    PHONE
    PRICE
    REF_CODE
    SHIP_CITY
    SHIP_NAME
    SHIP_STATE
    SHIP_STREET1
    SHIP_ZIP
    SOURCE
    TID
    cards-realtime.amex.authorization.log   
    Added On:  12/17/14
    Level:  Trace
    Category:  cards-realtime.authorization
    Status:  Active
    Group:  processing
    File Name:  cards-realtime.amex.authorization.log
    Resource:  $app-home/jboss-7.4.0/standalone/log/processing/cards-realtime.amex.authorization.log
    Legacy File Name:  
    Сontains information about the processor's incoming requests and outgoing responses (amex)
    Request Fields [Show Info]

    BIT11, BIT12, BIT13, BIT19, BIT22, BIT24, BIT25, BIT26, BIT27, BIT3, BIT31, BIT31_ACQUIRED_REFERENCE_DATA, BIT33, BIT37, BIT4, BIT4_AMOUNT, BIT41, BIT42, BIT43, BIT47, BIT48, BIT49, BIT56, BIT63, BIT7, CHARGE_TRANSACTION_FK, MERCHANT_ACCOUNT_CODE, RETAIL_TRANSACTION_CYCLE_FK
    Name Description
    BIT11 Unique trace number that identifies a transaction. Assigned by a merchant.
    BIT12 Year, month, day and local time when the transaction took place at the card acceptor location.
    BIT13 Date embossed on the face of the card supported by the processor.
    BIT19 Country code of the merchant's mailing address.
    BIT22 Code that identifies terminal capability, security data and specific conditions present at the time the transaction occurred at the point of service.
    BIT24 Function code. Assigned by the processor.
    BIT25 Reason code of the merchant. Assigned by the processor.
    BIT26 MCC code of the merchant.
    BIT27 Length of the approval code.
    BIT3 Code that indicates the financial service being requested. Assigned by the processor.
    BIT31 Reference data associated with the acquirer.
    BIT31_ACQUIRED_REFERENCE_DATA Reference data associated with the acquirer received in response.
    BIT33 Identification code of the forwarding institution.
    BIT37 Retrieval reference number. Assigned by the processor.
    BIT4 Total transaction amount.
    BIT4_AMOUNT Total transaction amount received in response.
    BIT41 Code that identifies a specific terminal at a merchant location.
    BIT42 Identifier of the merchant in a POS transaction.
    BIT43 Name and location of the card acceptor.
    BIT47 Additional data associated with the cardholder. This data field is used only for transactions where the cardholder is not present.
    BIT48 Extended payment indicator that consists of the plan type and number of installments. Assigned by the processor.
    BIT49 Code of the currency used in transaction.
    BIT56
    BIT63 Data that is required to process certain types of Authorization Request (1100) messages, such as American Express Travelers Cheque, and verifications for Cardmember Name, Address, ZIP Code, and Telephone Number.
    BIT7 System date and time when a merchant transmits the transaction information to the processor.
    CHARGE_TRANSACTION_FK Reference to the entity that represents real-time financial transaction.
    MERCHANT_ACCOUNT_CODE Code of Merchant Account to which instance of this object is attributed to.
    Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
    The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
    RETAIL_TRANSACTION_CYCLE_FK Reference to the entity that represents a group of real-time transactions which must be settled together.
    Response Fields [Show Info]

    BIT11, BIT12, BIT13, BIT19, BIT22, BIT24, BIT25, BIT26, BIT27, BIT3, BIT31, BIT31_ACQUIRED_REFERENCE_DATA, BIT32, BIT33, BIT37, BIT38_APPROVAL_CODE, BIT4, BIT4_AMOUNT, BIT41, BIT42, BIT43, BIT44_ADDITIONAL_RESPONSE_DATA, BIT47, BIT48, BIT49, BIT54_ADDITIONAL_AMOUNTS, BIT56, BIT62_PRIVATE_DATA, BIT63, BIT7, CHARGE_TRANSACTION_FK, MERCHANT_ACCOUNT_CODE, MESSAGE_TYPE_IDENTIFIER, RETAIL_TRANSACTION_CYCLE_FK
    Name Description
    BIT11 Unique trace number that identifies a transaction. Assigned by a merchant.
    BIT12 Year, month, day and local time when the transaction took place at the card acceptor location.
    BIT13 Date embossed on the face of the card supported by the processor.
    BIT19 Country code of the merchant's mailing address.
    BIT22 Code that identifies terminal capability, security data and specific conditions present at the time the transaction occurred at the point of service.
    BIT24 Function code. Assigned by the processor.
    BIT25 Reason code of the merchant. Assigned by the processor.
    BIT26 MCC code of the merchant.
    BIT27 Length of the approval code.
    BIT3 Code that indicates the financial service being requested. Assigned by the processor.
    BIT31 Reference data associated with the acquirer.
    BIT31_ACQUIRED_REFERENCE_DATA Reference data associated with the acquirer received in response.
    BIT32 Identification code of the acquiring institution processing the request.
    BIT33 Identification code of the forwarding institution.
    BIT37 Retrieval reference number. Assigned by the processor.
    BIT38_APPROVAL_CODE Approval code generated within the processor's system.
    BIT4 Total transaction amount.
    BIT4_AMOUNT Total transaction amount received in response.
    BIT41 Code that identifies a specific terminal at a merchant location.
    BIT42 Identifier of the merchant in a POS transaction.
    BIT43 Name and location of the card acceptor.
    BIT44_ADDITIONAL_RESPONSE_DATA Additional data associated with cardholder and included in response.
    BIT47 Additional data associated with the cardholder. This data field is used only for transactions where the cardholder is not present.
    BIT48 Extended payment indicator that consists of the plan type and number of installments. Assigned by the processor.
    BIT49 Code of the currency used in transaction.
    BIT54_ADDITIONAL_AMOUNTS Additional amounts included in processed transaction.
    BIT56
    BIT62_PRIVATE_DATA Private data associated with a cardholder received in response.
    BIT63 Data that is required to process certain types of Authorization Request (1100) messages, such as American Express Travelers Cheque, and verifications for Cardmember Name, Address, ZIP Code, and Telephone Number.
    BIT7 System date and time when a merchant transmits the transaction information to the processor.
    CHARGE_TRANSACTION_FK Reference to the entity that represents real-time financial transaction.
    MERCHANT_ACCOUNT_CODE Code of Merchant Account to which instance of this object is attributed to.
    Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
    The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
    MESSAGE_TYPE_IDENTIFIER Identifier of the type of the message.
    RETAIL_TRANSACTION_CYCLE_FK Reference to the entity that represents a group of real-time transactions which must be settled together.
    cards-realtime.heartland.authorization.log   
    Added On:  12/17/14
    Level:  Trace
    Category:  cards-realtime.authorization
    Status:  Active
    Group:  processing
    File Name:  cards-realtime.heartland.authorization.log
    Resource:  $app-home/jboss-7.4.0/standalone/log/processing/cards-realtime.heartland.authorization.log
    Legacy File Name:  
    Сontains information about the processor's incoming requests and outgoing responses (heartland).
    Request Fields [Show Info]

    , ACCOUNT_DATA_SOURCE, ACQUIRER_BIN, AGENT_BANK_NUMBER, AGENT_CHAIN_NUMBER, BATCH_NUMBER, CANCEL_DATA1, CANCEL_DATA2, CARD_ACCEPTOR_DATA, CARDHOLDER_ID_CODE, CHARGE_TRANSACTION_FK, CITY_CODE, INDUSTRY_CODE, MARKET_SPECIFIC_DATA, MERCHANT_ACCOUNT_CODE, MERCHANT_CATEGORY_CODE, MERCHANT_NUMBER, MERCHANT_SETTLEMENT_AGENT_NUMBER, RECORD_FORMAT, REQUESTED_ACI, RETAIL_TRANSACTION_CYCLE_FK, REVERSAL_TRANSACTION_ID, SECONDARY_AMOUNT, SHARING_GROUPS, STORE_NUMBER, TERMINAL_NUMBER, TIME_ZONE_DIFFERENTIAL, TRANSACTION_AMOUNT, TRANSACTION_CODE, TRANSACTION_SEQUENCE_NUMBER
    Name Description
    Identifies the merchant to a direct debit switch.

    This field must be supplied for all direct debit request transactions except for the Interlink Debit Cancel (Transaction Code 95). This number is provided by the signing member or processor.
    ACCOUNT_DATA_SOURCE Contains code identifying the source of the customer data entered in field:

    • D - Full magnetic stripe read and transmit, Track two
    • H - Full magnetic stripe read and transmit, Track one
    • T - Manually keyed, Track two capable
    • X - Manually keyed, Track one capable
    • @ - Manually keyed, terminal has no card reading capability
    ACQUIRER_BIN Contains a six-character numeric Visa assigned Bank Identification Number (BIN) issued by the merchant's member bank or processor. The Acquirer BIN identifies the member bank that signed the merchant using the POS application.
    AGENT_BANK_NUMBER Contains an agent number assigned by the signing member or processor. The number identifies an institution which signs merchants as an agent of a member. The member uses this number to identify the agent within TSYS Acquiring Solutions’ system.
    AGENT_CHAIN_NUMBER Contains a merchant chain identification number assigned by the signing member or processor. The member uses this number to identify the merchant chain within the TSYS Acquiring Solutions’ system.
    BATCH_NUMBER Contains a batch sequence number generated by the terminal. The number wraps from 999 to 001. This number is also transmitted as the data capture batch number. Batch numbers should not be repeated within five days.
    CANCEL_DATA1 The following sub-fields are required when performing an ATM or Debit Non-Confirm Authorization request, or when performing an Authorization Reversal request, a Debit Reversal/Cancel request, or a AFD Completion Advice message. For all other transaction types, this field should be submitted without data.

    Approval Code:
    Contains approval code returned in the original authorization response record. This is the authorization code for the completed AFD transaction, or the transaction to be either partially or completely reversed. For a debit non-confirm purchase or ATM authorization transactions, the approval code will be space filled.

    Local Transaction Date:
    Contains value reflecting the local transaction date returned in the original authorization response record for the AFD sale or the transaction to be canceled or reversed. For a debit non-confirm purchase or ATM authorization transactions, this field will contain the local transaction date.

    Local Transaction Time:
    Contains the local transaction time of the original authorization request for the AFD sale or the transaction to be either partially or fully reversed. The Local Transaction Time must be submitted in HHMMSS format. For a debit non-confirm purchase or ATM authorization transactions, this field will contain the local transaction time.

    Retrieval Reference Number:
    In AFD Completion Advice messages and reversal transactions, this field must contain Retrieval Reference Number returned in the original authorization response. For debit non-confirm purchase or ATM authorization transactions, this field contains two parts. The first four characters are a yddd date (Julian date) format. The last eight characters are a numeric transaction identification number.
    CANCEL_DATA2 The following sub-fields are required when requesting any of the following Authorization Transaction Codes: A3, A4, B1, B2, B3, B4, C1, C3, C4 and 5C. This field does not contain data for any other transaction types.

    System Trace Audit Number:
    Must contain the System Trace Audit Number returned in the confirmation data field of the debit authorization response record for the transaction to be canceled or reversed. For a debit non-confirm purchase transaction, this number uniquely.

    Network Identification Code:
    When returned in a debit authorization response message, this value designates the debit network through which the request was processed. When performing an Authorization Reversal, this field must contain the one-character Network Identification Code returned in the confirmation data field of the authorization response record for the item to be canceled or reversed. For a debit non-confirm or ATM authorization transactions, the network identification code field will be space-filled.
    CARD_ACCEPTOR_DATA The following sub-fields are required for direct debit transactions. For all other transactions, the following sub-fields should be configured as parameters within the POS system but need not necessarily contain data.

    The format of this 40-byte field is:

    “NNNNNNNNNNNNNNNNNNNNNNNNNLLLLLLLLLLLLLSS”
    where
    NNNN... 1-25 A/N Merchant Name
    LL.....LL 26-38 A/N Merchant City
    SS 39-40 A/N Merchant State

    For Direct Marketing merchants and preferred customer/passenger transport transactions, this field should contain a customer service phone number in XXX-XXXXXXX format.
    CARDHOLDER_ID_CODE Contains a code that specifies the method used to verify the identity the cardholder. The values can be used in conjunction with AVS and Recurring and Installment Requested ACI Indicators.

    • K - Personal Identification Number 32-character DUK/PT
    • M - Card Present: Unable to read Mag stripe, sending Address Verification Data
    • N - Card Not Present: Includes e-Commerce and Full Address Verification Data
    • Z - Cardholder Signature - Terminal has a PIN Pad
    • @ - Cardholder Signature - No PIN pad available
    CHARGE_TRANSACTION_FK Reference to the entity that represents real-time financial transaction.
    CITY_CODE Contains the code used to further identify the merchant location (ZIP Code).
    INDUSTRY_CODE Used to identify the industry type of the merchant submitting the authorization request.

    • R - Retail
    • D - Direct Marketing
    MARKET_SPECIFIC_DATA The following sub-fields contain market specific data for hotel and auto rental transactions. The market specific data sub-fields need not be supplied for incremental authorization or authorization reversal transactions.

    The format of this field is: “PIDD.”
    • P - Prestigious Indicator (This indicator is used by participants in Visa’s Prestigious Lodging Program)
    • I - Market Specific Data Identifier (The market specific data identifier is used to indicate which industry data is being submitted)
    • DD - Stay or Rental Duration (When the market specific data is supplied in an incremental transaction, this sub-field represents the number of additional days for the hotel stay or auto rental)

    • P - Non-participating properties should put a “space”
    • I - Bill Payment Transaction
    • DD - For Bill Payment this sub-field should be set to “00.”
    MERCHANT_ACCOUNT_CODE Code of Merchant Account to which instance of this object is attributed to.
    Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
    The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
    MERCHANT_CATEGORY_CODE Contains a number assigned by the signing member or processor to identify a merchant industry classification.

    This value is similar to the Standard Industry Code (SIC).
    MERCHANT_NUMBER Contains a unique number, assigned by the signing merchant’s bank or processor. Used to identify the merchant within the TSYS Acquiring Solutions system.
    MERCHANT_SETTLEMENT_AGENT_NUMBER Identifies the merchant settling agent. Provided by the signing member or processor.
    RECORD_FORMAT Identifies the message format with the TSYS Acquiring Solutions system.

    • D - Credit Card Authorization request messages (Groups I and III)
    • T - Debit/Electronic Benefits Transfer - EBT request messages (Groups I, II, and III)
    REQUESTED_ACI Contains the Requested Authorization Characteristics Indicator (ACI) used to identify an authorization request as potentially qualifying for CPS (Custom Payment Services) and MasterCard Merit programs. If a merchant chooses not to participate in CPS, the Requested ACI value should default to an “N.”
    Y - Device is CPS capable
    R - Recurring Payment. No AVS required
    N - Device is not CPS capable
    RETAIL_TRANSACTION_CYCLE_FK Reference to the entity that represents a group of real-time transactions which must be settled together.
    REVERSAL_TRANSACTION_ID When performing either an Incremental Authorization or Authorization Reversal request, this field must contain the Transaction Identifier returned in the original authorization response record. For all other transaction types, this field should be submitted without data.
    SECONDARY_AMOUNT Secondary amount associated with the transaction representing a cashback amount.

    This is a variable length field from zero to 12-character numeric in length. This field contains a secondary transaction amount related to the transaction type and industry indicated. The transaction amount is to be presented with an implied decimal point. For example, $.01 could be represented as 1, 01, or 001. The allowable number of significant digits, as well as the positioning of any implied decimal point, are dictated by the Currency Code designated. In the United States, the allowable number of significant characters is seven with an implied decimal point.
    In industries where cash back is permitted on purchase transactions, this field could contain a cash back amount.
    For Authorization Reversal transactions, this field must contain the final settlement amount for a partial reversal, and is not used for a full reversal.
    SHARING_GROUPS Contains a listing of direct debit and EBT networks that a POS device can access. Provided by the signing member or processor. The values must correspond to one of the Visa assigned direct debit network types. This data is part of the TSYS Acquiring Solutions direct debit data.
    STORE_NUMBER Contains a number assigned by the signing member, processor, or merchant to identify a specific merchant store within the TSYS Acquiring Solutions’ system.
    TERMINAL_NUMBER Contains a number assigned by the signing member, processor, or merchant to identify a unique terminal within a merchant location.

    Because the terminal number submitted in the authorization request is echoed back to the terminal in the authorization response, this field can additionally be used in controller-based environments to assist in the matching and routing of authorization request and response messages at the point of concentration.
    TIME_ZONE_DIFFERENTIAL Contains a code used to calculate the local time within the TSYS Acquiring Solutions authorization system.

    The differential is calculated by the signing member or processor, providing the standard local time zone differential from Greenwich Mean Time (GMT). The first character numeric specifies the direction of the differential and offset increment as well as whether daylight savings is observed, and the last two-character numeric specify the magnitude of the differential.
    For now, such values is used - 705, 706, 707, 708
    TRANSACTION_AMOUNT Contains the transaction amount to be authorized. The transaction amount is to be presented with implied decimal point.

    For all Authorization Reversal transactions, this field contains the Total Authorization Amount (the total of all previous authorizations performed for a particular transaction or associated with a single Transaction ID).
    TRANSACTION_CODE Contains a code identifying the type of authorization or function being requested.

    In conditions where an authorization request has been submitted to the host but no response was ever received, the transaction code should be converted to its corresponding “Repeat” value and resubmitted for authorization.

    • 54 - Standard Authorization Request
    • 56 - Used primarily in Direct Marketing, Mail, and Telephone Order Environments
    • 59 - Used to reverse a completed credit authorization prior to batch settlement
    • 93 - Standard Debit Authorization Request
    • 94 - Direct Debit: Purchase Return
    • 5A - Same as code '59', except the reversal is being submitted after batch settlement occurred
    • 5B - Bill Payment Transaction (Credit Card)
    • 9C - Debit transactions without a PIN
    • A3 - Automatic Reversal: Direct Debit Purchase
    • A4 - Automatic Reversal: Direct Debit Purchase Return
    TRANSACTION_SEQUENCE_NUMBER Contains a terminal-generated transaction sequence number to be submitted in all authorization request messages.

    This number is echoed back to the terminal for purposes of assisting in the matching of authorization request and response messages.
    This value must be in the range of 0001 - 9999 and is incremented on each authorization request message. This number is automatically incremented from 9999 to 0001.
    Response Fields [Show Info]

    , ACCOUNT_DATA_SOURCE, ACQUIRER_BIN, AGENT_BANK_NUMBER, AGENT_CHAIN_NUMBER, APPROVAL_CODE, AUTHORIZATION_RESPONSE_TEXT, AUTHORIZATION_SOURCE_CODE, AVS_RESULT_CODE, BATCH_NUMBER, CANCEL_DATA1, CANCEL_DATA2, CARD_ACCEPTOR_DATA, CARD_LEVEL_RESULTS, CARDHOLDER_ID_CODE, CAVV_RESULTS_CODE, CHARGE_TRANSACTION_FK, CITY_CODE, COMMERCIAL_CARD_RESPONSE_INDICATOR, FIRST_ACCOUNT_TYPE1, FIRST_ACCOUNT_TYPE2, FIRST_AMOUNT, FIRST_CURRENCY_CODE, FIRST_SIGN, FOURTH_ACCOUNT_TYPE1, FOURTH_ACCOUNT_TYPE2, FOURTH_AMOUNT, FOURTH_CURRENCY_CODE, FOURTH_SIGN, HOST_MESSAGE_IDENTIFIER, INDUSTRY_CODE, LOCAL_TRANSACTION_DATE, LOCAL_TRANSACTION_TIME, MARKET_DATA_IDENTIFIER, MARKET_SPECIFIC_DATA, MERCHANT_ACCOUNT_CODE, MERCHANT_CATEGORY_CODE, MERCHANT_NUMBER, MERCHANT_SETTLEMENT_AGENT_NUMBER, NETWORK_ID_CODE, RECORD_FORMAT, REQUESTED_ACI, RESPONSE_CODE, RETAIL_TRANSACTION_CYCLE_FK, RETRIEVAL_REFERENCE_NUMBER, RETURNED_ACI, REVERSAL_TRANSACTION_ID, SECOND_ACCOUNT_TYPE1, SECOND_ACCOUNT_TYPE2, SECOND_AMOUNT, SECOND_CURRENCY_CODE, SECOND_SIGN, SE
    Name Description
    Identifies the merchant to a direct debit switch.

    This field must be supplied for all direct debit request transactions except for the Interlink Debit Cancel (Transaction Code 95). This number is provided by the signing member or processor.
    ACCOUNT_DATA_SOURCE Contains code identifying the source of the customer data entered in field:

    • D - Full magnetic stripe read and transmit, Track two
    • H - Full magnetic stripe read and transmit, Track one
    • T - Manually keyed, Track two capable
    • X - Manually keyed, Track one capable
    • @ - Manually keyed, terminal has no card reading capability
    ACQUIRER_BIN Contains a six-character numeric Visa assigned Bank Identification Number (BIN) issued by the merchant's member bank or processor. The Acquirer BIN identifies the member bank that signed the merchant using the POS application.
    AGENT_BANK_NUMBER Contains an agent number assigned by the signing member or processor. The number identifies an institution which signs merchants as an agent of a member. The member uses this number to identify the agent within TSYS Acquiring Solutions’ system.
    AGENT_CHAIN_NUMBER Contains a merchant chain identification number assigned by the signing member or processor. The member uses this number to identify the merchant chain within the TSYS Acquiring Solutions’ system.
    APPROVAL_CODE Contains fixed approval code returned in the original authorization response record.

    This is the authorization code for the completed AFD transaction, or the transaction to be either partially or completely reversed. For a debit non-confirm purchase or ATM authorization transactions, the approval code will be space filled.
    AUTHORIZATION_RESPONSE_TEXT Contains a response or display text message. This message can be used by the terminal to display the authorization result. The display text must not be used to determine the nature of a response message.
    AUTHORIZATION_SOURCE_CODE Contains code indicating the source of the authorization code. The received code must be stored and resubmitted in the data capture settlement record.
    AVS_RESULT_CODE Contains the Address Verification Result Code. An Address Verification Result Code can provide additional information concerning the authentication of a particular transaction for which cardholder Address Verification was requested. An Address Verification result code of “0” is returned in the response message when no address verification has been requested. The value returned should be stored and submitted as part of the data capture settlement record.
    BATCH_NUMBER Contains a batch sequence number generated by the terminal. The number wraps from 999 to 001. This number is also transmitted as the data capture batch number. Batch numbers should not be repeated within five days.
    CANCEL_DATA1 The following sub-fields are required when performing an ATM or Debit Non-Confirm Authorization request, or when performing an Authorization Reversal request, a Debit Reversal/Cancel request, or a AFD Completion Advice message. For all other transaction types, this field should be submitted without data.

    Approval Code:
    Contains approval code returned in the original authorization response record. This is the authorization code for the completed AFD transaction, or the transaction to be either partially or completely reversed. For a debit non-confirm purchase or ATM authorization transactions, the approval code will be space filled.

    Local Transaction Date:
    Contains value reflecting the local transaction date returned in the original authorization response record for the AFD sale or the transaction to be canceled or reversed. For a debit non-confirm purchase or ATM authorization transactions, this field will contain the local transaction date.

    Local Transaction Time:
    Contains the local transaction time of the original authorization request for the AFD sale or the transaction to be either partially or fully reversed. The Local Transaction Time must be submitted in HHMMSS format. For a debit non-confirm purchase or ATM authorization transactions, this field will contain the local transaction time.

    Retrieval Reference Number:
    In AFD Completion Advice messages and reversal transactions, this field must contain Retrieval Reference Number returned in the original authorization response. For debit non-confirm purchase or ATM authorization transactions, this field contains two parts. The first four characters are a yddd date (Julian date) format. The last eight characters are a numeric transaction identification number.
    CANCEL_DATA2 The following sub-fields are required when requesting any of the following Authorization Transaction Codes: A3, A4, B1, B2, B3, B4, C1, C3, C4 and 5C. This field does not contain data for any other transaction types.

    System Trace Audit Number:
    Must contain the System Trace Audit Number returned in the confirmation data field of the debit authorization response record for the transaction to be canceled or reversed. For a debit non-confirm purchase transaction, this number uniquely.

    Network Identification Code:
    When returned in a debit authorization response message, this value designates the debit network through which the request was processed. When performing an Authorization Reversal, this field must contain the one-character Network Identification Code returned in the confirmation data field of the authorization response record for the item to be canceled or reversed. For a debit non-confirm or ATM authorization transactions, the network identification code field will be space-filled.
    CARD_ACCEPTOR_DATA The following sub-fields are required for direct debit transactions. For all other transactions, the following sub-fields should be configured as parameters within the POS system but need not necessarily contain data.

    The format of this 40-byte field is:

    “NNNNNNNNNNNNNNNNNNNNNNNNNLLLLLLLLLLLLLSS”
    where
    NNNN... 1-25 A/N Merchant Name
    LL.....LL 26-38 A/N Merchant City
    SS 39-40 A/N Merchant State

    For Direct Marketing merchants and preferred customer/passenger transport transactions, this field should contain a customer service phone number in XXX-XXXXXXX format.
    CARD_LEVEL_RESULTS Contains code created by Visa during the authorization process.

    Conditional in the response record. It will only be returned if the values are non-zero.
    CARDHOLDER_ID_CODE Contains a code that specifies the method used to verify the identity the cardholder. The values can be used in conjunction with AVS and Recurring and Installment Requested ACI Indicators.

    • K - Personal Identification Number 32-character DUK/PT
    • M - Card Present: Unable to read Mag stripe, sending Address Verification Data
    • N - Card Not Present: Includes e-Commerce and Full Address Verification Data
    • Z - Cardholder Signature - Terminal has a PIN Pad
    • @ - Cardholder Signature - No PIN pad available
    CAVV_RESULTS_CODE Indicates whether the authentication value submitted by the merchant can be validated by Visa or the issuer.
    CHARGE_TRANSACTION_FK Reference to the entity that represents real-time financial transaction.
    CITY_CODE Contains the code used to further identify the merchant location (ZIP Code).
    COMMERCIAL_CARD_RESPONSE_INDICATOR If the Commercial Card Request Indicator (this field is utilized to request that TSYS Acquiring Solutions systems return a value in the authorization response message identifying whether the card type being presented was a Commercial Card. This field is currently defaulted to 010, and is supported for Visa and MasterCard transactions only) was supplied in the authorization request, the host responds with one of the following response indicators identifying the card being processed.

    When a response indicator has been received indicating that the approved card is a Business, Corporate, or Purchasing Card, the POS device should prompt for addendum data elements as needed for settlement.
    FIRST_ACCOUNT_TYPE1 Contains identifiers for account types.
    FIRST_ACCOUNT_TYPE2 Contains identifiers for account types.
    FIRST_AMOUNT Contains any additional amounts related to the authorization request or response.
    FIRST_CURRENCY_CODE Contains currency code identifying the currency for the returned additional amount.
    FIRST_SIGN Indicates whether the amount is a debit or credit.
    FOURTH_ACCOUNT_TYPE1 Contains identifiers for account types.
    FOURTH_ACCOUNT_TYPE2 Contains identifiers for account types.
    FOURTH_AMOUNT Contains any additional amounts related to the authorization request or response.
    FOURTH_CURRENCY_CODE Contains currency code identifying the currency for the returned additional amount.
    FOURTH_SIGN Indicates whether the amount is a debit or credit.
    HOST_MESSAGE_IDENTIFIER Contains a unique host message identifier assigned by the authorizing system and returned in debit card response messages. Reserved for future use and will most likely contain spaces. This value must be recorded and submitted in the debit confirmation record.
    INDUSTRY_CODE Used to identify the industry type of the merchant submitting the authorization request.

    • R - Retail
    • D - Direct Marketing
    LOCAL_TRANSACTION_DATE Contains value reflecting the local transaction date (in MMDDYY format) returned in the original authorization response record for the AFD sale or the transaction to be canceled or reversed. For a debit non-confirm purchase or ATM authorization transactions, this field will contain the local transaction date.
    LOCAL_TRANSACTION_TIME Contains the local transaction time of the original authorization request for the AFD sale or the transaction to be either partially or fully reversed. The local transaction time must be submitted in HHMMSS format. For a debit non-confirm purchase or ATM authorization transactions, this field will contain the local transaction time.
    MARKET_DATA_IDENTIFIER Used to indicate which industry data is being submitted.

    When this sub-field is supplied in an incremental transaction, it should use the same value that was requested in the original authorization transaction.
    MARKET_SPECIFIC_DATA The following sub-fields contain market specific data for hotel and auto rental transactions. The market specific data sub-fields need not be supplied for incremental authorization or authorization reversal transactions.

    The format of this field is: “PIDD.”
    • P - Prestigious Indicator (This indicator is used by participants in Visa’s Prestigious Lodging Program)
    • I - Market Specific Data Identifier (The market specific data identifier is used to indicate which industry data is being submitted)
    • DD - Stay or Rental Duration (When the market specific data is supplied in an incremental transaction, this sub-field represents the number of additional days for the hotel stay or auto rental)

    • P - Non-participating properties should put a “space”
    • I - Bill Payment Transaction
    • DD - For Bill Payment this sub-field should be set to “00.”
    MERCHANT_ACCOUNT_CODE Code of Merchant Account to which instance of this object is attributed to.
    Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
    The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
    MERCHANT_CATEGORY_CODE Contains a number assigned by the signing member or processor to identify a merchant industry classification.

    This value is similar to the Standard Industry Code (SIC).
    MERCHANT_NUMBER Contains a unique number, assigned by the signing merchant’s bank or processor. Used to identify the merchant within the TSYS Acquiring Solutions system.
    MERCHANT_SETTLEMENT_AGENT_NUMBER Identifies the merchant settling agent. Provided by the signing member or processor.
    NETWORK_ID_CODE Contains a code that specifies the network to be used for transmission of the message and determines the program rules that apply to the transaction.
    RECORD_FORMAT Identifies the message format with the TSYS Acquiring Solutions system.

    • D - Credit Card Authorization request messages (Groups I and III)
    • T - Debit/Electronic Benefits Transfer - EBT request messages (Groups I, II, and III)
    REQUESTED_ACI Contains the Requested Authorization Characteristics Indicator (ACI) used to identify an authorization request as potentially qualifying for CPS (Custom Payment Services) and MasterCard Merit programs. If a merchant chooses not to participate in CPS, the Requested ACI value should default to an “N.”
    Y - Device is CPS capable
    R - Recurring Payment. No AVS required
    N - Device is not CPS capable
    RESPONSE_CODE Contains code identifying the type of authorization or function being requested.

    In conditions where an authorization request has been submitted to the host but no response was ever received, the transaction code should be converted to its corresponding “Repeat” value and resubmitted for authorization.
    RETAIL_TRANSACTION_CYCLE_FK Reference to the entity that represents a group of real-time transactions which must be settled together.
    RETRIEVAL_REFERENCE_NUMBER Contains value reflecting the transaction Retrieval Reference Number returned by the authorizing system.

    The POS system should record the retrieval reference number received in the original authorization response. The Retrieval Reference Number from the original response is required when submitting AFD Completion Advice messages and when submitting incremental authorizations, or authorization reversal requests that must be settled for direct debit transactions.
    RETURNED_ACI Contains the Returned Authorization Characteristics Indicator (ACI).
    Provides information concerning the transactions’ CPS qualification status. It is not recommended that the POS system attempt to interpret the meaning of this value. Instead, the POS system should extract whatever value is returned in this field and submit it in the data capture settlement record. The POS system should not interpret any relationship between this field and the presence of data in either the Transaction Identifier or Validation Code fields.
    REVERSAL_TRANSACTION_ID When performing either an Incremental Authorization or Authorization Reversal request, this field must contain the Transaction Identifier returned in the original authorization response record. For all other transaction types, this field should be submitted without data.
    SECOND_ACCOUNT_TYPE1 Contains identifiers for account types.
    SECOND_ACCOUNT_TYPE2 Contains identifiers for account types.
    SECOND_AMOUNT Contains any additional amounts related to the authorization request or response.
    SECOND_CURRENCY_CODE Contains currency code identifying the currency for the returned additional amount.
    SECOND_SIGN Indicates whether the amount is a debit or credit.
    SETTLEMENT_DATE Contains the transaction settlement date returned by the TSYS Acquiring Solutions authorization system and is submitted in MMDD format.
    SHARING_GROUPS Contains a listing of direct debit and EBT networks that a POS device can access. Provided by the signing member or processor. The values must correspond to one of the Visa assigned direct debit network types. This data is part of the TSYS Acquiring Solutions direct debit data.
    SPEND_QUALIFIED_INDICATOR Optionally sent by Visa in an autorization response message. The merchant's intercharge rate may be determined by spend qualified indicator. See the specification of the processor for more information.
    STORE_NUMBER Contains a number assigned by the signing member, processor, or merchant to identify a specific merchant store within the TSYS Acquiring Solutions’ system.
    SYSTEM_TRACE_AUDIT_NUMBER Must contain System Trace Audit Number returned in the confirmation data field of the debit authorization response record for the transaction to be canceled or reversed. For a debit non-confirm purchase transaction, this number uniquely identifies a cardholder transaction. The trace number remains unchanged for all messages throughout the life cycle of the transaction.
    TERMINAL_NUMBER Contains a number assigned by the signing member, processor, or merchant to identify a unique terminal within a merchant location.

    Because the terminal number submitted in the authorization request is echoed back to the terminal in the authorization response, this field can additionally be used in controller-based environments to assist in the matching and routing of authorization request and response messages at the point of concentration.
    THIRD_ACCOUNT_TYPE1 Contains identifiers for account types.
    THIRD_ACCOUNT_TYPE2 Contains identifiers for account types.
    THIRD_AMOUNT Contains any additional amounts related to the authorization request or response.
    THIRD_CURRENCY_CODE Contains currency code identifying the currency for the returned additional amount.
    THIRD_SIGN Indicates whether the amount is a debit or credit.
    TIME_ZONE_DIFFERENTIAL Contains a code used to calculate the local time within the TSYS Acquiring Solutions authorization system.

    The differential is calculated by the signing member or processor, providing the standard local time zone differential from Greenwich Mean Time (GMT). The first character numeric specifies the direction of the differential and offset increment as well as whether daylight savings is observed, and the last two-character numeric specify the magnitude of the differential.
    For now, such values is used - 705, 706, 707, 708
    TRANSACTION_AMOUNT Contains the transaction amount to be authorized. The transaction amount is to be presented with implied decimal point.

    For all Authorization Reversal transactions, this field contains the Total Authorization Amount (the total of all previous authorizations performed for a particular transaction or associated with a single Transaction ID).
    TRANSACTION_CODE Contains a code identifying the type of authorization or function being requested.

    In conditions where an authorization request has been submitted to the host but no response was ever received, the transaction code should be converted to its corresponding “Repeat” value and resubmitted for authorization.

    • 54 - Standard Authorization Request
    • 56 - Used primarily in Direct Marketing, Mail, and Telephone Order Environments
    • 59 - Used to reverse a completed credit authorization prior to batch settlement
    • 93 - Standard Debit Authorization Request
    • 94 - Direct Debit: Purchase Return
    • 5A - Same as code '59', except the reversal is being submitted after batch settlement occurred
    • 5B - Bill Payment Transaction (Credit Card)
    • 9C - Debit transactions without a PIN
    • A3 - Automatic Reversal: Direct Debit Purchase
    • A4 - Automatic Reversal: Direct Debit Purchase Return
    TRANSACTION_IDENTIFIER Contains a transaction identifier (Visa, American Express or Discover) or Reference Number (MasterCard). The POS device does not attempt to interpret the meaning of any data appearing in this field. Data returned in this field is recorded and submitted as part of the data capture settlement format.
    TRANSACTION_SEQUENCE_NUMBER Contains a terminal-generated transaction sequence number to be submitted in all authorization request messages.

    This number is echoed back to the terminal for purposes of assisting in the matching of authorization request and response messages.
    This value must be in the range of 0001 - 9999 and is incremented on each authorization request message. This number is automatically incremented from 9999 to 0001.
    VALIDATION_CODE Discover Usage:
    Used to indicate the magnetic stripe condition and the vulnerability for fraud in Discover Network Card Transactions.

    Non-Discover Usage:
    Can contain specific information generated by the card issuer. The POS device should not attempt to interpret the meaning of any data appearing in this field. Data returned in this field is recorded and submitted as part of the data capture settlement format.
    VERIFICATION_RESULT_CODE Contains the host returned CVV2/CVC2/CID result code.
    cards-realtime.heartland-portico.authorization.log   
    Added On:  12/17/14
    Level:  Trace
    Category:  cards-realtime.authorization
    Status:  Active
    Group:  processing
    File Name:  cards-realtime.heartland-portico.authorization.log
    Resource:  $app-home/jboss-7.4.0/standalone/log/processing/cards-realtime.heartland-portico.authorization.log
    Legacy File Name:  cards-realtime.heartlandportico.authorization.log
    Сontains information about the processor's incoming requests and outgoing responses (heartland-portico).
    Request Fields [Show Info]

    ACTION, ALIAS, ALLOW_PARTIAL_AUTH, AMT, BALANCE_INQUIRY_TYPE, CARD_HOLDER_ADDR, CARD_HOLDER_CITY, CARD_HOLDER_EMAIL, CARD_HOLDER_FIRST_NAME, CARD_HOLDER_LAST_NAME, CARD_HOLDER_PHONE, CARD_HOLDER_PO_NBR, CARD_HOLDER_STATE, CARD_HOLDER_ZIP, CARD_PRESENT, CASH_BACK_AMT_INFO, CPC_REQ, CURRENCY, CVV2_STATUS, DEVELOPER_ID, DEVICE_ID, DIRECT_MKT_INVOICE_NBR, DIRECT_MKT_SHIP_DAY, DIRECT_MKT_SHIP_MONTH, ECOMMERCE, ELECTRONIC_VOUCHER_SERIAL_NBR, FIRST_ADDITIONAL_AMT, FIRST_ADDITIONAL_AMT_TYPE, FOURTH_ADDITIONAL_AMT, FOURTH_ADDITIONAL_AMT_TYPE, GRATUITY_AMT_INFO, INVOICE_NBR, LICENSE_ID, MERCHANT_ACCOUNT_CODE, OFFLINE_AUTH_CODE, ONE_TIME_PAYMENT, READER_PRESENT, REQUEST_TYPE, SECOND_ADDITIONAL_AMT, SECOND_ADDITIONAL_AMT_TYPE, SITE_ID, SITE_TRACE, TAX_AMT, TAX_TYPE, THIRD_ADDITIONAL_AMT, THIRD_ADDITIONAL_AMT_TYPE, USER_NAME, VERSION_NBR, VOUCHER_APPROVAL_CD
    Name Description
    ACTION Type of Alias action requested
    Valid values are as follows: DELETE, ADD, CREATE.
    ALIAS Alternate identifier used to reference a stored value account.
    ALLOW_PARTIAL_AUTH Indicates whether partial authorization is supported. Default is 'N'.

    Valid values = 'Y' or 'N'.
    AMT Contains total amount of additional amounts.
    BALANCE_INQUIRY_TYPE Balance Inquiry Type:

    CASH = Cash Benefits
    FOODSTAMP = Food Stamp
    CARD_HOLDER_ADDR Cardholder address that can be used for address verification.
    CARD_HOLDER_CITY Cardholder city.

    Maximum length = 20.
    CARD_HOLDER_EMAIL Cardholder email address.
    Maximum length = 40.
    CARD_HOLDER_FIRST_NAME Cardholder first name.

    Maximum length = 26.
    CARD_HOLDER_LAST_NAME Cardholder last name.

    Maximum length = 26.
    CARD_HOLDER_PHONE Cardholder phone number.

    Maximum length = 10.
    CARD_HOLDER_PO_NBR Purchase order number assigned by the cardholder.

    Maximum length = 17.
    CARD_HOLDER_STATE Cardholder state.

    Maximum length = 20.
    CARD_HOLDER_ZIP Cardholder zip code that can be used for address verification.

    Maximum length = 9.
    CARD_PRESENT Indicates whether a card reader was present when card data was manually entered.

    Valid values = Y or N.
    CASH_BACK_AMT_INFO Cash back amount information, the portion of the settlement amount that represents cash back given to the cardholder.
    CPC_REQ Commercial card request.

    Valid values = Y or N.
    CURRENCY Identifies the currency of the transaction amount.
    CVV2_STATUS Indicates why the CVV2 value was not provided. Valid values include: ILLEGIBLE and NOTPRESENT.

    Note:This field is NOT used for EBT transactions.
    DEVELOPER_ID Developer Identifier, field length is exactly 6 characters.

    NOTE: Even though this field is optional in the schema, it is now required for all new certifications.
    DEVICE_ID Device identifier, assigned by Heartland Payment Systems during registration.
    DIRECT_MKT_INVOICE_NBR Invoice number for direct marketing.

    Maximum length = 25.
    DIRECT_MKT_SHIP_DAY Ship day for direct marketing.
    DIRECT_MKT_SHIP_MONTH Ship month for direct marketing.

    ECOMMERCE Identifies this transaction as eCommerce or mail order/telephone order.

    Valid values = ECOM or MOTO
    ELECTRONIC_VOUCHER_SERIAL_NBR Serial Number provides by EBT voice authorization System.
    FIRST_ADDITIONAL_AMT First Amount object.

    The first amount must have an AmtType of "4S."
    FIRST_ADDITIONAL_AMT_TYPE The first amount type is '4S'.
    FOURTH_ADDITIONAL_AMT Fourth Amount object.
    FOURTH_ADDITIONAL_AMT_TYPE Type of forth amount object: date and time.
    GRATUITY_AMT_INFO If present, revises (replaces) the gratuity amount information of the original auth. If not present, does not affect the gratuity amount information, if any, of the original auth. This element is for informational purposes only and does not affect the authorized amount.
    INVOICE_NBR Invoice number for direct marketing.

    Maximum length = 25
    LICENSE_ID License identifier, assigned by Heartland Payment Systems Administrator during registration.
    MERCHANT_ACCOUNT_CODE Code of Merchant Account to which instance of this object is attributed to.
    Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
    The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
    OFFLINE_AUTH_CODE Authorization code obtained from the Issuer outside of the POS Gateway.

    Maximum characters = 8
    ONE_TIME_PAYMENT Indicates whether this is a one time payment (Y) or a recurring payment.

    Valid values = Y or N.
    READER_PRESENT Indicates whether a card reader was present when card data was manually entered.

    Valid values = Y or N.
    REQUEST_TYPE Contains an identifier to aid in determining the type of client's request.
    SECOND_ADDITIONAL_AMT Second Amount object.
    SECOND_ADDITIONAL_AMT_TYPE Type of second ammount.
    SITE_ID Site identifier, assigned by Heartland Payment Systems during registration.
    SITE_TRACE Site trace, specified by client and echoed in the response for validation.
    TAX_AMT Tax amount.
    TAX_TYPE Tax type indicator that qualifies the CPC tax amount.
    THIRD_ADDITIONAL_AMT Third Amount object.
    THIRD_ADDITIONAL_AMT_TYPE Type of third amount.
    USER_NAME User name, assigned by Heartland Payment Systems Administrator during registration.
    VERSION_NBR POS Version Number.

    NOTE: Even though this field is optional in the schema, it is now required for all new certifications.
    VOUCHER_APPROVAL_CD Provided by EBT Voice Authorization System.
    Response Fields [Show Info]

    ACTION, ALIAS, ALLOW_PARTIAL_AUTH, AMT, BALANCE_AMOUNT, BALANCE_INQUIRY_TYPE, CARD_HOLDER_ADDR, CARD_HOLDER_CITY, CARD_HOLDER_EMAIL, CARD_HOLDER_FIRST_NAME, CARD_HOLDER_LAST_NAME, CARD_HOLDER_PHONE, CARD_HOLDER_PO_NBR, CARD_HOLDER_STATE, CARD_HOLDER_ZIP, CARD_PRESENT, CASH_BACK_AMT_INFO, CPC_REQ, CURRENCY, CVV2_STATUS, DEVELOPER_ID, DEVICE_ID, DIRECT_MKT_INVOICE_NBR, DIRECT_MKT_SHIP_DAY, DIRECT_MKT_SHIP_MONTH, ECOMMERCE, ELECTRONIC_VOUCHER_SERIAL_NBR, FIRST_ADDITIONAL_AMT, FIRST_ADDITIONAL_AMT_TYPE, FOURTH_ADDITIONAL_AMT, FOURTH_ADDITIONAL_AMT_TYPE, GRATUITY_AMT_INFO, INVOICE_NBR, LICENSE_ID, MERCHANT_ACCOUNT_CODE, NOTES, OFFLINE_AUTH_CODE, ONE_TIME_PAYMENT, POINTS_BALANCE_AMT, READER_PRESENT, REFUND_AMOUNT, REQUEST_TYPE, REWARDS, SECOND_ADDITIONAL_AMT, SECOND_ADDITIONAL_AMT_TYPE, SITE_ID, SITE_TRACE, SPLIT_TENDER_CARD_AMT, TAX_AMT, TAX_TYPE, THIRD_ADDITIONAL_AMT, THIRD_ADDITIONAL_AMT_TYPE, USER_NAME, VERSION_NBR, VOUCHER_APPROVAL_CD
    Name Description
    ACTION Type of Alias action requested
    Valid values are as follows: DELETE, ADD, CREATE.
    ALIAS Alternate identifier used to reference a stored value account.
    ALLOW_PARTIAL_AUTH Indicates whether partial authorization is supported. Default is 'N'.

    Valid values = 'Y' or 'N'.
    AMT Contains total amount of additional amounts.
    BALANCE_AMOUNT If authorized, the new balance on the gift card.
    BALANCE_INQUIRY_TYPE Balance Inquiry Type:

    CASH = Cash Benefits
    FOODSTAMP = Food Stamp
    CARD_HOLDER_ADDR Cardholder address that can be used for address verification.
    CARD_HOLDER_CITY Cardholder city.

    Maximum length = 20.
    CARD_HOLDER_EMAIL Cardholder email address.
    Maximum length = 40.
    CARD_HOLDER_FIRST_NAME Cardholder first name.

    Maximum length = 26.
    CARD_HOLDER_LAST_NAME Cardholder last name.

    Maximum length = 26.
    CARD_HOLDER_PHONE Cardholder phone number.

    Maximum length = 10.
    CARD_HOLDER_PO_NBR Purchase order number assigned by the cardholder.

    Maximum length = 17.
    CARD_HOLDER_STATE Cardholder state.

    Maximum length = 20.
    CARD_HOLDER_ZIP Cardholder zip code that can be used for address verification.

    Maximum length = 9.
    CARD_PRESENT Indicates whether a card reader was present when card data was manually entered.

    Valid values = Y or N.
    CASH_BACK_AMT_INFO Cash back amount information, the portion of the settlement amount that represents cash back given to the cardholder.
    CPC_REQ Commercial card request.

    Valid values = Y or N.
    CURRENCY Identifies the currency of the transaction amount.
    CVV2_STATUS Indicates why the CVV2 value was not provided. Valid values include: ILLEGIBLE and NOTPRESENT.

    Note:This field is NOT used for EBT transactions.
    DEVELOPER_ID Developer Identifier, field length is exactly 6 characters.

    NOTE: Even though this field is optional in the schema, it is now required for all new certifications.
    DEVICE_ID Device identifier, assigned by Heartland Payment Systems during registration.
    DIRECT_MKT_INVOICE_NBR Invoice number for direct marketing.

    Maximum length = 25.
    DIRECT_MKT_SHIP_DAY Ship day for direct marketing.
    DIRECT_MKT_SHIP_MONTH Ship month for direct marketing.

    ECOMMERCE Identifies this transaction as eCommerce or mail order/telephone order.

    Valid values = ECOM or MOTO
    ELECTRONIC_VOUCHER_SERIAL_NBR Serial Number provides by EBT voice authorization System.
    FIRST_ADDITIONAL_AMT First Amount object.

    The first amount must have an AmtType of "4S."
    FIRST_ADDITIONAL_AMT_TYPE The first amount type is '4S'.
    FOURTH_ADDITIONAL_AMT Fourth Amount object.
    FOURTH_ADDITIONAL_AMT_TYPE Type of forth amount object: date and time.
    GRATUITY_AMT_INFO If present, revises (replaces) the gratuity amount information of the original auth. If not present, does not affect the gratuity amount information, if any, of the original auth. This element is for informational purposes only and does not affect the authorized amount.
    INVOICE_NBR Invoice number for direct marketing.

    Maximum length = 25
    LICENSE_ID License identifier, assigned by Heartland Payment Systems Administrator during registration.
    MERCHANT_ACCOUNT_CODE Code of Merchant Account to which instance of this object is attributed to.
    Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
    The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
    NOTES Contains rewards messages to be displayed on a receipt, mobile app, or web page to inform an account holder about special rewards or promotions available on the account.
    OFFLINE_AUTH_CODE Authorization code obtained from the Issuer outside of the POS Gateway.

    Maximum characters = 8
    ONE_TIME_PAYMENT Indicates whether this is a one time payment (Y) or a recurring payment.

    Valid values = Y or N.
    POINTS_BALANCE_AMT If authorized, the new balance on the stored value account in points.
    READER_PRESENT Indicates whether a card reader was present when card data was manually entered.

    Valid values = Y or N.
    REFUND_AMOUNT If authorized, the new balance that was on the card before it was deactivated and should be refunded to the cardholder.
    REQUEST_TYPE Contains an identifier to aid in determining the type of client's request.
    REWARDS Identifies rewards (dollars or points) added to the account as a result of a transaction.
    SECOND_ADDITIONAL_AMT Second Amount object.
    SECOND_ADDITIONAL_AMT_TYPE Type of second ammount.
    SITE_ID Site identifier, assigned by Heartland Payment Systems during registration.
    SITE_TRACE Site trace, specified by client and echoed in the response for validation.
    SPLIT_TENDER_CARD_AMT If insufficient funds on gift card to complete sale, the split tender portion of the total sale that was subtracted from the gift card balance.
    TAX_AMT Tax amount.
    TAX_TYPE Tax type indicator that qualifies the CPC tax amount.
    THIRD_ADDITIONAL_AMT Third Amount object.
    THIRD_ADDITIONAL_AMT_TYPE Type of third amount.
    USER_NAME User name, assigned by Heartland Payment Systems Administrator during registration.
    VERSION_NBR POS Version Number.

    NOTE: Even though this field is optional in the schema, it is now required for all new certifications.
    VOUCHER_APPROVAL_CD Provided by EBT Voice Authorization System.
    cards-realtime.mercurypay.authorization.log   
    Added On:  12/17/14
    Level:  Trace
    Category:  cards-realtime.authorization
    Status:  Active
    Group:  processing
    File Name:  cards-realtime.mercurypay.authorization.log
    Resource:  $app-home/jboss-7.4.0/standalone/log/processing/cards-realtime.mercurypay.authorization.log
    Legacy File Name:  
    Сontains information about the processor's incoming requests and outgoing responses (mercurypay)
    Request Fields [Show Info]

    ADDRESS, AMOUNT_CASHBACK, AMOUNT_PRESCRIPTION, AMOUNT_PURCHASE, AVS_DATA, CHARGE_TRANSACTION_FK, CUSTOMER_CODE, INVOICE_NO, MEMO, MERCHANT_ACCOUNT_CODE, MERCHANT_ID, NAME, OPERATOR_ID, PARTIAL_AUTH, REF_NO, RETAIL_TRANSACTION_CYCLE_FK, RETURN_CODE, STATUS, TAX, TERMINAL_ID, TRAN_CODE, TRAN_TYPE, VOUCHER_NUMBER, ZIP
    Name Description
    ADDRESS
    AMOUNT_CASHBACK Amount of change after the purchase, issued in cash.
    AMOUNT_PRESCRIPTION
    AMOUNT_PURCHASE Amount of purchased goods
    AVS_DATA This is referred to as Address Verification Service (AVS).

    Though not impacting the actual authorization approval, a better processing rate is achieved for some (retail, QSR,) merchants if address information is supplied when the card is not swiped.
    CHARGE_TRANSACTION_FK Reference to the entity that represents real-time financial transaction.
    CUSTOMER_CODE The actual PO number, the merchant’s zip code, or the transaction invoice number, will sufficient to meet the Level II reporting requirements.
    INVOICE_NO The locally generated always incrementing individual transaction number.
    MEMO Required field in all ActiveX and WebServices integrations
    MERCHANT_ACCOUNT_CODE Code of Merchant Account to which instance of this object is attributed to.
    Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
    The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
    MERCHANT_ID Merchant identifier, assigned by processor.

    The typical format for a Mercury Merchant ID combines an 11 digit numeric value, separated with an ‘=’ and a 6 digit alpha value as in: 884300XXXXX=ABCDEF.. Is returned without the "Nick Name" in the response.

    NAME Name of the provider account.

    Generated automatically by default. Comprised of a merchant account code followed by the type of provider profile for which it is defined.
    OPERATOR_ID Identifier of the operator carrying the transaction.
    PARTIAL_AUTH Use of the data element will “allow” a partial approval if the balance on the card is less than the purchase amount requested.
    The transaction will approve for the authorized balance amount available on the card and will not decline the transaction.
    REF_NO A transaction reference value returned in the transaction response and indicates that an approved transaction has been “referenced” and is added to the current batch file.

    This field is used as a “filler value” on the initial request until an actual host value is returned indicating the transaction is now in the batch file; a true RefNo is returned on the response and logged at the host for all completed transactions.
    RETAIL_TRANSACTION_CYCLE_FK Reference to the entity that represents a group of real-time transactions which must be settled together.
    RETURN_CODE Identifies the any error type.
    Value will be zero if transaction processed normally.

    See Return Codes for possible values.
    STATUS Indicates the outcome of the command:
    "Success" = Command completed successfully
    "Error" = Error processing command by processor
    TAX Commission fee for card payment

    The purchase amount tag will be the total charge, including tax.
    The tax field breaks out the tax amount for Level II reporting purposes only.
    TERMINAL_ID TerminalID is never used on MercuryPay; always use TerminalName if requiring a terminal identifier
    TRAN_CODE The actual transactions run (as in Sale, Return, Balance, etc.) under these specific tenders.
    TRAN_TYPE Transaction Types include Credit, Debit, EBT, FSA, Gift/Prepaid, Loyalty, Admin, Canadian Debit /EMV and CheckAuth.
    VOUCHER_NUMBER
    ZIP ZIP Code.
    Response Fields [Show Info]

    ACQ_REF_DATA, ADDRESS, AMOUNT_AUTHORIZE, AMOUNT_BALANCE, AMOUNT_CASHBACK, AMOUNT_GRATUITY, AMOUNT_PRESCRIPTION, AMOUNT_PURCHASE, AUTH_CODE, AVS_DATA, AVS_RESPONSE, CAPTURE_STATUS, CARD_TYPE, CHARGE_TRANSACTION_FK, CMD_STATUS, CUSTOMER_CODE, CVV_RESULT, DSIX_RETURN_CODE, INVOICE_NO, MEMO, MERCHANT_ACCOUNT_CODE, MERCHANT_ID, NAME, OPERATOR_ID, PARTIAL_AUTH, PROCESS_DATA, RECORD_NO, REF_NO, RESPONSE_ORIGIN, RETAIL_TRANSACTION_CYCLE_FK, RETURN_CODE, STATUS, TAX, TERMINAL_ID, TEXT_RESPONSE, TRAN_CODE, TRAN_TYPE, USER_TRACE_DATA, VOUCHER_NUMBER, ZIP
    Name Description
    ACQ_REF_DATA This is a transaction routing and market data (allow up to 200 Alpha-numeric characters in length) and is required to be submitted with all PreAuthCapture request, with ReverseFSASale and used in conjunction with a VoidSale for Reversals.
    When submitted it is always included in the <TranInfo> data node.
    ADDRESS
    AMOUNT_AUTHORIZE Sum of authorization.
    AMOUNT_BALANCE Amount available on the card balance.
    AMOUNT_CASHBACK Amount of change after the purchase, issued in cash.
    AMOUNT_GRATUITY Amount of tips.
    AMOUNT_PRESCRIPTION
    AMOUNT_PURCHASE Amount of purchased goods
    AUTH_CODE Authorization Code returned by the processor.
    AVS_DATA This is referred to as Address Verification Service (AVS).

    Though not impacting the actual authorization approval, a better processing rate is achieved for some (retail, QSR,) merchants if address information is supplied when the card is not swiped.
    AVS_RESPONSE The Response Code to the Address Verification Service.
    CAPTURE_STATUS Will inform the POS if the transaction was "Captured" or "NotCaptured."
    CARD_TYPE Reflect the card type entered submitted ("VISA" "M/C" "AMEX" "DCLB" "DCVR" "JCB" "DEBIT" "FSA" "FSADebit" "OTHER")
    CHARGE_TRANSACTION_FK Reference to the entity that represents real-time financial transaction.
    CMD_STATUS Status, received if there are transactions with the same amount and on the same card.

    Indicates the outcome of the command:
    “Approved” = transaction approved by payment processor;
    “Declined” = transaction declined by payment processor;
    “Success” =command completed successfully;
    “Error” =error processing command.
    CUSTOMER_CODE The actual PO number, the merchant’s zip code, or the transaction invoice number, will sufficient to meet the Level II reporting requirements.
    CVV_RESULT A code that reflects the outcome of the CVV2/CVC2 check.


    DSIX_RETURN_CODE Server specific or DSIClientX specific TCP/IP six digit codes corresponding to a single or dynamic or variable message text.
    INVOICE_NO The locally generated always incrementing individual transaction number.
    MEMO Required field in all ActiveX and WebServices integrations
    MERCHANT_ACCOUNT_CODE Code of Merchant Account to which instance of this object is attributed to.
    Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
    The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
    MERCHANT_ID Merchant identifier, assigned by processor.

    The typical format for a Mercury Merchant ID combines an 11 digit numeric value, separated with an ‘=’ and a 6 digit alpha value as in: 884300XXXXX=ABCDEF.. Is returned without the "Nick Name" in the response.

    NAME Name of the provider account.

    Generated automatically by default. Comprised of a merchant account code followed by the type of provider profile for which it is defined.
    OPERATOR_ID Identifier of the operator carrying the transaction.
    PARTIAL_AUTH Use of the data element will “allow” a partial approval if the balance on the card is less than the purchase amount requested.
    The transaction will approve for the authorized balance amount available on the card and will not decline the transaction.
    PROCESS_DATA Transaction routing and market data (allow up to 200 Alpha-numeric characters in length) and is required to be submitted with all PreAuthCapture request, with ReverseFSASale and used in conjunction with a VoidSale for Reversals. When submitted it is always included in the <TranInfo> data node.
    RECORD_NO Mercury's proprietary tokenization method. This is the returned token reference.

    A RecordNo will be requested with two tags:
    1. the Frequency of the token requested ("OneTime" or "Recurring")
    2. either a request for token ("RecordNumberRequested") or the actual token returned in the original response.
    REF_NO A transaction reference value returned in the transaction response and indicates that an approved transaction has been “referenced” and is added to the current batch file.

    This field is used as a “filler value” on the initial request until an actual host value is returned indicating the transaction is now in the batch file; a true RefNo is returned on the response and logged at the host for all completed transactions.
    RESPONSE_ORIGIN
    RETAIL_TRANSACTION_CYCLE_FK Reference to the entity that represents a group of real-time transactions which must be settled together.
    RETURN_CODE Identifies the any error type.
    Value will be zero if transaction processed normally.

    See Return Codes for possible values.
    STATUS Indicates the outcome of the command:
    "Success" = Command completed successfully
    "Error" = Error processing command by processor
    TAX Commission fee for card payment

    The purchase amount tag will be the total charge, including tax.
    The tax field breaks out the tax amount for Level II reporting purposes only.
    TERMINAL_ID TerminalID is never used on MercuryPay; always use TerminalName if requiring a terminal identifier
    TEXT_RESPONSE Optional response message from the processor about the transaction status.
    TRAN_CODE The actual transactions run (as in Sale, Return, Balance, etc.) under these specific tenders.
    TRAN_TYPE Transaction Types include Credit, Debit, EBT, FSA, Gift/Prepaid, Loyalty, Admin, Canadian Debit /EMV and CheckAuth.
    USER_TRACE_DATA Сertain information associated with the authorization.
    VOUCHER_NUMBER
    ZIP ZIP Code.
    cards-realtime.migs.authorization.log   
    Added On:  12/17/14
    Level:  Trace
    Category:  cards-realtime.authorization
    Status:  Active
    Group:  processing
    File Name:  cards-realtime.migs.authorization.log
    Resource:  /cards-realtime.migs.authorization.log
    Legacy File Name:  
    Сontains information about the processor's incoming requests and outgoing responses (migs)
    Request Fields [Show Info]

    CHARGE_TRANSACTION_FK, MERCHANT_ACCOUNT_CODE, RETAIL_TRANSACTION_CYCLE_FK, VPC_ACCESS_CODE, VPC_TX_SOURCE, VPC_TX_SOURCE_SUB_TYPE, VPC3_DS_ENROLLED, VPC3_DS_STATUS
    Name Description
    CHARGE_TRANSACTION_FK Reference to the entity that represents real-time financial transaction.
    MERCHANT_ACCOUNT_CODE Code of Merchant Account to which instance of this object is attributed to.
    Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
    The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
    RETAIL_TRANSACTION_CYCLE_FK Reference to the entity that represents a group of real-time transactions which must be settled together.
    VPC_ACCESS_CODE Identifier that is used to authenticate you as the merchant while you are using the Virtual Payment Client. Generated and allocated to you by the Payment Server.
    VPC_TX_SOURCE Allows the merchant to specify the source of the transaction.

    This can only be used if the merchant has their privilege set to use this command, otherwise the transaction will be set to the merchant's default transaction source as defined by your Merchant Manager.
    VPC_TX_SOURCE_SUB_TYPE Allows the merchant to flag the subtype of transaction for the cardholder's order.
    VPC3_DS_ENROLLED The VERes.enrolled field. It will take values:
    • Y - Yes
    • N - No
    • U - Unavailable for Checking.
    VPC3_DS_STATUS Included only if payment authentication was used and a PARes was received by the MPI. It will take values:
    • Y - Yes
    • N - No
    • A - Attempted Authentication
    • U - Unavailable for Checking.
    Response Fields [Show Info]

    CHARGE_TRANSACTION_FK, MERCHANT_ACCOUNT_CODE, RETAIL_TRANSACTION_CYCLE_FK, VPC_ACCESS_CODE, VPC_ACQ_C_S_C_RESP_CODE, VPC_ACQ_RESPONSE_CODE, VPC_AMOUNT, VPC_AUTHORISED_AMOUNT, VPC_AUTHORIZE_ID, VPC_BATCH_NO, VPC_CAPTURED_AMOUNT, VPC_CARD, VPC_COMMAND, VPC_CSC_RESULT_CODE, VPC_MERCH_TXN_REF, VPC_MERCHANT, VPC_MESSAGE, VPC_ORDER_INFO, VPC_RECEIPT_NO, VPC_REFUNDED_AMOUNT, VPC_SHOP_TRANSACTION_NO, VPC_TICKET_NO, VPC_TRANSACTION_NO, VPC_TX_SOURCE, VPC_TX_SOURCE_SUB_TYPE, VPC_TXN_RESPONSE_CODE, VPC_VER_SECURITY_LEVEL, VPC_VER_STATUS, VPC3_DS_ENROLLED, VPC3_DS_STATUS
    Name Description
    CHARGE_TRANSACTION_FK Reference to the entity that represents real-time financial transaction.
    MERCHANT_ACCOUNT_CODE Code of Merchant Account to which instance of this object is attributed to.
    Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
    The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
    RETAIL_TRANSACTION_CYCLE_FK Reference to the entity that represents a group of real-time transactions which must be settled together.
    VPC_ACCESS_CODE Identifier that is used to authenticate you as the merchant while you are using the Virtual Payment Client. Generated and allocated to you by the Payment Server.
    VPC_ACQ_C_S_C_RESP_CODE The response code generated by the Issuing Bank in relation to the Card Security Code.
    VPC_ACQ_RESPONSE_CODE Acquirer's Response Code is generated by the financial institution to indicate the status of the transaction.
    VPC_AMOUNT The amount of the transaction in the smallest currency unit expressed as an integer.
    VPC_AUTHORISED_AMOUNT The total amount of the original authorisation transaction.
    VPC_AUTHORIZE_ID An identifying code issued by the bank to approve or deny the transaction.
    VPC_BATCH_NO A date supplied by the acquirer to indicate when this transaction will be settled.
    VPC_CAPTURED_AMOUNT The amount of the capture transaction in the smallest currency unit expressed as an integer.
    VPC_CARD A code issued by the Payment Server for the card type used by the cardholder in the transaction.
    VPC_COMMAND Indicates the transaction type. Must be equal to pay capture, refund, voidCapture, voidRefund, voidPurchase.
    VPC_CSC_RESULT_CODE The response code generated by the MiGS Payment Server in relation to the Card Security Code.

    Should be used for a more accurate representation of the CSC Response:
    M: Valid or matched CSC
    N: Code invalid or not matched
    P: CSC Not Processed
    S: Merchant indicates CSC not present on card
    U: Card issuer is not registered and/or certified
    VPC_MERCH_TXN_REF A unique value created by you to identify the DO. It is used to track the progress of a transaction and allows it to be identified on the Payment Server should a communication's failure occur and the DR is not received.
    VPC_MERCHANT The unique merchant ID assigned by Payment Processor.
    VPC_MESSAGE Indicates any errors the transaction may have encountered.
    VPC_ORDER_INFO Your own identifier used to identify the transaction with the cardholder. For example, a shopping cart number, an order number, or an invoice number.
    VPC_RECEIPT_NO Passed back to the cardholder for their records if the merchant application does not generate its own receipt number. Also known as the Reference Retrieval Number (RRN), which is a unique identifier.
    VPC_REFUNDED_AMOUNT The amount of the refund transaction in the smallest currency unit expressed as an integer.
    VPC_SHOP_TRANSACTION_NO The transaction reference number of the original authorisation or purchase transaction.
    VPC_TICKET_NO Allows to include a ticket number, such as an airline ticket number in the DO. It is stored on the Payment Server database for the transaction and is not returned in the DR.
    VPC_TRANSACTION_NO A unique number generated by the Payment Server for the transaction. It is stored in the Payment Server as a reference and used to perform actions such as a refund or capture.
    VPC_TX_SOURCE Allows the merchant to specify the source of the transaction.

    This can only be used if the merchant has their privilege set to use this command, otherwise the transaction will be set to the merchant's default transaction source as defined by your Merchant Manager.
    VPC_TX_SOURCE_SUB_TYPE Allows the merchant to flag the subtype of transaction for the cardholder's order.
    VPC_TXN_RESPONSE_CODE A response code that is generated by the Payment Server to indicate the status of the transaction.
    VPC_VER_SECURITY_LEVEL Is generated at the card issuer as a token to prove that the cardholder was enrolled and authenticated OK.

    Contains the security level to be used in the AUTH message.
    '05' - Fully Authenticated.
    '06' - Not authenticated, (cardholder not participating), liability shift.
    '07' - Not authenticated. Usually due to a system problem, for
    example the merchant password is invalid.
    VPC_VER_STATUS The status codes used by the Payment Server.
    VPC3_DS_ENROLLED The VERes.enrolled field. It will take values:
    • Y - Yes
    • N - No
    • U - Unavailable for Checking.
    VPC3_DS_STATUS Included only if payment authentication was used and a PARes was received by the MPI. It will take values:
    • Y - Yes
    • N - No
    • A - Attempted Authentication
    • U - Unavailable for Checking.
    cards-realtime.transfirst.authorization.log   
    Added On:  12/17/14
    Level:  Trace
    Category:  cards-realtime.authorization
    Status:  Active
    Group:  processing
    File Name:  cards-realtime.transfirst.authorization.log
    Resource:  $app-home/jboss-7.4.0/standalone/log/processing/cards-realtime.transfirst.authorization.log
    Legacy File Name:  
    Сontains information about the processor's incoming requests and outgoing responses (transfirst)
    Request Fields [Show Info]

    CHARGE_TRANSACTION_FK, RETAIL_TRANSACTION_CYCLE_FK
    Name Description
    CHARGE_TRANSACTION_FK Reference to the entity that represents real-time financial transaction.
    RETAIL_TRANSACTION_CYCLE_FK Reference to the entity that represents a group of real-time transactions which must be settled together.
    Response Fields [Show Info]

    ADDITIONAL_AMOUNT_ACCOUNT_TYPE, ADDITIONAL_AMOUNT_AMOUNT, ADDITIONAL_AMOUNT_AMOUNT_SIGN, ADDITIONAL_AMOUNT_AMOUNT_TYPE, ADDITIONAL_AMOUNT_CURRENCY_CODE, CARD_TYPE, CHARGE_TRANSACTION_FK, EXT_RSP_CODE, FAULT_ERROR_CODE, FAULT_ERROR_MESSAGE, MAP_CAID, RETAIL_TRANSACTION_CYCLE_FK, TRAN_DATA_AMT, TRAN_DATA_AUTH, TRAN_DATA_STAN
    Name Description
    ADDITIONAL_AMOUNT_ACCOUNT_TYPE
    ADDITIONAL_AMOUNT_AMOUNT
    ADDITIONAL_AMOUNT_AMOUNT_SIGN
    ADDITIONAL_AMOUNT_AMOUNT_TYPE
    ADDITIONAL_AMOUNT_CURRENCY_CODE
    CARD_TYPE Type of the credit card used for the transaction.
    CHARGE_TRANSACTION_FK Reference to the entity that represents real-time financial transaction.
    EXT_RSP_CODE
    FAULT_ERROR_CODE
    FAULT_ERROR_MESSAGE
    MAP_CAID
    RETAIL_TRANSACTION_CYCLE_FK Reference to the entity that represents a group of real-time transactions which must be settled together.
    TRAN_DATA_AMT
    TRAN_DATA_AUTH
    TRAN_DATA_STAN
    cards-realtime.worldpay.authorization.log   
    Added On:  12/17/14
    Level:  Trace
    Category:  cards-realtime.authorization
    Status:  Active
    Group:  processing
    File Name:  cards-realtime.worldpay.authorization.log
    Resource:  $app-home/jboss-7.4.0/standalone/log/processing/cards-realtime.worldpay.authorization.log
    Legacy File Name:  
    Сontains information about the processor's incoming requests and outgoing responses (worldpay)
    Request Fields [Show Info]

    BIT11, BIT12, BIT13, BIT18, BIT22, BIT3, BIT38, BIT4_APPROVED_AMOUNT, BIT42, BIT54, BIT59, BIT60_REASON_CODE, BIT62_DEBIT_EBT_NETWORK_RESPONSE_DATA, BIT7, CHARGE_TRANSACTION_FK, MERCHANT_ACCOUNT_CODE, MESSAGE_TYPE, RETAIL_TRANSACTION_CYCLE_FK
    Name Description
    BIT11 This number is echoed in response messages to assist in matching to requests. It is not expected that the same STAN (System Trace Audit Number) be used in any subsequent reversal advice.
    BIT12 The local transaction time. Formatted as HHMMSS where HH is 2-digit hour, MM - 2-digit minutes, and SS - 2-digit seconds.
    BIT13 The local transaction date.
    Formatted as YYMMDD, where YY is 2-digit year, MM - 2-digit month, and DD - 2-digit day.
    BIT18 Identifies the merchant's Standart Industrial Classification (SIC) code and associated market type.
    BIT22 Defines the conditions under which the card account number/PAN is entered and the terminal PIN capabilities. Field is mandatory for all entry modes.
    BIT3 Describes the type of transaction and the accounts it affects.
    BIT38 The authorization reference returned by the card issuer (or in case of delegated authorization, by the acquirer).
    BIT4_APPROVED_AMOUNT The full requested approved amount for authorization/capture.
    BIT42 Indicates which merchant originated the transaction.
    Assigned by WorldPay.
    BIT54 This field is included only for purchases with cash back account balances and reversals.
    BIT59 Free form. This information is returned in all approval responces.
    BIT60_REASON_CODE Identify the reason for a reversal or an advice.
    BIT62_DEBIT_EBT_NETWORK_RESPONSE_DATA This field only be returned for Debit and EBT transactions that are approved or denied by the network.
    BIT7 Represents the time and date that the transaction is transmitted from the payment switch, gateway, or POS device.
    CHARGE_TRANSACTION_FK Reference to the entity that represents real-time financial transaction.
    MERCHANT_ACCOUNT_CODE Code of Merchant Account to which instance of this object is attributed to.
    Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
    The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
    MESSAGE_TYPE The 4 digit numeric field classifying the high level function of the message.
    RETAIL_TRANSACTION_CYCLE_FK Reference to the entity that represents a group of real-time transactions which must be settled together.
    Response Fields [Show Info]

    , BIT11, BIT12, BIT122, BIT13, BIT15_SETTLEMENT_DATE, BIT18, BIT22, BIT3, BIT37, BIT38, BIT38_AUTHORIZATION_IDENTIFICATION_RESPONSE, BIT39_WORLD_PAY_RESPONSE_DATA, BIT4, BIT4_APPROVED_AMOUNT, BIT40, BIT42, BIT44_RESPONSE_DATA, BIT48_ADDRESS_VERIFICATION_RESULT, BIT48_AMERICAN_EXPRESS_RESPONSE_DATA, BIT48_AUTHENTICATION_VERIFICATION_VALUE_RESULT_CODE, BIT48_CARD_VERIFICATION_RESULT, BIT48_COMMERCIAL_CARD_RESPONSE, BIT48_CREDIT_RESPONSE_DATA, BIT48_MASTER_CARD_RESPONSE_DATA, BIT48_PREPAID_CARD_DATA, BIT48_VISA_RESPONSE_DATA, BIT54, BIT54_ADDITIONAL_AMOUNTS, BIT54_BALANCE, BIT54_CASHBACK_AMOUNT, BIT54_PARTIAL_APPROVED_AMOUNT, BIT54_TIP_AMOUNT, BIT59, BIT59_WORLD_RETRIEVAL_DATA, BIT60, BIT60_REASON_CODE, BIT61, BIT62_DEBIT_EBT_NETWORK_RESPONSE_DATA, BIT7, BIT90, BIT95, MERCHANT_ACCOUNT_CODE, MESSAGE_TYPE, RETAIL_TRANSACTION_CYCLE_FK
    Name Description
    The Summary Data Identifiers pertain to Purchase card, PINIess debit, and petroleum transactions.
    BIT11 This number is echoed in response messages to assist in matching to requests. It is not expected that the same STAN (System Trace Audit Number) be used in any subsequent reversal advice.
    BIT12 The local transaction time. Formatted as HHMMSS where HH is 2-digit hour, MM - 2-digit minutes, and SS - 2-digit seconds.
    BIT122 This field carries the Line Item details required for Petroleum, Level III Purchase/Commercial card qualification and used in conjunction with the Summary Data.
    BIT13 The local transaction date.
    Formatted as YYMMDD, where YY is 2-digit year, MM - 2-digit month, and DD - 2-digit day.
    BIT15_SETTLEMENT_DATE Required for all 0500 requests and returned in financial responces.

    MMDD.
    BIT18 Identifies the merchant's Standart Industrial Classification (SIC) code and associated market type.
    BIT22 Defines the conditions under which the card account number/PAN is entered and the terminal PIN capabilities. Field is mandatory for all entry modes.
    BIT3 Describes the type of transaction and the accounts it affects.
    BIT37 A unique transaction reference created at the POS device.
    BIT38 The authorization reference returned by the card issuer (or in case of delegated authorization, by the acquirer).
    BIT38_AUTHORIZATION_IDENTIFICATION_RESPONSE Authorization reference returned by the card issuer (or in case of delegated authorization, by the acquirer).
    BIT39_WORLD_PAY_RESPONSE_DATA Defines the disposition of a previous message or an action taken as a result of receipt of a previous message.
    BIT4 The full requested amount for authorization/capture.
    BIT4_APPROVED_AMOUNT The full requested approved amount for authorization/capture.
    BIT40 Defines and qualifies the transaction originated from the POS device.
    BIT42 Indicates which merchant originated the transaction.
    Assigned by WorldPay.
    BIT44_RESPONSE_DATA This field is used for WorldPay rejection reason and response literal.
    BIT48_ADDRESS_VERIFICATION_RESULT Contains the AVS verification response code which is returned in the Authorization Request Response message when the AVS functionality is used during transaction processing.
    BIT48_AMERICAN_EXPRESS_RESPONSE_DATA This subelement is for the financial network code and banknet reference number.
    BIT48_AUTHENTICATION_VERIFICATION_VALUE_RESULT_CODE MasterCard UCAF/AAV or Visa CAVV results, left justified and space filled.
    BIT48_CARD_VERIFICATION_RESULT Field return when CVV/CVC2/CVV2/CID is sent for a transaction.
    BIT48_COMMERCIAL_CARD_RESPONSE This subelement is sent in response to the type of purchase card transactions.
    BIT48_CREDIT_RESPONSE_DATA This subelement is sent in response to certain credit card transactions, including Visa and MasterCard.
    BIT48_MASTER_CARD_RESPONSE_DATA This subelement is for the financial network code and banknet reference number.
    BIT48_PREPAID_CARD_DATA This subelement is for the Prepaid Card ID and password.
    BIT48_VISA_RESPONSE_DATA This subelement is for reference number and validation code for approved transactions.
    BIT54 This field is included only for purchases with cash back account balances and reversals.
    BIT54_ADDITIONAL_AMOUNTS Included only for purchases with cash back account balances and reversals.
    BIT54_BALANCE Available balance.
    BIT54_CASHBACK_AMOUNT The subelement for the amount type.
    The requested/approved amount in the Request/Response messages.
    BIT54_PARTIAL_APPROVED_AMOUNT The subelement for the amount type.
    BIT54_TIP_AMOUNT The amount of tips.
    BIT59 Free form. This information is returned in all approval responces.
    BIT59_WORLD_RETRIEVAL_DATA Free Form. This element is returned in all approved transactions and approved financial responses.
    BIT60 This data element and its subelements identify the reason for a reversal or an advice.
    BIT60_REASON_CODE Identify the reason for a reversal or an advice.
    BIT61 Element, that is used as Point of Service (POS) Data in WorldPay.
    BIT62_DEBIT_EBT_NETWORK_RESPONSE_DATA This field only be returned for Debit and EBT transactions that are approved or denied by the network.
    BIT7 Represents the time and date that the transaction is transmitted from the payment switch, gateway, or POS device.
    BIT90 Required in reversal messages to assist acquirer and issuer in matching it to the original message.
    BIT95 Used for reversal advices only, and may be more or less than the original transaction amount.
    MERCHANT_ACCOUNT_CODE Code of Merchant Account to which instance of this object is attributed to.
    Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
    The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
    MESSAGE_TYPE The 4 digit numeric field classifying the high level function of the message.
    RETAIL_TRANSACTION_CYCLE_FK Reference to the entity that represents a group of real-time transactions which must be settled together.
    unicharge-api.log   
    Added On:  04/23/15
    Level:  Debug
    Category:  unibroker.util
    Status:  Active
    Group:  status
    File Name:  unicharge-api.log
    Resource:  $unibroker-home/jboss/logs/unicharge-api.log
    Legacy File Name:  unicharge-api.log
    Contains information about incoming requests and outgoing responses going through UniBroker.
    cards-realtime.credorax-epower.authorization.log   
    Added On:  10/30/15
    Level:  Trace
    Category:  cards-realtime.authorization
    Status:  Active
    Group:  processing
    File Name:  cards-realtime.credorax-epower.authorization.log
    Resource:  $app-home/jboss-7.4.0/standalone/log/processing/cards-realtime.credorax-epower.authorization.log
    Legacy File Name:  cards-realtime.credorax.epower.authorization
    Сontains information about the processor's incoming requests and outgoing responses (credorax-epower)
    Request Fields [Show Info]

    A1, A2, A4, A9, C1, C10, C2, C3, C5, C7, H9, I1, I2, I8, M, O
    Name Description
    A1 Reference number of the transaction. Corresponds to the referenceNumber field in the gateway.
    A2 Payment source of the transaction. Corresponds to the transactionIndustryType field in the gateway.
    A4 Amount of the transaction. Corresponds to the amount field in the gateway.

    Two exponents are implied. No decimal point is used (except for currencies with zero exponents).
    A9 Category of the transaction. Corresponds to the transactionCategory field in the gateway.
    C1 Name of the cardholder. Corresponds to the holderName field in the gateway.
    C10 Cardholder's billing address postal/zip code. Corresponds to the zipCode field in the gateway.
    C2 Cardholder's contact phone number (e.g., 999-999-9999). Corresponds to the phone field in the gateway.
    C3 Cardholder's email address. Corresponds to the email field in the gateway.
    C5 Street name of the cardholder's billing address. Corresponds to the street field in the gateway.
    C7 City name of cardholder's billing address. Corresponds to the city field in the gateway.
    H9 Value identifying the transaction in a submitter’s system. Corresponds to the transactionCode field in the gateway.
    I1 Description of the transaction. Corresponds to the memo field in the gateway.
    I2 Descriptor associated with the transaction. Corresponds to the descriptor field in the gateway.
    I8 3D Secure data.

    Consists of 3 different values, delimited by a colon sign:
    • ECI (сorresponds to the authenticationStatus field)
    • CAVV/AAV (сorresponds to the authenticationVerificationValue field)
    • XID (сorresponds to the authenticationCode field)
    M Merchant ID associated with the merchant account. Corresponds to the merchantAccountCode field in the gateway.
    O Operation code that is used to determine the requested service.

    Possible values:
    • 1 - Sale
    • 2 - Authorisation
    • 3 - Capture
    • 4 - Authorisation Void
    • 5 - Referral Credit
    • 6 - Independent Credit
    • 7 - Sale Void
    • 8 - Refund Void
    • 9 - Capture Void
    Response Fields [Show Info]

    T, Z1, Z13, Z14, Z15, Z16, Z17, Z2, Z3, Z4, Z5, Z6, Z9
    Name Description
    T Date of the transaction. Corresponds to the transactionDate field in the gateway.
    Z1 Response ID.
    Z13 Returns reference number of underlying provider. Corresponds to the providerReferenceNumber field in the gateway.
    Z14 CVV2 response code. Corresponds to the cvv2ResponseCode field in the gateway.

    • M - CVV2/CVC2 Match
    • N – CVV2/CVC2 No Match
    • P – Not processed
    • S – The CVV2 should be on the card but the merchant indicates it is not.
    • U – CVV2/CVC2 Unavailable – issuer does not support
    • Y – CVC1 Incorrect
    • - – Not processed
    Z15 Authorized amount. Corresponds to the amount field in the gateway.