Define & Attach a Compliance Policy
Define & Attach a Compliance Policy
This guide walks you through defining a compliance policy for an asset — setting regulation parameters, reading the policy back, and triggering a compliance check.
Prerequisites
- An organization set up (Onboard an Organization)
- An asset created (see step 2 of Deploy a Gated Asset, or create one via the dashboard)
- An API key with
assets:writeandassets:readscopes
A compliance policy can be attached before or after asset deployment. It is common to create the asset, attach the policy, and then deploy.
1. Install and authenticate
2. Set the compliance policy
Attach a compliance policy to your asset. This example configures a Regulation D policy with accredited investor requirements:
When chain_eid is provided, the API returns 202 Accepted — the policy is saved and
queued for on-chain registration. Without chain_eid, it returns 200 with the saved
policy. Either way, the response includes policyId and assetId for tracking.
On-chain policy registration is asynchronous. Listen for the signum.compliance.rule_synced
event to confirm the policy is live on the smart contract.
Policy fields
3. Read the policy back
Retrieve the current compliance policy for an asset:
4. Trigger a compliance check
Queue an async compliance check against a wallet to verify it meets the policy requirements:
The API returns 202 Accepted. The check runs asynchronously — use webhooks or poll for
the result.
5. Listen for compliance events
Four compliance event channels notify you of policy and check lifecycle changes:
See Subscribe to Webhooks for how to receive these events, or browse the full payload schemas in the API Reference.
Reference
- API Reference — operations and webhook payload schemas
- Compliance — API — REST operations for compliance
- Policies & Enforcement — deep-dive into the compliance model
Next steps
- Deploy a Gated Asset — create, deploy, and distribute a token
- Async Operations — polling and webhook correlation patterns