> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cryptoprocessing.us/llms.txt
> Use this file to discover all available pages before exploring further.

# Transactions report

**Available to all roles (Roles determine what each user can see and do in the portal.) except**

You can export the history of your transactions for a selected period.

**Step 1**

In your portal, go to the **Transactions** tab.

**Step 2**

Click **Filters** and specify the date range and other filters.

**Step 3**

Click **Export** to generate the report.

The report can take from a few seconds to a few minutes to generate. If it's done within a few seconds, it will be downloaded immediately. If it takes longer, you can find and download it later within 30 days using the **Reports** icon in the left panel.

The report is a CSV file showing the *transactions* and *entries* that match the filters.

* A **transaction** is the highest-level abstraction: a deposit that you received, a withdrawal that you sent, an automatic withdrawal that a system initiated, etc. One transaction may span multiple rows. Its type is [TRANSACTION\_TYPE](#param-transaction-type), and its unique identifier is [TRANSACTION\_ID](#param-transaction-id).

* An **entry** is a more granular action within the transaction. For example, a withdrawal transaction may include a withdrawal entry and an automatic conversion entry. Each entry takes exactly one row. Its type is [TYPE](#param-type), and its unique identifier is [ENTRY\_ID](#param-entry-id).

* For an even more granular view of each entry, see the [Payments report](https://docs.cryptoprocessing.us/reporting/payments-report.md).

## Transaction and entry types

**TRANSACTION\_TYPE** `enum`

The type of the transaction the entry belongs to.

Possible values related to [deposits](https://docs.cryptoprocessing.us/deposits.md):

* `deposit` — a crypto deposit to [a system deposit address or a customer deposit address](https://docs.cryptoprocessing.us/deposits.md#types-of-deposit-addresses).
* `deposit_wallet_client` — a crypto deposit to the [merchant top-up address](https://docs.cryptoprocessing.us/deposits.md#types-of-deposit-addresses).
* `deposit_exchange` — a crypto deposit [with conversion](https://docs.cryptoprocessing.us/deposits.md#deposits-with-conversion).

Possible values related to [payment requests](https://docs.cryptoprocessing.us/payment-requests.md):

* `payment_request_deposit` — a crypto deposit to a payment request address.
* `payment_request_refund` — an [automatic refund](https://docs.cryptoprocessing.us/payment-requests/refunds.md#automatic-refunds).
* `payment_request_manual_refund` — a [manual refund](https://docs.cryptoprocessing.us/payment-requests/refunds.md#manual-refunds).

Possible values related to [withdrawals](https://docs.cryptoprocessing.us/withdrawals.md):

* `withdrawal` — a crypto withdrawal.
* `withdrawal_exchange` — a crypto withdrawal [with conversion](https://docs.cryptoprocessing.us/withdrawals.md#withdrawals-with-conversion).
* `withdrawal_instant` — an [instant crypto withdrawal](https://docs.cryptoprocessing.us/withdrawals.md#instant-withdrawals).
* `withdrawal_instant_exchange` — an [instant crypto withdrawal](https://docs.cryptoprocessing.us/withdrawals.md#instant-withdrawals) with conversion.
* `withdrawal_to_cold_client` — an [automatic withdrawal to a cold address](https://docs.cryptoprocessing.us/merchant-administration/configure-automatic-withdrawals-to-cold-addresses.md).

Possible values related to [exchanges](https://docs.cryptoprocessing.us/exchanges.md):

* `exchange` — a conversion between two currencies.

Possible values related to [fiat operations](https://docs.cryptoprocessing.us/fiat/top-up-fiat.md):

* `top_up` — a fiat top-up.

**TYPE** `enum`

The type of the entry (one row in the file).

Possible values: `deposit`, `deposit_wallet_client`, `withdrawal`, `withdrawal_to_cold_client`, `exchange`, `top_up` (a fiat top-up), `transfer` (an internal move between wallets).

## Transaction identifiers

**TRANSACTION\_ID** `integer`

The unique identifier of the transaction to which the entry belongs. It is identical for all entries in the same transaction.

**ENTRY\_ID** `integer`

The unique identifier of the entry (one row in the file).

**PAYMENT\_REQUEST\_ID** `string | null`

The identifier of the [payment request](https://docs.cryptoprocessing.us/payment-requests.md). Empty if the transaction isn't related to a payment request.

**INVOICE\_ID** `integer | null`

The identifier of the invoice. Empty if the transaction isn't related to an invoice.

## Merchant identifiers

**CLIENT\_ID** `integer`

The ID of the merchant account in CryptoProcessing.

**CLIENT\_NAME** `string`

The name of the merchant account in CryptoProcessing.

## Amounts and currencies

**AMOUNT\_FROM** `number`

The amount that was sent, received, or converted.

**CURRENCY\_FROM** `string`

The currency of `AMOUNT_FROM`. See [Currency codes](https://docs.cryptoprocessing.us/api-reference/currency-codes.md).

**AMOUNT\_TO** `number | null`

The resulting amount of an [exchange](https://docs.cryptoprocessing.us/exchanges.md).

**CURRENCY\_TO** `string | null`

The currency of `AMOUNT_TO`. See [Currency codes](https://docs.cryptoprocessing.us/api-reference/currency-codes.md).

**AMOUNT\_EQUIVALENT** `number`

The fiat equivalent of `AMOUNT_FROM`.

**EQUIVALENT\_CURRENCY** `string`

The currency of `AMOUNT_EQUIVALENT`. See [Currency codes](https://docs.cryptoprocessing.us/api-reference/currency-codes.md).

**MINING\_FEE\_AMOUNT** `number | null`

The amount of the mining fee, which is paid to the miners in the blockchain network.

**MINING\_FEE\_CURRENCY** `string | null`

The currency of `MINING_FEE_AMOUNT`. See [Currency codes](https://docs.cryptoprocessing.us/api-reference/currency-codes.md).

**PROCESSING\_FEE\_AMOUNT** `number | null`

The amount of the processing fee, which is paid to CryptoProcessing.

**PROCESSING\_FEE\_CURRENCY** `string | null`

The currency of `PROCESSING_FEE_AMOUNT`. See [Currency codes](https://docs.cryptoprocessing.us/api-reference/currency-codes.md).

**CROSS\_CURRENCY** `"Yes" | null`

`Yes` if the deposit was sent in a different currency than the one the deposit address was created for.

## Custom data

**FOREIGN\_ID** `string | null`

Custom identifier that was provided as `foreign_id` when creating the deposit address, initiating the withdrawal, or creating the payment request via the API.

**END\_USER\_REFERENCE** `string | null`

Custom identifier that was provided as `end_user_reference` when creating the deposit address, initiating the withdrawal, or creating the payment request via the API. See [User data collection](https://docs.cryptoprocessing.us/user-data-collection.md).

**NOTE** `string | null`

A note for the transaction. The system adds notes automatically for some transactions, such as cross-currency deposits and accepted underpayments. You can also add a note when [creating a withdrawal](https://docs.cryptoprocessing.us/withdrawals/create-a-withdrawal.md) in the portal.

## Transaction source

**ORIGIN** `enum | null`

How the transaction was initiated, or how the [deposit address](https://docs.cryptoprocessing.us/deposits.md#types-of-deposit-addresses) was created.

Possible values:

* `users` — in the portal.
* `api_keys` — via the API.

Empty for invoice and payment request transactions.

**CREATED\_BY** `string | null`

The initiator of the transaction: the user's email address or the internal ID of the API key. Empty for deposits and some system-initiated transactions, such as withdrawals to cold addresses or automatic refunds.

## Date and status

**DATE** `YYYY-MM-DD HH:MM:SS`

The date and time of the entry.

**UPDATED\_AT** `YYYY-MM-DD HH:MM:SS`

The date and time of the transaction's last update.

**STATUS** `enum`

The status of the entry. See [Deposit statuses](https://docs.cryptoprocessing.us/deposits/statuses.md) and [Withdrawal statuses](https://docs.cryptoprocessing.us/withdrawals/statuses.md).

Possible values: `pending`, `verifying`, `waiting_for_documents`, `not_confirmed`, `processing`, `confirmed`, `rejected`, `declined`, `error`, `cancelled`.

## Blockchain data

**ADDRESS** `string | null`

The recipient's crypto address.

**SENDER\_ADDRESS** `string | null`

The sender's crypto address. Empty if there are multiple sender addresses.

**TAG** `string | null`

The [tag field](https://docs.cryptoprocessing.us/deposits/tags.md) of the recipient's address. Empty if the currency doesn't use tags.

**TXID** `string | null`

The unique identifier of the transaction. For on-chain transactions, the TXID is public and can be found in a blockchain explorer. For [off-chain deposits](https://docs.cryptoprocessing.us/deposits.md#off-chain-deposits) and [off-chain withdrawals](https://docs.cryptoprocessing.us/withdrawals.md#off-chain-withdrawals), the TXID is internal.

## Risk scoring

**RISKSCORE** `integer | null`

The [risk score](https://docs.cryptoprocessing.us/deposits/risk-scoring.md) of the transaction, from 0 to 100. Empty if the risk score was not calculated.

**RISKSCORE\_SCORECHAIN** `integer | null`

The [risk score](https://docs.cryptoprocessing.us/deposits/risk-scoring.md) of the transaction from Scorechain, from 0 to 100. Empty if the risk score was not calculated.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.