The transaction is the payment action initiated by the shopper or the merchant. The action is finalized with the confirmation of the checkout phase. Unlike settlements, finalizing the transaction does not imply automatically that the funds have been successfully transferred.
The Dashboard Transactions Reports page in Verifone Central allows you to view and export comprehensive reports on transactions that you can filter according to Organisation, Merchant ID, Currency, Product or Payment Method (wallet) used for the transaction. The same Transactions report can be generated by choosing Transactions in the drop-down list of the Reports menu section.
To view and export transaction reports from Dashboard, follow these steps:
- Log in to your Verifone Central account.
- Navigate to Reports and select Transactions.
Your transaction report includes all transactions from all your Payment Channels, including refunds and pre-authorizations.
In addition to filtering your transactions by the organisation and Merchant ID, you can also apply the following filters to your transactions:
- Transaction or settlement date
- Transaction details
- Transaction identifiers
Filter by transaction or settlement date
Click Created date or Settled date to filter transactions based on a date range.
- If ‘Created date’ is selected, the filter will include transactions initiated during the selected date range
- If ‘Settled date’ is selected, the filter will include transactions settled during the selected date range
Filter by transaction details
Select + Add Filter to filter transactions based on the following transaction details:
- Channel: Where the sale originated, e.g., from terminal or online (Note: For New Zealand, the ‘POS’ means the transaction was processed on an EFTPOS terminal in-store)
- Currency: Currency in which the transaction was tendered, e.g., New Zealand Dollar (NZD)
- Product: The card type used by the cardholder
- Transaction type: The type of transaction, e.g., sale or refund
- Transaction status: The status of the transaction, e.g., approved or declined
- Wallet: You can view and export reports that display your transactions based on the wallet used (Google Pay, Apple Pay, MobilePay, Vipps, etc.)
- Stored Credential Type: Stored data used to authorize payment in recurring transactions. There are two types:
- Sign up- for the initial payment
- Charge- for recurring payments
- Processor: The acquirer bank or institution that processed the payment.
- Account Type: The type of account used in the transaction, whether it is a Debit or a Credit account.
Filter by transaction identifiers
You can search for transactions based on transaction identifiers (see below). Select a transaction identifier from the dropdown menu, enter the correct value for the transaction(s) you are searching for into the search bar and then click Search.
You can find some of these identifiers on your terminal receipts.
Note: Applicable for NZ only.
- Terminal ID: You can find this on all of your receipts. It is the last four digits of the ‘TSP’ number
- STAN (System Trace Audit Number): The 6-digit number incremented for each transaction the terminal sends
- Note: New Zealand users can find this on their EFTPOS receipt as the ‘Tran’ number. Example: 000287.
- RRN (Reference Retrieval Number): Only available on some merchant EFTPOS receipts. Made up of the date the transaction was processed and the transaction STAN number (System Trace Audit Number). Example: 200807030680.
- Batch Number: This is the settlement date of the transaction in the format YYDDMM
- Reference: For transactions processed on an EFTPOS terminal in-store, this is the RRN
- Settlement ID: Not applicable for New Zealand
- Transaction ID: For New Zealand transactions processed on an EFTPOS terminal in-store, this is the RRN
Click a particular transaction to see additional details about the transaction:
- Organization: The organization associated with this transaction
- Reference: The transaction reference number. For New Zealand in-store EFTPOS terminals, this is the RRN
- Channel: Where the sale originated, i.e., on a terminal or online. If the channel is given as ‘POS’, this means the transaction was processed on a terminal in-store.
Click on the tabs to see more information about the transaction:
- History: Past transactions with their log information: date, time, amount, currency, user
- Actions: Operations that can be performed on each transaction such as: Capture, Void and Refund. The actions available depend on the type and status of the transaction.
- Details: More detailed information on the transactions including organization, settlement status and 3DS details. See the Report column section below for more information.
- Customer: General customer information such as name, billing and shipping address.
- Documents (Available in limited regions): The tab enables the option to resend either the Merchant or Cardholder Copy of the transaction receipt. After clicking the appropriate button, you will need to enter an email address.
- (Available in Israel)
- You are also able to see the Invoice4U identifier of the receipts below the Merchant and Cardholder Copies
- You have the option of e-mailing the Merchant and Cardholder Copies
- (Available in France) Merchants using Carte Bancaire services also have the option of e-mailing copies of the Merchant and Cardholder receipts
- (Available in Israel)
Once you’ve applied filters to display the transactions you want to export, click Export CSV to generate a transaction report for download.
1. Select the report type:
- ‘Basic report’ will contain the same columns as the transaction table in the Portal
- ‘Full report’ will export all transaction detail fields
2. Click Download CSV
- See the report columns section for definitions of all transaction detail fields
Below are definitions for all of the transaction detail fields included in the full reports. Each field is listed also with their availability as filters and search criteria.
|Field Name||Definition (region specific)||Mandatory||
(= basic CSV)
CSV full report
|Created||Date of transaction||Yes||Yes||Yes||Yes||Yes|
|Reference||Unique ID of the transaction||Yes||Yes||Yes||No||Yes||Yes|
|Organisation ID||Organisation ID||Yes||No||No||Yes||No||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||Yes||Yes||Yes|
|Product||Payment method used to place the order||Yes||Yes||No||Yes||Yes||Yes|
|Orig. Amount||Initial amount of the transaction||Yes||Yes||No||No||Yes||No|
|Current Amount||Current amount of the transaction (after some actions)||Yes||Yes||No||No||Yes||Yes|
|Status||Status of the transaction||Yes||Yes||No||Yes||Yes||Yes|
|Type||Type of the transaction||Yes||Yes||No||Yes||No||Yes|
|Transaction ID||ID of the transaction||Yes||No||Yes||No||Yes||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.||Yes||No||Yes||No||Yes||Yes|
|Settlement Batch ID||Batch ID assigned to a settlement batch||Yes||No||Yes||No||Yes||Yes|
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.
|Card number||Primary Account Number or Card Number. Displayed in an encrypted format||Yes||No||Yes||No||Yes||Yes|
|Expires (card)||Expiry date of the card||Yes||No||No||No||No||
Merchant reference is a value (up to 50 characters) that is assigned by the merchant in each transaction for their own identification.
|Processor STAN||Number that is assigned by a counter in the gateway (or the terminal) to identify the uniqueness against processor.||Yes||No
|Provider reference||Type indicator for the contract that is being processed||Yes||No||No||No||No||Yes|
|Provider Transaction IDA||Transaction ID generated by the provider||Yes||No||Yes||No||No||Yes|
|RRN||Retrieval Reference Number may be used as reference against Acquirers||Yes||No||Yes||No||Yes||Yes|
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.
|Subscription ID||Identifier of the subscription or agreement in the payment provider's system||Yes||No||Yes||No||No||No|
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.
|Channel||Sales channel of the transaction (ecom, mail, POS)||Yes||No||No||Yes||No||
|Currency||Currency of the transaction||Yes||No||No||Yes||Yes||No|
|Wallet||Wallet that was used to initiate the transaction (eg. Google Pay, Apple Pay, Vipps, MobilePay etc)||Yes||No
|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
|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||No||Yes|
|Actions||The available actions per transaction||-||No||No||No||No||Yes|
|Authorisation code||Value assigned by the Acquirer for specific authorized transactions||-||No||No||No||No||Yes|
|Response||Response received from the acquirer||-||No||No||No||Yes||Yes|
|Response description||Description of the response received from the acquirer||-||No||No||No||Yes||Yes|
|Response code||Code of the response received from the acquire||-||No||No||No||Yes||Yes|
|Acquirer response code||Acquired Response Code||-||No||No||No||Yes||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||Yes||Yes|
|Technology||Entry mode (breakdown of cards like mag stripe, chip insert or contactless)||-||No||No||No||Yes||Yes|
|Authentication mode||Authentication method||-||No||No||No||No||Yes|
|Cardholder choice||Brand choice||-||No||No||No||No||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||Yes||Yes|
|Transaction fee||Fees applicable for the transaction||-||No||No||No||Yes||Yes|
|Settlement amount||Amount settled||-||No||No||No||No|
|Batch created||Date of the Batch creation||-||No||No||No||No||Yes|
|Settlement date||Date of the settlement||-||No||No||No||Yes||Yes|
|Acquirer||Type indicator to identify the acquirer of the payment||-||No||No||No||Yes||Yes|
|Processor||Type indicator to identify the processor of the payment||-||No||No||No||Yes||Yes|
Transaction ID assigned for 3DS1.0.2 transactions
Unique value assigned by the Issuer to distinguish the 3ds transaction. Is it similar to the Authorisation code, but for 3DS
|Status(3DS)||Status of the 3DS check (e.g., successful, failed, etc.)||-||No||No||No||No||Yes|
|Enrolled||Card enrolled for 3DS||-||No||No||No||No||Yes|
|Scheme transaction ID||Transaction ID assigned by the schemes for 3DS1.0.2 transactions||-||No||No||No||No||
|Version||Version of 3DS||-||No||No||No||No||
|Challenge indicator||Did the issuer request challenge the cardholder?||-||No||No||No||No||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||No||
|Name||Shopper full name||-||No||No||No||Yes||Yes|
|Shipping address||Shopper shipping address||-||No||No||No||Yes||Yes|
|IP address||IP Address v4 where the event originated.||-||No||No||No||No||Yes|
|Documents||Available documents - receipts||-||No||No||No||No||Yes|
|Instalment payment index||
Field is applicable for Israel only.
Possible values are:
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||Yes||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||No||Yes|