Transaction details fields
Last updated: 21-Feb-2023
Below are definitions for all of the transaction detail fields available in Verifone Central. Each field is listed also with their availability as filters and search criteria.
| Field Name | Definition (region specific) |
List (= basic CSV) |
Search | Filters |
CSV full report |
Details |
|---|---|---|---|---|---|---|
| Account Number | Transaction detail displayed only for the Check instrument type | No | No | No | N/A | Yes |
| Account Type | Type of the account used for the payment (credit/debit) | No | No | Yes | account_type | Yes |
| Acquirer | Type indicator to identify the acquirer of the payment | No | No | No | N/A | Yes |
| Acquirer Merchant ID | Identifier assigned to the Merchant and known by the Acquirer (it is not supported by all the acquirers) | No | Yes | No | acquirer_merchant_id | Yes |
| Acquirer Response Code | Acquired Response Code | No | No | No | acquirer_response_code | Yes |
| Actions | The available actions per transaction | No | No | No | header.source.acquirer | Yes |
| ARN | Acquirer Reference Number is the "transaction ID " set by the Acquirer. It is usually used when communicating to banks and schemes. | No | No | No | arn | Yes |
| Authentication mode | Authentication method | No | No | No | N/A | Yes |
| Authentication value | Unique value assigned by the Issuer to distinguish the 3ds transaction. Is it similar to the Authorisation code, but for 3DS | No | No | No | N/A | Yes |
| Authorisation Code | Value assigned by the Acquirer for specific authorized transactions | No | No | No | N/A | Yes |
| AVS Outcome | Text that informs of the outcome of a requested shopper address validation. | No | No | No | N/A | Yes |
| Batch Created | Date of the Batch creation | No | No | No | N/A | Yes |
| Batch Number | Batch or settlement date as assigned by the Payment Acceptor (in most cases Verifone) for the POI or merchant. This is not the same as the batch that can be assigned by the acquirer. | No | Yes | No | Yes | Yes |
| Bin Number* |
The Bank Identification Number contains the first 6-8 digits of the Primary Account Number (PAN). The BIN (or a BIN range) is assigned to a card issuer. Note: *8-digit BIN is available only in Israel (ABS) |
No | Yes | No | card.bin | No |
| Cardholder choice | Brand choice | No | No | No | N/A | Yes |
| Card Number | Primary Account Number or Card Number. Displayed in an encrypted format | No | Yes | No | masked_card_number | Yes |
| Card token | Identifier associated with the payment card that allow to search data related to that payment card in a safe way | No | Yes | No | N/A | Yes |
| Cashier Name | Name of the Cashier who created the transaction (not used for all the providers) | No | No | No | cashier_name | Yes |
| Challenge indicator | Did the issuer request challenge the cardholder? | No | No | No | N/A | Yes |
| Channel | Sales channel of the transaction (ecom, mail, POS) | No | No | Yes | N/A | Yes |
| Check Number | Transaction detail displayed only for the Check instrument type | No | No | No | N/A | Yes |
| Created | Date of transaction | Yes | No | Yes | created_at_date | Yes |
| Cross border fee | Cross border fee., a fee taken for processing cross boarder (when a payment card of a cardholder and a merchant are located in different countries) transactions. | No | No | No | N/A | Yes |
| Currency | Currency of the transaction | No | No | Yes | Curr.amount currency code | No |
| Current Amount | Current amount of the transaction (after some actions) | Yes | No | No | Curr.amount | Yes |
| Customer ID | Identifier as a string for the Customer. This is for the Verifone defined customer ID e.g from the customer service. | No | No | No | customer._id | Yes |
| Documents | Available documents - receipts | No | No | No | N/A | Yes |
| Enrolled | Card enrolled for 3DS | No | No | No | N/A | Yes |
| Shopper email | No | No | No | customer.email_address | Yes | |
| Expires (card) | Expiry date of the card | No | No | No | N/A | Yes |
| External Merchant ID | Merchant ID in the client's system (used by Woodforrest) | No | Yes | No | N/A | Yes |
| Fraud score | The fraud score returned by the Fraud Protection Service | No | No | No | fraud_score | Yes |
| Fraud insights | The list of insights for the score | No | No | No | fraud_reason_insights | Yes |
| Instalment payment index |
Field is applicable for Israel only. Possible values are:
|
No | No | No | issuer_instalment_payment_index | No |
| Invoice number | Identifier of the invoice created for a transaction | No | No | No | N/A | Yes |
| IP Address | IP Address v4 where the event originated. | No | No | No | N/A | Yes |
| Merchant ID | Identifier assigned to the Merchant and known by the Merchant or Client, whether this is an external Client, Client System or Gateway, i.e., this field is for the MID used internally by VF | Yes | Yes | Yes | merchant_id | Yes |
|
Merchant reference |
Merchant reference* is a value (up to 50 characters) that is assigned by the merchant in each transaction for their own identification (*In CSV report use the merchant_reference column, the "Merchant Reference" column is deprecated) |
No | Yes | No | merchant_reference | Yes |
| Name | Shopper full name | No | No | No | N/A | Yes |
| Organisation | Organisation name | Yes | No | No | organisation.name | Yes |
| Organisation ID | Organisation ID | No | No | Yes | Entity | Yes |
| Orig. Amount | Initial amount of the transaction | Yes | No | No | Orig.amount | No |
| Processor | Type indicator to identify the processor of the payment | No | No | No | sourcePIM | Yes |
| Processor STAN | Number that is assigned by a counter in the gateway (or the terminal) to identify the uniqueness against processor. | No | Yes | No | stan | Yes |
| Product | Payment method used to place the order | Yes | No | Yes | Product | Yes |
| Provider reference | Type indicator for the contract that is being processed | No | No | No | N/A | Yes |
| Provider transaction ID | Transaction ID generated by the provider | No | Yes | No | processor_transaction_id | Yes |
| Merchant ID | Identifier assigned to the Merchant and known by the Merchant or Client, whether this is an external Client, Client System or Gateway, i.e., this field is for the MID used internally by VF | Yes | Yes | Yes | merchant_id | Yes |
| Reason code |
The reason code for the transaction status |
No | No | No | fraud_reason_code | Yes |
| Reference | Unique ID of the transaction | Yes | Yes | No | Reference | Yes |
| Response | Response received from the acquire | No | No | No | N/A | Yes |
| Response Code | Description of the response received from the acquirer | No | No | No | N/A | Yes |
| Response description | Code of the response received from the acquire | No | No | No | response_message | Yes |
| RRN | Retrieval Reference Number may be used as reference against Acquirers | No | Yes | No | processorRRn | Yes |
| Scheme transaction ID | Transaction ID assigned by the schemes for 3DS1.0.2 transactions | No | No | No | N/A | Yes |
| Settlement amount | Amount settled | No | No | No | N/A | Yes |
| Settlement Batch ID | Batch ID assigned to a settlement batch | No | Yes | No | settlement_id | Yes |
| Settlement date | Settlement date | No | No | No | settlement_date | Yes |
| Shipping address | Shopper shipping address | No | No | No | shipping_information.address | Yes |
| Site Reference | An identifier for the Site that is unique to the Merchant Organisation. This will be used to locate this instance of a Site. | No | No | No | site_reference_id | Yes |
| Status | Status of the transaction | Yes | No | Yes | Status | Yes |
| Status (3DS) | Status of the 3DS check (e.g., successful, failed, etc.) | No | No | No | N/A | Yes |
| STAN | Verification method for API calls. Verification is done through a number that is assigned by a counter in the gateway (or the terminal) to identify the uniqueness against Acquirers. | No | Yes | No | Yes | Yes |
| Stored Credential type |
A signup or enrolment request for the stored credentials A subsequent charge request for the stored credentials, related to a previous signup |
No | No | Yes | stored_credentials_type | No |
| Subscription ID | Identifier of the subscription or agreement in the payment provider's system | No | Yes | No | N/A | No |
| Technology | Entry mode (breakdown of cards like mag stripe, chip insert or contactless) | No | No | No | technology | Yes |
| Terminal ID |
Identifier assigned to POI and known by the Merchant or Client, whether this is an external Client, Client System or Gateway -- an ID assigned to each POS. For ecommerce it is assigned by the gateway. It distinguishes the requestor. |
No | Yes | No | terminal_id | Yes |
| Title | Shopper title | No | No | No | N/A | Yes |
| Transaction fee | Fees applicable for the transaction | No | No | No | payment_processing_fee_amount | Yes |
| Transaction ID | ID of the transaction | No | Yes | No | _id | Yes |
| Transaction logs (type, state, amount, currency, date&time, user) | The previous states of the transactions, users and their actions performed on that particular transaction | No | No | No | N/A | Yes |
| Type | Type of the transaction | Yes | No | Yes | N/A | Yes |
| Version | Version of 3DS | No | No | No | N/A | Yes |
| Wallet | Wallet that was used to initiate the transaction (eg. Google Pay, Apple Pay, Vipps, MobilePay etc) | No
|
No | Yes | payment_method | Yes |
| XID |
Transaction ID assigned for 3DS1.0.2 transactions |
No | No
|
No | N/A | Yes |
Rate this article:
