Chainalysis Integration for Banks, Payment Firms and Exchanges
A Chainalysis integration pre-screens withdrawals before custody signs, holds flagged deposits in your ledger and routes alerts to your case tool. Protofire builds it for banks, payment firms and exchanges, and your compliance team keeps the rules. In 2021 we built the DEX core for Swarm Markets, BaFin-licensed at launch.

Reviewed by Luis Medeiros, Field CTO at ProtofireLast reviewed: November 2026
On this page
Work shipped for 60+ networks and 95+ protocols, including
What a Chainalysis integration has to decide
After you sign with Chainalysis, your Chainalysis integration has to say whether custody waits for KYT when a withdrawal request arrives. The integration also has to say what happens when the answer is late.
On Fireblocks, for example, Chainalysis has a window of 1 minute for an outgoing transfer and 10 minutes for an incoming one. Once Chainalysis misses that window, the Fireblocks default is "outgoing is sent, incoming is released". The default comes from a Fireblocks setting called bypassScreeningDuringServiceOutages, and the firm can set it to false.
Chainalysis supplies risk levels, alerts and the Reactor investigation tool. Your firm decides what an alert does to the books, who reviews the alert and what the file shows an examiner. For firms that hold their own Chainalysis contract, Protofire integrates Chainalysis through the custody platform's connector or directly against the KYT API.
Four ways a Chainalysis setup breaks
Chainalysis can score only the transfers that reach it, and each custody connector sends it a different set of transfers.EU payment and crypto-asset service providers review their screening system at least once a year. They also document what the system can and cannot detect (EBA/GL/2024/15, paras 6-7). On a Chainalysis setup, the four gaps that follow are the first lines of that yearly record.
Transfers that do not reach KYT
Fireblocks does not register an outgoing ERC-20 transfer that lacks a USD price, and an incoming transfer without a USD price raises no alert. So the transfer moves without a KYT score. Ripple Custody screens counterparty addresses, but its documentation describes no KYT transfer records. Protofire builds a daily count of the transfers that moved without a KYT result. We then register each of those transfers from a backlog once KYT answers.
When the KYT answer arrives after the transfer
On Fireblocks, with bypassScreeningDuringServiceOutages set to false, an outgoing transfer fails and an incoming transfer is frozen. Dfns has a skipChainalysisFailure switch. When that switch is on, a Chainalysis error lets the transfer pass. Protofire writes the rule for a missing answer with your compliance team and sets the rule in each connector. We also keep a backlog of the transfers that moved while the answer was missing.
KYT alerts that freeze nothing by themselves
A Severe KYT alert freezes nothing by itself. Dfns' inbound wallet screening "reports results without blocking". A custody freeze takes effect inside custody, but your ledger records the customer's balance. Protofire books the hold in your ledger, so the custody and ledger states match.
Chainalysis coverage that varies by network
Sumsub's table of Chainalysis coverage marks most listed networks "Pre-growth", with "Listed assets only". So the depth of Chainalysis support differs from one network to another. Protofire checks each new asset against Chainalysis coverage and your custody connector before the asset is listed.
Chainalysis products, APIs and network coverage
- Products
- KYT for transfers, Address Screening for wallets, VASP Risking for counterparty providers, Sentinel for token issuers, Reactor for investigations.
- Interfaces
- KYT API and Address Screening API. The API reference is behind Chainalysis' customer login.
- Reach
- Chainalysis' KYT page states "400+ networks and 50M+ tokens".
- Address Screening
- Address Screening scores a wallet before a transfer exists, such as a saved withdrawal address. KYT scores and monitors the transfers.
- Travel Rule
- Chainalysis' product list has no Travel Rule messaging product. So a provider such as Notabene, Sumsub or 21 Analytics handles the Travel Rule messages.
Checked November 2026 against Chainalysis' documentation and the connector documentation of Fireblocks, Dfns and Ripple.
What you get from a Chainalysis integration with Protofire
Screening rules your compliance team has signed
Each threshold, severity level and screening point is tied to your risk assessment, and the reason for each one is on file. Protofire sets a pseudonymous ID for each customer and drafts the rules that your administrators apply in the custody console. We test the rules against known high-risk and clean addresses.
Withdrawals signed after the KYT and Travel Rule checks
Custody signs a withdrawal after both the KYT pre-screen and the Travel Rule result are in. Protofire calls KYT and Address Screening at each point where a transfer moves. We rescreen saved addresses on a schedule and write a separate rule for missing originator data. Our EU Travel Rule guide sets out the reach of each Travel Rule provider.
Flagged deposits held in your ledger
The customer sees a deposit as pending and gets no credit until KYT and the Travel Rule check pass. Protofire builds suspense and blocked-funds positions in core banking, a custody subledger or the exchange's own balance ledger. We agree the posting rules for hold, release, return and freeze with finance. Your own staff release the hold in custody. Our Fireblocks integration page covers how the custody events themselves are booked.
KYT alerts in the case queue your analysts already work
A KYT alert above the agreed severity opens a case in your case tool. The case shows the customer, the transfer, the alert ID and the exposure. Your decision is written back to the alert in KYT, and analysts open Reactor from the case. Crypto alerts appear next to your fiat alerts.
An evidence store an examiner can replay
The evidence store keeps each raw Chainalysis response with the rule version, the decision, the approvers and the times. The reports show screened routes, bypassed checks, hold times and alerts per rule. Your team can write the yearly review from those reports.
How a Chainalysis project with Protofire runs
- Step 1
Review of your connector, rules and ledger
First, an engineer reads your custody connector settings, your KYT rules, the assets you list and the ledger where held deposits are booked. A written proposal follows. The proposal sets out findings and a plan in phases. - Step 2
Screening calls and ledger holds first
Protofire builds the screening points and the ledger holds together, so no deposit is credited before its result is in. Test runs with known high-risk and clean addresses follow. - Step 3
Alert routing and reports after the holds
Alert routing, the evidence store and the reports come next. - Step 4
Ownership and access after launch
The code, configuration and runbooks are yours. Your staff hold the credentials the service runs on. After launch, Protofire keeps read-only access unless your written scope adds a role that can initiate requests. Your team runs the integration, or Protofire's managed onchain operations service can watch it.
How work with Protofire starts
You send your custody connector, your KYT rules and the ledger where held deposits are booked.The written proposal then maps each screening point to a phase. 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.
Our record: Swarm Markets and a MiCA compliance blueprint
Protofire's public record here is engineering for a licensed venue and a published blueprint of the vendors that a licensed firm rents.The same holds for a Chainalysis integration: the operator runs the check, and the engineers build software around its result.
Swarm Markets DEX core and subgraph, 2021
Swarm Markets was a BaFin-licensed DEX at launch where only KYC-verified wallets trade. In 2021 Protofire built the Swarm Markets DEX core and subgraph, and both repositories are public. Swarm held the license and ran the KYC. The Swarm Markets case describes the build.
Day-One MiCA Compliance Stack blueprint
Protofire's Day-One MiCA Compliance Stack for CASPs lists Chainalysis among the screening-data vendors that a new CASP rents. The blueprint covers screening next to onboarding, Travel Rule and records.
What Chainalysis supplies and what your firm decides
Chainalysis supplies the data, and the firm makes the decision.A risk level is exposure data. A risk level does not say whether the transfer reached KYT, whether the Travel Rule data arrived or what to do with the money. A clean score can also arrive while the Travel Rule message is missing.
Chainalysis runs its own platform and the risk levels it returns. Your compliance team keeps the KYT rules, each release decision and each report to an FIU or a sanctions authority. Protofire writes the code that applies the rules you sign.
Even with the use of blockchain analytics tools, DPTSPs are reminded to customise the risk parameters/rules within the tool, as appropriate, to be aligned with their ML/TF risk appetite and compliance policies.
When a Chainalysis project with Protofire does not fit
You do not need outside engineers when your case tool already pulls KYT alerts.The same is true when one connector and KYT's own case management cover your product.
- Your case tool already lists a Chainalysis connector. For example, Corsa syncs alerts every 10 minutes by default and pushes status changes back to KYT. Protofire's case-routing work then becomes configuration, or drops out.
- You run one custody platform and one product, and you work alerts in KYT. The connector and KYT's case management are enough until a hold has to be posted to a ledger.
- You buy a white-label crypto offer with Chainalysis built in. Then the vendor of that offer owns the KYT calls.
- Your problem is joining several vendors, of which Chainalysis is one. Protofire's compliance integration service covers KYC, screening and Travel Rule vendors as one decision.
Protofire does not set your risk appetite or thresholds, and does not run Chainalysis itself. We neither decide nor file reports to an FIU or a sanctions authority. Protofire takes no signing, admin or approval role in custody, and we hold no financial or crypto-asset license. After go-live, Protofire operates the integration only under a written scope.
FAQ
What is a Chainalysis integration?
Who can build a Chainalysis integration for a bank, a payment firm or an exchange?
How does KYT screen a withdrawal before it is signed, and a deposit after it arrives?
Why did a transfer not reach Chainalysis?
Do we need both KYT and Address Screening?
Can we still use the Chainalysis Sanctions Oracle?
What customer data does Chainalysis receive, and where does Protofire appear in a DORA register?
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.
