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:write and assets:read scopes

1. Install and authenticate

import { SignumClient } from "@signum-tech/sdk";
const signum = new SignumClient({
  apiKey: process.env.SIGNUM_API_KEY,
});

2. Set the compliance policy

Attach a compliance policy to your asset. This example configures a Regulation D policy with accredited investor requirements:

const policy = await signum.orgs.assets.compliancePolicy.set(
  orgId,
  assetId,
  {
    regulation_type: "reg_d",
    min_kyc_level: 2,
    accredited_investor_required: true,
    blocked_countries: ["IRN", "PRK", "CUB"],
    max_holders: 2000,
    lockup_period_days: 365,
    transfer_restricted: false,
    chain_eid: 30101,
  }
);
console.log(policy); // The saved policy

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.

Policy fields

3. Read the policy back

Retrieve the current compliance policy for an asset:

const current = await signum.orgs.assets.compliancePolicy.get(orgId, assetId);
console.log(current.regulationType);          // "reg_d"
console.log(current.requiresAccreditation);   // true
console.log(current.blockedCountries);        // ["IRN", "PRK", "CUB"]

4. Trigger a compliance check

Queue an async compliance check against a wallet to verify it meets the policy requirements:

const check = await signum.compliance.check({
  wallet: "0xabc...def",
  chainEid: 30101,
  assetId: assetId,
});
console.log(check.accepted);  // true
console.log(check.checkId);   // "chk_abc123"
console.log(check.message);   // Guidance on result delivery

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