# Transaction History

### Transaction Types

Each transaction includes details like date, time, and status, ensuring full transparency.

#### License Purchases

* **Details**: License name, purchase date, amount spent (e.g., USDK), validity (start/end dates).
* **Statuses**:
  * **Pending**: Purchase initiated, awaiting payment confirmation.
  * **Completed**: Purchase successful.
  * **Failed**: Payment failed; license not issued.
  * **Refunded**: Refund processed (if applicable).
* **Conditions**:
  * Pending transactions fail if unconfirmed within 24 hours.
  * Refunds require approval.

#### Link Events

* **Details**: License name, linked Minting Utility Token amount, linking period, expiry date.
* **Statuses**:
  * **Pending**: Link request initiated, awaiting on-chain confirmation.
  * **Active**: Link confirmed; rewards accruing.
  * **Cancelled**: Link request cancelled within 1 hour.
  * **Expired**: Linking period ended.
  * **Completed**: Rewards paid out or transferred.
* **Conditions**:
  * Status updates to Active on blockchain confirmation.
  * Expired status triggers at period end.

#### Rewards

* **Details**: Reward type (LYK-W/LYK-R), amount, credit/claim date.
* **Statuses**:
  * **Credited**: Rewards added to balance.
  * **Claimed**: Rewards transferred to wallet.
  * **Auto Debit**: Rewards relinked via Auto Linking.
  * **Auto Swap**: Rewards converted per user settings.
* **Conditions**:
  * Auto Debit applies when Auto Linking is ON.
  * Auto Swap follows user-configured conversions.

#### Minting Utility Token Actions

* **Details**: License name, Minting Utility Token amount, action type (Unlock/Claim), date.
* **Statuses**:
  * **Pending Unlock**: Unlock request in process.
  * **Unlocked**: Minting Utility Tokens ready for claiming.
  * **Claimed**: Minting Utility Tokens transferred to Minting Utility Token wallet.
  * **Failed**: Action failed (e.g., processing error).
* **Conditions**:
  * Unlock precedes claiming.
  * Pending Unlock times out after 24 hours.

#### Period Upgrades

* **Details**: License name, previous/new linking period, upgrade date.
* **Statuses**:
  * **Requested**: Upgrade initiated.
  * **Completed**: New period active.
  * **Failed**: Insufficient balance or other issues.
* **Conditions**:
  * Downgrades are blocked.
  * Failed upgrades revert to original period.

#### Hardware Linking/Delinking

* **Details**: Hardware name/type, linked license, action type (Link/Delink), date.
* **Statuses**:
  * **Pending Link**: Linking initiated.
  * **Linked**: License linked to hardware.
  * **Delinking Requested**: Delinking in process.
  * **Delinked**: License removed.
  * **Failed**: Action failed.
* **Conditions**:
  * Auto-delinking occurs on license expiry.
  * Pending actions time out if unconfirmed.

### Filtering and Sorting

* **Filters**:
  * **Transaction Type**: License purchases, linking, rewards, Minting Utility Token actions, upgrades, hardware actions.
  * **Status**: Pending, Completed, Failed, etc.
  * **Date Range**: Select specific timelines.
  * **License/Hardware**: View transactions for specific items.
* **Sorting**:
  * By date (recent to oldest or vice versa).
  * By amount (where applicable).
  * By status.
* **Search**: Find transactions by hardware ID, license ID, or type.

### Exporting History

* Download filtered transaction history in **XLS** or **CSV** format for record-keeping.
* Exported data includes only filtered results for targeted analysis.

### Accessing Transaction History

1. Navigate to **DeFi360 > CloudK > Transaction History** or click **View All** from the homepage.
2. Use filters and sorting to customize your view.
3. Click **Export** to download your transaction log.

See Managing Licenses or Managing Hardware for related actions.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.homnifi.com/homnifi-101/defi360/welcome-to-cloudk/transaction-history.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.