WhiteBIT tax: handling your WhiteBIT crypto taxes
Working out your WhiteBIT tax? WhiteBIT is a European exchange offering spot, futures and staking, plus a feature worth knowing about at tax time — WhiteBIT Codes, which move funds between users and can muddle your history. This guide covers what WhiteBIT provides, how its activity is taxed, how to export your full record, and how CryptaTax files it. General information, not tax advice.
General information, not tax advice. What WhiteBIT reports and which documents it offers can change and varies by country, and the treatment of futures differs by jurisdiction — verify against WhiteBIT and your local tax authority or a qualified advisor.

Does WhiteBIT report your crypto to the tax authorities?
Whether WhiteBIT shares data with your tax authority depends on your country and changes over time, so do not treat “they won't know” as a plan. Exchanges are increasingly inside information-reporting frameworks that push account and transaction data to tax authorities, and that net is widening, not narrowing. The safe approach is to assume your WhiteBIT activity is visible and to report it correctly — which is exactly what a clean, reconciled WhiteBIT tax report lets you do.
Whatever WhiteBIT does or does not file on your behalf, the legal duty to report your gains and income is yours. That is why getting your full history out of WhiteBIT and reconciling it properly matters more than whether a particular summary lands in your inbox.
What WhiteBIT tax documents you can get
Like most exchanges, WhiteBIT can hand you raw data and sometimes summaries, but it generally cannot produce your final tax numbers — because it only sees what happened on WhiteBIT, not the coins you moved in from a wallet or another exchange. From your account you can usually obtain:
- a transaction history export (CSV or similar) covering your activity, deposits and withdrawals;
- an order / trade history showing each fill with its fees;
- sometimes a gain/loss or account summary, whose accuracy still depends on whether your full cost-basis picture is present — which on a single exchange it rarely is.
The catch with anything WhiteBIT generates on its own is cost basis and scope. If you sent coins to WhiteBIT that you bought elsewhere, WhiteBIT does not know what you paid, so any gain it shows can be wrong. Reliable numbers come from combining your WhiteBIT history with every other wallet and exchange you use — the job CryptaTax does.
Types of WhiteBIT activity and how each is taxed
A single WhiteBIT account usually mixes several kinds of activity, and each is taxed differently. Sorting your history into these buckets is most of the battle — the sections below cover the WhiteBIT-specific ones in full.
Spot trades
Each spot disposal is a capital gain or loss — proceeds minus cost basis.
Futures
WhiteBIT's futures produce realized PnL and funding in a separate ledger, taxed differently from spot in most countries.
Staking rewards
Staking and earn rewards are usually income at their value on receipt, then carry that value as basis.
WhiteBIT Codes and transfers
Codes and ordinary deposits/withdrawals move your own funds and are transfers, not sales — but they need correct classification (below).
WhiteBIT Codes and internal transfers
The WhiteBIT-specific thing to watch is WhiteBIT Codes — redeemable vouchers that move balances between accounts. In your history a code can look like a deposit or a withdrawal, but economically it is usually just your own funds moving, or a transfer to or from someone else, rather than a trade. Classified naively, a code can be mistaken for an acquisition or a disposal and distort your numbers.
The fix is the same discipline as any transfer: identify what the code actually represents and match it to the corresponding leg, so it is not booked as a phantom buy or sale. CryptaTax treats code-driven movements as transfers by default and lets you confirm the few that are genuinely income or gifts, so your WhiteBIT history reconciles cleanly.
Futures and staking on WhiteBIT
Beyond spot, WhiteBIT runs futures and staking. Futures produce realized PnL and funding in their own ledger and are taxed differently from spot disposals in most countries — capture the full record and apply your rules. Staking rewards are generally income at their value on receipt, with that value carried forward as cost basis. Both are easy to miss in a spot-only export, so CryptaTax reads them separately and classifies each correctly.
WBT, cashback and referral rewards
WhiteBIT has its own token, WBT, and runs cashback, referral and promotional programmes around it. The tax point is easy to miss: tokens or cashback you receive for trading, referring a friend or holding WBT are generally income at their value when they land in your account, and that value then becomes the cost basis for an eventual sale. Because these arrive as small, irregular credits rather than trades, a plain trade export tends to skip them entirely. If you later cash out or spend that WBT, it is a separate disposal measured against the basis set when you received it. CryptaTax reads reward and cashback inflows, values them on receipt, and carries the basis forward so the later disposal is right too.
How to export your full WhiteBIT transaction history
You have two ways to get your data out, and the choice mainly affects how much manual work is left over:
- API connection (recommended) — create a read-only API key in your WhiteBIT account and connect it to CryptaTax. This pulls your history automatically and keeps it current, with no spreadsheets to download each time.
- CSV export — download your history from WhiteBIT and import it. This works everywhere but is a snapshot, so you repeat it whenever you trade again, and you must export each ledger, not just one.
Whichever you choose, make sure the export covers your entire time on WhiteBIT, not just the current tax year. Cost basis depends on when you first acquired each coin, so a partial history produces partial — and usually wrong — numbers.
Common WhiteBIT reconciliation issues
Most wrong WhiteBIT tax figures come from a handful of recurring problems. Knowing them up front saves hours of clean-up:
- Transfers in and out of WhiteBIT — moving your own coins between WhiteBIT, a wallet or another platform is not a sale, but naive tools record it as one and invent a gain. Both legs must be matched.
- Missing cost basis — coins bought elsewhere and sold on WhiteBIT have no basis in the WhiteBIT export alone; the basis has to come from the source.
- Fees — trading and withdrawal fees affect your gain and must be attributed correctly.
- WhiteBIT Codes — can look like deposits or withdrawals but are usually transfers; classify them correctly.
- Futures ledger — perpetual PnL and funding are separate from spot.
- Staking rewards — income receipts a trades-only export can miss.
How CryptaTax does your WhiteBIT taxes for you
CryptaTax connects your WhiteBIT account alongside every other wallet and exchange you use, then does the reconciliation the export cannot:
- Import your complete WhiteBIT history by read-only API or CSV.
- Match transfers between WhiteBIT and your other accounts so they are not taxed as disposals.
- Classify trades, futures PnL, staking rewards and conversions and rebuild cost basis across every source using a consistent method.
- Produce a report — capital gains and income — ready to file or hand to your accountant, with each figure traceable to its source transaction.
The result is one set of numbers for your whole portfolio, with WhiteBIT as one input among many, rather than a stack of exports you stitch together by hand. Import your exchanges and wallets → · Crypto tax calculator →
Why your WhiteBIT numbers are only part of the picture
It bears repeating because it is the root of most errors: WhiteBIT can only ever report on what happened inside WhiteBIT. The moment you move coins to a wallet, trade on a second exchange, or earn rewards on-chain, your true tax position spans sources none of them sees in full. A figure that looks authoritative on a WhiteBIT statement can still be wrong for your return, simply because WhiteBIT is missing context it never had. CryptaTax treats WhiteBIT as one feed among many and reconciles across all of them, which is the only way to get a number that holds up.
Setting up the WhiteBIT connection safely
When you connect WhiteBIT to any tax tool, use a read-only API key. A read-only key lets the tool see your history but cannot trade, withdraw or move funds — so even if it leaked, your assets are safe. A few sensible habits:
- create the key with read-only / view permissions only — never enable trading or withdrawals;
- if WhiteBIT offers IP allow-listing, restrict the key where practical;
- name the key so you remember what it is for, and revoke it if you stop using the tool;
- prefer the API connection over emailed CSVs, which can sit unencrypted in your inbox.
CryptaTax only ever needs to read your WhiteBIT history to do the maths; it never needs the ability to move your funds, and you stay in full control of your account.
Mistakes to avoid with your WhiteBIT taxes
- Only exporting the current year — cost basis depends on your full history on WhiteBIT.
- Trusting a single gain/loss summary blindly — it cannot know the basis of coins you moved in from elsewhere.
- Ignoring transfers — your own moves in and out of WhiteBIT are not sales; treat them as transfers or you will overpay.
- Booking a WhiteBIT Code as a buy or sale — most are transfers and should be matched, not taxed.
- Skipping the futures ledger — perpetual PnL is taxable in its own right.
Your WhiteBIT tax checklist
- export or connect your full WhiteBIT history, from your first transaction;
- connect every other wallet and exchange so transfers can be matched;
- classify WhiteBIT Codes as transfers (or confirm the few that are income/gifts);
- include futures PnL and staking rewards, not just spot trades;
- apply a consistent cost-basis method allowed in your country;
- produce a report where every figure traces back to a source transaction.
Work through that list once and your WhiteBIT taxes stop being a guess. CryptaTax does every step of it for you, turning a year of WhiteBIT activity into numbers you can stand behind.
Other exchanges and wallets
Use more than one venue? That is the norm, and it is exactly why an exchange's own numbers fall short. Connect each one so your report covers everything: Binance, KuCoin, OKX, Bybit, or see the full integrations list.
FAQ
It depends on your country and changes over time. Exchanges are increasingly inside information-reporting frameworks, and the trend is toward more data-sharing, not less. Assume your WhiteBIT activity is visible and report it correctly.
Usually a transaction history export and a trade history, and sometimes an account or gain/loss summary. Any summary WhiteBIT produces can be wrong for coins you moved in from elsewhere, because it does not know their original cost basis.
A WhiteBIT Code usually moves your own funds or transfers value to or from another person, so it is generally not a sale. It should be matched as a transfer rather than booked as a buy or disposal — CryptaTax treats them as transfers by default.
Moving your own coins between WhiteBIT and a wallet you control is not a taxable sale. It only looks like one if a tool fails to match the two legs — which CryptaTax does automatically.
Connect WhiteBIT to CryptaTax by read-only API key or CSV, let it reconcile your history with your other wallets and exchanges, and it produces a capital-gains and income report ready to file.
All the way to your first transaction on WhiteBIT. Cost basis depends on when you acquired each coin, so a partial export produces partial — and usually wrong — numbers.