1
In your portal, go to the Transactions tab.
2
Click Filters and specify the date range and other filters.
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.
- 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, and its unique identifier is 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, and its unique identifier is ENTRY_ID.
- For an even more granular view of each entry, see the Payments report.
Transaction and entry types
enum
The type of the transaction the entry belongs to.Possible values related to deposits:
deposit— a crypto deposit to a system deposit address or a customer deposit address.deposit_wallet_client— a crypto deposit to the merchant top-up address.deposit_exchange— a crypto deposit with conversion.
payment_request_deposit— a crypto deposit to a payment request address.payment_request_refund— an automatic refund.payment_request_manual_refund— a manual refund.
withdrawal— a crypto withdrawal.withdrawal_exchange— a crypto withdrawal with conversion.withdrawal_instant— an instant crypto withdrawal.withdrawal_instant_exchange— an instant crypto withdrawal with conversion.withdrawal_to_cold_client— an automatic withdrawal to a cold address.
exchange— a conversion between two currencies.
top_up— a fiat top-up.
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
integer
The unique identifier of the transaction to which the entry belongs. It is identical for all entries in the same transaction.
integer
The unique identifier of the entry (one row in the file).
string | null
The identifier of the payment request. Empty if the transaction isn’t related to a payment request.
integer | null
The identifier of the invoice. Empty if the transaction isn’t related to an invoice.
Merchant identifiers
integer
The ID of the merchant account in CryptoProcessing.
string
The name of the merchant account in CryptoProcessing.
Amounts and currencies
number
The amount that was sent, received, or converted.
string
The currency of
AMOUNT_FROM. See Currency codes.string | null
The currency of
AMOUNT_TO. See Currency codes.number
The fiat equivalent of
AMOUNT_FROM.string
The currency of
AMOUNT_EQUIVALENT. See Currency codes.number | null
The amount of the mining fee, which is paid to the miners in the blockchain network.
string | null
The currency of
MINING_FEE_AMOUNT. See Currency codes.number | null
The amount of the processing fee, which is paid to CryptoProcessing.
string | null
The currency of
PROCESSING_FEE_AMOUNT. See Currency codes."Yes" | null
Yes if the deposit was sent in a different currency than the one the deposit address was created for.Custom data
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.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.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 in the portal.
Transaction source
enum | null
How the transaction was initiated, or how the deposit address was created.Possible values:
users— in the portal.api_keys— via the API.
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
YYYY-MM-DD HH:MM:SS
The date and time of the entry.
YYYY-MM-DD HH:MM:SS
The date and time of the transaction’s last update.
enum
The status of the entry. See Deposit statuses and Withdrawal statuses.Possible values:
pending, verifying, waiting_for_documents, not_confirmed, processing, confirmed, rejected, declined, error, cancelled.Blockchain data
string | null
The recipient’s crypto address.
string | null
The sender’s crypto address. Empty if there are multiple sender addresses.
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 and off-chain withdrawals, the TXID is internal.
Risk scoring
integer | null
The risk score of the transaction, from 0 to 100. Empty if the risk score was not calculated.
integer | null
The risk score of the transaction from Scorechain, from 0 to 100. Empty if the risk score was not calculated.