What Exchange and Transaction Data to Save After a Cryptocurrency Swap

A completed crypto exchange produces two related records: the service request and the blockchain transaction. Keep enough information to connect them without storing secrets that could give someone control of your wallet. The glossary below explains each record, where to find it, and how it helps if you need to verify an amount, investigate a delay, contact support, or prepare financial records.

Glossary of records worth keeping

Exchange request or order

Exact meaning: the instruction submitted to an exchange service, including the assets, amounts, addresses, selected network, and quoted conditions. In simple terms: it is the service-side record of what you asked the exchanger to do. Where it appears: on the request page, in a status notification, or in correspondence from the service. What it affects: save the request ID, creation time, exchange direction, displayed amounts, selected network, recipient address, refund address if provided, and final status.

Transaction

Exact meaning: a signed instruction submitted to a blockchain network, such as a transfer from one address to another. In simple terms: it is the on-chain movement used to fund the request or deliver the exchanged asset. Where it appears: in the sending wallet and a block explorer for the relevant network. What it affects: record each transaction separately when an exchange has both an incoming payment and an outgoing payout.

TXID or transaction hash

Exact meaning: the identifier generated from transaction data and used to locate a particular transaction. Bitcoin documentation describes the TXID as a hash of the serialized transaction, while Ethereum documentation refers to the equivalent identifier as a transaction hash. In simple terms: it is the lookup key for the on-chain record. Where it appears: in the wallet’s transaction details, the exchange request status, or a block explorer. What it affects: save the full value without shortening it; a screenshot showing only its first and last characters is not a reliable substitute. ^[1]

Blockchain and network

Exact meaning: a blockchain stores the ordered transaction history, while the network is the operating environment through which transactions are broadcast, validated, and included in blocks. In simple terms: the asset name alone may not identify the route used for a transfer. Where it appears: in the wallet’s send screen, the exchange request, and the selected block explorer. What it affects: preserve the network exactly as displayed and use an explorer for that network when checking the TXID. Sending through an unsupported or incorrect network can prevent normal crediting and may make recovery difficult or impossible.

Asset, coin, and token

Exact meaning: “asset” is the broad category; a coin is native to its blockchain, while a token is represented through rules or a contract on a host blockchain. In simple terms: identical or similar tickers do not prove that two wallet entries use the same network or token contract. Where it appears: in asset selectors, wallet details, transaction records, and explorer token-transfer sections. What it affects: save the asset ticker and, for a token, the network and contract identifier when the wallet or explorer displays it.

Address

Exact meaning: the destination or source identifier used in a blockchain transfer. In simple terms: it shows where the funds came from or were sent. Where it appears: in the request, wallet history, and explorer transaction details. What it affects: retain the complete deposit, recipient, and refund addresses that were actually used. Compare full values rather than relying only on matching prefixes and suffixes.

Memo or Tag

Exact meaning: an additional destination identifier required by some receiving services or transfer routes. In simple terms: several customers may use a shared address, and the Memo or Tag tells the recipient which account or request to credit. Where it appears: beside the destination address when required. What it affects: save it exactly as issued and include it with the address in any support request. Never invent one when none is provided.

Network fee and gas

Exact meaning: a network fee pays for blockchain processing; on Ethereum-compatible networks, gas measures the computational work associated with a transaction, and the resulting gas charge forms the transaction fee. In simple terms: this is an on-chain cost, not automatically the same as an exchange service charge. Where it appears: in wallet confirmations and explorer records. What it affects: keep the fee actually recorded on-chain and any separately displayed service fee. Ethereum transactions require fees and use gas-related fields such as the gas limit and fee per gas. ^[2]

Confirmation

Exact meaning: evidence that a transaction has been included in a block and has accumulated the network-specific level of settlement required by the receiving service. In simple terms: “broadcast,” “confirmed,” and “credited by the exchanger” describe different stages. Where it appears: in the block explorer and request status. What it affects: note the transaction status, block number or height if shown, confirmation count, and the time you checked them. A service may wait for its required number of confirmations before updating the request. ^[3]

Liquidity and slippage

Exact meaning: liquidity is the available capacity to complete an exchange at prevailing conditions; slippage is the difference between an indicative or expected execution value and the resulting value when conditions or available liquidity change. In simple terms: the preliminary amount and final amount may not always be identical. Where it appears: in quote terms, minimum-received fields, or final request results when the service provides them. What it affects: retain the initial quote, any stated quote-expiry condition, the amount sent, and the amount ultimately delivered. Do not reconstruct these figures later from a current market price.

Relationship map: from request to verifiable result

Object → network or environment → action → confirmation → verifiable result

1. Object: identify the exact asset being exchanged, including whether it is a native coin or a token.
2. Network or environment: record the selected blockchain network and any token contract, Memo, or Tag shown for the route.
3. Action: preserve the exchange request ID and the transaction details created when funds are sent or paid out.
4. Confirmation: use the complete TXID to check whether the transaction is pending, included in a block, successful, or failed. A wallet notification alone does not replace the underlying on-chain record.
5. Verifiable result: connect the request ID with the incoming and outgoing TXIDs, final amounts, addresses, fees, status, and completion time.

This chain matters because an exchange request can exist before any blockchain payment is made, and an on-chain payment can be confirmed before the service has credited or completed the request. Keeping both layers makes it possible to show what was requested, what was transferred, and what was received.

Do not confuse these closely related terms

Transaction and exchange request

A transaction belongs to a blockchain; a request belongs to the exchange service. One request may involve more than one transaction, such as the customer’s deposit and the service’s payout. Giving support only the TXID may not identify the request, while giving only the request ID does not independently prove what happened on-chain. Save both.

Asset and network

The asset answers “what is being transferred?” The network answers “where and under which protocol is it being transferred?” Recording “USDT” without its network can leave an incomplete trail because the token may exist in different network environments. Before sending, confirm that the asset, network, address format, and available exchange direction all match the request. Current pair and network availability should be checked before creating each request.

Coin and token

A native coin pays the network’s own fees, while a token operates on another blockchain and may require that network’s native coin for outgoing fees. Confusing the two can lead to an incomplete fee record or use of the wrong explorer. Preserve the ticker, network, and token contract when it is displayed.

Fee and gas

“Fee” is a broad term. Gas is a network-specific unit associated with computation on Ethereum-compatible systems; the paid network charge is calculated from gas-related values. An exchange may also show a separate service charge or incorporate costs into its displayed result. Store each value under the label originally used instead of combining unrelated charges into one number.

Seed phrase and private key

A private key authorizes control over a particular blockchain account or address. A seed phrase or wallet backup can be used to restore a broader set of wallet keys. Neither is a receipt, transaction identifier, or support credential. Do not place seed phrases, private keys, wallet passwords, or authentication codes in screenshots, cloud folders, spreadsheets, emails, or support messages. A wallet backup can restore private keys, which is why exposure may compromise wallet control. ^[4]

Practical example: assembling a complete exchange record

Suppose you intend to exchange one supported asset for another. First, use the exchange request page to check whether the required pair and network are currently available. Before transferring funds, save the request ID, exchange direction, selected network, deposit address, recipient address, expected amount, quote conditions, and Memo or Tag if one is issued.

After sending, copy the outgoing TXID from the wallet. Check it in the appropriate block explorer and retain the source address, destination address, transferred amount, network fee, status, block reference, and confirmation information. When the exchanged asset arrives, repeat the process for the payout transaction and add the actual received amount and completion status to the same record.

A screenshot can preserve context, but searchable text is more useful for long identifiers. Store the full request ID, addresses, TXIDs, and amounts as text, then keep screenshots or exported receipts as supporting evidence. If the request undergoes additional compliance checks, retain the service’s requests and status notices, but protect identity documents and other sensitive files with appropriate access controls. Verification requirements can vary by exchange direction and compliance results, so confirm the current requirements before creating a request.

Post-exchange record checklist

• Exchange request or order ID.
• Date and time the request was created and completed, including the displayed time zone when available.
• Source asset, destination asset, and exchange direction.
• Selected blockchain network for each transfer.
• Amount requested, amount sent, expected amount, and final amount received.
• Initial quote and expiry or rate conditions, if the service displayed them.
• Complete deposit, recipient, source, destination, and refund addresses as applicable.
• Memo or Tag, but only when issued for the transfer.
• Incoming and outgoing TXIDs, stored as copyable text.
• On-chain status, block reference, confirmations, and time checked.
• Network fee and any separately identified exchange charge.
• Request status history, receipts, and relevant support correspondence.
• Reason for a cancellation, refund, or manual review if the service provides one.

In a wallet, look for labels such as transaction details, hash, network, fee, from, to, amount, and status. In a block explorer, search using the full TXID and verify the network before interpreting the result. In exchange documentation, distinguish estimated values from completed values and general processing descriptions from the status of your specific request.

Keep these records in a location protected by strong authentication and restricted access. Do not store wallet secrets with the exchange archive. Retention periods and reporting obligations differ between countries and individual circumstances; if records may be needed for accounting, tax, compliance, or a dispute, determine the applicable local requirements rather than relying on a universal retention period.