Ripple (XRP)
Ripple (XRP) on Ledger Enterprise: destination tags, and when you must include one.
How Ripple differs
The XRP Ledger uses a reserve model. An Account cannot hold a zero balance. The network locks a minimum amount of XRP in every Account, and locks more for each object the Account owns.
The reserve is not a fee and it is not spendable. It reduces the available balance for as long as the Account exists.
Payments also carry an optional destination tag, which identifies the payee inside an address that many customers share.
For the protocol itself, see the XRP Ledger documentation.
Token coverage
Ledger Enterprise supports XRP only on Ripple. Issued tokens and trust lines are not supported.
Minimum balance
The network sets the reserve, not Ledger Enterprise. Validators can vote to change it.
Base reserve
1 XRP
Every Account
Owner reserve
0.2 XRP
Each object an Account owns
Note: These amounts were checked against the XRP Ledger reserves documentation on 7 October 2026. Validators can vote them up or down.
Because tokens and trust lines are not supported here, an Account normally owns no objects. The base reserve is then the whole of it.
Destination tags
A destination tag is a number that identifies who a payment is for, inside an Account that many people share.
Exchanges and custodians often hold XRP for thousands of customers in one address. The address tells the network where to send the payment. The destination tag tells the recipient whose Account to credit.
The field is optional in the transfer form. It takes a whole number, and the network sets an upper limit that the form checks for you.
Warning: If your recipient asks for a destination tag, you must include it. A payment that arrives without the tag reaches the right address but cannot be matched to your Account. Recovering it means contacting the recipient's support team, and some cannot recover it at all.
The tag and the address are one piece of information. Take both from the recipient together.
You cannot send XRP to the Account's own address, even with a destination tag. The interface and the API both refuse it.
Destination tags on Whitelists
A Whitelist entry for XRP can carry its own destination tag. A Master Administrator sets it when they add the address.
When the recipient matches a whitelisted address that has a tag, the send form fills in the Destination tag field and locks it. Governance authorizes only transfers that carry that exact tag. A whitelisted address without a tag accepts any tag. See Whitelists.
Related
Last updated