Deposits and withdrawals
XRP: the right address, but no deposit credit?
At a glance
When an XRP recipient requires a destination tag, the address alone may not identify your account. Check both against its receiving instructions. If you already sent with a missing or wrong tag, preserve the hash and contact official support; recovery is not guaranteed.
On this page
A transfer can name the right exchange address without identifying the right customer. For XRP deposits that require a destination tag, check the address and tag together before sending. If you have already sent, preserve the transaction details before trying anything else.
One address, different customers
The XRPL documentation explains that a destination tag supplies information for the recipient's own systems to process a payment. It can distinguish customers behind a shared address. The tag is not a second wallet address.
Kraken's XRP deposit guide gives a concrete example of this arrangement: its XRP deposit instructions require an account-specific tag. That is a Kraken example, not proof that every wallet uses the same setup. Always use the receiving service's current instructions.
A routing example you can check
Imagine a fictional exchange with a shared receiving address and two customers, Alice and Bruno. Each has a different assigned tag. We use names rather than actual tag numbers or addresses so this illustration cannot be mistaken for deposit instructions.
| Information sent | What the example establishes | What it does not establish |
|---|---|---|
| Shared address alone | Which receiving address was specified | Whether Alice was identified |
| Shared address + Alice's assigned tag | The intended customer reference matches Alice | Whether all deposit checks passed |
| Shared address + a different tag | The customer reference differs | That Alice will receive credit |
This is a deliberately limited model. Matching both fields is a routing check, not a guarantee of credit. Keep the asset, network and current deposit requirements in the review too. The transfer checklist covers those separate checks.
Missing and wrong are different problems
When a receiving account enables the XRPL RequireDest setting, a payment missing its destination tag is rejected. That presence check is not confirmation that the supplied value belongs to you. An accepted transaction and correct customer attribution are different questions. Protocol explanation.
Coinbase's help page warns that an absent or incorrect required tag can delay credit or cause loss. Do not assume a successful sending-screen status proves that your receiving balance was updated.
If the transfer has already been sent
Prepare a short private support record: receiving service, asset and network, transaction hash, amount, time, expected tag, and the tag actually shown in the transaction record. Mark an unknown value as unknown. Keep a screenshot of the receiving instructions if available; redact unrelated personal information.
Ask official support to investigate the specific transaction. For funds sent to Coinbase with an incorrect tag, Coinbase asks customers to contact its support with the transaction hash and says recovery assistance may be possible. Kraken warns that missing-tag deposits can sometimes be irretrievable. Neither statement is a recovery guarantee. Do not send another deposit simply to try to correct the first one's tag.
A useful message is: “My XRP transfer has not appeared in my account. Here is its transaction hash and the expected versus recorded destination tag. Please confirm what your official recovery process requires.” This template is an original organizational aid, not a promise that a provider will accept or resolve the case. Never include a password, private key or recovery phrase.
Before the next transfer
Read the destination's fresh receive instructions, compare both fields in the final confirmation screen, and resolve any missing tag input with official support before proceeding. A completed transfer cannot be repaired merely by changing a saved address-book label afterward. For the separate distinction between network confirmation and account credit, see our Bitcoin deposit explainer; its Bitcoin confirmation rules do not apply to XRP.
Editorial note: prepared by CoinFom with AI-assisted research, writing, translation and review. No transfer or recovery request was performed for this article. The routing example is fictional. Sources checked September 28, 2026; service instructions can change. This is educational information, not investment advice. CoinFom may earn referral commissions on other pages; this article has no referral signup link. See About, our editorial policy, or send a correction.