Tags can identify hosted-account beneficiaries.
XRP Payment Attribution Guide
XRP destination tags tell an off-ledger system who or what to credit.
A Destination Tag is a 32-bit unsigned integer attached to an XRPL transaction. It helps a recipient using one address for many customers or purposes map the payment correctly.
What tags do
A tag adds payment context to a shared destination address.
Exchanges, issuers, merchants and applications can assign tags to customers, invoices or contracts. The destination address receives the payment; the off-ledger system interprets the tag.
They can map payments to orders or contracts.
The number has no universal meaning.
The recipient defines how its tags are interpreted.
What tags do not do
A tag does not enforce payment logic on-ledger.
XRPL records the number, but the ledger does not know which customer, invoice or agreement it represents. Correct crediting depends on the recipient’s application logic.
Tags do not create separate wallet balances.
They do not prove a deliverable was completed.
They do not replace amount verification.
They should not contain secret credentials.
Missing tags
Omitting a required tag can create an ambiguous payment.
When many users share one address, the recipient may see the funds but not know whom to credit. Manual investigation may be necessary unless the account requires destination tags.
RequireDest can reject payments lacking a tag.
RequireDest cannot determine whether a supplied tag is valid.
Wrong tags can still need support intervention.
Always copy payment instructions from the intended workflow.
Tags in contracts
Unique tags can associate funding with a specific agreement.
A platform can issue a tag for a contract and match incoming ledger activity to that record. Verification must still check the destination, asset, delivered amount, validation status and other required context.
Treat the tag and address as one instruction set.
Do not reuse unrelated contract details.
Verify the validated transaction result.
Use X-addresses where the receiving system supports them.
Official XRPL references
Verify the protocol behavior.
Ledger features and amendments can evolve. Check the current XRP Ledger documentation before implementing or funding a transaction.
Frequently asked questions
XRP Destination Tags Explained
What is an XRP destination tag?
It is a numeric transaction field that helps a recipient map a payment to a customer, purpose, invoice or other off-ledger record.
Does every XRP payment need a destination tag?
No. Use one when the recipient requires or supplies it.
What happens if I forget the tag?
The payment may be rejected when RequireDest is enabled, or it may arrive without enough information for the recipient to credit it automatically.
Can the XRP Ledger tell whether a tag is correct?
No. The ledger records the tag, while the receiving system decides what that number means.
Explore XRPL Integration →See the commercial solution and payment workflow.Read More Payment Guides →Explore crypto escrow, milestone contracts and safer internet work.Follow the Money →Understand verification, release, refunds and fee routing.Review the Risks →Understand what payment infrastructure can and cannot protect.
Rules before risk
Structure the agreement before money or work changes hands.
Create a wallet-based contract with defined milestones, deadlines, review rules and XRP settlement instructions.