How ArcLend Protocol Cut Borrower Onboarding from 72 Hours to 4 — Without Sacrificing Collateral Coverage
About ArcLend Protocol
ArcLend Protocol is a permissioned DeFi lending platform serving institutional and accredited borrowers across Ethereum and EVM-compatible chains. Unlike open-access lending protocols, ArcLend's competitive position depends on the compliance rigor it enforces — institutional capital allocates to ArcLend because the protocol runs KYC and transaction monitoring standards comparable to a traditional credit desk. Compliance is not overhead at ArcLend; it is the product.
The Challenge
ArcLend was running into two separate compliance problems that had been treated as independent but were, in practice, compounding each other.
The first was borrower onboarding. Manual KYC averaged 72 hours end-to-end for straightforward individual applicants, and five or more days for complex entity structures — holding companies, multi-jurisdiction trusts, DAO-adjacent structures with layered beneficial ownership. Institutional borrowers, who had approached ArcLend precisely because of its compliance standards, were walking away mid-onboarding. Drop-off was running at 28%, nearly all of it in the document review phase.
The second problem was collateral screening. ArcLend's compliance program screened wallets at deposit — confirming that collateral wasn't flagged at the moment it entered the protocol. What it did not do was monitor collateral continuously across the loan lifecycle. A wallet that was clean at deposit could be flagged by sanctions list updates the following week, and the protocol would have no visibility into that change until the next manual audit cycle.
"We are technically OFAC-compliant at the moment of deposit. We are not OFAC-compliant across the loan lifecycle."— General Counsel, ArcLend Protocol
The gap between point-in-time compliance at deposit and continuous compliance across the life of the loan was the most significant legal exposure in the protocol — and it was the kind of gap that tends to surface at the worst possible moment.
The Solution
Infinihash deployed both KYC and KYT in a coordinated five-week integration, treating the two systems as a unified compliance layer rather than two separate tools.
On the KYC side, the Infinihash KYC API replaced manual document review end-to-end. OCR extraction with per-field confidence scoring handled routine submissions without reviewer intervention. Liveness checks were integrated directly into the applicant flow. Complex ownership structures — entities with layered beneficial ownership, multi-jurisdiction trustee arrangements — were routed to an exception queue with pre-extracted entity data already populated, so reviewers were adjudicating ambiguity rather than reconstructing entity graphs from uploaded PDFs.
On the KYT side, every borrower wallet was registered with the Infinihash monitoring API at the moment a credit line was activated. From that point, each collateral deposit was screened against the OFAC SDN index and the full entity label set in real time. Webhooks delivered state changes — new sanctions designations, label updates, pattern alerts — directly to ArcLend's internal systems. A whitelist of known-clean counterparty wallets was maintained to suppress repeat screenings on established relationships. ArcLend's smart contracts were wired to receive hold signals from the compliance API, enabling protocol-level response to compliance events without manual intervention.
The Results
Borrower onboarding dropped from 72 hours to 4 hours for standard applicants, and to 18 hours for complex entity structures that previously averaged five days. Analyst time spent on routine KYC fell 78%, redirected entirely to edge cases. Applicant drop-off fell from 28% to 11%.
Sanctions coverage reached 100% of collateral across the full loan lifecycle, including wallets already in the protocol at integration time, which were retroactively enrolled. In six months of production operation, ArcLend recorded zero false-positive collateral freezes — the whitelist and behavioral context eliminated the noise that typically makes continuous monitoring operationally painful.
Collateral freeze response time — from a sanctions designation event to protocol-level hold signal — reached a p95 of under 90 seconds. LP due diligence preparation, previously an eight-hour manual compilation exercise, fell to 45 minutes because the compliance API could generate a current-state summary of all borrower and collateral positions on demand.
"We were essentially running two separate compliance programs that never talked to each other — one for who could borrow, one for where the collateral came from. The gap between them was where our real exposure lived. What Infinihash gave us is a single API surface that closes that gap. KYC tells us who the borrower is. KYT tells us whether their money is clean, not just at deposit time but every day the loan is outstanding. For a lending protocol, that's the whole compliance picture — and we have it now in a way we genuinely did not before."
Key Takeaways
- Permissioned lending protocols need two compliance layers working in concert — identity verification of the borrower and continuous monitoring of the collateral — not two separate point-in-time checks.
- 72-hour onboarding windows cost deals already won with institutional borrowers; the drop-off happens after intent, not before it.
- Point-in-time sanctions screening at deposit is insufficient for a protocol that holds collateral across a loan lifecycle — continuous monitoring via webhooks is the correct standard.
- Event-driven webhooks wired to smart contract logic close the gap between on-chain collateral events and compliance-program awareness without requiring manual audit cycles.
- Running KYC and KYT through a unified API surface eliminates entity model divergence — the borrower identity known to KYC is the same entity monitored by KYT, with no reconciliation layer required.
Building a permissioned lending protocol or DeFi compliance program? Let's talk.
Talk to the team