Feature flags and rules engine

​

Flag types

​

How flags resolve

1. Company override — manual per-company on/off override takes highest priority.
2. Plan-linked auto-rules — rules auto-generated from the plan the company is subscribed to.
3. Manual rules with conditions — custom targeting rules you define with operator-based conditions.
4. Default — the flag’s default value (on or off) when no rule matches.

​

Rules and conditions

• Rule type — BOOLEAN (always match), EVENT (match on event data), TRAIT (match on company traits), or ZKTLS (match on verified claims).
• Conditions — one or more conditions with attribute, operator, and value fields.
• Priority — rules are evaluated in priority order; the first matching rule wins.

​

Creating flags

1. A unique key (e.g., analytics_export, priority_support)
2. A name and description
3. A flag type (boolean, event, trait, or zkTLS)
4. A default value — what to return when no rule matches

​

SDK access

// React — UI gating
import { useFlag, useFlags } from "@arcenpay/react";

const enabled = useFlag("analytics_export");
const flags = useFlags(["analytics_export", "export_pdf"]);

// Node.js — authoritative server-side checks
const enabled = await client.checkFlag("analytics_export", { id: "company_123" });

​

FeatureFlagGuard component

import { FeatureFlagGuard } from "@arcenpay/react";

<FeatureFlagGuard featureKey="export_pdf" walletAddress={walletAddress}>
  <ExportButton />
</FeatureFlagGuard>

​

Bulk flag checks

const result = await client.checkEntitlement("analytics_export", { id: "company_123" });
// result.enabled — boolean
// result.reason — why it resolved this way (plan, override, default)

​

Next steps

• Entitlements — understand the difference between flags and full entitlements (with usage state)
• Feature gating guide — practical guide to gating features in your app
• Companies — understand how companies are identified for flag resolution