> ## Documentation Index > Fetch the complete documentation index at: https://docs.enfuce.com/llms.txt > Use this file to discover all available pages before exploring further. # Transaction conditions > Transaction conditions define the specific circumstances under which a card transaction occurred. For example, they describe whether the chip was read or if the transaction was contactless, how the cardholder was authenticated, and whether the transaction was e-commerce or card-present. 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](/guides/the-control-you-want/card-programme-insights/transaction-file-description) (CONDITION\_LIST). Additionally, we aggregate multiple transaction conditions into a single Transaction Condition Code, which is available for each transaction through the [Transaction API](/payment/api/transaction) as transactionConditionCode. ## Transaction data export file / CONDITION\_LIST This list defines the transaction conditions that are included in the [Transaction data export files](/guides/the-control-you-want/card-programme-insights/transaction-file-description) 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 | Name | Code | Description | | :-------------------------------------------------- | :----------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------- | | Terminal (automatic device) | `TERM` | Terminal (automatic device) | | No automatic devices is used in transaction | `NO_TERM` | No automatic devices is used in transaction | | Card present | `CARD` | Card present in transaction | | Cardholder present | `CARDHOLDER` | Cardholder present | | Merchant present | `MERCH` | Somebody from merchant site is present | | Merchant not present | `NO_MERCH` | Merchant not present | | ATM | `ATM` | Terminal Type: ATM | | Terminal Type: CAT1 (Automated Dispensing Machine) | `CAT1` | Terminal Type: CAT1 (Automated Dispensing Machine) | | Terminal Type: CAT2 (Self-Service Terminal) | `CAT2` | Terminal Type: CAT2 (Self-Service Terminal) | | Terminal Type: CAT3 (Limited Amount Terminal) | `CAT3` | Terminal Type: CAT3 (Limited Amount Terminal) | | Imprinter | `IMPRINTER` | Imprinter is used in transactions | | Cardholder not present | `NO_CARDHOLDER` | Cardholder not present | | Card not present | `NO_CARD` | Card not present | | Attended terminal | `POS` | Attended terminal | | Unattended terminal | `TERM_UNATT` | Unattended terminal | | Mail Order | `MAIL` | Mail Order | | Phone order | `PHONE` | Phone order | | Mail or phone order | `MOTO` | Mail or phone order | | Recurring transaction | `RECURRING` | Recurring transaction | | Chip information is read | `READ_CHIP` | Chip information is read | | Information is read from track | `READ_TRACK` | Information is read from track | | Key entry | `KEY_ENTRY` | Key entry card input mode | | Partial Grade | `PART_GRADE` | Chip transaction without chip data | | CVC2 is used | `CVC2` | CVC2 is used | | PIN based transaction | `PBT` | PIN is used for cardholder authentication | | Contactless transaction | `CONTACTLESS` | Contactless transaction | | PIN terminal | `TERM_PIN` | PIN terminal | | Cardholder is authenticated | `AUTHENTICATED` | Cardholder is authenticated | | Cardholder not authenticated | `NO_AUTH` | Cardholder not authenticated | | Cardholder Authentication Entity: authorizing agent | `AUTH_AGENT` | Cardholder authenticated by authorization agent | | Offline transaction | `OFFLINE` | Offline transaction | | Online transaction | `ONLINE` | Online transaction | | PIN online | `PBT_ONLINE` | PIN is verified in online | | PIN crypted | `PBT_CRYPTO` | PIN is crypted | | Chip card | `CARD_CHIP` | Chip card | | Chip card is defined by service code | `CHIP_SVC` | Chip card is defined by service code | | Card Data Input Capability: Chip | `TERM_CHIP` | Terminal can read chip data | | Card Data Input Capability: Magnetic Stripe data | `TERM_TRACK` | Terminal can read magnetic stripe data | | Card Data Input Capability: Key Entry | `TERM_KEY_ENTRY` | Terminal can process key entry | | Card Data Input Capability: Contactless Chip | `TERM_CHIP_CTLS` | Terminal can process chip contactless transaction | | Chip data is transmitted | `DATA_CHIP` | Chip data is read | | Track data is transmitted | `DATA_TRACK` | Track data is read | | Transaction with Cardholder certificate | `SECURE_CODE` | Cardholder was certified | | Secure Attempt | `SECURE_ATTEMPT` | Unsuccessful merchant attempt to certify cardholder | | Authenticated transaction | `TRANS_AUTH` | Transaction has been authenticated | | Electronic Network transaction | `ENET` | Electronic operation performed through Electronic Network (Internet, Mobile Network, etc.) | | Transaction without cardholder certification | `NO_SECURE` | Transaction without cardholder certification | | Transaction through secure line | `LINE_SECURE` | Transaction through secure line | | Transaction through insecure line | `LINE_INSECURE` | Transaction through insecure line | | Mobile/remote POS | `MPOS` | A mobile acceptance solution which operates over an open network. It is an extension of a traditional POS system. | | Token initiated/Token Entry | `TOKEN` | A numeric identifier (token) is used in place of a PAN to initiate a transaction. | | Stored card details | `STORED` | Card details are stored with the retailer and called upon as transactions are performed, e.g. hotel reservation, Internet wallets, RFID tokens (ISO) | | Check PIN in offline capability | `CPBL_OFFLINE_PIN` | In transaction processing it was possible to check PIN in offline | | Terminal Capability: Offline PIN | `CPBL_OFFLINE_PIN` | Terminal can process offline PIN | ## Interpreting the Condition List Below are some examples of Condition Lists and their interpretations. | Type | Condition list | Conditions | | :----------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ATM transaction | ATM, TERM\_UNATT, TERM, TERM\_CHIP, TERM\_TRACK, AUTHENTICATED, TRANS\_AUTH, PBT, CARD, CARDHOLDER, NO\_MERCH, CARD\_CHIP, READ\_CHIP, DATA\_CHIP | The transaction is an ATM transaction. The terminal is capable of reading both the chip and track data. The transaction is authenticated using the card, and it is PIN-based. Both the card and cardholder were present, while the merchant was not. The chip was read, and the chip data was transmitted. | | Contactless POS transaction | POS, TERM, TERM\_CHIP, TERM\_CHIP\_CTLS, CONTACTLESS, NO\_AUTH, CARD, CARDHOLDER, MERCH, CARD\_CHIP, CHIP\_SVC, CPBL\_OFFLINE\_PIN, READ\_CHIP, DATA\_TRACK, DATA\_CHIP | Contactless POS (Point of Sale) transaction. | | Automated fuel dispenser transaction | TERM\_UNATT, CAT1, TERM, TERM\_CHIP, AUTHENTICATED, AUTH\_CARD, TRANS\_AUTH, PBT, PBT\_OFFLINE, CARD, CARDHOLDER, NO\_MERCH, CARD\_CHIP, CHIP\_SVC, CPBL\_OFFLINE\_PIN, READ\_CHIP, DATA\_TRACK, DATA\_CHIP | The transaction was made using an unattended terminal where the cardholder was present, and the card used was a chip card. The transaction was authenticated, the terminal supports both offline PIN verification and EMV chip functionality, with the transaction being authorized and processed using the chip. | | E-commerce purchase | ENET, NO\_SECURE, LINE\_SECURE, NO\_CARD, NO\_CARDHOLDER, NO\_MERCH, KEY\_ENTRY | Online transaction where the cardholder was not physically present, the card details were manually entered. The transaction did not involve secure authentication protocols (NO\_SECURE), but it was processed over a secure network (LINE\_SECURE). | | Recurring Mail/Phone order | POS, TERM, MOTO, RECURRING, NO\_AUTH, NO\_CARD, NO\_CARDHOLDER, MERCH, STORED | A recurring transaction, done remotely, where neither the card nor the cardholder is physically present, and there was no authentication involved. The merchant used stored card data. | ## Transaction API / transactionConditionCode The Transaction Condition Code is available through the [Transaction API](/payment/api/transaction). 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). | Type | Code | Description | | :------------------------------------------ | :--- | :---------------------------------------------------------------------------------------------------------- | | Cash withdrawal at ATM | ATM | mag stripe card, cardholder authentication with PIN | | | ATMC | chip card, cardholder authentication with PIN | | | ATMF | chip card, terminal has read mag stripe, cardholder authentication with PIN | | | ATMK | digital wallet (contactless), cardholder authentication with PIN | | | ATML | contactless card, cardholder authentication with PIN | | E-com (insecure channel) | NEU | ecom transaction with PAN & exp, no 3DS | | | NEU2 | ecom transaction with PAN & exp & CVV, no 3DS | | | TEU | e-com transaction with token | | E-com (secure channel (e.g. https)) | NEV | no CVV, no 3DS | | | NEV2 | no 3DS | | | PES | 3DS attempted | | | PET | 3DS authenticated | | | SEU | stored credentials | | | TES | with token, 3DS attempted | | | TET | with token, 3DS authenticated | | | TEV | with token, no 3DS | | | TEV2 | token and CVV, no 3DS | | No terminal | NMN | no terminal, card credentials (PAN & exp) manually captured, cardholder authenticated with signature. | | | NMN2 | no terminal, card credentials (PAN & exp & CVV) manually captured, cardholder authenticated with signature. | | Mail/phone order | NMO | mail/phone order with PAN & exp | | | NMO2 | mail/phone order with PAN & exp & CVV | | Recurring | NMR | recurring order with PAN & exp & CVV | | | NMR2 | recurring order with PAN & exp | | Merchant initiated transction (not e-com) | NMS | merchant initiated transaction with stored card credentials | | Unknown | NNK | merchant has used condition combinations that are unexpected and can’t be categorised | | Purchase at vending machine | PO1 | mag stripe card, cardholder authentication with PIN | | | PO1C | chip card, cardholder authentication with PIN | | | PO1F | chip card, terminal has read mag stripe, cardholder authentication with PIN | | | PO1G | chip card, chip only partially authenticated, cardholder authentication with PIN | | | PO1K | digital wallet (contactless), cardholder authentication with PIN | | | PO1L | chip contactless card, cardholder authentication with PIN | | Purchase at physical store | POE | mag stripe card, cardholder authentication with signature | | | POEC | chip card, cardholder authentication with signature | | | POEF | chip card, terminal has read mag stripe, cardholder authentication with signature | | | POEG | chip card, chip only partially authenticated, cardholder authentication with signature | | | POEK | digital wallet | | | POEL | chip contactless, no cardholder authentication | | | POEP | mag stripe card, mag stripe only partially authenticated, cardholder authentication with signature | | | POES | digital wallet, cardholder authentication with signature (mag stripe card) | | | POM | card credentials (PAN\&exp) keyed to terminal, cardholder authentication with signature | | | POM2 | card credentials (PAN\&exp\&CVV) keyed to terminal, cardholder authentication with signature | | | POS | mag stripe card, cardholder authentication with PIN | | | POSC | chip card, cardholder authentication with PIN | | | POSF | chip card, terminal has read mag stripe, cardholder authentication with PIN | | | POSG | chip card, chip only partially authenticated, cardholder authentication with PIN | | | POSK | digital wallet (contactless), cardholder authentication with PIN | | | POSL | chip contactless, cardholder authentication with PIN | | | POSS | contactless mag stripe, cardholder authentication with PIN | | Purchase at self-service terminal | POT | mag stripe card, cardholder not authenticated | | | POTC | chip card, cardholder not authenticated | | | POTF | chip card, terminal has read mag stripe, cardholder not authenticated | | | POTG | chip card, chip only partially authenticated, cardholder not authenticated | | | POTK | digital wallet (contactless) | | | POTL | chip contactless, cardholder not authenticated | | Purchase at self-service terminal (offline) | POU | mag stripe card, cardholder not authenticated | | | POUC | chip card, cardholder not authenticated | | | POUF | chip card, terminal has read mag stripe, cardholder not authenticated | | | POUG | chip card, chip only partially authenticated, cardholder not authenticated | | | POUK | digital wallet | | | POUL | chip contactless, cardholder not authenticated | | Purchase at in-flight terminal (offline) | POV | mag stripe card, cardholder not authenticated | | | POVC | chip card, cardholder not authenticated |