Understand what the service will credit
A skin deposit, website credit and crypto transfer are different transactions. Read which balance the service will credit, the selected method and any stated minimum or fee. A referral promotion does not change the destination you should verify.
Keep the quote or deposit order before sending. If a previous payment is already missing, trace that payment first. Creating another order will not explain the first transaction.
For a Steam offer, inspect the recipient and items
Open the offer through Steam and compare it with the website’s transaction record. Check the recipient, items and the direction of the transfer. Stop if an unexpected account contacts you or an offer changes before confirmation.
Keep the offer ID and current status. Do not send a Steam password, authenticator code, recovery code or full trade-URL token to a supposed helper. An item restriction should be checked on the item itself rather than bypassed with another account.
For crypto, confirm all three identifiers
Compare the asset, network and receiving address shown by the service with the sender’s selection. Preserve the transaction hash after a transfer. A confirmed transaction on the wrong network does not prove the correct casino deposit was credited.
For a bank or payment provider, retain the casino order ID and the sender’s payment reference. Record whether the debit is pending, completed or reversed. A completed bank debit and a credited casino balance are different statuses.
If the balance is missing, report the mismatch
Tell support which method you used and give the amount, original currency, time and references. For crypto, include the network and public hash; for a provider, include the order and payment references.
Share private payment proof only through the official support channel. Do not pay an extra “release” charge to a person who contacts you privately. Ask which stage remains unresolved and retain any return or refund reference the operator supplies.
Useful next steps
Sources and scope
Reviewed on 4 October 2026. These sources explain the published process; the troubleshooting checklist is StrikePot’s editorial guidance. Account-specific instructions come from the service handling the request.