On XRP Ledger, freezing a trust-line token restricts how it can move, while clawback can reduce a holder's balance of an issuer's token when the required authority is enabled. These mechanisms do not let a token issuer freeze or claw back native XRP. Identify the exact asset and issuer before diagnosing a blocked transfer or an unexpected balance change.
Start with currency plus issuer, not the wallet's headline
A wallet can show native XRP and several issued assets together. For a trust-line token, the currency code alone is not enough to identify the asset: include the issuing account. A familiar ticker does not establish that two balances have the same issuer or control settings. The native coin and token explanation helps separate those layers before you investigate permissions.
This article focuses on trust-line tokens. XRP Ledger also has Multi-Purpose Tokens with their own issuance settings; do not copy a trust-line flag checklist into every token format. The current clawback documentation distinguishes those mechanisms. It explicitly excludes native XRP from clawback, while the freeze documentation separately excludes XRP from issuer freezing.
Read what each control changes
| Control or condition | Scope in this article | What the holder may observe | Important distinction |
|---|---|---|---|
| Individual freeze | A particular trust line | Restricted token spending, with defined issuer interactions | It does not by itself remove the displayed balance |
| Deep freeze | A particular trust line with stronger restrictions | Transfers with other holders restricted in both directions | Direct issuer interactions have specific rules |
| Global freeze | Issuer-wide trust-line token restrictions | More than one holder affected | It is not a native-XRP freeze |
| Clawback authority enabled | Issuer capability for its trust-line tokens | A capability visible in issuer configuration | Capability alone is not proof an execution occurred |
| Successful clawback action | The specified issuer's token balance | A recorded reduction attributable to that action | It is different from a normal payment signed by the holder |
| Custodial account restriction | The platform's own ledger or service | Trading or withdrawals unavailable | It is not automatically a protocol freeze of native XRP |
The table is a scope map, not a complete payment-rules implementation. For example, ordinary individual freeze and deep freeze are not interchangeable: the official guide describes different receiving restrictions and direct interactions with the issuer. Read the applicable state rather than interpreting every failed send as the same event. A wallet message may summarize several possible causes.
A frozen balance and a reduced balance need different evidence
Consider a fictional holder with 50 units of issued token Z. A restriction can leave the 50-unit balance visible while preventing a proposed transfer under the applicable rules. Adding more XRP for fees does not itself remove that issuer-side restriction. First identify the state and the failed transaction's result; do not treat every blocked send as proof that tokens were already taken away.
In a different fictional case, a permitted clawback of 12 Z succeeds and no other balance-changing events occur. The holding becomes 38 Z. That requires an actual ledger action and corresponding balance evidence, not just a flag saying clawback is allowed. Record the transaction and issuer before making an accusation or asking support why the app 'lost' 12 units. The quantities are illustrative, not a real issuer incident.
Also check ordinary payments, trades and the token identity when explaining a decrease. A lower portfolio price is different from fewer token units. Do not infer clawback from a changed dollar estimate or a screenshot alone. Use a trusted explorer and the actual transaction metadata. Our XRPScan guide provides a starting point for reading accounts and transactions.
Issuer capability has prerequisites
For trust-line tokens, the official guide says clawback is disabled by default and the issuing account must enable the appropriate setting before the relevant account has existing issuance and owner-directory objects. Do not assume every issuer can switch it on retroactively for an established distribution. Inspect the actual issuer configuration and current protocol documentation rather than treating the feature's existence as universal authority.
Read combinations of flags carefully. The clawback documentation describes incompatibility with No Freeze, while the freeze guide gives No Freeze a more specific meaning than 'every possible restriction is impossible.' Avoid building a safety conclusion from the reassuring name of one flag. You need the asset type, issuer settings and the relevant action, not a single label taken out of context.
Keep network permissions separate from platform access
If a custodial exchange prevents a withdrawal of XRP, that can be the platform's account restriction rather than an issuer freezing native XRP on the ledger. Conversely, an issued-token restriction can exist independently of your exchange login. Locate which system rejected the action: wallet submission, validated ledger execution or the service's own withdrawal process. Each requires a different support record.
Do not pay an unknown helper to unlock an issuer-controlled token or attempt to route around a compliance restriction. Contact the issuer or platform through independently verified channels and provide the relevant asset and transaction evidence. A new wallet application may present the state differently, but changing the display does not modify the ledger's issuer controls.
- Identify whether the asset is native XRP, a trust-line token or another token type.
- For a trust-line token, record both currency and issuing account.
- Inspect the holder's relevant trust-line state and the issuer's applicable settings.
- If a transfer failed, inspect its actual result instead of inferring a balance reduction.
- If units decreased, locate the action and metadata that explain the change.
- Use official issuer or platform support for restrictions without sending secrets or an unlocking payment.
Check acceptance before planning another transfer
A service accepting native XRP does not thereby accept every token issued on XRP Ledger. Before a no-account swap, verify the asset and network offered in the current order. An XRP exchange route is not a general deposit address for an unrelated trust-line currency. If the issuer's restrictions prevent movement, do not create multiple payment attempts to test whether one slips through.
For a suspected clawback, the Clawback transaction reference is the primary format and result source. Keep the account configuration check separate from that transaction check. A precise final note states the asset, issuer, observed setting, actual action and resulting units. That is stronger evidence than a generic claim that 'XRP was frozen' when the affected balance was a particular issued token or a custodial record.
FAQ
Can the XRP clawback feature take native XRP?
No, the documented issuer clawback mechanism applies to eligible issued tokens, not native XRP. A custodial platform restriction is a separate issue.
What does clawback mean for an XRPL token holder?
An eligible issuer can execute a supported action that reduces its token balance held by the specified account. An enabled capability alone does not prove that such an action happened.
Does the XRP Ledger clawback amendment make every token clawback-enabled?
No, token type and issuer configuration still matter. For trust-line tokens, the documentation describes prerequisites that prevent treating it as a universal retroactive switch.