Asset-and-network minimum
The threshold belongs to a specific asset on a specific network. USDT on Tron, Ethereum, and other supported networks can have different minimums even though the ticker is identical.

A successful blockchain transaction can still fail a platform’s deposit rules.
The block explorer shows a green Success, while the exchange balance remains at zero. That confirmation proves the funds reached an address on the selected network; it does not prove the platform’s internal system accepted the deposit.
Sending the same amount again—or hurriedly “topping up” the first transfer—can make matters worse. Minimums are often applied per transaction, so two small deposits may remain two uncredited deposits rather than one combined payment. Extra transfers also create more fees and transaction records to untangle.
Until the details are checked, this is best treated as a crediting-policy issue. Record the transaction hash, asset, network, destination address, memo or tag, and the amount received after withdrawal fees. Then compare those facts with the platform’s stated minimum and contact support. Some services can credit small deposits manually, sometimes for a fee; others may not recover them at all.
Asset-and-network minimum
The threshold belongs to a specific asset on a specific network. USDT on Tron, Ethereum, and other supported networks can have different minimums even though the ticker is identical.
Amount entered
This is the withdrawal amount requested at the sending wallet or exchange. It is not always the amount that reaches the deposit address.
Network or withdrawal fee
Some services subtract the fee from the requested amount; others add it separately. If 10 USDT is requested and 1 USDT is deducted, only 9 USDT may arrive and count toward the minimum.
Net received amount
This is the amount shown on-chain at the destination address. Deposit systems commonly compare this figure—not the sender’s total cost—with the required minimum.
Crediting requirement
A valid transfer may remain pending until enough block confirmations have accumulated. That delay is separate from a below-minimum deposit.
Open the current deposit page and record the asset, network, and stated minimum. Avoid relying on an old screenshot, saved instructions, or a minimum shown for another network.
Find the transaction ID in the sending wallet, then inspect it in the network’s block explorer. Compare the amount delivered to the deposit address with the platform’s minimum, accounting for any fee deducted by the sender.
Compare the explorer’s recipient with the deposit page. Verifying the current sportsbook deposit address can reveal a copied, outdated, or unrelated destination.
A transfer at or above the minimum can still fail if it used an unsupported network, sent a different token, or omitted a required memo, tag, or destination ID. These are routing problems rather than minimum-deposit problems.
If every detail matches, check whether the platform’s required confirmations have been reached. Only a confirmed transfer whose net delivered amount is below the listed threshold should be treated as a true below-minimum case.
Explorer records help support distinguish an amount issue from a routing or confirmation issue.
A top-up sometimes works, but it is not a universal fix. The result depends on how the receiving platform records deposits—not simply on the total visible at the blockchain address.
Platforms generally use one of several approaches:
Even when aggregation is documented, the second transfer should leave room for any network or withdrawal-side fee that reduces the amount received. Reusing an old address also requires confirmation that the platform still supports it.
Before sending more, check the platform’s deposit policy for wording such as cumulative, per transaction, or deposits below the minimum will not be credited. If the rule is unclear, support should confirm whether a top-up to the same address will release the earlier amount.
A speculative top-up can create a second unresolved deposit. Wait for written documentation or a support reply that identifies the required address, network, asset, and amount.
Open the transaction hash in the correct network’s block explorer. Confirm that it succeeded, note its confirmation count, and check the destination address.
Record the transaction hash, exact asset and network, amount received on-chain, destination address, and timestamp in UTC. A ticker alone may be ambiguous across networks.
Include the platform account identifier and any deposit memo, tag, or payment ID. Do not include the account password.
Capture the withdrawal record and block-explorer result, including status, amount, address, and hash. Redact unrelated balances or personal information.
State that the deposit was below the minimum, then ask whether manual crediting or paid recovery is available. These are the details support typically needs to trace an uncredited deposit.
Keep the ticket number and reply in the same thread to avoid duplicate investigations.
Legitimate support does not need a seed phrase, private key, password, or two-factor authentication code. Avoid unsolicited direct messages, remote-access requests, and unofficial “recovery” websites; use only the platform’s verified support channel.
How long can an under-minimum deposit take to appear?
Automatic credit may arrive after additional deposits are aggregated, but only where the platform supports that behavior. Manual review can take several business days, especially when wallet operations or compliance teams must approve an adjustment.
Will support always credit a valid on-chain transfer?
No. A confirmed transaction proves that funds reached an address, but it does not override the platform’s minimum-deposit policy. Some operators credit such transfers as a courtesy; others wait for aggregation or decline recovery entirely.
Why can the recovery fee exceed the missing deposit?
Recovery may require wallet access, manual accounting, and a separate on-chain transaction. Platforms often charge a fixed administrative fee plus network costs, making small deposits uneconomical to retrieve.
When is a deposit effectively unrecoverable?
Recovery may be impossible when the wrong network or unsupported asset was used, routing information was omitted, or the receiving wallet cannot be accessed safely. A platform may also classify technically recoverable funds as unrecoverable when the operational cost exceeds their value.
Confirm the live minimum immediately before sending. Limits can change by asset, network, account, or payment provider.
The withdrawal network must match the network shown on the receiving platform. Copy any required memo, tag, or destination identifier along with the address.
Check whether fees are deducted from the entered amount. When costs are high, consider lower-fee crypto choices for sportsbook deposits rather than reducing the delivered amount too close to the threshold.
Use the exchange’s preview to confirm that the destination will receive more than the minimum. A small buffer protects against fee calculations, rounding, or display differences.
Keep the deposit instructions, address, amount, network, timestamp, and transaction hash. Screenshots taken before submission can clarify what the platform displayed at the time.
A small test transfer is useful only when it still meets the stated minimum.
A confirmed blockchain transfer cannot normally be canceled or pulled back. Sending a top-up is worth considering only when the operator confirms that deposits to the same account and address are combined; otherwise, it may create a second under-minimum transaction.
For readers comparing deposit methods, fees, confirmation times, and crediting rules, the broader sportsbook crypto payment guide provides useful context. The safest next step remains evidence-led: wait for settlement, correct faulty details, or escalate a valid but undersized deposit.