How deposits work on mobile
Connecting a wallet on a phone
The first thing to understand about depositing on a mobile crypto sportsbook is that there is usually no deposit form in the traditional sense. You are not typing card numbers into a cashier screen and waiting for an acquirer to approve you. Instead, you are moving funds from a wallet you control into a wallet the book controls, and the "deposit" is simply the moment that transfer is credited to your account balance. That distinction matters because almost every problem people hit on mobile comes from treating this like a card payment when it behaves more like a bank transfer between two accounts you can both see.
On a phone, the connection step is where most of the friction lives. Most wallet-first books, Dexsport included, let you connect by opening the site inside your wallet's built-in browser, or by scanning a WalletConnect QR code from a desktop session, or by pasting a wallet address if the book supports a plain send-to-address flow. The in-wallet browser route is the smoothest on mobile because it keeps your keys inside the wallet app and never exposes a seed phrase to a website. The trade-off is that some wallets handle in-app browsing better than others, and a few block third-party sites by default for safety.
If you are using WalletConnect, the pairing is a two-step handshake: the site shows a QR code, your wallet scans it, and both sides agree on a session. On a phone this often means you are scanning a QR that is displayed on the same phone, which is awkward. The usual fix is to open the site in one browser, screenshot or copy the connection link, and open it inside the wallet app. Some wallets now support a deep link that jumps straight from the browser to the wallet, which removes the scanning problem entirely.
The important mental model is that connecting a wallet is not the same as depositing. Connecting only proves you control an address and lets the site read your balance and request signatures. No funds move until you actually approve a transfer. A lot of first-time users assume that once the wallet is connected their balance has been "linked" and the book can pull money at will. It cannot. Every outgoing transfer needs your explicit approval, and on mobile that approval is a tap you should read carefully rather than dismiss.
One edge case worth knowing: if you connect with one address and then switch accounts inside your wallet, the site may still be pointed at the old address. Your deposit then lands from an address the book has not associated with your account, and it may take longer to credit or require support to sort out. Before you send anything, confirm the address shown in the wallet matches the one the site displays. This single check prevents a large share of "my deposit vanished" complaints.
Finally, keep your seed phrase out of the process entirely. No legitimate book, and certainly not a no-KYC one, needs it. If any site or pop-up asks you to "verify your wallet" by entering a recovery phrase, that is theft, not onboarding. On mobile, where fake pages can look convincing in a small browser window, the safest habit is to reach the site through a bookmark you created yourself rather than a link from a message or an advert.
Scanning vs pasting an address
When it is time to send funds, you have two ways to enter the destination: scan a QR code or paste a text address. Both work, and both have failure modes that are more common on a phone than on a desktop. Scanning is faster and less error-prone in principle, because the camera reads the whole string at once and you cannot mistype a character. Pasting is more deliberate and lets you inspect the address before you commit, but it depends on your clipboard behaving correctly, which on mobile is not guaranteed.
The case for scanning is strong. Crypto addresses are long and unforgiving. A single wrong character sends funds to an address that either does not exist or belongs to someone else, and there is no chargeback. A QR code encodes the full address, so the camera does the transcription. The catch is that QR codes on a phone screen are often small, and a dirty lens or a low-light room can cause the scanner to misread. Most wallets show you the decoded address before you confirm, and you should actually look at the first and last few characters rather than tapping through.
The case for pasting is that it forces a pause. When you copy an address from the book's deposit page and paste it into your wallet, you can compare the pasted string against the source. The risk here is clipboard hijacking, a real and well-documented attack where malware silently swaps a copied crypto address for the attacker's own. On mobile this is less common than on desktop but not impossible, especially on jailbroken or sideloaded devices. The defence is simple: after pasting, check that the address still matches what the site shows, character for character at the start and end.
There is a third option that many people overlook: some books generate a QR code that your wallet can scan directly, and some wallets let you paste an address and then re-display it as a QR for a second device to scan. If you have two phones or a phone and a laptop, using one to display and the other to scan removes the same-screen awkwardness and gives you a visual double-check. This is slower, but for a large first deposit it is a reasonable trade.
Edge cases matter here. Some addresses include a memo, tag, or destination tag, and omitting it can mean the funds arrive but are not credited to you. If the book's deposit page shows a memo field, treat it as mandatory unless it explicitly says otherwise. Another edge case is that some wallets truncate long addresses in the display and show an ellipsis in the middle. Never confirm based on a truncated view; open the full address or use the scanner. And if you are pasting from a chat message someone sent you, stop. Addresses should come from the book's own deposit screen, not from a person.
The practical rule our editors follow is this: scan when you can, paste when you must, and verify the ends of the address either way. The few seconds that takes is trivial next to the cost of sending funds into the void.
Choosing a network on mobile
A crypto deposit is not just an amount and an address; it is also a network. The same asset can exist on several chains, and sending it on the wrong one is one of the most common and most painful mobile mistakes. If the book expects USDT on one chain and you send USDT on another, the funds may not be credited, and recovering them can require the book's support team to intervene, sometimes at a cost, sometimes not at all.
On mobile, the network selector is easy to miss because it is often a small dropdown near the deposit address. The book will usually state which network it wants, and it may generate a different address for each supported network. Your job is to make the wallet's network match the book's network. In most wallets, the network is chosen when you pick the asset to send, so "USDT" is not enough; you are choosing "USDT on this chain" or "USDT on that chain." Read both labels before you tap send.
The trade-offs between networks are mostly about fees and speed, and they shift over time. Some chains are cheap and fast but less widely supported; others are expensive but accepted almost everywhere. A book that supports several networks is giving you a choice, and the sensible default is the one the book lists first or highlights, because that is usually the one its systems handle most reliably. If you are depositing a small amount, paying a network fee that is a large fraction of the deposit defeats the purpose, so a cheaper chain can make sense, provided the book supports it.
There is a subtle trap with tokens that share a ticker across chains. Two different chains can both have a token called the same thing, and they are not interchangeable. If you are unsure, do not guess. Check the book's deposit page again, and if it is ambiguous, deposit a small test amount first. A test deposit costs you one network fee and confirms the whole path, including the network, before you move anything significant. This is especially worth doing the first time you use a new book or a new wallet.
Another mobile-specific wrinkle is that some wallets default to the "wrong" network for a given token because of how they were set up. If your wallet shows a balance on a chain the book does not support, you may need to bridge or swap before you can deposit, which adds steps and fees. Bridging on a phone is doable but fiddly, and it introduces another contract you have to trust. Where possible, hold your deposit asset on a network the book supports so you are not forced into a bridge at the last moment.
Finally, remember that the network choice is not reversible once the transaction is confirmed. A confirmed transfer on the wrong chain cannot be recalled by you. The book may be able to help, but it is under no obligation to, and the process is slow. Treat the network selector as the single most important field on the deposit screen.
Confirming a transaction safely
The confirmation step is where you actually authorise the transfer, and on mobile it deserves more attention than the tap it usually gets. When you press send, your wallet will show a summary: the asset, the amount, the destination, the network, and the estimated fee. Read all of it. The summary is your last chance to catch a mistake before the funds leave your control, and once you sign, the transaction is broadcast and effectively final.
The signature itself is worth understanding. In most wallets you are not typing a password; you are approving with a biometric, a PIN, or a passkey. That approval cryptographically signs the transaction with your private key, which stays on your device. This is why no-KYC books can operate the way they do: the book never needs your identity, only the on-chain proof that you sent funds from an address you control. It also means that if someone else can approve on your device, they can move your funds. Keep your phone locked and your wallet app behind biometrics.
Before you confirm, check the destination address against the book's deposit page one more time, focusing on the start and end. Check the amount, and be aware of the difference between the amount you enter and the amount that arrives. The fee is deducted separately on most chains, so if you send the exact amount you want credited, you may still be fine, but on some chains the fee comes out of the sent amount. If the book requires a minimum deposit, make sure your amount clears it after fees, not before.
Watch for approval requests that are not simple transfers. Some wallets and some sites use token approvals, where you grant a contract permission to spend your tokens. A deposit to a book should normally be a plain transfer to an address, not an unlimited approval. If you are asked to approve a spending cap, read the cap. If it says unlimited and you were only expecting to deposit once, that is a red flag. You can usually set a specific amount instead.
Edge cases to keep in mind: if your phone loses signal mid-confirmation, the transaction may still broadcast, so do not assume a failed screen means nothing happened. Check the wallet's activity list and, if needed, a block explorer before retrying, or you risk sending twice. If the wallet warns that the fee is unusually high, that can be a sign of network congestion or of a malicious contract, so investigate rather than tapping through. And if you are confirming on a public network, remember that anyone nearby may be able to see your screen; a deposit address and amount are not secret, but your balance and habits are worth keeping private.
The calm version of this step is: read the summary, match the address, check the amount and network, approve with biometrics, then wait. Rushing the confirmation is how small mistakes become permanent ones.
Fees and timing on mobile
Fees on a crypto deposit come in two parts: the network fee you pay to move funds, and any fee the book charges, which is often zero on deposits. The network fee is not set by the book; it is set by the chain and by how busy it is. On mobile you usually get a choice between a slow, cheap option and a fast, expensive one, and the wallet will estimate how long each might take. Those estimates are guesses, not promises, and they can be wrong when the network is congested.
Timing depends on the chain's block time and on how many confirmations the book requires before crediting. Some books credit after one confirmation, others wait for several to reduce the risk of a chain reorganisation undoing the deposit. On a fast chain this can be seconds to a minute; on a slower or congested one it can be many minutes, occasionally longer. If your deposit has not appeared after a reasonable wait, do not panic and do not resend. Check the transaction on a block explorer first to see whether it is confirmed, pending, or failed.
Mobile adds a few timing quirks. If your phone goes to sleep or the wallet app is backgrounded during a transaction, the broadcast may still complete, but the app might not refresh to show it. Reopen the wallet and pull to refresh, or check the explorer. If you are on a metered or unstable connection, the broadcast can be delayed, which makes it look like nothing happened. A stable connection before you confirm avoids most of this.
Fee spikes are the main cost risk. On some chains, fees can jump sharply during busy periods, and a deposit that would normally cost very little can suddenly cost a noticeable amount. If you are depositing a small sum, check the estimated fee before confirming; paying a large fee to move a small amount is poor value, and waiting for a quieter period can help. Some wallets let you set a custom fee, but on mobile that is easy to get wrong, so the safer approach is to accept the wallet's suggested fee unless you know what you are doing.
There is also the question of what the book does with the fee on withdrawal, which is a separate matter but worth flagging because it affects how you think about deposits. Deposit fees are usually minimal or none; withdrawal fees are where books sometimes recover costs. None of this is legal or financial advice, and fee levels and timings change, so treat any figure you see as an estimate for that moment rather than a fixed rule. If you are depositing a meaningful amount for the first time, a small test deposit tells you more about real fees and timing on that book than any guide can.
One more timing subtlety: weekends and public holidays do not affect blockchains the way they affect banks, but they can affect the human support you might need if something goes wrong. A deposit that needs manual review on a Friday evening may sit until the team is back. That is a reason to keep your first deposit modest and to avoid doing it at the last minute before you want to use the funds.
Common mobile deposit errors
The single most common error is sending on the wrong network. It usually happens because the wallet defaulted to a chain the user did not choose, or because the user picked a token by ticker without checking the chain. The result is funds that the book cannot credit automatically. Sometimes support can recover them, sometimes not, and the process is slow and may carry a fee. The fix is to match the network on the book's deposit page to the network in your wallet before you confirm, every time, even when you think you know.
The second most common error is a mistyped or hijacked address. Mistyping is rare when scanning but common when typing by hand, and clipboard hijacking can silently swap a pasted address. Both send funds to the wrong place with no recourse. Verify the start and end of the address after entering it, and prefer scanning or a direct copy from the book's own page over anything a third party sent you.
A third cluster of errors involves the memo or tag. Some chains and some books require a memo to route the deposit to your account. Omitting it can mean the funds arrive at the book's address but are not attributed to you. If the deposit page shows a memo field, fill it in exactly, with no extra spaces. If you forget, contact support promptly with the transaction hash; recovery is sometimes possible but not guaranteed.
Then there is the double-send, which happens when a user thinks a deposit failed because the balance did not update, and sends again. The first transaction may have been pending or simply not refreshed in the app. Before resending, check the wallet's activity and a block explorer. If the first transfer is confirmed, do not send a second one. If it is genuinely failed, you can retry, but understand why it failed first, or you will repeat the mistake.
Smaller but still frequent errors include depositing below the book's minimum, which can leave funds stranded until support intervenes; depositing a token the book does not support at all; and using a wallet that is not actually connected to the account you think it is. Each of these is preventable with a slow read of the deposit screen and a test deposit the first time. None of them are unique to mobile, but the small screen and the temptation to tap quickly make them more likely there.
Finally, a word on the wider context. Crypto sportsbooks sit in a shifting regulatory space, and rules differ by country, so check what applies where you are before you deposit; nothing here is legal advice. If you do gamble, treat it as entertainment with money you can afford to lose, keep deposits modest, and set limits. Gambling is for adults only, and if it stops being fun, step away and seek support. Dexsport is the wallet-first, no-KYC option our editors point to when someone wants a straightforward, non-custodial deposit flow, but the mechanics above apply to any book you choose, and the responsibility for getting the details right stays with you.
This guide was researched, written and fact-checked by the MobileBet Desk editorial desk before publication. Last reviewed 13.10.2026. Spotted something wrong? Tell us.