Transaction list
The main Transactions view shows all submitted transactions with:
Filter by status, severity, date range, tags, direction, or search by transaction ID.
Transaction detail
Click a transaction to see:- Score breakdown — which rules matched and their individual contributions
- Linked parties — applicant and counterparty details
- Payment method — card, bank transfer, crypto wallet details
- Crypto Monitoring — for crypto transactions, a dedicated section showing:
- Provider risk score and severity badge (Crystal, Merkle Science, etc.)
- Transfer details (transaction hash, wallet address, blockchain, direction)
- Source of funds tab — pie chart of entity type distribution and sortable entity table with received/sent amounts and hop distances
- Counterparty connections tab — entities the wallet has transacted with, filterable by direct/indirect exposure
- Visualization button — interactive graph view of wallet relationships and fund flows using a node-edge diagram
- Travel rule - for virtual asset transfers, a dedicated tab showing the exchange status, rail, counterparty VASP (name, LEI, due-diligence score), the IVMS originator/beneficiary data cards, and the full status timeline.
Analysts with write access can act directly from here: Confirm/Reject ownership (
UNCONFIRMED_OWNERSHIP), Confirm corrected address (an inboundTRPtransfer inCOUNTERPARTY_MISMATCHED_DATA), Resend inquiry (unroutable outbound transfers), Finish transfer (report the on-chain hash on aCOMPLETEDoutbound transfer), and Cancel transfer. See Travel rule - Network graph — interactive node-edge visualization of transaction relationships and fund flows. See crypto screening
- Related transactions — other transactions involving the same subject or counterparty, with quick navigation
- Notes — internal analyst notes with timestamps, author names, and team member mentions
- Remediation — linked verification session if the transaction is in
AWAITING_USER - Timeline — full history of status changes, rule matches, analyst actions, and webhook deliveries
Rules management
All transaction monitoring rules are created and managed from the console. From the Rules tab:- View all active, disabled, and built-in rules
- See execution counters (how many times each rule has matched)
- Enable or disable rules without deleting them
- Create custom rules with the rule builder
- Edit conditions, velocity windows, and actions
Overview & analytics
The Overview tab displays transaction analytics:- Transaction count and volume over time
- Average transaction amount
- Approved vs. rejected vs. flagged trend chart (with previous period overlay)
- Category and action-type breakdowns
- User geography distribution
- Top rules triggered
- Analyst performance metrics
- Score distribution histogram
Bulk operations
Select multiple transactions to perform batch actions:- Export to CSV — download transaction data with configurable column selection
- Bulk status update — change the status of selected transactions (or all matching current filters) at once
- Bulk delete — remove selected transactions and their associated data
Travel Rule workspace
The Travel Rule tab is the compliance team’s home for the managed exchange, in four sub-tabs:- Transfers - every
travelRuletransaction with its sender, recipient, amount, direction, and exchange status; click a row to open the transaction and act on it from its Travel Rule tab. - Unmatched deposits - inbound Travel Rule transfers still waiting on counterparty data (
AWAITING_COUNTERPARTYorNOT_ENOUGH_COUNTERPARTY_DATA). - VASP directory - search the counterparty directory, including due-diligence scores and reachable rails.
- Address book - register, edit, and remove the wallet addresses inbound transfers resolve against, with each entry’s ownership-verification state.
Settings
Configure score thresholds, default currency, and blockchain analytics provider preferences from Transactions > Settings. Select remediation workflows directly on rules that move transactions toAWAITING_USER. See Settings for details.
The same page carries the Travel Rule card, with the master Travel Rule toggle in its header and three sections:
- VASP profile - your legal name, LEI, compliance email, jurisdiction, your read-only travel address (copyable once assigned), and the Discoverable in the VASP directory switch.
- Exchange policy - name matching strictness, confirmation timeout, on-timeout outcome, threshold amount, auto-accept for inbound transfers, and the Allow self-declaration / Allow screenshot proof proof-method switches.
- Interoperability networks - one row per network (Global Travel Rule, TRUST, VerifyVASP, Sygna Bridge).
A green Your membership badge marks networks you connected your own credentials for in the Marketplace, and the other rows link to the Marketplace with Connect in marketplace.
A network routes transfers only through a membership you connected yourself, because Didit has no platform membership on these networks today: it is onboarding as a provider.
Until you connect one, the row shows Not yet available instead of a switch.
Over GTR, VerifyVASP and Sygna Bridge, Didit reads the counterparty’s answer from the network; TRUST only sends, so a transfer delivered over it stays
AWAITING_COUNTERPARTYand moves toEXPIREDafter the confirmation deadline unless you cancel it. See Travel Rule networks.
Marketplace
The Marketplace section (own sidebar entry) is where you connect your own provider accounts:- Crypto monitoring: connect an existing blockchain analytics API key and pay the connected-key screening fee.
- Travel Rule networks - connect your own GTR, TRUST, VerifyVASP, or Sygna Bridge membership credentials. A network routes Travel Rule transfers only through a membership you connected, because Didit has no platform membership on these networks today: it is onboarding as a provider. TRUST only sends today, and receiving a transfer over any network is not switched on yet. CODE, TRISA, Notabene, and Veriscope are Request access tiles: they have no integration today and cannot route transfers. Each Request access request you send shows its status (Open, Contacted, In progress, Live or Declined) with Didit’s latest note. When Didit changes the status or the note, it emails the teammate who made the request, while they are still in your organization; a request made with an API key gets no email. See Travel Rule networks for what each network reaches today.
Next steps
Alerts
Alert triage and lifecycle.
Cases
Investigation workflow.
Rules
Configure the rule engine.