Global Ledger Integration

Compliance is a mandatory part of the execution layer. When an institution sends funds, risk screening must happen before the transaction is broadcast, not after. That principle has shaped our native integration with Chainalysis. Today, we are extending that model.

Dfns now integrates Global Ledger as an alternative KYT and AML data source which combines well with our policies, permissions, webhooks and other security and compliance-led components. This gives customers more flexibility in sourcing compliance intelligence while preserving the same enforcement logic and operational guarantees.

Screen outbound transfers before they hit the network

The integration connects Global Ledger’s advanced-tier API directly into Dfns transaction policies. The focus is precise: outgoing transfers. Before a transaction is broadcast, policies query the client’s dedicated Global Ledger environment using their own API key and base domain. The response is evaluated in real time against a configurable risk score threshold.

If the risk score exceeds the defined threshold, or if Global Ledger raises an alert, the policy is triggered. From there, the transaction can be blocked, escalated, or routed through additional approvals depending on the organization’s configuration. Risk intelligence becomes enforceable control.

This mirrors the native architecture of our Chainalysis integration: compliance data flows directly into the policy framework, without requiring customers to build separate monitoring pipelines or custom middleware.

Connect your own GlobalLedger instance, keep your keys

Each customer connects Dfns to their own Global Ledger instance. API keys remain customer-owned and isolated. Dfns does not centralize or proxy compliance data across clients. Both Global Ledger’s essential- and advanced-tier supported chains are included in the scope, ensuring coverage and signal quality aligned with institutional standards. The activation model remains simple: once credentials are provided, compliance checks are embedded directly into wallet policies. No additional infrastructure, no external orchestration.

Change your KYT provider without changing your policies

Not every institution standardizes on the same KYT provider. Procurement constraints, jurisdictional requirements, and cost considerations vary. By integrating Global Ledger, Dfns allows customers to diversify vendors without fragmenting enforcement logic. The compliance provider may change, policies don’t. Transactions are still evaluated before execution. Governance rules still apply. Decisions remain deterministic and auditable.

Embed compliance at the transaction layer

The deeper point here is architectural. As regulatory expectations increase across jurisdictions, from MiCA in Europe to evolving FinCEN guidance in the United States, institutions need compliance tooling that is composable, meaning they can swap providers, adjust thresholds, and extend coverage without re-engineering their wallet infrastructure.

Dfns is building toward that model. Chainalysis, and now GlobalLedger, are the first two options. The policy engine is designed to accommodate others. The principle stays constant: compliance intelligence must be evaluated at the point of execution, deterministically, with full auditability, before a transaction reaches the network.

Learn more about Global Ledger: globalledger.io
Start building on Dfns today: app.dfns.io