Denylisting a token blocks it from visibility in Ripple Custody. Use this to remove spam, scam, or unwanted tokens from your operational views.
When you denylist a token:
- The token moves to the denylisted tab.
- Token balances are hidden from account views.
- You cannot create transfer orders using the token.
- Historical transfers involving this token are hidden.
Denylisting does not affect the actual token balance on the blockchain. The tokens still exist in the account but are hidden from Ripple Custody views.
To denylist tokens that have not been reviewed:
- Go to Settings and then Assets Management.
- Click Manage unclassified or denylisted.
- Click the Unclassified tab.
- Find the token(s) you want to denylist.
- Click Deny at the end of the token row.
- Review the confirmation dialog showing the token details.
- Click Submit for Approval.
- On your mobile device, open the Ripple Custody Auth & Sign app and sign the intent.
Bulk denylisting from unclassified creates a single intent, requiring only one signature.
To denylist tokens that are currently allowlisted:
- Go to Settings and then Assets Management.
- Find the token you want to denylist.
- Do one of the following:
- Click the contextual menu (⋮) at the end of the token row and select Deny asset.
- Select the token and click the Lock icon.
- Review the confirmation dialog showing the token details.
- Click Submit for Approval.
- On your mobile device, open the Ripple Custody Auth & Sign app and sign the intent.
Denylisting from allowlisted creates individual intents for each token. If you select multiple tokens, a progress indicator shows the status of each intent.
The confirmation dialog warns that:
- Token balances will be hidden.
- Transfer history involving the token will be hidden.
- The token can be restored later if needed.
Before signing, you can expand the intent payload to review the JSON. This includes:
| Field | Description |
|---|---|
| Asset details | Token name, symbol, and contract address |
| Ledger | The blockchain where the token exists |
| Action | The operation being performed (v0_ValidateTickers with lock: Locked or v0_LockTicker) |
| Intent ID | The unique identifier for this request |
Reviewing the intent payload ensures you are signing exactly what you expect. This is especially important for bulk operations involving multiple tokens.
The tokens appear in the denylisted tab with a warning banner.
The tokens are denylisted when the intent is successfully executed.