Crypto deposit not credited: build the evidence file first

When a crypto deposit does not appear in a casino balance, the first useful question is not “where is my money?” but “what does each system show?” The sending wallet, blockchain explorer, casino cashier and account ledger hold different parts of the evidence.

Duelbits’ official help says its support requires a transaction hash or reference number to investigate an uncredited deposit. It recommends finding the TXID in the sending wallet, checking the transaction status and supplying the identifier or screenshots if the issue remains unresolved. Those instructions describe Duelbits support; they do not prove another casino’s process or availability in New Zealand.

Start with the transaction hash

A transaction hash, TXID or transaction ID identifies the public-ledger transaction. Open the sending wallet’s transaction history, select the relevant transfer and copy the full identifier. Do not type it manually from a shortened display.

Open the correct explorer independently and paste the TXID. Save the explorer URL and a screenshot showing:

• transaction status;
• asset and token contract where relevant;
• selected blockchain network;
• destination address;
• amount transferred;
• fee paid;
• block height and confirmations;
• date and time.

If the explorer cannot find the TXID, check that the explorer matches the network. A transaction on Tron will not appear on Ethereum, even if the token ticker is the same.

Preserve the cashier instruction

The explorer proves what the blockchain processed. It does not prove what the casino requested. Save the original cashier screen or deposit instruction containing the asset, network, address, memo or tag, minimum amount and required confirmations.

Compare the destination character by character. For tokens, compare the contract or asset identifier as well. A correct-looking ticker is insufficient when the same token exists on several networks.

If the cashier address has changed since the transfer, keep the old instruction. Do not send a second payment to the new address until the first case has been reviewed.

Check the transaction state

An external service can show a purchase or withdrawal as pending before it has broadcast an on-chain transaction. In that case, there may be an order number but no valid TXID yet. Contact the sending provider with its order reference.

If the transaction is on-chain but unconfirmed, monitor it rather than repeatedly contacting the casino. Network congestion or a low-priority fee can delay confirmation. Duelbits notes that casinos cannot accelerate blockchain confirmations.

If the transaction is confirmed to the correct destination but the casino balance is unchanged, the issue has moved to processor matching or internal account credit. That is the point to contact authenticated casino support with the complete evidence file.

Evidence checklist for support

Prepare one concise message containing:

1. account username or support-safe user ID;
2. deposit date, time and time zone;
3. asset and exact network;
4. amount sent;
5. full TXID and explorer link;
6. destination address and memo or tag;
7. confirmation count;
8. screenshot of the cashier instruction;
9. screenshot of the wallet receipt;
10. screenshot of the account deposit history;
11. a short statement of the mismatch.

Do not include a seed phrase, private key, wallet password, one-time code or full identity document in an ordinary chat message. Support can investigate a public transaction using its hash.

The most useful description is factual: “The transaction has twelve confirmations on the named network, the destination matches the instruction, but no deposit appears in the account history.” Avoid sending multiple long messages with changing amounts or timestamps.

Common causes to test

Wrong network

The asset may be correct but the chain may differ from the cashier instruction. Recovery can be impossible. Do not claim that an address is recoverable merely because its format exists on both chains.

Wrong token or contract

A wallet can display an imitation or wrapped token under a familiar ticker. Compare the contract or asset ID with the issuer and cashier documentation.

Missing memo or tag

Some systems use a shared deposit address plus an account-specific memo, destination tag or payment ID. The transfer can succeed on-chain without being allocated automatically.

Below-minimum transfer

A transfer below the published minimum may not credit. Preserve the minimum shown when the address was generated; do not assume that sending another amount will merge automatically.

Not enough confirmations

The casino may wait for more confirmations than the wallet uses for its green “completed” label. Check the operator’s own threshold.

Processor or ledger delay

If every on-chain field matches and the threshold is complete, internal processing may still be pending. Only the operator or its payment processor can inspect that ledger.

What not to do

Do not send a duplicate deposit to “wake up” the first one. Do not pay an unofficial recovery fee sent by direct message. Do not let an unknown helper control the device or import the wallet.

Do not post the casino account email, full wallet balance or identity documents publicly. A TXID and public address are visible on-chain, but linking them to personal data creates unnecessary privacy risk.

If support asks for additional evidence, verify that the request comes through the operator’s authenticated site or published support address. Preserve the case number and transcript.

Operator and support scope

This page does not confirm that Duelbits or another crypto casino accepts New Zealand players. The source explains its own support workflow. Territorial eligibility, operator identity and dispute routes require separate evidence.

Build a four-record deposit file

An uncredited deposit is easier to diagnose when the evidence is divided into four records instead of compressed into one screenshot. The first record is the cashier request: what asset, network, destination and optional memo the receiving service displayed. The second is the wallet authorisation: what the sender approved, including amount and fee. The third is the blockchain receipt: what the network actually confirmed. The fourth is the casino ledger: whether the operator detected, accepted and credited the transfer.

Name the files so another person can follow the sequence without guessing. A practical set is 01-cashier-request, 02-wallet-receipt, 03-explorer-result and 04-account-ledger. Include the local date and time in each filename. If the screen uses a relative label such as “12 minutes ago”, capture the device clock or write the exact time separately. Relative times become ambiguous once the case is reviewed later.

The four records answer different questions. A cashier screenshot cannot prove broadcast. A wallet receipt cannot prove the destination belonged to the casino request. An explorer page cannot prove that an account-specific memo was entered. An empty account ledger cannot prove the chain failed. Keeping the records separate prevents one correct fact from being mistaken for proof of the whole payment path.

Before contacting support, create a one-line comparison for every field: requested asset versus sent asset; requested network versus recorded network; requested address versus on-chain destination; requested memo versus transaction memo; displayed minimum versus amount after any sender-side deduction; required confirmations versus current confirmations. Mark each pair as match, mismatch or not shown. “Not shown” is important because it identifies the exact detail that support must clarify.

Read the TXID without exposing wallet secrets

A TXID is a public identifier, not an authorisation credential. Sharing it with authenticated support lets the investigator find the same public transaction. It does not let support spend funds. A seed phrase, private key, signing request, wallet password or one-time authentication code is completely different: those items can authorise access and must never be supplied for a credit investigation.

Copy the hash using the wallet’s copy control, paste it into a plain text field and compare the first and last eight characters with the explorer result. This catches truncated clipboard contents and accidental selection of an address instead of a transaction ID. Open the explorer through a known bookmark or the network’s official documentation rather than a link sent by an unsolicited “recovery agent”.

Token transfers need an extra reading step. On account-based chains, the outer transaction can show the native coin value as zero while an event or token-transfer section records the token amount. Save the token contract, decimal-adjusted amount and recipient shown in that transfer record. Do not conclude that no value moved merely because the top-level native-value field is zero.

Batch withdrawals and processor sweeps can also make a receipt look unfamiliar. A single transaction may have several outputs, or a processor may forward funds after the initial deposit. For the support case, the relevant proof remains the original transfer from the sending wallet to the destination supplied by the cashier. Do not replace that record with a later internal movement unless support explicitly identifies it as part of the same deposit.

Diagnose the stage before choosing the contact

If the sending service shows an order but no TXID, the payment has not yet produced verifiable on-chain evidence. The sending exchange, broker or wallet service is the correct first contact. Ask whether the order was approved, queued, rejected or broadcast and request the TXID if broadcast occurred. The casino cannot locate a transaction that the network has never seen.

If a valid TXID exists but the explorer shows pending, keep the explorer link and monitor confirmation progress. Do not create competing transactions unless the wallet provider documents a safe fee-replacement method for that network and transaction type. A second ordinary transfer is not a fee bump; it is a second payment.

If the transaction is confirmed but a required memo or tag is absent, state that explicitly. The transfer may have reached a shared address without the information needed for automatic allocation. Only the receiving service can determine whether manual attribution is possible. Recovery should never be described as guaranteed, and an unknown person asking for a separate “unlock payment” is not evidence of a legitimate process.

If the transaction is confirmed to a different address or network, preserve the records and stop. Contact the sending service and the intended receiver through their official channels, but recognise that irreversible settlement may limit recovery. Do not edit screenshots or omit the mismatch in the hope that support will treat it as an ordinary credit delay; accurate routing information is essential to any genuine investigation.

If every field matches and the confirmation threshold is complete, the case belongs with the casino’s authenticated support. Provide the evidence once, obtain a ticket number and add later updates to that ticket. Multiple simultaneous cases can split the history and cause repeated identity checks.

Amount reconciliation and decimal checks

Compare the amount using the asset’s native unit and the number of decimals shown by the explorer. A wallet may display a rounded value while the transaction contains a more precise quantity. Copy the explorer amount rather than retyping a rounded app display. Where a token contract is involved, confirm that the explorer has applied the correct decimals; a raw integer is not automatically the human-readable token amount.

Also separate the transfer amount from the network fee. On many networks the fee is paid in addition to the token amount, but some custodial services deduct a withdrawal fee from the requested amount. If the casino minimum applies to the amount received, a sender-side deduction can move the deposit below that threshold. Record the gross request, the service fee and the net on-chain amount as three different values.

Do not convert the crypto amount to New Zealand dollars using today’s market rate when describing an older transfer. If a fiat equivalent is relevant, preserve the rate and timestamp shown at the time. The primary reconciliation should remain in the exact asset units because that is what the blockchain and receiving processor can match.

For deposits made through a QR code, compare the decoded address and any embedded amount or memo with the text fields on the cashier page. The QR image itself is not a durable record unless it can be decoded later. Save the written destination as well, and note whether the request had an expiry time.

Write a support message that can be actioned

Use a subject that identifies the problem and network, for example “Confirmed USDT transfer on Tron not credited — TXID ending 91ab”. In the first sentence, state the date, amount and account-safe identifier. In the second, state the explorer status and confirmation count. Then list the destination, memo status, cashier request time and attachments. End with one question: ask support to trace the transaction and confirm whether any additional account-verification step is required.

Avoid theories in the opening message. Claims that the casino “lost” or “stole” a deposit do not help an investigator locate the transfer. Equally, do not accept a generic answer that fails to address the TXID. A useful response should acknowledge the identifier, state the current processing stage or request a specific missing field.

Keep the transcript in chronological order. Record when the ticket was opened, each response time, the case number and any promised review window. If the operator asks for a screen recording, ensure it does not reveal unrelated balances, authentication codes or recovery phrases. A targeted recording can show the wallet transaction page, copied TXID, public explorer and cashier history without opening security settings.

When the deposit is finally credited, save the account-ledger entry and compare the credited asset amount with the transaction receipt. Record whether the resolution was automatic after confirmations or required manual allocation. This closes the evidence trail and provides a reliable reference if the same payment route is used again.

A worked evidence map

Consider a transfer where the cashier requested a token on Network A, displayed address D and required a memo M. The wallet receipt shows the same token and address but the memo field is blank. The explorer confirms the transfer to D. The correct diagnosis is not “blockchain delay”: the network completed its part, while the allocation identifier is missing. The support request should highlight the blank memo and ask whether manual attribution is possible.

In a second case, the cashier and wallet fields match, but the explorer remains pending. The account ledger is expected to remain empty until the receiver’s confirmation policy is met. The evidence file should retain the pending TXID and monitor it; it should not claim that a confirmed deposit was ignored.

In a third case, the explorer shows enough confirmations and every requested field matches, yet the account history contains no entry. This is the clearest internal-reconciliation case. Send the four-record file to authenticated support and ask for a processor trace. The strength of the case comes from matching fields, not from the number of repeated messages sent.

These examples are diagnostic patterns, not statements about a particular casino. The Duelbits material establishes that a transaction hash or reference is central to its investigation process. Another operator can use different confirmation thresholds, minimums and ticket procedures, which must be taken from that operator’s live cashier and help pages.

Use the payment status timeline to identify the current stage and the network-matching checklist before future transfers.

Frequently asked questions

What is the most important item for support?

The full TXID or, if the transfer was never broadcast, the sending provider’s order reference.

Is a wallet screenshot enough?

No. Include the public explorer result and the casino’s original cashier instruction.

Should I send again if the address changed?

No. Preserve the first instruction and resolve that transaction before making another transfer.

Can support ask for my seed phrase?

No legitimate transaction investigation needs a seed phrase or private key.

Does this confirm casino access from New Zealand?

No. The source documents one operator’s support procedure, not territorial eligibility.

Official sources

• Duelbits Help: how to find your transaction hash
• Duelbits Help: deposit not credited

Bottom line: prove what was requested and what the blockchain executed before asking support to reconcile the account ledger.