Compliance

Covalent screens a transfer with the enabled integrations your compliance rules read, and applies those rules to the results. The API exposes the outcome on the transfer, and lets you manage the rules, integrations, cases and reports behind it.

Screening Sources

Integration	Screens
Elliptic	Wallet exposure, through Elliptic's synchronous wallet screening
TRM Labs	Address sanctions exposure, through the TRM Sanctions API
ComplyAdvantage	Names, for sanctions, PEPs and adverse media, through its Search API
Crystal Intelligence	Wallet risk scores, through Crystal Risk Check

An integration screens a transfer only while it is enabled, has credentials saved for the transfer's environment, and an active rule for that stage reads its result. See Integrations and Providers and Integrations.

Rules

Compliance rules decide what a screening result means for the transfer: flag records a match and lets the transfer continue, require_review holds it for an officer, and block holds it with a rejected verdict. Rules can run before the provider exchange (precheck), after it (postcheck), or both. Manage them with /api/v2/rules or in the dashboard; see Rules and Thresholds.

Transfer Relationship

Compliance checks are attached to transfers. A transfer's detail includes:

• The compliance verdict (compliance.status)
• How many checks it has (compliance.total)
• A page of its checks: each with its integration's name and display name, the check's type and status, the vendor's raw response (masked for a role without pii:view), and its duration in milliseconds

GET /api/v2/transfers/:id?checksLimit=50&checksOffset=0

Held Transfers

A transfer moves to held when a rule or a review stops its automatic progression. A transfer held for review has state: held with compliance pending; one blocked has compliance rejected. From held:

• PATCH /api/v2/transfers/:id with { "action": "retry", "reason": "..." } queues it again.
• A transfer held for review, incoming or outgoing before its provider exchange began, can be rejected with the reject action; an incoming one can be accepted with accept.
• Resolving the case linked to it resumes it (approved) or rejects it (rejected).

Through the API

Task	Endpoints
Read screening results	GET /api/v2/transfers, GET /api/v2/transfers/:id
Manage compliance rules	/api/v2/rules
Manage regulatory thresholds	/api/v2/thresholds (live key for changes)
Save integration credentials, enable and test	/api/v2/integrations
Work cases	/api/v2/cases
Read and download reports	/api/v2/reports, /api/v2/report-types

Promoting test rules to live, and drafting and filing reports, are dashboard actions.

Reference Pages

Page	Covers
Transfer Lifecycle	Transfer states, valid transitions, party statuses, compliance verdicts, and rejection reasons.
Cases	Case lifecycle, case types, priorities, categories, and report statuses.