Reporting Details
Last updated: 17-Oct-2024
The reporting page provides merchants with comprehensive details regarding each order / transaction that takes place in the account. The orders / transactions data from the reporting page can be viewed and analyzed using specific keywords or filters or reports can be exported in CSV file.
Below are definitions for all of the orders / transaction detail fields available in Verifone Central.
| Field Name | Definition (region specific) |
|---|---|
| Account Type | Type of the account used for the payment (credit/debit) |
| Acquirer | Type indicator to identify the acquirer of the payment |
| Acquirer Account Type | A field that indicates how the transaction was processed by the acquirer (it can be either debit or credit). |
| Acquirer Merchant ID | Identifier assigned to the Merchant and known by the Acquirer (it is not supported by all the acquirers) |
| Acquirer Response Code | Acquired Response Code |
| Acquirer Settlement ID | An identifier given to a settlement by the acquirer. |
| Actions | The available actions per transaction |
| ARN | Acquirer Reference Number is the "transaction ID " set by the Acquirer. It is usually used when communicating to banks and schemes. |
| Authorization Date Time | The date returned in the authorization response message |
| Authentication mode | Authentication method |
| Authentication value | Unique value assigned by the Issuer to distinguish the 3ds transaction. Is it similar to the Authorization code, but for 3DS |
| Authorization Code | Value assigned by the Acquirer for specific authorized transactions |
| AVS Outcome | Text that informs of the outcome of a requested shopper address validation. |
| Batch Created | Date of the Batch creation |
| Batch File Number | Internal identifier assigned to the settlement file sent for batch settlement to the acquirer. |
| 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. |
| Capture Status | Identifier that indicates whether the transaction resulted in the capture of the authorization. |
| Cashback Amount | A part of the purchase price returned to the customer as a reward or incentive in a payment transaction |
| Cashier Name | Name of the Cashier who created the transaction (not used for all the providers) |
| Cashier ID | ID of the Cashier who created the transaction (not used for all the providers) |
| Cardholder choice | Brand choice |
| Card Expiry Month | A 2 digit value displayed on the card indicating the month when the card will expire. |
| Card Expiry Year | A 4 digit value displayed on the card indicating the month when the card will expire. |
| Card Number | Primary Account Number or Card Number. Displayed in a masked format |
| Card Token | Identifier associated with the payment card that allow to search data related to that payment card in a safe way |
| Challenge indicator | Indicator that determines if the issuer request challenge the cardholder. |
| Channel | Sales channel of the transaction (eComm, mail, POS) |
| Cheque Account Number | The masked cheque holder's account number |
| Cheque Number | The cheque sequence number. |
| Customer Billing City | Shopper's billing city. |
| Customer Billing Country Code | Shopper's country code |
| Customer Billing First Name | Shopper's first name as displayed in the address. |
| Confirm Date Time | Identifier that indicates the transaction capture date and time |
| Contract ID | An identifier used to identify a contract from a Merchant perspective. As this may not be unique across Gateways or Acquirers, the UUID is used as the surrogate key. |
| Created | Date of transaction |
| Creation date time | Date and time when the transaction has made |
| Credit Term | Terms under which the transaction is performed. |
| 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 |
| Currency | Currency of the transaction |
| Current Amount/ Transaction amount | Current amount of the transaction (after some actions). Also mapped as Transaction amount, which can be found under the Fee Details in the Details section. |
| Customer App Phone Number | The phone number to be used for the Contact. If you include this property there should be at least one phone number. |
| Customer ID/Payer ID | Identifier as a string for the Customer. This is for the Verifone defined customer ID e.g from the customer service. The field is termed as Customer ID in the Customer Information section and as Payer ID in the Details tab of the transaction side-menu. |
| CVV Result | The result of a Card Verification Value check. The CVV or CVV2 are not stored, only an indicator to the result is captured after the verification. |
| Description |
Flexible identifier that can be used to represent various types of amount descriptions, providing clarity for different transaction values. Example: if a refund is done in Verifone Central and a refund note is added, the same note will appear in the Description field under the Transaction details section. |
| Device ID | Identifier used by an Estate Management System. |
| (Device) Serial Number | A value to indicate the device serial number. |
| Electronic Commerce Indicator | It indicates the level of authentication that was performed during an electronic commerce (e-Commerce) transaction. Each ECI value represents different authentication outcomes or levels of security. |
| Enrolled | Card enrolled for 3DS |
| Shopper email | |
| External Merchant ID | Merchant ID in the client's system (used by Woodforrest) |
| Fraud score | The fraud score returned by the Fraud Protection Service |
| Fraud Reason Insights | The list of reasons for the fraud score |
| Invoice number | Identifier of the invoice created for a transaction |
| IP Address | IP Address where the event originated. |
| 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 |
| Merchant Present | Identifier which signals whether the merchant was present or not during the transaction. |
| 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) |
| Message No | A number assigned by a transaction initiator(originator) to assist in identifying a transaction uniquely. |
| Name | Shopper full name |
| Organization | Organization name |
| Organization ID | Organization ID |
|
Orig. Amount/ Total transaction amount |
Initial amount of the transaction or total amount of the transaction. Also mapped as Total Transaction amount, which can be found under the Fee Details in the Details section. |
| Orig.amount currency code | Transaction payment currency |
| Payment Account Reference | A unique non-sensitive reference to the cardholder PAN (Payment Account Number). |
| Processor | Type indicator to identify the processor of the payment |
| Product | Payment method used to place the order |
| Provider reference | Type indicator for the contract that is being processed |
| Provider transaction ID | Transaction ID generated by the provider |
| Reason code | The reason code for the transaction status |
| Reference | Unique ID of the transaction, generated by the acquirer's system |
| Refusal Code | A numeric value related to the Refusal reason in the Transaction request. |
| Refusal reason | The reason a transaction has been refused within the payment ecosystem by the client/Verifone/acquirer. This reason is set by the component that is refusing this transaction request. |
| Response | Response received from the acquire |
| Response Code | Description of the response received from the acquirer |
| Reuse Token ID | A reusable token issued by Verifone or a third-party that is used to represent previously stored cardholder data. |
| Reuse Token Context | Any setup that uses a token to make a transaction secure. This will filter transactions according to the following token contexts: Stored Credentials (token used in the Stored Credential context), Tokenization (token requested in the non-Stored Credential context) or Instrument (token used as an instrument). |
| RRN | Retrieval Reference Number, may be used as reference against Acquirers |
| Sales Identifier | An external identifier from the POS or third-party for the transaction. Also known as 'Customer Transaction Reference' or 'third party reference' |
| Scheme Identifier | Identifier sent by the acquirer in the authorization response message, and sent in a subsequent authorization request messages associated with the same transaction. |
| Scheme Reference ID | Data typically used in stored credential transactions. |
| Scheme Transaction ID | Transaction ID assigned by the schemes for 3DS authentication. |
| Settlement amount | Calculated amount to be settled, cross border fee is deducted if applicable. Only a few processor supports this field |
| Settlement Batch ID | Identifier assigned to a settlement batch |
| Settlement date | Settlement date |
| Shipping address | Shopper shipping address |
| Shipping Information City | Shopper shipping city |
| Shipping Information Country | Shopper shipping country |
| Shopper Interaction | Type of software/hardware interface from which payment has been made |
| Shipping Information Postal Code | Shipping address post code |
| Shipping Information State | Shopper shipping state |
| Site Reference | An identifier for the Site that is unique to the Merchant Organization. It is used to locate the instance of a Site. |
| State | Displays details on the current transaction state |
| Status | Status of the transaction |
| Status (3D Secure Authentication) | Status of the 3DS check (e.g., successful authentication, failed authentication, etc.) |
| 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. The length of STAN will depend upon acquirer. |
| 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 |
| Subscription ID | Identifier of the subscription or agreement in the payment provider's system |
| Surcharge fee | Processing fees or additional costs applied to customers, included in the original purchase price. |
| Tax Amount | The amount of tax to be paid on the purchase |
| Technology | Entry mode (breakdown of cards like mag stripe, chip insert or contactless) |
| Terminal ID | Identifier assigned to POI and known by the Merchant or Client, whether this is an external Client, Client System or Gateway |
| Transaction fee | Fees applicable for the transaction |
| Transaction ID | ID of the transaction |
| Transaction Online Flag | Identifier that specifies if the transaction was submitted online or was captured offline and subsequently submitted to the processor or acquirer. |
| Transaction type | Type of the transaction. See more in Transaction Types and Statuses. |
| 3D Secure Version | Version of 3DS |
| User agent | The full user agent string of the device the customer used to submit the transaction. |
| Wallet | Wallet that was used to initiate the transaction (eg. Google Pay, Apple Pay, Vipps, MobilePay etc) |
| XID | Transaction ID assigned for 3DS1.0.2 transactions |
Related articles
Rate this article:
