Decoder details
What the XRP decoder checks
Validation checks
- Classic r-address and X-address encoding and checksum rules.
- Embedded X-address network flag and optional destination tag.
- Numeric destination-tag range and supported xrp: payment parameters.
Supported inputs
- XRPL classic r-addresses
- Mainnet and testnet X-addresses
- xrp: payment URIs
What this tool cannot verify
- A classic address does not indicate whether a destination tag is required for a particular recipient.
- Always obtain the destination tag from the receiving service; format validation cannot recover a missing tag.
Technical references
Common questions
What is the difference between an XRP classic address and X-address?
A classic address identifies an XRPL account. An X-address can combine a classic account with a destination tag and network flag in one encoded value.
Can the decoder tell me whether a destination tag is required?
No. It can validate a supplied tag or decode one from an X-address, but only the receiving service can confirm whether its deposit flow requires a tag.