Skip to content

Transaction file description

Transaction

Field name Field type Mandatory Details
REPORTING_DATE DATE DATE YYYY-MM-DD
The date when transactions have been posted. Data has been extracted end of day of this date. Files are provided the next day.
INSTITUTION_ID NUMBER(6,0) Yes The institution ID setup at Enfuce.
ADD_INFO VARCHAR2(3900) No Additional field which contains miscellaneous data of transaction. Data is marked with tags.
AUTH_CODE VARCHAR2(32) No The authorisation code of the transaction. The authorisation code is usually 6 digits and is assigned either by Enfuce or Payment scheme in case of stand-in processing. The authorisation code is not unique, the same authorisation code can appear multiple times. Note that it is also possible that not all transactions are authorised, in which case there is no authorisation code.
BANKING_DATE DATE DATE YYYY-MM-DD.
The system’s banking date when the transaction has been processed.
CARD_SEQUENCE_NUMBER VARCHAR2(32) No The card sequence with which the transaction has been performed.
CORRECTED_ID NUMBER(18,0) No Updated database ID for the transaction after correction.
CORRECTION_TYPE VARCHAR2(32) No If the transaction has been corrected this field states the type of correction that has been made. The possible values are: J (= Adjustment), R (=Reversal), * (=Repost)
DIRECTION VARCHAR2(6) No Describes if the transaction is debiting or crediting. Possible values: Credit, Debit.
ID NUMBER(18,0) Yes Enfuce generated database ID for the transaction. The ID is unique among transactions and authorisations.
TRANS_AMOUNT NUMBER(28,10)) No The amount of the transaction in the currency the merchant has charged it in. E.g. if a customer makes a purchase in USD and the cards currency is EUR. Then the TRANSACTION_AMOUNT will be in USD and SETTLEMENT_AMOUNT in EUR. If the purchase is done in the same currency as the cards currency the TRANSACTION_AMOUNT=SETTLEMENT _AMOUNT.
TRANS_CURRENCY VARCHAR2(3) No The currency in which the transaction was made.
TRANS_DATE DATE No The local date (and time) when the transaction was made. Local date/time= the date/time in the time zone in which the payment terminal is: YYYY-MM-DDThh:mm:ss
For MasterCard transactions, the date and time stamp both are provIDed as those both are available in a clearing file.
For Visa, only the date is available as Visa only includes the date in clearing files.
TRANS_ARN VARCHAR2(32) No Transaction IDentification number, generated by the acquirer according to payment scheme rules (Acquirer Reference Number).
TRANS_CITY VARCHAR2(32) No Merchant city
TRANS_COUNTRY_CODE VARCHAR2(32) No Merchant country
TRANS_DETAILS VARCHAR2(255) No Merchant name
TRANS_IRN VARCHAR2(32) No Transaction IDentification number, provIDed to the payment scheme by the issuer (Issuer Reference Number
TRANS_MCC VARCHAR2(32) No The merchant category code of the transaction (ISO 18245).
TRANS_REASON VARCHAR2(3900) No If transaction has been disputed, this fields may contain additional information about the dispute.
TRANS_RESPONSE_CODE VARCHAR2(32) No Additional information related to the posting. In combination with the posting status it indicates in both successful and non-successful cases if any additional findings were done during the posting.
Note that the response code is just additional information on top of the posting status. Regardless of the response code, the posting status determines if the transaction is successfully posted or not. Examples of response codes:
– “0” = Successfully posted
– “13” = Difference between authorisation and transaction amount
– “101” = Unauthorised transaction
TRANS_RRN VARCHAR2(32) No Transaction IDentifier, generated according to payment scheme rules (Retrieval Reference Number)
TRANS_SRN VARCHAR2(255) No Registration number, assigned by the merchant or acquirer (Source Registration Number).
MERCHANT VARCHAR2(32) No ID number of the merchant (as informed in the incoming clearing file)
PAYEE_COUNTRY_CODE VARCHAR2(32) No In person to person payments, the registered country of the payee.
PAYER_COUNTRY_CODE VARCHAR2(32) No In person to person payments, the registered country of the payer.
POSTING_STATUS VARCHAR2(32) No Indicates if Enfuce has successfully posted the transaction during transaction processing to a card or account. Possible values:
“Posted”
The posting status will be “posted” when transaction has been successfully posted to card or account. This is the posting status of all successful transactions that are still valID.
“InActive”
The posting status of the original transaction will be updated to “InActive” if a reversal transaction linked to it is successfully posted.
“Closed”
If a reversal is posted the posting status “Closed” of the reversal transaction will indicate that it is successfully posted, i.e. the transaction has been successfully reversed.
“Decline Service”
The transaction could not be posted to card or account. One example is that the transaction type is not permitted to card or account.
“Decline”
The transaction could not be posted to card or account. One example is that the card or account status does not allow posting.Mapping to Transaction API postingStatus:”POSTED” = “Posted”
“POSTED_DISPUTE” = “Decline Service”
“CLOSED” = “Closed”
“PENDING” = N/A in batch file (transaction is only pending for a short period of time while being processed)
“REJECTED” = “Decline”
PREVIOUS_ID NUMBER(18,0) No Database ID linking the transaction to a previous authorisation or transaction.
SETTLEMENT_DATE DATE No YYYY-MM-DD. The date the transaction was processed in Enfuce system.
SETTL_AMOUNT NUMBER(28,10) No Payment scheme settlement amount. Settlement amount is the gross amount that needs to be settled to payment scheme. The settlement amount does not include any transaction based fees calculated by Enfuce e.g. mark-up or ATM fee.
SETTL_CURRENCY VARCHAR2(3) No Payment scheme settlement currency
LOCAL_AMOUNT NUMBER(28,10) No The total amount charged from the cardholder. This amount includes the settlement amount and potential additional transaction based fees (e.g. mark-up).
SOURCE_CARD_REFERENCE_NUMBER VARCHAR2(255) No Foreign key to transaction source card.
SOURCE_CARD_ID NUMBER(18,0) No Foreign Enfuce generated key to transaction source card.
SOURCE_CONTRACT_NUMBER VARCHAR2(255) No Foreign key to transaction source account.
SOURCE_ACCOUNT_ID NUMBER(18,0) No Foreign Enfuce generated key to transaction source account.
SOURCE_CATEGORY VARCHAR2(32) No Possible values: Accountant, Contract, Merchant
SOURCE_CHANNEL VARCHAR2(32) No Possible values:
“VISA”
Used for settlement records
“Our Visa Cards”
Used for card transactions received in clearing files
“Mastercard (IPM)”
Used for settlement records
“Our MC Cards”
Used for card transactions received in clearing files
“RBS”
Used for incoming payments
“Internal”
Used for transactions posted via API
“Affiliated”
Used for closed loop transactions
SOURCE_COUNTRY_CODE VARCHAR2(32) No Country code of where the transaction has been performed.
SOURCE_MEMBER_IDN VARCHAR2(32) No Acquirer ID (DE 32 in ISO 8583)
SOURCE_MESSAGE_CODE VARCHAR2(32) No
SOURCE_NUMBER VARCHAR2(255) No Merchant terminal ID
SOURCE_ON_US_FLAG VARCHAR2(32) No If the transaction source is a closed loop (=on us) or not.
TARGET_CARD_REFERENCE_NUMBER VARCHAR2(255) No Foreign key to transaction target card.
TARGET_CARD_ID NUMBER(18,0) No A card ID of a card to which a transaction has been posted to.
TARGET_CONTRACT_NUMBER VARCHAR2(255 No Foreign key to transaction target account.
TARGET_ACCOUNT_ID NUMBER(18,0) No An account ID to which a transaction has been posted to.
TARGET_CATEGORY VARCHAR2(32) No Possible values: Accountant, Contract, Merchant
TARGET_CHANNEL VARCHAR2(32) No Possible values:
“VISA”
Used for settlement records
“Our Visa Cards”
Used for card transactions received in clearing files
“Mastercard (IPM)”
Used for settlement records
“Our MC Cards”
Used for card transactions received in clearing files
“RBS”
Used for incoming payments
“Internal”
Used for transactions posted via API
“Affiliated”
Used for closed loop transactions
TARGET_COUNTRY_CODE VARCHAR2(32) No Country code of where the transaction has been posted to.
TARGET_MEMBER_IDN VARCHAR2(32) No Transaction target.
TARGET_MESSAGE_CODE VARCHAR2(32) No
TARGET_NUMBER VARCHAR2(255) No
TARGET_ON_US_FLAG VARCHAR2(32) No If the transaction target is a closed loop (=on us) or not.
CONDITION_LIST VARCHAR2(3900) No See possible values in the separate transaction condition list below.
TRANS_TYPE_NAME VARCHAR2(255) No Configured name of the transaction type.
TRANS_TYPE_CODE VARCHAR2(32) No Code of the transaction type.
TRANS_TYPE_SERVICE_CLASS VARCHAR2(32) No Service class of the transaction type.
POSTING_DATE DATE YYYY-MM-DD. On which Enfuce has processed the transaction. In practice, a date when Visa/MC has sent a clearing file including the transaction to Enfuce and Enfuce has imported the respective clearing file to Enfuce system.
FEE_1_CODE VARCHAR2(32) No Transaction fee 1 type code
FEE_1_AMOUNT NUMBER(28,10) No Transaction fee 1 amount
FEE_1_CURRENCY VARCHAR2(3) No Transaction fee 1 currency
FEE_2_CODE VARCHAR2(32) No Transaction fee 2 type code
FEE_2_AMOUNT NUMBER(28,10) No Transaction fee 2 amount
FEE_2_CURRENCY VARCHAR2(3) No Transaction fee 2 currency
FEE_3_CODE VARCHAR2(32) No Transaction fee 3 type code
FEE_3_AMOUNT NUMBER(28,10) No Transaction fee 3 amount
FEE_3_CURRENCY VARCHAR2(3) No Transaction fee 3 currency
FEE_4_CODE VARCHAR2(32) No Transaction fee 4 type code
FEE_4_AMOUNT NUMBER(28,10) No Transaction fee 4 amount
FEE_4_CURRENCY VARCHAR2(3) No Transaction fee 4 currency
FEE_5_CODE VARCHAR2(32) No Transaction fee 5 type code
FEE_5_AMOUNT NUMBER(28,10) No Transaction fee 5 amount
FEE_5_CURRENCY VARCHAR2(3) No Transaction fee 5 currency
MAIN_ID NUMBER(18,0) Related main transaction ID
SOURCE_MEMBER_COUNTRY VARCHAR2(3) No Acquirer country code. The country is informed according to ISO 3166 Alpha-3 standard.
COMMENT_TEXT VARCHAR(255) No Free “text” data submitted during Transaction API transaction posting

Transaction conditions

This list defines what are the transaction conditions which are added to Transaction files and can be found from field called “CONDITION_LIST”.
Example of an ATM transaction: ATM, TERM_UNATT, TERM, TERM_CHIP, TERM_TRACK, AUTHENTICATED, TRANS_AUTH, PBT, CARD, CARDHOLDER, NO_MERCH, CARD_CHIP, READ_CHIP, DATA_CHIP.

→ This can be understood by using the list below that transaction is ATM transaction and terminal has been capable of reading chip and track. Transaction is authenticated by using card and transaction is PIN based transaction. Card and cardholder has been present. Merchant has not been present, chip has been read and chip data has been transmitted.
Example of a contactless 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.

→ POS (Point of Sale) transaction which is done contactless
Example where card has been used in a automated fuel dispenser: 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.

Example of the ecomm purchase: ENET, NO_SECURE, LINE_SECURE, NO_CARD, NO_CARDHOLDER, NO_MERCH, KEY_ENTRY.
Example of the Mail/Phone order/Reccuring transaction:
POS, TERM, MOTO, RECURRING, NO_AUTH, NO_CARD, NO_CARDHOLDER, MERCH, STORED.

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 presents
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)
Terminal Type: CAT4 (in-flight commerce terminal) CAT4 Terminal Type: CAT4 (in-flight commerce terminal)
Terminal Type: CAT7 (transponders) CAT7 Terminal Type: CAT7 (transponders)
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
Ecommerce transaction ECOMMERCE Ecommerce transaction
Ecommerce no SSL ECOM_NO_SSL Ecommerce no SSL
Ecommerce SSL ECOM_SSL Ecommerce SSL
Ecommerce with cardholder certificate ECOM_CERT Ecommerce with cardholder certificate
Ecommerce with unsuccessful merchant attempt to certify cardholder ECOM_ATTEMPT Ecommerce with unsuccessful merchant attempt to certify cardholder
Ecommerce without cardholder certification NO_ECOMM_CERT Ecommerce without cardholder certification
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
Partial track PART_TRACK Partial track
CVC2 is used CVC2 CVC2 is used
PIN based transaction PBT PIN is used for cardholder authentication
Signature based transaction SBT Signature based transaction
Business Addendum exists BUSN_ADDENDUM Business Addendum exists
Contactless transaction CONTACTLESS Contactless transaction
Manual Verification of signature SBT_MAN Manual Verification of signature
Electronic Verification of signature Manual Verification of signature Electronic Verification of signature
Cardholder is authenticated AUTHENTICATED Cardholder is authenticated
Cardholder not authenticated NO_AUTH Cardholder not authenticated
Cardholder Authentication Entity: card AUTH_CARD cardholder authenticated by card
Cardholder Authentication Entity: merchant AUTH_MERCH Cardholder authenticated by merchant
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 offline PBT_OFFLINE PIN is verified in offline (by card)
PIN crypted PBT_CRYPTO PIN is crypted
PIN clear PBT_CLEAR PIN is sent in clear (not crypted)
Read chip is failed FAIL_CHIP Read chip is failed
Read track is failed FAIL_TRACK Read track is failed
Chip card CARD_CHIP Chip card
Chip card is defined by service code CHIP_SVC Chip card is defined by service code
Magnetic stripe card CARD_TRACK Magnetic stripe card
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: OCR TERM_OCR Terminal can process OCR transaction. Optical Character Recognition or OCR is a technology that recognizes text within an image.
Card Data Input Capability: BAR TERM_BAR Terminal can process BAR transaction
Card Data Input Capability: Contactless Chip TERM_CHIP_CTLS Terminal can process chip contactless transaction
Card Data Input Capability: Contactless Magnetic Stripe TERM_TRACK_CTLS Terminal can process contactless track transaction
Chip data is transmitted DATA_CHIP Chip data is read
Track data is transmitted DATA_TRACK Track data is read
Late transaction LATE Late transaction (in comparing with standard time frame for such transaction) (old-fashioned)
Transaction with Cardholder certificate SECURE_CODE Cardholder was certified
Secure Attempt SECURE_ATTEMPT Unsuccessful merchant attempt to certify cardholder
Short Message Service Protocol MBSMS Operation performed using Short Message Service protocol
Web-Browser WEB Operation performed using Web-Browser
PIN2 based transaction PIN2 Transaction authenticated using PIN2
Installment transaction INSTALLMENT Installment transaction is a method of selling on credit, through which a seller of goods receives part of the purchase price at the time the goods are delivered and the balance thereof by installment payments over a fixed period.
Cardholder was authenticated by merchant SECURE_BY_MERCH Cardholder was authenticated by merchant (usually ecommerce)
Authenticated using Password List Card MNET Transaction authenticated using PWL_CARD
Authenticated using OTP_LIST OTP_LIST Transaction authenticated using One-Time Password from List
Authenticated using OTP_SMS OTP_SMS Transaction authenticated using One-Time Password delivered by SMS
Authenticated using OTP_AID OTP_AID Transaction authenticated using One-Time Password generated by AID token
Authenticated using OTP_HMAC OTP_HMAC Transaction authenticated using One-Time Password generated by OATH token
Authenticated using OTP_CAP OTP_CAP Transaction authenticated using One-Time Password generated by CAP calculator
Authenticated using OTP_DPA OTP_DPA Transaction authenticated using One-Time Password generated by DPA calculator
Authenticated using OTP_MMA OTP_MMA Transaction authenticated using One-Time Password generated by MMA calculator
Authenticated using static password PASSWORD Transaction authenticated using static password
Authenticated transaction TRANS_AUTH Transaction has been authenticated
Cardholder Authentication Entity: CAD AUTH_CAD Cardholder authenticated by Card acceptance device
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
TeleBank Application TBAPPL Operation performed using TeleBank Application
Cardholder Authentication method: bio-verification BVF_AUTH Transaction has been authenticated by a bio-verification method
Authenticated using finger print BVF_FINGER_PRINT Transaction has been authenticated by the finger print bio-verification method
Key Map Service is used KEY_MAP External system performed mapping some (for example, device) account number to the cardholder’s funding account number
Mobile/remote POS MPOS A mobile acceptance solution which operates over an open network. It is an extension of a traditional POS system.
Read remote chip REMOTE_CHIP PAN entry via Remote Chip
PIN was not entered NO_PIN PIN entry required, PIN pad present, but PIN was not entered
Wallet Service ProvIDer WALLET Operation performed using Wallet Service ProvIDer
Issuer Risk Monitoring RM_ISS Authenticated transaction using issuer’s Risk Based
Decisioning Merchant Risk Monitoring RM_MERCH
Digital Secure Remote Payment Transaction DSRP Digital Secure Remote Payment Transaction
Token initiated TOKEN A numeric IDentifier (token) is used in place of a PAN to initiate a transaction.
Token Entry TOKEN A numeric IDentifier (token) is used in place of a PAN to initiate a transaction.
Deferred transaction DEFERRED When the financial presentment takes place after an agrees period of time has elapsed (ISO)
Stored card details STOREDm Card details are stored with the retailer and called upon as transactions are performed, e.g. hotel reservation, Internet wallets, RFID tokens (ISO)
Signature by CVM Results SBT_EMV Signature verification indicated by EMV field 9F34 (CVM Results)
Check PIN in offline capability CPBL_OFFLINE_PIN In transaction processing it was possible to check PIN in offline
In-App Authentication AUTH_APPL Cardholder authenticated by an Application
Terminal Capability: Offline PIN TERM_OFFLINE_PIN Terminal can process offline PIN
Terminal Capability: Offline PIN CPBL_OFFLINE_PIN Terminal can process offline PIN
Information is read from QR code READ_QR Information about consumer or merchant is read from QR code
Consumer QR code QR_CONS QR code contains information about consumer (account number, etc.)
Merchant QR code QR_MERCH QR code contains information about merchant (merchant name, merchant ID, account number, etc.)
information is read from track READ_TRACK Information is read from track