Skip to content

TRM Labs Integration for Firms That Screen Customer Transfers

A firm on TRM Labs needs software that files each transfer under the customer's account ID. It also holds deposits while a result is pending and catches late alerts. Protofire builds that software. In 2021 we built the DEX core of Swarm Markets, a BaFin-licensed DEX at launch.

Luis Medeiros

Reviewed by Luis Medeiros, Field CTO at ProtofireLast reviewed: November 2026

On this page
  1. Overview
  2. Four problems
  3. TRM facts
  4. What you get
  5. Why Protofire
  6. Phases of work
  7. How work starts
  8. Who decides
  9. Not the right fit
  10. Related guides and services
  11. FAQ

Work shipped for 60+ networks and 95+ protocols, including

  • Chainlink
  • Ethereum
  • Solana
  • Safe
  • Ripple
  • Aave

TRM results can arrive hours after the transfer

TRM results can arrive hours after the transfer they judge. So your firm needs a hold that it controls and a way to catch late alerts. For example, your compliance team has picked TRM Labs, and a customer deposit has just confirmed onchain. Your TRM Labs integration has to say whether the credit waits, and what happens when TRM's answer comes hours later.

TRM Wallet Screening assesses an address "prior to authorizing a transaction" (TRM). TRM Transaction Monitoring takes a transfer "before or after it's processed", in the words of Persona's TRM connector docs (Persona). Transaction Monitoring then rescreens transactions daily and raises alerts under multi-condition rules (TRM).

Fireblocks' TRM docs say that its timeout windows "are measured in hours". When a window closes with no result, a default verdict applies unless your policy sets another. The default is Accept for an incoming transfer, "since the funds have already arrived", and Reject for an outgoing one (Fireblocks).

TRM supplies scores, statuses, alerts and its own case management. Your firm decides which call gates which step, where the money waits and who closes an alert. Protofire integrates TRM Labs through the custody connector or directly, on your own TRM contract.

TRM Wallet Screening and Transaction Monitoring inside a firm's transfer flow

A TRM result can arrive hours after the transfer it judges. So the firm's ledger holds the money, and the alert intake reconciles what TRM reports later.

The firm

App and operations screens

Address book, pending-deposit view and the release queue.

Ledger and holds

Core system or client-balance ledger, with suspense positions.
TRM Labs

TRM Wallet Screening

Address risk, returned before a withdrawal is authorized.

TRM Transaction Monitoring

Registered transfers, rules, daily rescreening, alerts and TRM's own case management.
The firm's other vendors

Custody platform and case tool

Fireblocks, Utila or the firm's own signer. Unit21, Corsa or the bank's AML case system.
Protofire builds

Transfer service

Address screens, transfer registration, holds and Wait windows.

Alert intake

Webhook receiver, scheduled read-back and closure relay.

Evidence store

Raw TRM responses, UUIDs, rule versions, and each decision with its approver.

Four problems that TRM results leave to your firm

TRM scores what is registered with it, and each connector and each customer mapping decides what reaches TRM.TRM's API reference is behind its customer login (TRM docs). So the field names in this section come from Persona's connector.

Transfers filed under the wrong customer

TRM groups transfers under an account external ID. In Persona's connector, the account external ID is a required field on each transfer (Persona). Corsa's connector matches that ID to a client. Unless Corsa's connector is set to create missing clients, it skips alerts that it cannot match until a matching client exists (Corsa). If payouts for many end customers share one account ID, their alert histories merge. Protofire sends a pseudonymous ID for each customer account and keeps the mapping table in your audit file.

TRM results that arrive after the credit

TRM added webhooks for Transaction Monitoring alerts in February 2026 and noted that "Polling for alerts can introduce avoidable delays" (TRM). As of November 2026, TRM's public pages describe no webhook payload, signature or retry policy. So the alert intake that Protofire builds treats each webhook as a signal and fetches the alert by its UUID. A scheduled list of open alerts catches a webhook that did not arrive. The Fireblocks setting bypassScreeningDuringServiceOutages does not apply to TRM.

Outgoing Fireblocks transfers missing from TRM monitoring

As of November 2026, Fireblocks' TRM page says: "Outgoing transactions are not registered with TRM Labs transaction monitoring during Early Access." Fireblocks screens outgoing transactions through Wallet Screening instead (Fireblocks). Protofire registers each confirmed withdrawal directly as a CRYPTO_WITHDRAWAL under the account ID that matches the Customer Reference ID that Fireblocks sends. So incoming and outgoing transfers both appear in the customer's TRM history.

A TRM alert does not move a balance

Nothing in a TRM alert moves a balance until your ledger or custody policy acts. Persona's connector shows an alert with a status of Open or Closed, a risk score level from 1 to 15 and an owner. The alert is closed as Flagged or Dismissed, with a justification (Persona). Protofire books each deposit to a suspense position. The deposit is held there until its TRM transfer shows Succeeded and the alerts above the agreed level are Closed. If a status is still Pending at the cut-off that your compliance team signs, the daily hold report shows it as stale. A Dismissed closure lets your posting service release the amount. A Flagged closure sends the amount to a blocked position or to a return that your own staff approve.

[...] VASPs should [...] identify suspicious patterns in VA transactions and detect rapid transfer of VAs using transactions monitoring and blockchain analytics tools.
Financial Action Task Force (FATF), Targeted update, Inter-governmental body that sets the global AML/CFT standard · Targeted Update on Implementation of the FATF Standards on Virtual Assets and Virtual Asset Service Providers, July 2026

TRM Labs products, API documentation and regions

Products
TRM's Crypto Compliance products are Wallet Screening, Transaction Monitoring, Entity Due Diligence, Know-Your-Asset and Real-Time Supervision (TRM).
API documentation
The API reference is behind TRM's customer login. The public sets are Sanctions and Chainabuse (TRM docs). The Sanctions and Beacon Network API is free, and its docs are sent on request (TRM docs).
Regions
TRM's status page lists US, EU and GovCloud. It shows the Wallet Screening and Transaction Monitoring APIs as separate US and EU components (TRM status).

Checked November 2026 against TRM Labs' product pages, llms.txt and status page, and the TRM documentation of Fireblocks, Persona, Corsa and Sumsub.

What you get from a TRM Labs integration with Protofire

Account IDs mapped to your customers

Your compliance team signs the table that shows which customer each account ID stands for. Protofire maps a pseudonymous account ID to each customer in your core banking or client records. We also call Wallet Screening before each withdrawal is signed, and we register final deposits and sent withdrawals with Transaction Monitoring.

Pending deposits held in your own ledger

The customer sees a pending deposit while your finance team's posting rules decide the rest. Protofire builds the suspense and blocked-funds lines and the posting rule for each result. On Fireblocks, your compliance team sets a Wait window for each direction. Your Fireblocks admins enter that window as a custom rule, which takes precedence over the defaults (Fireblocks). A daily report shows the age of each held amount.

Late TRM alerts in your analysts' queue

Your analysts see TRM alerts where they already work, including alerts that the webhook missed. Protofire builds the webhook endpoint, the read-back by alert UUID and the scheduled list of open alerts. A count shows what the webhook missed. Closures that your analysts record are sent back to TRM with the deciding analyst's email, with retry. The closures are sent on a TRM API key that your firm issues and can revoke.

A TRM rule history that an examiner can read

Your compliance team writes the TRM rules from its risk assessment and enters them in TRM. Protofire runs test screens of known addresses against those rules. We copy each change that TRM's risk-engine audit log shows and pair it with the reason and approver from your change record.

A write-once store of TRM requests and decisions

A write-once store keeps each TRM request and response, with the transfer and alert UUIDs. The store also keeps the closures and the rule versions. Reports cover holds and stale statuses. Other reports cover missed webhooks and alerts per rule.

Our record: the DEX core of Swarm Markets, a BaFin-licensed DEX

Protofire's record includes Swarm Markets, a BaFin-licensed DEX at launch where only KYC-verified wallets trade.In 2021 our engineers built the Swarm DEX core and its subgraph. The DEX core is a Balancer fork, and we also contributed to dOTC. Swarm held the license and ran the KYC. The Swarm work applies to a TRM Labs integration, because our code was written to work beside a compliance check that the operator ran.

Phases of a TRM project with Protofire

  1. Step 1

    An engineer reads your TRM setup first

    A written proposal follows, with findings and a plan in phases. The first phase checks each field on this page against TRM's API reference under your login.
  2. Step 2

    Account IDs, screening calls and holds come first

    The mapping table, the screening calls and the ledger holds are delivered together. So a deposit is credited only after its TRM status is known.
  3. Step 3

    Alert intake and the closure relay come next

    The webhook receiver, the read-back and the case-tool sync are built in this phase, with the reports. The alert route is settled as webhook plus read-back.
  4. Step 4

    Code, credentials and operation after launch

    The code, configuration and runbooks are yours. Your staff hold the credentials that the services run on. Your team runs the integration, or Protofire's managed onchain operations service can watch it.

How work with Protofire starts

You send us the TRM products you license and the region your TRM account runs in.You also send your custody platform and the ledger that records held deposits. The services call TRM on credentials that your staff issue and hold. A service that Protofire runs after launch runs under a written scope, which names each write call that the service sends to TRM. The terms in this section apply to each phase, as set out on how we work.

Proposal
In writing, one business day after the discovery call: findings, a plan in phases and the first step we recommend.
Price
Fixed per phase when you commission it, against written acceptance criteria. Overruns inside them are ours to absorb, invoices follow delivered milestones, and you can stop at any phase boundary. Anything we operate after launch is priced in the proposal as its own recurring line, with the notice to end it.
Ownership
Code we write for you, contracts, the keys and credentials this work creates and the accounts your infrastructure runs in are yours by contract, within the license of any third-party software involved. Keys that a custody platform or a staking provider holds under its own key model stay with it under your contract; every other custody key stays with you or the custodian you appoint. Where the scope places something on servers we rent, it says what moves to you and when. An NDA is available from your first message, and we sign a data processing agreement (DPA) together with it.
After launch
Delivery closes with a hypercare window and a defect warranty, with their terms written into the proposal. A service we operate continues under its written scope until that scope ends.
Access
Read-only by default. A role that can start requests only if your written scope names one; never a signer, approver, administrator, key holder or recovery role on your contracts, wallets or custody platform. Services we build call each platform on credentials your staff issue and keep in your vault. Anything that approves or moves funds runs in your environment, and a scope under which we operate a service lists every write call it makes. Where the scope has us operate nodes, validators, monitors, explorers or indexers, it names the role and any key we hold on those servers, and in your own cloud account you can remove it.
Licenses
Protofire is an engineering firm and holds no financial or crypto-asset license; licensed activity stays with you and your providers.

How we work shows a worked proposal.

What TRM supplies and what your compliance team decides

TRM supplies the data and the alerts, and your compliance team makes the decisions on them.TRM publishes incidents and maintenance per region and per API on its status page.

Your compliance team signs the rules and closes alerts under its own name. It files reports to an FIU and decides what a Flagged closure means for a return. Protofire builds the code that applies the rules you sign. Protofire gives no legal opinion and takes no compliance decision.

When a TRM setup does not need Protofire

You may not need Protofire when a tool you already run connects to TRM, or when TRM's own features cover your product.

  • Your case tool already connects to TRM. Unit21 brings TRM Transaction Monitoring alerts into its case management (Unit21). Corsa's docs describe a sync in both directions (Corsa). Sumsub's docs describe screening with a TRM rule bundle under your own TRM contract (Sumsub). In that case, the alert intake that Protofire builds becomes configuration.
  • You run an exchange on HollaEx. HollaEx's plugin docs say that HollaEx screens held deposits and withdrawals with your own TRM account. The same docs say that HollaEx falls back to TRM's Sanctions screening (HollaEx).
  • Your analysts work alerts in TRM's case management, and your ledger books no hold.
  • Your sanctions checks run at low volume on TRM's free Sanctions and Beacon Network API (TRM docs).
  • You need a risk assessment or VASP diligence. TRM's Compliance Advisory sells both.

Protofire holds no financial or crypto-asset license. Protofire takes no signing, admin or approval role in custody.

FAQ

What is a TRM Labs integration?
A TRM Labs integration is the software that calls TRM Wallet Screening before a withdrawal is signed. It also registers deposits and withdrawals with TRM Transaction Monitoring under each customer's account ID. The integration holds funds in the firm's ledger while a result is pending and brings TRM alerts into case work. Protofire builds TRM Labs integrations, and the firm's compliance team sets the rules.
Who can build a TRM Labs integration for a bank, a payment firm or an exchange?
Protofire builds the firm's own part of a TRM Labs integration, which is the holds, the late-alert intake and the evidence store. TRM supplies screening, monitoring and case management. As of November 2026, Fireblocks sells TRM as an Early Access add-on. Utila's October 2024 announcement shows TRM risk inside Utila's wallet screens (Utila).
Do we need TRM Wallet Screening, Transaction Monitoring or both?
A firm needs both TRM products if it holds customer funds and needs alerts after a transfer settles. Transaction Monitoring watches registered transfers against the firm's rules and rescreens them daily (TRM). Fireblocks splits the two products by direction. Incoming transfers go through Transaction Monitoring, and outgoing ones go through Wallet Screening (Fireblocks).
Should TRM alerts arrive by webhook or by polling?
TRM alerts should arrive both by webhook and by polling. TRM added webhooks for Transaction Monitoring alerts in February 2026, and the webhooks send alert events to your endpoint as they happen (TRM). A scheduled read of open alerts catches a webhook that did not arrive. A read-back confirms each update you sent.
Which networks can TRM monitor for deposits?
TRM's deposit coverage depends on the network and on the connector. TRM's key facts give 185 blockchains as of October 2026 (llms.txt). But Persona's TRM connector lists 49 of its 66 networks for all transfers. The connector lists the other 17, including Monero, Lisk and Neo, for withdrawals only (Persona). Sumsub tells TRM users to check per chain whether token screening is available (Sumsub).
Where does TRM process our data?
Where TRM processes your data depends on your TRM account. TRM's status page shows separate US and EU APIs (TRM status). TRM's privacy policy states compliance with the EU-U.S. Data Privacy Framework (TRM).

Get a proposal

Tell us what you are building. An engineer reads it, we have a short call, and the written proposal follows within one business day.

Luis MedeirosField CTO, reads every request · LinkedIn

A demo or repository link also works.