If the taxpayer already has export files, CSV upload is usually the easiest first step. Use API mode only when the source has a controlled read-only credential path and the beta status below supports it.
Recommended starting mode: API key
Beta source status: api-beta
Read-only API credential validation and live-sync imports are wired for private beta, with CSV retained as the evidence fallback.
Use read-only API keys only; if a live pull is incomplete or fails, upload Luno CSV exports before relying on the estimate.
Setup steps
- Open Luno in a browser and go to Profile, Security, or API Keys.
- Create a new API key named SARS CryptaTax Staging.
- Enable read-only balances, account transactions, order or trade history, and transfer history.
- Keep withdrawals, sends, trading, and account-management permissions disabled.
- Paste the key ID and secret into Connect accounts, validate once, then rotate the key after the test sprint if needed.
Notes
- Use a simple source name like 'Russell Luno account'. It does not need to match Luno exactly.
- If the taxpayer already exported files, CSV upload is still a good fallback.
- The app stores the secret encrypted and only shows a masked key hint after saving.
Recommended starting mode: API key
Beta source status: api-beta
Read-only API credential validation and live-sync imports are wired for private beta, with CSV retained as the evidence fallback.
Use read-only API keys only; if a live pull is incomplete or fails, upload VALR trade and wallet-history exports before relying on the estimate.
Setup steps
- Open VALR and go to API Keys from account settings.
- Create a read-only API key for history access.
- Paste the API key and secret into Connect accounts.
- Leave trading and withdrawals disabled.
Notes
- The source name is your own internal label, not a strict VALR account identifier.
- Use CSV mode if the taxpayer wants the fastest manual path instead.
Recommended starting mode: API key
Beta source status: api-beta
Read-only API sync is wired for spot, deposits, withdrawals, margin, futures income, convert, and earn reward rows in private beta.
Use read-only API keys only; keep Binance CSV exports for advanced products, incomplete permissions, or live-pull gaps.
Setup steps
- Open Binance on the web and go to Account, then API Management.
- Create a system-generated API key named SARS CryptaTax Staging.
- Allow only read-only account information, spot trade history, wallet deposit or withdrawal history, and the extra read-only history areas you used, such as futures, margin, convert, or earn.
- Keep withdrawals, universal transfer, trading, margin trading, and futures trading permissions disabled.
- Paste the API key and secret into Connect accounts, validate once, then revoke or rotate after testing if this is a temporary key.
Notes
- Use a clear source name like '2026 Binance account' so it stays easy to recognize later.
- If Binance asks for IP restrictions and there is no fixed server IP yet, treat the key as temporary and revoke it after testing.
- If the key setup feels like too much, upload CSVs manually first and come back later.
Recommended starting mode: API key
Beta source status: api-beta
Read-only API credential validation and live-sync imports are wired for private beta, including spot execution, transaction-log, deposit, withdrawal, and borrow-interest rows.
Use read-only API keys only; if a live pull is incomplete or fails, upload Bybit statements or CSV exports before relying on the estimate.
Setup steps
- Open Bybit on the web and go to Account and Security, then API Management.
- Create a system-generated API key named SARS CryptaTax Staging.
- Enable read-only unified account balances, transaction logs, spot execution history, deposit records, withdrawal records, and asset history.
- Keep withdrawals, orders, trading, sub-account transfer, and account settings permissions disabled.
- Paste the API key and secret into Connect accounts, validate once, then revoke or rotate after testing if this is a temporary key.
Notes
- The source name is only for the workspace. Keep it simple and recognizable.
- If Bybit exposes permission groups, choose the smallest read-only group that still exposes account and transaction history.
- CSV upload remains a valid fallback if the taxpayer already has exports ready.
Recommended starting mode: Public wallet address
Beta source status: requires practitioner review
Public address import is wired for supported chains, but DeFi, bridges, LP, NFT, and contract activity can still require review.
Use public-address import for simple transfers only; use wallet CSVs or practitioner notes for complex activity.
Setup steps
- Open MetaMask and copy the public 0x wallet address for the account you want to import.
- Choose the chain to import first: Ethereum, Polygon, Base, Arbitrum, Optimism, or Avalanche C-Chain.
- Paste only the public wallet address in Connect accounts.
- Never provide seed phrases, private keys, recovery phrases, wallet passwords, or unsigned transaction files.
- Use Pull latest activity to create the first wallet import once the address is saved.
Notes
- This beta path uses an indexer to pull historical public transfers for the selected chain.
- DeFi, bridges, LP positions, NFTs, and contract interactions may still need review after import.
- CSV remains the fallback if a chain is not supported by the address beta yet.
Recommended starting mode: Public wallet address
Beta source status: requires practitioner review
Public address import is wired, but swaps, NFTs, staking, bridges, and protocol activity can still require review.
Use public-address import for simple balance movements only; use wallet CSVs or practitioner notes for complex activity.
Setup steps
- Open Phantom, Solflare, Backpack, or the Solana wallet app you use.
- Copy the public wallet address for the account you want to import.
- Paste only the public address in Connect accounts and keep the chain set to Solana.
- Never provide seed phrases, private keys, recovery phrases, wallet passwords, or unsigned transaction files.
- Use Pull latest activity to create the first Solana wallet import once the address is saved.
Notes
- This beta path reads public Solana transaction history and converts SOL and SPL-token balance movements into import rows.
- Swaps, NFT sales, staking rewards, bridges, and complex DeFi interactions may still need review after import.
- CSV remains the fallback if an explorer or wallet export has richer labels for a specific activity set.
Recommended starting mode: Public wallet address
Beta source status: requires practitioner review
Public address import is wired for visible address activity, but multi-address wallets and ownership context can still require review.
Use public-address import for simple address history only; use wallet CSVs or practitioner notes for multi-address wallets.
Setup steps
- Open the Bitcoin wallet app or hardware-wallet companion you use.
- Copy the public receive address that has tax-year activity.
- Paste only the public address in Connect accounts and keep the chain set to Bitcoin.
- Never provide seed phrases, private keys, recovery phrases, wallet passwords, unsigned transaction files, or xprv keys.
- If your wallet rotates addresses, add each public address with activity until xpub support is added.
Notes
- Bitcoin uses a UTXO model, so a single public address only covers activity visible on that address.
- This beta path turns BTC address movements into transfer rows with miner fees separated where the data source provides them.
- CSV remains the fallback for multi-address wallets or exports with richer counterparty labels.
Recommended starting mode: CSV upload
Beta source status: csv-only
CSV import is the practitioner-beta fallback for self-custody and wallet exports.
Use CSV upload when public-address import does not capture enough labels or protocol context.
Setup steps
- Open MetaMask Portfolio, the relevant block explorer, or your wallet-history export tool.
- Export the full South African tax-year activity as CSV.
- Keep timestamps, transaction hashes, token symbols, in/out amounts, gas fees, chain names, and wallet labels intact.
- Never upload seed phrases, private keys, recovery phrases, wallet passwords, or unsigned transaction files.
- Save a wallet CSV source inside Connect accounts, then upload the raw export exactly as downloaded.
Notes
- If the export has separate amount-in and amount-out columns, the importer will infer transfer direction where possible.
- DeFi swaps, bridges, liquidity positions, NFTs, and contract interactions may still be flagged for review until the CA edge-case pack is complete.
- Wallet address import by public address is a later automation lane; CSV is the safest first validation path.
Recommended starting mode: CSV upload
Beta source status: csv-only
Coinbase is currently a CSV-first source in practitioner beta.
Use manual CSV exports; API automation is deferred.
Setup steps
- Open Coinbase and export the account history or transaction CSV.
- Save a Coinbase source inside Connect accounts.
- Upload the CSV during setup or later from Import activity.
Notes
- Use a source name that helps you recognize the export later, like 'Russell Coinbase 2026'.
- CSV-first support keeps the setup light while broader provider automation is still expanding.
Recommended starting mode: CSV upload
Beta source status: csv-only
Kraken is currently a CSV-first source in practitioner beta.
Use manual ledger or trade CSV exports; API automation is deferred.
Setup steps
- Open Kraken and export the ledger or trade history CSV.
- Save a Kraken source inside Connect accounts.
- Upload the CSV during setup or later from Import activity.
Notes
- Use a clear source name so the uploaded files stay easy to identify later.
- Start with CSVs first, then revisit automation later if live provider support expands.
Recommended starting mode: CSV upload
Beta source status: csv-only
Manual CSV upload is the supported fallback for sources that are not live-validated.
Use CSV upload when API credentials are unavailable, unvalidated, or outside the beta source list.
Setup steps
- Save the source first so the taxpayer has a named account in the workspace.
- Upload the CSV immediately during account setup or later from Import activity.
- Review and clarify anything the normalization step could not resolve.
Notes
- Manual CSV is the safest fallback when API setup feels too technical.
- You can still convert a CSV-only source to API mode later.
