Skip to main content
We capture these conditions during the authorization and transaction processing. Multiple transaction conditions can apply to a single transaction. These are listed under CONDITION_LIST and can be accessed through the Transaction data export files (CONDITION_LIST). Additionally, we aggregate multiple transaction conditions into a single Transaction Condition Code, which is available for each transaction through the Transaction API as transactionConditionCode.

Transaction data export file / CONDITION_LIST

This list defines the transaction conditions that are included in the Transaction data export files and can be found under the field named CONDITION_LIST. Within the CONDITION_LIST, each transaction includes multiple conditions that describe various aspects of the transaction, such as:
  • The method of cardholder authentication
  • The method used to capture the card credentials
  • The type of payment terminal used
  • Whether the cardholder was present during the transaction

Interpreting the Condition List

Below are some examples of Condition Lists and their interpretations.

Transaction API / transactionConditionCode

The Transaction Condition Code is available through the Transaction API. Unlike the CONDITION_LIST which lists multiple conditions, the transactionConditionCode is an aggregated value. Please note:
  • Many conditions are rare or only apply in specific cases, such as when the card only has a magnetic stripe.
  • Regulations vary across regions, and certain types may be considered non-applicable in Europe due to PSD2, but still permitted in other parts of the world.
  • Enfuce’s fraud rules automatically decline high-risk transaction types (e.g., chip terminals that fall back to mag stripe).