
Why off-ramp providers struggle to get the counterparty data they need
Pooja Shah, Rain
Moment at 55:20Episode 6 · Stablecoins Go Mainstream: Inside the New Payments Stack
Protofire builds blockchain compliance integration for regulated crypto firms that have chosen KYC, screening and Travel Rule vendors. We join the vendors' answers into one recorded outcome per transfer before custody signs or a deposit is credited. In 2021 we built the DEX core of Swarm Markets, BaFin-licensed at launch.

Reviewed by Luis Medeiros, Field CTO at ProtofireLast reviewed: November 2026
Work shipped for 60+ networks and 95+ protocols, including
In blockchain compliance integration, the decision belongs where compliance can still stop a crypto transfer. Compliance can stop a withdrawal before custody signs it and a deposit before the ledger credits it. For an issuer, compliance can also stop a transfer inside the token contract. After those points, the chain has already moved the value.
A firm that has chosen its KYC, screening and Travel Rule vendors still has to settle which answer custody waits for. When a withdrawal request arrives, each vendor answers in its own format. For example, Fireblocks lists three screening vendors side by side. Chainalysis returns a risk category, Elliptic returns a numeric score, and TRM Labs returns a category with an extra Wait outcome (Fireblocks). A category and a score need a mapping before they can be compared.
Since 30 December 2025, the EBA's sanctions-screening guidelines expect each crypto transfer to be screened before the assets reach the beneficiary (EBA/GL/2024/15, para 19). If nothing joins the vendors, each answer is stored in that vendor's own log. The firm then cannot show one decision per transfer or the rule version behind it.
Vendors answer, and the decision service records one outcome per transfer.
Protofire writes the rule set that turns four vendor answers into go, review or stop. The four are KYC status, the Travel Rule result, address risk and name hits. Each vendor timeout also gets a written rule. On Fireblocks, your administrators set a custody policy that accepts withdrawals only from the decision service's API user (Fireblocks).
Protofire hands each review to the case manager that your analysts already use. The analyst then decides with the vendor answers in front of them.
A lapsed identity or a new sanctions hit stops the customer's next crypto withdrawal. After each list change, Protofire rescreens the customer base. We also re-run withdrawals already in the queue against the new list.
A transfer to a provider and a transfer to a self-hosted wallet come with different duties. Protofire classifies each destination and matches EU providers against ESMA's register. We also collect ownership proofs where the law asks for them, and we rescreen the whitelist.
A deposit under review is kept in a finance-approved hold. Protofire books returns to the originator for transfers that lack data. We book freezes for confirmed sanctions matches. The firm pays the gas for a return, and that gas is booked as the firm's cost. For an issuer, we add transfer and freeze rules inside the token through ERC-3643 development.
The evidence store that Protofire builds keeps raw vendor answers, rule versions, decisions and reviewers. The store also keeps a written list of what each vendor can and cannot detect. A vendor change leaves the history readable. After launch, Protofire can watch vendor timeouts and unanswered Travel Rule messages under a written scope, as part of managed onchain operations.
A firm can buy identity checks, risk data and Travel Rule messaging from vendors.The decision that joins them is built firm by firm.
Bought from a vendor: KYC and KYB checks, including unhosted wallet verification at some vendors
Protofire builds: A customer status that the transfer service reads, refreshed when a sanctions list changes
Bought from a vendor: Results from Chainalysis, Elliptic or TRM Labs, each in a different format
Protofire builds: One severity scale that compliance signs, with each raw answer stored next to the decision
Bought from a vendor: Protocols and networks such as TRP, GTR and TRISA
Protofire builds: Counterparty classification, the send and receive steps, and a count of counterparties that fail to send data
Bought from a vendor: Each vendor's own logs
Protofire builds: One record per transfer, with the vendor answers beside it
In 2021 Protofire built the DEX core and subgraph for Swarm Markets.Swarm Markets was a BaFin-licensed DEX at launch, and only KYC-verified wallets trade on it. We also contributed to its dOTC contracts. Both repositories are public.
Swarm held the licenses and ran KYC itself. The Swarm Markets work applies to compliance integration because it was engineering for a venue whose operator holds the license and runs KYC. Protofire integrates Chainalysis, Elliptic, TRM Labs, Notabene and Sumsub, and each integration has its own page.
A withdrawal reaches custody after one recorded decision covers its customer status, destination, screening results and Travel Rule data.A deposit goes through the receiving side of the same checks before it is credited.
Checked November 2026 against the EUR-Lex texts and the EBA's guidelines.
The Travel Rule route is chosen before the build, and the route sets which counterparties you can reach.Routes differ in who they reach, and a firm usually needs more than one. On one Fireblocks workspace, Notabene cannot run alongside Sumsub or GTR (Fireblocks). TRISA and TRP have been interoperable since 2023. Both are now under the OpenVASP Association, and TRISA has been under it since 1 October 2026 (OpenVASP). Protofire's EU Travel Rule guide scores eight routes on reach and data security.
For transfers of crypto-assets, several messaging [...] systems exist [...]. Not all are interoperable, which means that CASPs might have to use multiple systems to be able to transact with their counterparties. This can create data integration issues and hamper institutions' ability to comply with travel rule requirements.
A separate integration fits poorly when one platform already covers your flow, or when you need a compliance function rather than engineering.
You tell us the compliance vendors you contract today, your custody platform and the system that credits customer balances.From that list, Protofire lists each vendor answer that the decision service must read at each of your control points. The decision service runs in your infrastructure. Your staff hold its credentials, and no Protofire operator holds them. You own the evidence store.
How we work shows a worked proposal.

Pooja Shah, Rain
Moment at 55:20Episode 6 · Stablecoins Go Mainstream: Inside the New Payments Stack
Tell us what you are building. An engineer reads it, we have a short call, and the written proposal follows within one business day.