Definition and scope
XRPL Token Clawback Explained addresses a distinct part of compliance, identity, and interoperability. Understand the issuer-enabled mechanism for recovering eligible issued-token balances.
XRPL includes tools for controlled deposits, issuer compliance, public identity, and cross-network systems. Several features in this category are amendment-dependent or evolving, so every eventual article must verify current Mainnet status and distinguish protocol capability from a particular service's legal obligations. Protocol controls can support a policy but do not establish identity, trustworthiness, regulatory compliance, or legal permission by themselves.
How it works
Clawback lets an issuer recover eligible balances of its own issued token when the issuer enabled the capability before distribution. The Clawback transaction identifies the holder and amount under protocol restrictions.
- Clawback: verify this field, object, or component against the cited protocol documentation.
- AllowTrustLineClawback: verify this field, object, or component against the cited protocol documentation.
- Holder: verify this field, object, or component against the cited protocol documentation.
- issuer: verify this field, object, or component against the cited protocol documentation.
Practical example and checks
An issuer documents permitted cases, enables AllowTrustLineClawback before issuance, applies dual approval, submits the exact holder and asset amount, and records the validated evidence.
For production use, preserve the exact signed or queried data, record the network and validated ledger reference, and compare the result with the current primary documentation before changing off-ledger state.
Open the related live demo or evidence lab →Limits, risks, and common confusion
Clawback cannot take native XRP and is not available for every legacy token or frozen configuration. Protocol ability does not determine whether a particular use is lawful or contractually justified.
Protocol controls can support a policy but do not establish identity, trustworthiness, regulatory compliance, or legal permission by themselves.
Current network status
Enabled on XRPL Mainnet. Clawback was enabled on XRPL Mainnet in feature responses from both official public servers at review time. Client and service support can still vary.
Status reviewed 2026-08-23. Amendment-dependent behavior must be rechecked against the network's live feature state before operational use.