Exchange setup guides

Use these simple setup notes when a taxpayer needs help choosing API access or CSV upload.

Quick rule

Start with the simplest path

If the taxpayer already has export files, CSV upload is usually the easiest first step. Use API mode when you want ongoing account pulls from a supported exchange.

Luno

South African investors who want read-only account pulls or a Luno CSV fallback.

Luno is a strong first-choice connection when the taxpayer already has a clean read-only API key available.

Recommended starting mode: API key

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.

Open related page

VALR

South African users who want exchange history pulled automatically from VALR.

VALR works well in API mode when the user is comfortable creating a read-only key.

Recommended starting mode: API key

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.

Open related page

Binance

Users who need Binance history and want ongoing pulls instead of manual exports.

Binance is usually best in API mode when you want repeated pulls and fewer manual uploads.

Recommended starting mode: API key

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.

Open related page

Bybit

Users who need a Bybit source and want read-only history syncing.

Bybit can be saved in API mode for automated pulls or with CSVs if the user prefers a lighter setup.

Recommended starting mode: API key

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.

Open related page

MetaMask / EVM address

MetaMask users who want to import wallet activity by public address instead of CSV.

EVM wallet address mode imports public transfer history without asking for private wallet credentials.

Recommended starting mode: Public wallet address

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.

Open related page

Solana wallet address

Solana users who want to import wallet activity by public address instead of CSV.

Solana wallet address mode imports public activity without asking for private wallet credentials.

Recommended starting mode: Public wallet address

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.

Open related page

Bitcoin wallet address

Bitcoin self-custody users who want to import BTC address activity without CSV files.

Bitcoin wallet address mode imports public BTC movement history without asking for private wallet credentials.

Recommended starting mode: Public wallet address

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.

Open related page

MetaMask / wallet CSV

Self-custody activity from MetaMask, block explorers, and wallet-history exports.

Wallet CSV mode keeps self-custody activity separate from exchange history and avoids handling private keys.

Recommended starting mode: CSV upload

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.

Open related page

Coinbase

Users who already exported Coinbase history and want a clean CSV-first import path.

Coinbase is currently handled through manual exports so the taxpayer can move forward without API setup.

Recommended starting mode: CSV upload

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.

Open related page

Kraken

Users with Kraken exports who want a straightforward manual import path.

Kraken is supported today as a CSV-first source so you can keep the reporting workflow moving.

Recommended starting mode: CSV upload

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.

Open related page

Manual CSV

Anyone who wants the simplest path: export files from the exchange, then upload them manually.

CSV upload is often the calmest place to start, especially when the user just wants to finish the report quickly.

Recommended starting mode: CSV upload

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.

Open related page

Preparing workspace

Loading the latest tax workspace context

We're checking your organization, active taxpayer, and operational state so the next screen arrives in a clean, trustworthy state.

This usually only takes a moment.

Exchange setup guides

Use these simple setup notes when a taxpayer needs help choosing API access or CSV upload.

Quick rule

Start with the simplest path

If the taxpayer already has export files, CSV upload is usually the easiest first step. Use API mode when you want ongoing account pulls from a supported exchange.

Luno

South African investors who want read-only account pulls or a Luno CSV fallback.

Luno is a strong first-choice connection when the taxpayer already has a clean read-only API key available.

Recommended starting mode: API key

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.

Open related page

VALR

South African users who want exchange history pulled automatically from VALR.

VALR works well in API mode when the user is comfortable creating a read-only key.

Recommended starting mode: API key

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.

Open related page

Binance

Users who need Binance history and want ongoing pulls instead of manual exports.

Binance is usually best in API mode when you want repeated pulls and fewer manual uploads.

Recommended starting mode: API key

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.

Open related page

Bybit

Users who need a Bybit source and want read-only history syncing.

Bybit can be saved in API mode for automated pulls or with CSVs if the user prefers a lighter setup.

Recommended starting mode: API key

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.

Open related page

MetaMask / EVM address

MetaMask users who want to import wallet activity by public address instead of CSV.

EVM wallet address mode imports public transfer history without asking for private wallet credentials.

Recommended starting mode: Public wallet address

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.

Open related page

Solana wallet address

Solana users who want to import wallet activity by public address instead of CSV.

Solana wallet address mode imports public activity without asking for private wallet credentials.

Recommended starting mode: Public wallet address

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.

Open related page

Bitcoin wallet address

Bitcoin self-custody users who want to import BTC address activity without CSV files.

Bitcoin wallet address mode imports public BTC movement history without asking for private wallet credentials.

Recommended starting mode: Public wallet address

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.

Open related page

MetaMask / wallet CSV

Self-custody activity from MetaMask, block explorers, and wallet-history exports.

Wallet CSV mode keeps self-custody activity separate from exchange history and avoids handling private keys.

Recommended starting mode: CSV upload

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.

Open related page

Coinbase

Users who already exported Coinbase history and want a clean CSV-first import path.

Coinbase is currently handled through manual exports so the taxpayer can move forward without API setup.

Recommended starting mode: CSV upload

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.

Open related page

Kraken

Users with Kraken exports who want a straightforward manual import path.

Kraken is supported today as a CSV-first source so you can keep the reporting workflow moving.

Recommended starting mode: CSV upload

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.

Open related page

Manual CSV

Anyone who wants the simplest path: export files from the exchange, then upload them manually.

CSV upload is often the calmest place to start, especially when the user just wants to finish the report quickly.

Recommended starting mode: CSV upload

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.

Open related page