Integrations
Designed to sit between blockchain infrastructure and banking execution.
Integration readiness is labeled honestly by category: what runs today, what has an adapter ready to be configured and what depends on an institution's own provider relationships.
How to read this page
Four readiness labels, defined before the list.
Most integration pages show vendor logos. This one shows the state of each interface, because that is the question a deployment programme actually has to answer.
- Available architectureImplemented and running in the platform today.
- Adapter-readyThe interface exists; the specific provider is configured per deployment.
- Institution-specific integrationShaped around the institution’s own systems during the deployment programme.
- Requires provider onboardingDepends on a commercial relationship the institution holds with the provider.
Categories
Grouped by the role each integration plays.
Blockchain data
How the platform reads the ledgers.
- Bitcoin Esplora access, UTXO history and address monitoringConnected
- Institution-controlled Bitcoin Core PSBT and broadcast adapterAdapter-ready
- Account-based network connectivity, per-network configurationAvailable architecture
- Real-time and backfill indexingAvailable architecture
Identity and obligations
Who the customer is, and what the transfer triggers.
- KYC / KYB provider integrationRequires provider onboarding
- Travel Rule messaging network integrationRequires provider onboarding
Execution providers
The systems that actually move value.
- Custody provider execution adapter, including external-signature Bitcoin PSBT workflowAdapter-ready
- Liquidity / conversion provider adapterAdapter-ready
- Core banking instruction and reconciliation adapterAdapter-ready
Records and secrets
Where the output and the credentials live.
- Case management, evidence export and reportingAvailable architecture
- Secret reference provider abstractionAvailable architecture
Provider names are not shown here as active integrations unless contractually confirmed for a given deployment.
Map ChainGuard onto your existing provider stack.
Map ChainGuard to your institution’s transaction, policy and evidence workflows.