A casino deposit can reach the address on the cashier screen and still fail to reach the player's balance. On a route that requires a memo or destination tag, copying the address alone leaves out the information the recipient uses to assign the money to an account.
The missing field can be short enough to overlook. Its job is specific: identify the intended customer or payment within the receiving business. A network confirmation does not fill it in afterwards. This is one particular cause of an on-chain payment staying pending in the cashier, rather than an explanation for every delayed deposit.
One XRP address can serve many customers
The XRP Ledger's tag documentation explains that destination tags help a business map payments at a shared address to individual customers. The tag gives the receiving service information for its own records. It does not create a separate XRP Ledger account for the player.
An illustrative cashier might therefore give two customers the same address but different tags. If a sender includes the wrong customer's tag, the address comparison alone will not reveal the mismatch. The receiving service needs to investigate the account assignment.
XRP also has a safeguard called RequireDest. When the receiving account enables it, the ledger rejects a payment that omits the destination tag. Without that setting, a payment can arrive without the information the business needs to match it automatically. Missing a tag therefore does not produce one universal result: inspect the transaction outcome before assuming the funds arrived.
There is another address format to recognise. An XRP X-address can encode the classic address and tag together. Whether a particular cashier and sending wallet accept that format must be established from their instructions; it is not a reason to guess a tag or ignore a separate required field.
Stellar memos follow different rules
The same label does not guarantee the same format. Stellar's transaction documentation defines several memo types, including text and a numeric ID. A memo is optional at the protocol level, but a receiving service can require one for account identification. Stellar also supports muxed accounts, which combine an underlying account with an identifier for a recipient sharing that account.
For a player, the instruction on the receiving cashier controls which destination format to supply. A sending form that asks for a memo type needs the correct type as well as the value. A number copied into a text memo should not be assumed equivalent to a numeric memo ID.
These fields are not interchangeable with a wallet's private note about a transfer. The reference must be included in the transaction in the form the recipient expects. If the sending service cannot supply that form, resolve the incompatibility before transferring funds.
The casino's instructions still matter
Stake's crypto-deposit help, dated 24 August 2026, gives an operator example: it says assets such as XRP require the correct address and memo/tag to credit a balance, and directs customers who make a mistake to live support to start recovery. That is a published support route, not a promise of repayment or a deadline.
Read the destination from the authenticated cashier for the selected asset and network. Keep its address and any required reference together when comparing them with the sending form. A tag does not fix an unsupported network or coin. Our crypto deposit-to-settlement guide follows those separate checks and the later account-credit process.
This article explains payment routing. It does not establish that a named casino is licensed or available in a reader's country.
Recovery starts with the receiving service
For a transfer already sent, assemble the transaction hash, asset and network, amount, destination address, and the tag or memo actually transmitted. Preserve the cashier instructions and the sender's withdrawal record. Compare what the recipient requested with what the transaction contains; a screenshot of the current balance cannot establish that comparison.
Coinbase's destination-tag guidance draws a useful boundary. For funds sent out from Coinbase with a missing or wrong reference, it says Coinbase cannot retrieve them and points to the receiving wallet or exchange. For an incorrect reference on funds sent into Coinbase, its own support may be able to help, using the transaction hash. Those are different directions of transfer and different support responsibilities.
A receiving casino or payment provider must establish whether it received the funds and can identify the intended account under its recovery process. Waiting for more confirmations cannot supply a missing reference. Sending another deposit also cannot be assumed to repair the first one. Ask for the original transfer's status and a case reference so that any credit or return can be matched to that transfer.
The address identifies where the payment goes. When the recipient requires a tag or memo, that second field identifies where it belongs in the recipient's records.
