Integrations
Covalent screens transfers with four integrations, each calling its vendor's HTTP API with the credentials your company saved.
Integrations
Section titled “Integrations”| Integration | Name | Type | Screens |
|---|---|---|---|
| Elliptic | elliptic |
Blockchain analytics | Wallet exposure, through Elliptic's synchronous wallet screening |
| TRM Labs | trmlabs |
Sanctions | Address sanctions exposure, through the TRM Sanctions API |
| ComplyAdvantage | complyadvantage |
Sanctions | Names, for sanctions, PEPs and adverse media, through its Search API |
| Crystal Intelligence | crystal |
Blockchain analytics | Wallet risk scores, through Crystal Risk Check |
Integration Use
Section titled “Integration Use”An enabled integration screens a transfer only when an active compliance rule for that stage reads its result: before evaluating the rules, Covalent calls the integrations they read, and records each call as a compliance check. A transfer's detail exposes each check, with the vendor's raw response for a role with pii:view. Your compliance rules decide what the results mean for the transfer.
Credentials
Section titled “Credentials”Save credentials for each environment with PUT /api/v2/integrations/:name (the integrations:write scope), or in the dashboard under Integrations. Credential values are never returned, and API clients never send vendor credentials with transfers.
- Test keys save test credentials, and live keys live credentials.
- Enabling or disabling an integration applies to both environments, and takes a live key.
POST /api/v2/integrations/:name/testchecks the connection with the environment's credentials.- An enabled integration without credentials for a transfer's environment does not screen it: the check fails. There is no simulated fallback.