Do Koinly and CoinTracker Work for Casino Deposits? What Breaks

In this article
  1. The Problem: What a Tracker Sees at a Casino Address
  2. How Each Tracker Reads Casino Flows by Default
  3. The Manual Tagging That Fixes It
  4. The Workflow We Recommend
  5. Verdict: Useful Engines, Blind Drivers
  6. Default Classification, Side by Side
  7. Casino Flow to Tag: A Quick-Reference Map

The Problem: What a Tracker Sees at a Casino Address

Picture the typical setup: a single gambling wallet with a few months of history — BTC and USDT-on-Tron deposits to several casinos, winning withdrawals coming back, a couple of coin swaps in between — synced to Koinly or CoinTracker by wallet address, with no CSVs and no manual entry, the way most players do it.

The core problem is structural: a casino deposit address looks like any other unknown address on-chain. The tracker sees coins leaving your wallet and has three guesses — a transfer to another wallet you own, a payment, or a sale. It has no way to know a casino sits on the other end, and no tracker we know of maintains a database of casino deposit addresses.

How Each Tracker Reads Casino Flows by Default

Left on automatic, both tools misclassify the same events in slightly different ways:

  • Deposits to casinos — Koinly treats them as a generic "Send" (a withdrawal to an unknown address); CoinTracker tends to mark them as "Transfer" and, crucially, can assume the destination is another wallet you own, treating a taxable disposition as a tax-free shuffle.
  • Winning withdrawals — both see incoming coins from an unknown address as a plain "Receive" or "Deposit" with zero cost basis. Left unfixed, that quietly turns your entire winnings into a fake capital gain when you later sell.
  • Losing sessions — invisible. Coins go out, nothing comes back, and the trackers carry a phantom "transfer out" forever.
  • Swaps and network fees — the one thing both handle correctly without help, including fee-as-disposition on Ethereum.

The Manual Tagging That Fixes It

Both trackers become usable once you re-tag casino transactions by hand. In Koinly, the workable pattern is marking casino deposits so they register as dispositions at fair market value rather than transfers — and tagging withdrawals of winnings so the incoming coins get a cost basis equal to their value on receipt, consistent with the windfall treatment we describe in the main CRA winnings guide. Koinly's "lost" and "gift" style tags exist, but be careful: "lost" is designed for stolen or inaccessible coins, not gambling losses, and using it to write off losing sessions is an aggressive position for a recreational player whose losses are not deductible anyway.

In CoinTracker the equivalent is reclassifying the auto-detected "Transfer" into a send/spend category and manually setting the received-side cost basis. Neither tool has a native "gambling" category as of early 2026 — everything is a workaround, and the workaround has to be applied to every casino transaction, every tax year.

The Workflow We Recommend

Keep one wallet exclusively for gambling, so every unknown counterparty in that wallet is by definition a casino — that single decision turns hours of forensic guessing into a batch re-tag. Sync the tracker monthly rather than at tax time, while you still remember which session was which. Keep your own one-line log per session (date, casino, coin, amount in, amount out) as the source of truth the tracker gets reconciled against. And prefer stablecoins for the gambling wallet where the casino supports them — flat CAD value between deposit and withdrawal means mistagged transactions cost you pennies, not thousands; see our payments guide for which sites take USDT on cheap networks.

Verdict: Useful Engines, Blind Drivers

Neither Koinly nor CoinTracker "works" for casino deposits unattended, and anyone who tells you to just sync and file is setting you up for a return full of phantom gains. But as price engines — timestamped CAD valuations for hundreds of micro-transactions feeding your ACB calculations — they are genuinely excellent, and re-tagging a dedicated gambling wallet takes an evening, not a week. That evening matters even more at no-KYC casinos, where the tracker plus your own log is the only paper trail that will ever exist.

This article is general information, not tax advice. How to classify your specific flows is exactly the kind of judgment call to make with a licensed CPA.

Default Classification, Side by Side

Both trackers publish how their transfer-detection works, and the mechanism is the same in both products: a "Transfer" is only recognized when the tracker can see both ends of the movement, meaning the receiving wallet or exchange has to be added to your account. A casino's deposit address is never something a player adds as their own wallet, so by the published logic of both tools it falls outside that pairing on the way in, and the same is true in reverse on the way out. Whether a given transaction actually lands as a clean "Transfer," a taxable "Send," or an ambiguous default depends on your account setup and sync method, which is why the terms below are described as defaults rather than guarantees.

BehaviourKoinly, by defaultCoinTracker, by default
Outgoing to a casino addressSend (disposal), unless manually tagged as a transferSend by default; becomes a Transfer only if that address is added as a wallet you own
Incoming from a casinoReceive, cost basis set to value at the time it landsReceive, cost basis set to value at the time it lands
Counted as a disposalYes, unless the deposit leg is retaggedYes, unless the deposit leg is retagged
Appears in the gains reportYes, as a disposal event at the deposit's FMVYes, as a disposal event at the deposit's FMV
What breaks on address reuseNothing technically; each transaction keeps its own hashSame — deduplication runs on transaction hash, not address

Source: Koinly and CoinTracker public documentation on transfer detection and transaction categories, September 2026.

That last row is the one worth sitting with, because it contradicts the instinct most players have. Reusing the same casino deposit address for every session doesn't confuse either tracker, and it doesn't cause double-counting — the software is built to key on the transaction hash, not the address. The real gap sits one level up: a casino's deposit address and its withdrawal-payout address are typically two different addresses for security reasons, since operators separate hot wallets that receive funds from the ones that send them out. Address-based matching, working exactly as documented, has no way to connect your deposit leg to your withdrawal leg of the same session, because the two legs never share an address to match on in the first place. Neither tool is malfunctioning when that happens — it's the expected result of how blockchain address matching is built to work.

Casino Flow to Tag: A Quick-Reference Map

Once the defaults are understood, the practical question is what to actually click for each type of casino flow. Two of these five are covered in general terms elsewhere on this page; the other three rarely get mentioned anywhere, including in either tracker's own casino-specific help material.

Casino flowCorrect tagWhat happens if you leave it untagged
Deposit to casino addressDisposal at fair market valueSits as an unlabelled Send; cost basis for the sold crypto is never recorded
Withdrawal of winningsNew receipt, cost basis = value at withdrawalOften imports with a zero or missing cost basis, inflating the eventual gain
Withdrawal of your own deposit backReturn of capital against original ACB, not a fresh acquisitionReads as a new taxable receipt, taxing money that was already yours
Conversion inside the casino balanceCrypto-to-crypto disposition at the moment of conversionInvisible — the swap happens on the casino's internal ledger, off-chain, so no tracker sees it at all
Bonus credited in coinNew acquisition, cost basis = value when creditedBlends into the withdrawal that eventually pays it out, losing its separate origin

Source: general disposition and cost-basis rules for crypto-assets, CRA crypto-assets guidance (canada.ca), September 2026.

The conversion row is the one an address-based tracker structurally cannot fix on its own. When a casino balance lets a player deposit in one coin and cash out in another — a real feature at several catalogued brands, see our USDT payment guide for which sites do this — the actual crypto-to-crypto trade never touches a public blockchain. Your synced wallet shows one coin going in and a different one coming out, with no on-chain event in between to represent the swap itself; the tracker can price both ends, but it can't reconstruct the disposition that technically happened between them without you entering it by hand.

The "return of capital" row leans on a principle the CRA applies elsewhere in its crypto-asset guidance: moving value you already own from one place you control to another isn't a new taxable event, only a change of location. A casino balance isn't a wallet in the strict sense, but the same underlying question — did ownership actually change, or did the same capital just come back — is the one to apply before accepting whatever category a tracker assigns by default, and it's exactly the kind of distinction our adjusted cost base guide works through in more detail. None of this is a substitute for advice from a licensed preparer on your specific transaction history.

Keep exploring