Skip to content
Independent XRP research, guides, and live data
Our standards

XRP Destination Tag: Don't Lose Your XRP

The destination tag is one of the most misunderstood features in XRP — and forgetting it is one of the most common mistakes. Here's everything you need to know.

··
Last reviewed: July 27, 2026
Answer in brief

A destination tag is a number that tells an exchange which customer a deposit belongs to. Always include it when sending XRP to an exchange. If you forget it, contact exchange support with your transaction hash — recovery is usually possible but slow. Personal wallets usually don't need one.

Key facts
What It IsNumerical identifier (up to 10 digits)
When RequiredSending to exchange deposit addresses
When Not RequiredSending to personal wallets
If ForgottenContact exchange support with tx hash
Recovery Time1-4 weeks typically
XRPL NameDestinationTag field
Number
Format
4.29B
Max Value
Exchanges
Required?
1-4 weeks
Recovery

What Is a Destination Tag?

A destination tag is a numerical identifier attached to an XRP transaction on the XRP Ledger. It's used to identify the recipient when multiple users share a single XRP address.

Simple Analogy

Think of it like a postal address: the XRP address is the apartment building, and the destination tag is the apartment number. Without the apartment number, your mail arrives at the building but nobody knows which unit it belongs to.

Why Exchanges Require Destination Tags

Every active XRP account requires a minimum reserve of 1 XRP. If an exchange created a separate address for each customer, they'd lock up millions of XRP in reserves. Instead, exchanges use one (or a few) XRP addresses and assign unique destination tags to each customer.

Cost Efficiency

One address serves millions of customers, saving the exchange from locking up millions of XRP in reserves.

Customer Identification

The destination tag tells the exchange which customer account to credit the deposit to.

Automated Processing

Exchanges automatically monitor incoming transactions and credit accounts based on destination tags.

XRPL Standard

The DestinationTag is a native XRPL transaction field — it's not an add-on but a core protocol feature.

How to Use Destination Tags

1. Get Your Tag from the Exchange

Go to your exchange's XRP deposit page. You'll see both an XRP address and a destination tag (a number). Both are required.

2. Copy-Paste Both Values

Never type these manually. Copy the address and destination tag exactly as shown. One wrong digit means lost funds.

3. Enter Both in Your Wallet

In your sending wallet (Xaman, Ledger, etc.), paste the address in the 'To' field and the destination tag in the 'Destination Tag' or 'Tag' field.

4. Double-Check Before Sending

Verify the address AND the tag match what the exchange shows. Send a small test transaction first for large amounts.

5. Confirm the Transaction

After sending, check the transaction on an XRPL explorer (xrpscan.com) to verify it includes the correct destination tag.

What to Do If You Forgot the Destination Tag

Don't Panic

Your XRP is not lost — it arrived at the exchange's wallet. The exchange just doesn't know it's yours. Most exchanges have a process to manually credit these deposits.

1. Find Your Transaction Hash

Look up your transaction on xrpscan.com or bithomp.com using your sending wallet address. Copy the transaction hash.

2. Contact Exchange Support

Open a support ticket. Include: your transaction hash, the amount sent, the XRP address you sent to, and your account email.

3. Verify Your Identity

The exchange will likely ask you to verify your identity to prove account ownership.

4. Wait for Manual Credit

Processing typically takes 1-4 weeks. Some exchanges charge a recovery fee ($5-$25). Be patient.

Technical Details

PropertyDetails
Field NameDestinationTag (in XRPL transaction format)
Data TypeUnsigned 32-bit integer
Value Range0 to 4,294,967,295
Required?Optional by default; accounts can enable RequireDest flag
Source TagsSenders can also set SourceTag to identify themselves
AmendmentCore XRPL feature since launch (2012)

Account owners can enable the RequireDest flag (asfRequireDest) on their XRPL account, which forces all incoming payments to include a destination tag. Transactions without a tag to a RequireDest account will be rejected by the network — preventing accidental tagless sends.

Frequently Asked Questions

What is an XRP destination tag?

A destination tag is a numerical identifier (up to 10 digits) attached to an XRP transaction. Exchanges use a single XRP address for all customers and use destination tags to identify which customer a deposit belongs to. Think of it like an apartment number — the XRP address is the building, the tag is your unit.

What happens if I forget the destination tag?

Your XRP arrives at the exchange's wallet but won't be credited to your account automatically. Contact support with your transaction hash — most exchanges can manually credit your account, though it may take 1-4 weeks and some charge a recovery fee.

Do I need a destination tag for all XRP transactions?

No — only when sending to addresses that require them, primarily exchange deposit addresses. Sending to personal wallets (Xaman, Ledger) typically doesn't need one.

Is a destination tag the same as a memo?

They serve similar purposes but are technically different. XRP destination tags are numerical identifiers native to the XRPL. Some exchanges use 'memo' interchangeably, but they're not the same field on all blockchains.

Can I choose my own destination tag?

When sending to an exchange, use the exact tag they provide. You can optionally require destination tags on your own account using the RequireDest flag in your XRPL account settings.

Where do I find the destination tag?

The exchange provides your destination tag on the XRP deposit page alongside the deposit address. It's usually a number between 1 and 4,294,967,295. Always copy-paste it — never type it manually.

Continue Learning

Send XRP Safely

Now that you understand destination tags, learn how to secure your XRP with self-custody.

Last updated: July 27, 2026. Written by the AllAboutXRP Editorial Team. Sources: XRPL.org documentation.

Get XRP insights delivered weekly

Free weekly newsletter. No spam, unsubscribe anytime.