Platforms / Bitpanda
exchange
MiCA entities linked
Bitpanda
Bitpanda typically supports API and/or CSV in EU tax tools. Export Fusion / Earn lines explicitly when present.
1. Data access
Export / sync paths we track for tax-history reconstruction.
API
- Create a Bitpanda API key with read permissions
- Connect in tax software as Bitpanda
spot many transferssome savings / Fusion products
CSV export
- Download Bitpanda transaction history CSV
- Import via software mapper
fills API gaps
Recommended together with API sync when available.
2. Known gaps
Where API or CSV usually fails.
| Activity | API | CSV | Notes |
|---|---|---|---|
| Spot trades | Yes | Yes | |
| Savings / Fusion | Partial | Often | Force CSV if missing |
3. Tax software that can ingest Bitpanda
From the CryptoTax Digest integrations matrix.
| Software | Support | Sync | Notes |
|---|---|---|---|
| Awaken | api | automatic | Captured 2026-07-17 |
| Blockpit | api | automatic | Captured 2026-07-17 |
| Waltio | api | automatic | Bitpanda API + file — Waltio help Platforms & Exchanges |
4. Regulatory snapshot (MiCA)
Linked legal entities when curated — never equate brand ≡ licence.
- Bitpanda GmbH (casp)
- Bitpanda Asset Management GmbH (casp)
Brand ≠ licence. Open each legal entity page before asserting MiCA authorisation.
Caveats
- Multiple Bitpanda legal entities may appear on MiCA — link all relevant ones
- UI export labels change — re-verify yearly
Educational — not tax, legal, or licence advice. Data-access grades are about reconstructable history, not solvency or security.