XRP Ledger guide for XRP exchanges and destination tags
For native XRP exchanges, select the XRP Ledger and follow the recipient's address and destination-tag instructions. Ledger settlement, exchange processing and crediting by a receiving platform are separate checks.
Reviewed September 10, 2026 · Primary source linked below
Native fee asset
XRP
Asset model
XRP and issued currencies
Network identity
XRP is the native asset of the XRP Ledger. Accounts maintain ledger entries and can also interact with issued currencies. An XRP token on BNB Smart Chain is not the native XRPL asset.
Address rules
An XRPL classic address begins with r. An X-address can combine a classic address, a tag and network information, but it must be supported by the form you are using. If the form expects a classic address and a separate tag, request those details from the receiver rather than placing the whole X-address in either field.
Fee mechanism
XRP Ledger transactions destroy a small amount of XRP as a fee. Account reserve rules are separate from the transaction fee and can affect how much XRP a wallet considers spendable.
Settlement
Check that the payment is included in a validated ledger and has a successful result. A provisional submission result is not final. Even a successful XRP payment to the correct shared address may still require the receiving platform to match its destination tag before crediting an account.
Memo or tag
An XRP destination tag is a number assigned by the receiver to identify a payment behind a shared address. It is separate from a classic address and is not a free-text memo. Copy the supplied value exactly; do not invent a tag when the receive screen provides none.
Tokens and representations
Native XRP on XRPL and a same-ticker token on another chain are different assets. Issued currencies on XRPL also have issuer identities and must not be confused with XRP.
MOST COMMON ROUTE ERROR
What usually goes wrong
Treating every missing-tag transfer as a successful payment with an uncredited balance. If the account enforces destination tags, an XRP payment without one can fail with tecDST_TAG_NEEDED. Check the final transaction result before deciding which issue applies.
CONCRETE EXCHANGE EXAMPLE
Follow both legs of the route
For a USDT-on-Ethereum to XRP exchange, the deposit uses Ethereum while the payout uses the XRP Ledger. A custodial recipient may supply an r-address and a numeric tag. Enter both in the payout instructions, then compare the eventual XRP transaction's destination and tag with those saved details.
BEFORE YOU SEND
XRPL checklist
- Choose native XRP on the XRP Ledger, rather than a same-ticker token on another chain.
- Use the receiving address format supported by the order form.
- Copy a destination tag whenever the receiving service requires one.
- Use the sending wallet's spendable balance, which accounts for reserve requirements.
- For a transfer already sent, check its validated result before treating it as delivered.
XRPL FAQ
Network-specific answers
Can the ledger verify that a destination tag belongs to me?
The tag helps the receiving service assign the payment in its own records. It does not identify your customer account to the ledger. A tag with the wrong number can therefore be different from an omitted tag that causes rejection.
Does a transaction hash prove my XRP payment succeeded?
No. Inspect the final result in a validated ledger. For an ordinary successful payment, look for tesSUCCESS as well as the intended destination and delivered XRP amount.
Is the XRP account reserve an exchange fee?
No. The account reserve is a ledger requirement that affects spendable XRP. It is separate from the transaction cost and any exchange charges. Check the wallet's spendable balance before sending.
CONNECTED REFERENCE PAGES