Understand how to read, interpret and use the transaction overview.
Definition: The transactions overview serves as a comprehensive record of all exchanges involving cost and refund services and their corresponding values pertaining to Izix profiles within the parking management system.
As an administrator, please familiarise yourself with the following related Izix features first:
Content:
- What is the transactions overview?
- What information can I find in the transactions overview?
- Tips on how to use the transactions list
1. What is the transactions list?
The purpose of the transactions list is to provide a centralised, organised, and detailed record of all transactions for effective management, transparency, and analysis. Below are the key purposes of maintaining a transactions list:
Tracking and Monitoring
- User Transactions: Allows administrators to view users parking payments and any associated fees for accountability and transparency.
- System Transactions: Enables administrators to monitor system activity, including, payments, refunds.
Dispute Resolution
- Provides a verifiable record to resolve disputes between users and the parking service (e.g. billing errors or refunds).
- Helps validate claims with timestamps, transaction types, and payment details.
2. What information can I find in the transactions overview?
In case of booking access without payment, the transaction (booking & cancellation) will be featured on the overview. In this case, the service provider column will be empty and the amount will show "0".
The transaction list can be found via the Parking Management Interface -> Transactions.
The transactions history shows:
- Date and Time: When the transaction took place. This represents the moment the reservation was made.
- User Information: The e-mail address of the user.
- Transaction Type: The nature of the transaction (payment or refund).
- Payment Method: Izix credit, Vaigo or Stripe
- Amount
- Status: The current state of the transaction (success or failed).
- Reason For Failure
The transaction list will always reflect the deduction of credits at the time of booking, which corresponds to the user's activity. The system will assign this deduction to the appropriate budget allowance period. For example, if a user books a parking space for the following week while their credits are replenished weekly, the transaction list will display the current week's date. Nonetheless, the credits utilised for that booking will be deducted from the budget for the upcoming week.
The transactions overview does not include references on:
- Credit demands & refusals
- Wallet Policies
3. Tips on how to use the transactions list
Izix users should be encouraged to make use of their personalised credits history to find a full overview of their credits usage including charges, refills, refunds and related Wallet Policies.
For parking system administrators, the transactions overview is a critical tool for managing operations, ensuring accuracy, and maintaining transparency within the parking system. Here is an overview of how it works and how administrators can utilise it:
- Using Filters:
- Filter by criteria like user, date, payment method, payment status, or type.
- Handling Discrepancies:
- Cross-reference transaction details with system logs or external payment providers to identify errors.
- Generating Reports:
- Export the transaction list for audits or further analysis.
You can only download reports covering up to 3 months at a time.
Note that while you can request logs from up to approximately 4 months ago, logs older than this are purged and no longer available.
For a more detailed data analysis, please refer to Izix insights instead.