Integration matrix

Only Akashnet-2 history from 9 Mar 2021 onwards imports. The article's Transition-to-Manual banner names "DeFi Kingdoms" (vendor copy error), not Akash. Vendor note: "Only transactions from the start (March 9, 2021) of the Akashnet-2 can be imported."

Divly's guide has you generate the CSV from your Algorand address with the third-party Stake Tax tool, then upload it to Divly. Vendor note: "Make sure to download the CSV file every time you want to include the latest transactions."

Vendor note: "you’ll need to add your public address from every wallet you use to interact with Algorand"

Listed as "Algorand" on TokenTax's integrations page, which does not state the import method.

Listed as "Aptos" on TokenTax's integrations page, which does not state the import method.

Vendor note: "you’ll need to add your public address from every wallet you use to interact with Arbitrum in order for Koinly to calculate your crypto taxes correctly"

Vendor note: "This integration is currently in BETA. Transactions from this API should be reviewed for accuracy once imported." Import is by entering a wallet address.

Some internal EVM transactions (wrapping withdrawals, bridging deposits) may not import automatically; ERC1155 NFT balances are not synced. Vendor note: "Missing transaction data must therefore be added manually."

Only the most recent 10k transactions sync; older ones must be added manually. Vendor note: "Older transactions need to be added manually"

Vendor note: "Certain internal transactions on EVM chains (e.g., withdrawal transactions related to wrapping; deposit transactions related to bridging) can currently not be imported automatically in all cases."

Divly's integration uses your public Avalanche address.

Koinly's guide covers Avalanche C-Chain. Vendor note: "This integration can support wallets with up to 50k transactions"

TokenTax's guide imports Avalanche C-Chain by wallet address; its X-Chain import is in beta and P-Chain needs its manual CSV template.

Listed as "Base" on TokenTax's integrations page, which does not state the import method.

Listed as "Berachain" on TokenTax's integrations page, which does not state the import method.

Vendor note: "Spot Market Trades older than 720 days (2 years) are not available via API."

Vendor note: "A CSV covers spot trades only. Card and bank purchases, and staking or mining rewards, need the API import or manual entry."

Vendor note: "The Binance API is not sufficient for tax reporting in most cases and is therefore not supported for tax imports."

Vendor note: "Missing data (not provided by Binance via API at all): Bot trades and NFT trades"

TokenTax's help article says new API connections are not currently possible; new/missing data via CSV. Vendor note: "Due to changes on Binance's end, new API connections are not currently possible (especially for U.S.-based users)."

CSV/Excel only (no API). The current v3 format (two files) does not cover Wealth (Earn, Loan, Dual Invest), RewardsHub, LaunchHub or fiat deposits/withdrawals.

Spot trades import; futures and copy-trading results are added with CoinLedger's Margin Gain transaction type. BingX limits export ranges, so several files may be needed.

API gives futures for the last 3 months only (max 1,000 trades) and no copy trading, Earn, conversions or Wealth; use CSV for those. Vendor note: "BingX's API has multiple limitations and may not provide all your data"

Blockpit's general blockchain-integration guide adds Bitcoin by public wallet address or extended public key (xpub, ypub or zpub).

Vendor note: "Some transactions that happened before June 1st 2022 may have the wrong timestamp (off by 1 hour) and need to be edited manually"

Listed as "Bitcoin" on TokenTax's integrations page, which does not state the import method.

Blockpit's wallet-integration guide says Bitcoin Cash may need an extended public key (xpub-style account address) rather than a single address.

Vendor note: "We recommend syncing your XPUB key rather than individual addresses."

Listed as "Bitcoin Cash" on TokenTax's integrations page, which does not state the import method.

Blockpit's guide covers API key import and lists Funding (Lending & Borrowing), OTC/P2P Trades and Securities Trades as not supported.

Vendor note: "Make sure to download the CSV file every time you want to include the latest transactions."

Vendor note: "If you have margin trades, you will need to connect an API to supply all necessary data."

ZenLedger's guide says it supports this platform but only describes import methods in general terms, not for this platform.

Blockpit's help article says the automatic import has ended; new transactions only via Blockpit's Excel template (CSV) or manual entry. Vendor note: "Automated bitFlyer integration has been discontinued as of Oktober 2026."

CoinLedger's only stated method is mapping your export into CoinLedger's own CSV format; no dedicated importer is named. Vendor note: "Import your transaction history directly into CoinLedger by mapping the data into the preferred CSV file format."

Vendor note: "Transactions older than 2 years are not available via API."

Vendor note: "Bitget exports up to 24 months of history, so generate multiple files to cover your full history"

Vendor note: "Bitget's API only provides transactions for the last 2 years"

Listed as "Bitget" on TokenTax's integrations page, which does not state the import method.

Blockpit's guide covers OAuth connection, API key, and a CSV upload. Vendor note: "The alternative Bitpanda CSV upload only includes crypto transactions, lacks sub-wallet structures, and is therefore incompatible with OAuth/API."

CoinLedger's only stated method is mapping your export into CoinLedger's own CSV format; no dedicated importer is named.

Vendor note: "Make sure to download the CSV file every time you want to include the latest transactions."

Vendor note: "Bitpanda's API does not provide: Staking rewards - rewards need to be added manually"

Blockpit's page confirms support but does not state the import method.

CoinLedger's only stated method is mapping your export into CoinLedger's own CSV format; no dedicated importer is named. Vendor note: "Import your transaction history directly into CoinLedger by mapping the data into the preferred CSV file format."

Vendor note: "Currency conversions are not provided by the Bitso API. These trades will need to be added manually until Bitso addresses the issue"

Vendor note: "Make sure to download the CSV file every time you want to include the latest transactions."

Vendor note: "Bitstamp may not return some of your trades between Feb 2018 and March 2018 which can cause balances to not match up."

ZenLedger's guide only describes pasting a Bitstamp receiving address; no API or CSV importer is stated. Confirm with ZenLedger.

CSV only (no API); referral commissions, other rewards and vouchers are not supported.

Vendor note: "Make sure to download the CSV files every time you want to include the latest transactions."

Quick swaps and 3rd-party payments are not provided by Bitunix and must be added manually.

CoinLedger's only stated method is mapping your export into CoinLedger's own CSV format; no dedicated importer is named. Vendor note: "Import your transaction history directly into CoinLedger by mapping the data into the preferred CSV file format."

Vendor note: "Fees are not included in the export and won't be handled in the tax calculations."

Blockpit's help article says the automatic import has ended; existing integrations became manual and new transactions only go in via Blockpit's CSV template or manual entry. Vendor note: "Automatic sync for Blast integrations has been discontinued."

Bridge deposits and native yield are not imported and must be added manually. Vendor note: "Native yield (ETH, USDB) is distributed without a transaction"

Listed as "Blast" on TokenTax's integrations page, which does not state the import method.

Vendor note: "Certain internal transactions on EVM chains (e.g., withdrawal transactions related to wrapping; deposit transactions related to bridging) can currently not be imported automatically in all cases."

Vendor note: "you’ll need to add your public address from every wallet you use to interact with the Binance Smart Chain"

Listed as "Binance Smart Chain" on TokenTax's integrations page, which does not state the import method.

Vendor note: "Classic Account: Spot Market Trades older than 365 days are not available via API."

Vendor note: "Perpetual and futures transactions are not supported by the import"

Vendor note: "Since Bybit only allows you to export max 1 year at a time, you will need to create one file per year."

Vendor note: "Can't import (not available via API): Bot trades Copy-trading Launchpool rewards NFT trades"

Vendor note: "Bybit spot transactions are supported via either API or CSV import."

Blockpit's page lists Byron-era and Shelley-era public keys.

Divly's integration uses your public Cardano stake key.

Vendor note: "Some transactions related to Liquidity Providing need to be fixed manually"

Listed as "Cardano" on TokenTax's integrations page, which does not state the import method.

Listed as "Celestia" on TokenTax's integrations page, which does not state the import method.

Vendor note: "If you used Coinbase Advanced, use the API import instead. Coinbase Wallet (self-custody) and the retired Coinbase Pro are separate imports."

Vendor note: "Coinbase CSV export is not supported for taxation because it does not include all required information."

Help article covers OAuth import (counted as API).

Blockpit lists this wallet as Base Wallet. Vendor note: "In Base Wallet (formerly Coinbase Wallet) you can create wallets for multiple blockchains (coins) or import your existing wallets using your public key".

Vendor note: "Coinbase Wallet gives you a separate address on each blockchain, so if you were active on more than one, add each address"

Divly imports Coinbase Wallet by public wallet address per blockchain. Vendor note: "Repeat the previous steps for each blockchain you want to import."

Vendor note: "Copy the public address for every coin that you have on it (even the ones with a zero balance)" Koinly lists it as Coinbase Wallet (prev. Base App).

Blockpit's page confirms support but does not state the import method.

CoinLedger's only stated method is mapping your export into CoinLedger's own CSV format; no dedicated importer is named. Vendor note: "Import your transaction history directly into CoinLedger by mapping the data into the preferred CSV file format."

API misses swaps, margin trades and Earn rewards. Blockpit says CoinEx shuts down on 22 Dec 2026 and has no native CoinEx CSV importer, so archive exports and add later data via its CSV template.

The CoinEx export is a zip of four CSV files; upload each one. Vendor note: "Make sure to download the CSV file every time you want to include the latest transactions."

API misses instant swaps, airdrops and referral commissions. Koinly says CoinEx is ceasing services, fully on 22 Dec 2026; export your CSV history before then.

Spot via CSV only; margin, futures and derivatives need a supporting plan or the Margin Add-On. Vendor note: "These types of transactions require the purchase of a supporting plan or the Margin Add-On."

Vendor note: "Make sure to download the CSV file every time you want to include the latest transactions."

Vendor note: "CoinSpot data is currently supported via CSV import only."

ZenLedger's guide says it supports this platform but does not state the import method for it.

Blockpit's guide says native Cosmos transactions are imported from December 2019 (CosmosHub V3) onwards.

Divly's guide has you generate the CSV from your Cosmos address with the third-party Stake Tax tool, then upload it to Divly. Vendor note: "Make sure to download the CSV file every time you want to include the latest transactions."

Vendor note: "you’ll need to add your public address from every wallet you use to interact with ATOM"

Listed as "Cosmos" on TokenTax's integrations page, which does not state the import method.

Not in ZenLedger's exchanges directory; its help article has you generate a CSV with the third-party stake.tax tool and upload it through ZenLedger's Custom CSV Upload portal. Vendor note: "ZenLedger will not recognize a transaction type labelled as 'Staking'."

Vendor note: "Certain internal transactions on EVM chains (e.g., withdrawal transactions related to wrapping; deposit transactions related to bridging) can currently not be imported automatically in all cases."

Vendor note: "Cannot import Bridge transactions. Max 10k normal transactions, erc20, erc721 transactions imported."

Vendor note: "Only the last 10-30k most recent transactions can be imported."

Blockpit's API guide covers the Crypto.com Exchange; the Crypto.com App has a separate CSV guide.

Vendor note: "NFTs and certain special products (like baskets or liquidity products) are not fully covered and may require manual entries"

Vendor note: "The Crypto.com API only provides transactions from the last 2 years."

Vendor note: "Crypto.com transactions are supported via either API or CSV import." Note: "Crypto.com Exchange activity is not included in the CSV."

XPUB keys must start with xpub/ypub/zpub; keys starting with "drkv" are not supported. Vendor note: "Keys starting with "drkv" are not supported"

API does not import options trades PnL, block trades, swaps or crypto buys; each subaccount needs its own Blockpit integration.

CoinLedger's only stated method is mapping your export into CoinLedger's own CSV format; no dedicated importer is named. Vendor note: "Import your transaction history directly into CoinLedger by mapping the data into the preferred CSV file format."

PnL syncs at the full traded amounts, so positions opened and settled in different tax years may need manual moves. Vendor note: "Deribit does not allow for accurate syncing of PNL."

Margin/derivative trades need CSV alongside the regular import, plus a supporting plan or the Margin Add-On.

ZenLedger's guide says it supports Deribit but only describes import methods in general terms across exchanges, not a Deribit-specific method. Vendor note: "Select the exchange that you are looking to import, and instructions will be provided for that specific exchange!"

Listed on Blockpit's DigiByte integration page; no DigiByte-specific help article was in the help collections fetched today, so the import method is not stated.

ZenLedger's page title misspells DigiByte as "DigitByte"; the body is about DigiByte (DGB).

Blockpit's wallet-integration guide says Dogecoin uses an extended public key with the prefix dgub (in place of Bitcoin's xpub).

Vendor note: "We recommend syncing your XPUB key rather than individual addresses."

CoinLedger's only stated method is mapping your export into CoinLedger's own CSV format; no dedicated importer is named. Vendor note: "Import your transaction history directly into CoinLedger by mapping the data into the preferred CSV file format."

PnL settlements from futures trading are not handled yet and must be added manually. Vendor note: "This integration does not yet handle PNL settlements from futures trading. These need to be added manually"

Listed as "dYdX" on TokenTax's integrations page, which does not state the import method.

RAM, network resources and CPU transactions are not supported. Vendor note: "Transactions with RAM, NETWORK RESOURCES and CPU are not supported."

Vendor note: "If you have used any other EVM networks with this address, then you will need to add those networks separately to Koinly"

Vendor note: "Certain internal transactions on EVM chains (e.g., withdrawal transactions related to wrapping; deposit transactions related to bridging) can currently not be imported automatically in all cases."

Vendor note: "you’ll need to add your public address from every wallet you use to interact with Ethereum Classic"

Listed as "Ethereum Classic" on TokenTax's integrations page, which does not state the import method.

Blockpit's guide imports eToro's XLS account statement and says only trades of the investment type Crypto can be imported; stock and CFD transactions cannot.

Vendor note: "only closed crypto positions import, because eToro does not expose the cost basis of positions you still hold open."

Divly imports eToro's XLSX file. Vendor note: "Make sure to download the XLSX file every time you want to include the latest transactions."

Koinly imports eToro's Excel account statement and lists stock trades, CFDs (including crypto CFDs) and ETFs as data it can't import. Vendor note: "Koinly only supports the English version of the Excel file"

Listed as "Etoro" on TokenTax's integrations page, which does not state the import method.

ZenLedger's guide says it supports this platform but only describes import methods in general terms, not for this platform.

Vendor note: "it does not include the fiat cost of crypto you bought inside Exodus, so those buys can import without a cost basis"

Vendor note: "Divly does not support the individual crypto files."

Vendor note: "Copy the public address for every coin that you have on it (even the ones with a zero balance)"

Vendor note: "Exodus data is currently supported via CSV import only."

Blockpit's help article says the automatic import has ended; existing integrations became manual and new transactions only go in via Blockpit's CSV template or manual entry. Vendor note: "Automatic sync for Fantom integrations has been discontinued."

Vendor note: "when there are 3 or more assets in the same transaction, Divly will import them as deposits and withdrawals."

Vendor note: "you’ll need to add your public address from every wallet you use to interact with FTM"

Vendor note: "Your API key will have to be renewed every 3 months."

Vendor note: "If you have performed margin trading on Gate please check with Divly support to see if this can be imported correctly."

Vendor note: "Futures history - the API only provides the last 180 days. Older transactions can be imported via CSV."

Vendor note: "Gate.io data is currently supported via CSV import only."

ZenLedger's guide says it supports this platform but does not state the import method for it.

Blockpit's help article says the automatic import has ended; new transactions only via Blockpit's Excel template (CSV) or manual entry. Vendor note: "Automated Gemini integration has been discontinued as of Oktober 2026."

Vendor note: "If you have made BCH trades these can't be automatically imported via the API."

Vendor note: "Certain internal transactions on EVM chains (e.g., withdrawal transactions related to wrapping; deposit transactions related to bridging) can currently not be imported automatically in all cases."

Vendor note: "you’ll need to add your public address from every wallet you use to interact with xDAI"

Listed as "Gnosis Chain" on TokenTax's integrations page, which does not state the import method.

Blockpit's help article says automatic sync for Harmony has been discontinued; existing integrations became manual and new transactions only go in via Blockpit's CSV template or manual entry. Vendor note: "Automatic sync for Harmony integrations has been discontinued."

CSV file downloaded from the Harmony Block Explorer; re-download it to include the latest transactions. Vendor note: "Divly will assume all transactions are "ONE"."

Address sync is a partial import: NFTs, parts of LP transactions and bridge transfers may be missing, gas fees are slightly overestimated, and it syncs at most 10k transactions. Vendor note: "This API can sync a maximum of 10k transactions"

TokenTax says this integration is in BETA. Vendor note: "Transactions from this API should be reviewed for accuracy once imported." Import is by wallet address; Harmony is not on its integrations page.

Vendor note: "you’ll need to add your public address from every wallet you use to interact with HBAR"

Vendor note: "Spot Market Trades older than 3 months are not available via API."

CoinLedger's only stated method is mapping your export into CoinLedger's own CSV format; no dedicated importer is named. The page is titled Huobi Global.

Vendor note: "Trades are limited to only the last 4 months. If your account is older than this, you will need to import CSV files for any older trades"

Listed as "Huobi (HTX)" on TokenTax's integrations page, which does not state the import method.

ZenLedger's guide says it supports this platform but only describes import methods in general terms, not for this platform. The page is titled Huobi.

Internal moves inside your Hyperliquid account (Spot/Perp, sub-accounts, vault and staking deposits) are deliberately not imported. Vendor note: "An API key or secret is not required."

Import is by wallet address only. CoinLedger books realised perpetual results as margin gain or loss and says the tax treatment of perpetuals and funding is unsettled. Vendor note: "No API keys or CSV files are required."

Syncs up to 10,000 transactions per wallet. Vendor note: "This integration can sync up to 10,000 transactions per wallet"

Listed as "Hyperliquid" on TokenTax's integrations page, which does not state the import method.

Blockpit's help article says the automatic import has ended; new transactions only via Blockpit's Excel template (CSV) or manual entry. Vendor note: "Automated Indodax integration has been discontinued as of Oktober 2026."

CoinLedger's only stated method is mapping your export into CoinLedger's own CSV format; no dedicated importer is named. Vendor note: "Import your transaction history directly into CoinLedger by mapping the data into the preferred CSV file format."

Listed as "Injective" on TokenTax's integrations page, which does not state the import method.

Covers IOTA Rebased, including the genesis airdrop balance from the IOTA Stardust snapshot. Vendor note: "IOTA Rebased transactions can be imported automatically"

Covers the IOTA Rebased network (live since May 2025); the old mainnet is a separate legacy integration. Vendor note: "Koinly supports the new IOTA network"

Native KAS auto-sync is paused until an integration update ships, and KRC-20 token support was discontinued in Sep 2026 (enter them manually or via CSV template). Vendor note: "Will resume automatic synchronization once the upcoming integration update is deployed."

Syncs one address at a time; add a separate Koinly wallet per Kaspa address. Vendor note: "This integration can only sync one address at a time."

Vendor note: "This integration imports both Cosmos SDK transactions as well as EVM transactions." A kava... or 0x address can be used.

Listed as "Kava" on TokenTax's integrations page, which does not state the import method.

Vendor note: "CoinLedger imports Kraken margin trades through the API method only, not through CSV."

Vendor note: "NFT purchases and sales are not fully detailed — exports show the crypto used, but not full NFT metadata"

Vendor note: "Koinly cannot currently import stock transactions, only the fiat (USD) part will be imported."

TokenTax's help article says new API connections are not currently possible; new/missing data via CSV. Vendor note: "Due to changes on Kraken's end, new API connections are not currently possible."

ZenLedger's guide says it supports this platform but does not state the import method for it.

Vendor note: "Transactions older than 365 days are not available via API."

Vendor note: "Note that KuCoin restricts API access for US users, so if you are in the US, use the file upload."

Vendor note: "The API is quick to set up but only returns the last 6 months of trades, making it less suitable for a complete tax report."

Vendor note: "Most of KuCoin's endpoints can't provide data older than 1 year. For historical transactions, CSV import is recommended"

TokenTax's help article says new API connections are not currently possible; new/missing data via CSV. Vendor note: "Due to changes on KuCoin's end, new API connections are not currently possible."

Vendor note: "Due to exchange limitations, we are unable to import transactions before 2/9/2019 via API, so you will need to reach out to Kucoin's support team to obtain an Excel sheet of those transactions and then convert it to our custom CSV format."

Since the Kusama Asset Hub migration, new transactions import via the Kusama Asset Hub integration and older ones only via the Kusama (legacy) integration. Vendor note: "old KSM transactions prior to the migration date are only available via the"

Imports from both the Kusama Relay Chain and Kusama Asset Hub. Vendor note: "This integrations imports transactions both from Kusama Relay Chain and Kusama Asset Hub."

Listed on Blockpit's LBank integration page (“Full LBank support”); no LBank-specific help article was in the help collections, so the import method is not stated.

CoinLedger's only stated method is mapping your export into CoinLedger's own CSV format; no dedicated importer is named. Vendor note: "Import your transaction history directly into CoinLedger by mapping the data into the preferred CSV file format."

File import only; Koinly recommends CSV over the LBank API. Vendor note: "The LBank API only returns trades only for last 7 days and only mainnet coins."

Vendor note: "The Ledger Live CSV covers basic transaction history but does not include enough detail for NFTs."

Listed as "Ledger Live" on TokenTax's integrations page, which does not state the import method.

Vendor note: "Certain internal transactions on EVM chains (e.g., withdrawal transactions related to wrapping; deposit transactions related to bridging) can currently not be imported automatically in all cases."

Listed as "Linea" on TokenTax's integrations page, which does not state the import method.

Blockpit's wallet-integration guide says Litecoin may need an extended public key (xpub), which it now detects automatically.

Vendor note: "We recommend syncing your XPUB (extended public key) rather than individual addresses."

Listed as "Litecoin" on TokenTax's integrations page, which does not state the import method.

CoinLedger's only stated method is mapping your export into CoinLedger's own CSV format; no dedicated importer is named. Vendor note: "Import your transaction history directly into CoinLedger by mapping the data into the preferred CSV file format."

Divly recommends its API import. Vendor note: "Luno CSV files are quite complex since the trades are duplicated in both currency's when exporting the files."

TokenTax imports Luno's downloaded statement per wallet. Vendor note: "Luno data is currently supported via CSV import only."

Listed as "Mantle" on TokenTax's integrations page, which does not state the import method.

CoinLedger's only stated method is mapping your export into CoinLedger's own CSV format; no dedicated importer is named. Vendor note: "Import your transaction history directly into CoinLedger by mapping the data into the preferred CSV file format."

Vendor note: "API is in beta so may not be fully functional"

Vendor note: "Interactions with smaller or newer protocols may import as uncategorized and need a quick manual label."

Vendor note: "Metamask does not have a native export function."

TokenTax's Ethereum wallets help article explicitly covers MetaMask via public address import.

Vendor note: "Spot Market Trades older than 30 days are not available via API."

Vendor note: "MEXC limits each export to 365 days, so export one file per year of trading."

Divly recommends its file import. Vendor note: "the API is limited to 7 days of trading history which is not enough for tax purposes"

Vendor note: "This API only gives access to the most recent 7 days of trade history"

Listed as "MEXC" on TokenTax's integrations page, which does not state the import method.

Blockpit's help article says automatic sync for Moonbeam has been discontinued; existing integrations became manual and new transactions only go in via Blockpit's CSV template or manual entry. Vendor note: "Automatic sync for Moonbeam integrations has been discontinued."

Blockpit says MultiversX is in maintenance mode: its data provider cannot index blocks after 25,377,294, so new transactions must be added manually. Vendor note: "Affected users currently need to add their new transactions manually."

Koinly lists this under its former name Elrond. Vendor note: "Formerly Elrond, MultiversX (EGLD)"

Koinly's notes say auto-compounded staking rewards have to be added manually to the staking pool wallet, and staking transfers need tagging as 'Add to Pool' or 'Receive from Pool'.

Vendor note: "Make sure to download the CSV file every time you want to include the latest transactions."