Export Audit History Report
Overview
This report will return all the events made on your account for the given time period. Events are any major changes to your account such transactions created, wallets created or wallet policy changes. The full set of events captured are listed below in detail.
The events have been recorded in our system since inception but the download tool only offers events from 16th December 2022.
Export events
The events recorded within the system are exported in CSV format with the following data.
event timestamp(UTC)
description
An example downloaded event would be:
Alice Bob <alice.bob@bitpanda.com> has requested a Subwallet creation with name test (subWalletId: d955ea0e-2edf-56gb-9e80-db8cb3df2cd4/ETH/15)
Event date / time
This will be the date / time that the event actually occurred.
Description
This will be a user friendly description of the event. It is made up of who performed the action, what action was performed and any additional metadata along with the event.
The "who" will be based on various different user types in the system. Below is a table of the types you can expect.
User Type | Example | Description |
ApiKey | API Key ****1a3aS6 | The action was performed by an API key and will display the last 6 digits for identification |
User | Alice Bob <alex.bob@bitpanda.com> | A user who was authentication with user credentials (i.e. email/PIN) |
User (via email authentication) | A user who performed an action via clicking a link in an email | |
Internal User | Bitpanda Custody Support <support@bitpandacustody.com> | The action was performed by Bitpanda Custody Support on your behalf |
Workflow User | Bitpanda Custody Workflow | This action was performed by a backend Bitpanda system and not as a direct result of user action. e.g. a Transaction will be signed by Bitpanda Custody Workflow as it is signed after a backend process has completed. |
From the example above, we can see that user: Alice Bob <alice.bob@bbitpanda.com> performed the action in question and they authenticated via email / PIN and NOT by an email link as it displays the given name and family name.
Event Names and their description
Below is a list of all the possible events that are recorded.
Num | Event Name | Description |
1
| DelegateSigned | A user has signed a transaction |
2 | TransactionInitiated | A transaction has been initiated |
3 | TransactionSigned | A transaction has been signed by our HSMs with the correct keys meaning the wallet policy was satisfied |
4 | TransactionSubmitted | A transaction has been submitted by TrustVault to the relevant chain |
5 | TransactionCancelled | A transaction was cancelled |
6 | WalletUpdateInitiated | A wallet change has been initiated (change of wallet policy) |
7 | WalletUpdateCompleted | A wallet change has been completed (change of wallet policy) |
8 | WalletUpdateCancelled | A wallet change has been cancelled |
9 | UserPinReset | A user has (re)-set their PIN (this will mean a new user account is now active) |
10 | UserRemovedFromOrg | A user has been removed from your organisation and can no longer access the account |
11 | UserAddedToOrg | A user has been added to your organisation and may be able to access the account. |
12 | AddressBookEntryCreateInitiated | A request has been made to create an address book entry |
13 | AddressBookEntryCreateCompleted | A request to create an address book entry has been completed |
14 | AddressBookEntryDeleteInitiated | A request to delete an address book entry has been initiated |
15 | AddressBookEntryDeleteCompleted | A request to delete an address book entry has been complete |
16 | SubwalletCreateInitiated | A request to create a sub-wallet has been initiated |
17 | SubwalletCreateCompleted | A request to create a sub-wallet has been completed |
18 | CreateWalletInitiated | A request to create a wallet has been initiated |
19 | CreateWalletCompleted | A request to create a wallet has been completed and the wallet is available to use |
20 | CreateWalletCancelled | A request to create a wallet has been cancelled |
21 | UserPermissionCreateCompleted | A request to add a permission to a user has been completed |
22 | UserPermissionDeleteCompleted | A request to delete a permission to a user has been completed |
Looking at our example again we can see that user Alice Bob requested the creation of a Subwallet call "test" (SubwalletCreateInitiated).
Initiated vs Completed
For many events in the system they can be initiated before they are completed. This is the case if the event requires an approval or if there is some time between the request and approval. In some circumstances the request and completion may be at the same time.
Process
To export a CSV of transactions, simply click the Export button and select Audit. This button is available in the top right of TrustVault Web Wallets section.
When you click Export Audit history you are presented with an option to choose the date period.
The options are:
31 days back from today
Custom Range
Select any date after 16th December 2022
max 31 days
Clicking Request will start the process and you will be returned with the email address that the results
Tip: This report can contain a large amount of data and can take a while to generate. Should you see a failure please try again and / or select a smaller date window. If problems persist please reach out to us for help.