Card programme insights
Transaction file description
Card programme insights
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 | VARCHAR2(32) | 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. |
| 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 |