Why Bitstamp Tax Reporting Is More Involved Than It Looks
Long-term holders and the multi-year basis problem
Bitstamp is one of the oldest continuously operating crypto exchanges, founded in 2011. That history creates a specific tax problem: users who bought BTC or ETH on Bitstamp years ago and are selling now need basis records that go back to the original acquisition - not just the current tax year. A yearly summary or a third-party sync only covers recent activity. The raw v2 CSV is the only way to prove the full lot history. Five things that add complexity to a Bitstamp tax year:
- If you bought BTC in 2015 and sold in 2025, the basis calculation requires those 2015 acquisition records - not just the 2025 sales
- Bitstamp handles multiple base currencies (EUR, USD, GBP) - the fiat equivalent of each trade depends on which currency was used at the time
- XRP transfers and ledger-specific operations can look similar to taxable disposals in the raw file if not handled correctly
- Bitstamp staking rewards need income treatment when received, separate from the later disposal calculation
- Third-party syncs and yearly summaries may not capture all row types - the v2 CSV export is the more complete source
Bitstamp does not issue tax forms
Bitstamp's public documentation is much clearer on transaction history exports, API access, and third-party tool integrations than on platform-issued tax forms. Bitstamp does not issue forms such as 1099-DA. The raw transaction-history CSV is your primary record regardless of which country you file from - there is no platform form to cross-check against.
How to Export Your Bitstamp Transaction History
The account activity history export
For this page, start with Bitstamp's account activity history export on the web platform:
- Log in to Bitstamp on the web.
- Open your account activity history - Bitstamp's official tutorial says this is where you can review and export past activity as a data file.
- Export the full history you need as the standard v2 CSV.
- If your history spans many years, export the full range rather than individual months - the complete lot sequence is required for basis to work correctly.
Pull the raw CSV first, then use any third-party sync or yearly summary as a cross-check rather than as the primary upload.
API endpoints as a completeness check
Bitstamp's official API exposes user_transactions and crypto-transactions endpoints. If you want to verify completeness against the CSV export, those endpoints can confirm whether all rows are present. For most users, the standard v2 CSV export from the web platform is sufficient.
Bitstamp Products and Their Tax Treatment
Spot trades - BTC, ETH, XRP, and other pairs
Selling crypto for fiat, exchanging one token for another, and spending appreciated crypto are typically taxable disposal events in all seven countries DYOR.tax supports. Bitstamp's spot market covers BTC, ETH, XRP, LTC, and other pairs traded against EUR, USD, and GBP. The cost basis of each lot, the holding period, and the sale proceeds determine the gain or loss on each trade.
Bitstamp Earn and staking rewards
Bitstamp staking rewards typically need income treatment when received - the fair market value at receipt is usually the taxable amount, and that same value sets the cost basis for any later disposal. Keep those reward rows in the CSV rather than filtering them before uploading. A staking reward received in December is a December income event even if you do not sell the tokens until next year.
XRP transfers and ledger notes
XRP has specific on-ledger transfer mechanics - the XRP Ledger requires a destination tag and reserves a minimum XRP balance on new addresses. In a Bitstamp export, XRP movements can appear that resemble deposits or withdrawals rather than standard buy/sell rows. Keep those rows intact in the CSV so transfers can be correctly separated from disposals in the basis calculation.
How DYOR.tax Processes Your Bitstamp CSV
What's in the report
DYOR.tax processes Bitstamp's v2 CSV, reconstructs supported buys, sells, transfers, and income events, and applies the correct country method: FIFO, LIFO, or HIFO for US filers; Section 104 pooling for UK filers (same-day and 30-day matching included); ACB for Canadian filers; FIFO for Australian, New Zealand, Indian, and South African filers. The output is a filing-ready report with lot-by-lot basis tracking and trade-level detail.
Supported countries
Bitstamp serves both EU and US users. DYOR.tax supports seven countries: United States, United Kingdom, Canada, Australia, New Zealand, India, and South Africa. Select the country in the calculator before generating the report.
Also available
If you used other exchanges alongside Bitstamp, the Kraken tax calculator, Coinbase tax calculator, and Revolut tax calculator follow the same CSV-upload flow and support the same seven countries.
Country-Specific Tax Treatment
The Bitstamp CSV is the raw input. The filing rules come from your home tax authority:
- US: IRS treats digital assets as property. Spot sales, swaps, and staking rewards are reportable. FIFO, LIFO, and HIFO all available. Full lot history from original purchase date required.
- UK: HMRC Section 104 pooling with same-day and 30-day matching. Crypto-to-crypto swaps are disposals. Staking receipts typically taxed as miscellaneous income first.
- Canada: CRA Adjusted Cost Base method. Multi-currency trades need fiat conversion to CAD at the transaction date. Disposals include sells, swaps, spending, and gifting.
- Australia: ATO FIFO. Most disposals including swaps trigger CGT events. Longer-term holdings may qualify for the 50% CGT discount.
- India: 30% flat tax on VDA gains plus surcharge and cess. Staking income separately reportable.
- New Zealand: IRD intent-based income test. Most crypto taxed as income rather than capital gain.
- South Africa: SARS revenue vs capital distinction. FIFO applied in DYOR.tax reports.
If staking rewards are part of your filing question, our staking tax guide explains how receipt and later disposal are typically handled in each jurisdiction.