Blacklist (Anti-Fraud)
Access prerequisites
- Permission (module):
manageAntifraudBlacklist - License/Feature: None
- Menu container: GENERAL → group Audit
What it is / when to use
The Blacklist screen (/antifraud-blacklist) lists the wallets and accounts marked as suspicious/blocked for the anti-fraud engine. When an operation has an origin or destination on the blacklist, critical severity rules fire (e.g., isFromBlacklistedSource, isPixKeyBlacklisted, to_blacklisted_destination), pushing the score toward automatic blocking.
Use this screen to audit which addresses/accounts are blocked, who added them and why.
Prerequisites
- Permission: module
manageAntifraudBlacklist. Permission is dual — CPM enum on the backend + dynamic module in the DB. - License/Feature: none.
- Dependencies on other screens: entries are consumed by AntifraudService during real-time evaluations (category
counterparty).
Step by step
Consult
- Go to GENERAL → Audit → Blacklist.
- The table loads the entries (local pagination: 10/20/50 per page).
- Consult the wallet, account, who approved it, the reason and the date of inclusion.
Add an entry
- Click Add at the top of the screen to open the form.
- Enter the Wallet and Account (required) and, optionally, the Reason for the block.
- Click Save to blacklist.
- The system requests step-up re-authentication — confirm your identity with password/MFA to finish.
- The Blocked by field is filled automatically with the authenticated operator.
Remove an entry
- On the desired row, click the trash icon (Actions column).
- Confirm the step-up re-authentication when prompted.
- The removal is permanent (hard delete) and the counterparty is no longer blocked by the blacklist rules.
Filters and columns
| Filter / Column | What it shows | Data source |
|---|---|---|
| Wallet | Blocked wallet address | wallet |
| Account | Associated account | account |
| Approved by | Administrator who added the entry | approved_by |
| Reason | Justification for the block | reason |
| Created at | Date/time of inclusion (formatted) | createdAt |
| Actions | Remove the entry (requires step-up) | — |
Business rules / considerations
Attention
- The blacklist is fed automatically from public sanctions lists (OFAC — SDN List and the list of sanctioned crypto addresses). That is, many entries arrive without manual action — they reflect regulatory sanctions.
- Blocking an address/account has a critical effect on anti-fraud: operations involving that counterparty tend to be blocked automatically. Record who approved and the reason for manual additions — this is the audit trail.
- Adding and removing require step-up (password/MFA re-authentication, ~5 min window). The same wallet cannot be blocked twice — the system rejects duplicates.
Operational impact
- A blacklist entry can immediately interrupt transactions of legitimate customers who interact with the listed counterparty. Review carefully before adding manually and confirm there is no undue overlap with the Whitelist.