​

Action-Scoped Enforcement

​

What is Action-Scoped Enforcement?

• Verification happens for the action (the scope) — Not for the user, session, or platform broadly
• Enforcement is limited — Only affects the specific action being verified
• No cross-action tracking — Each action is independent
• No persistent monitoring — No surveillance beyond the immediate action

​

How It Works

​

Traditional Approaches

• Session-based verification — Verify once, trust for entire session
• User-based verification — Verify user identity, apply broadly
• Platform-wide monitoring — Track behavior across all actions
• Persistent tracking — Store verification state for reuse

​

BotShield’s Approach

• Action-specific verification — Verify presence for this specific action
• Limited enforcement — Only this action requires verification
• No cross-action data — Each verification is independent
• No persistent state — Verification is consumed by the action

​

Example: Checkout Flow

# User wants to checkout -- create a verification request for the checkout scope
POST /operations/sdk/create-verification-link
{
  "scope": "checkout.complete",
  "metadata": { "order_id": "checkout-12345" }
}
# → User verifies → result delivered to your Svix webhook endpoint → checkout proceeds

# Later, same user wants to post a comment
# This requires a NEW verification -- the previous one does not carry over
POST /operations/sdk/create-verification-link
{
  "scope": "comment.create",
  "metadata": { "comment_id": "comment-67890" }
}
# → Fresh verification required

​

Benefits

​

Selective Enforcement

• Checkout — Always verify
• Comment posting — Verify for new users only
• Account recovery — Always verify
• Profile update — Verify for sensitive changes only

​

Standard vs Elevated Scopes

• Standard — passes when the user has either an active MultiPass credential or a fresh Face ID event. Best for routine actions (commenting, signing up).
• Elevated — always demands a live Face ID for this action, even when the user’s MultiPass is active. Best for high-impact actions (payments, withdrawals, account changes).

​

Comparison

​

Privacy Implications

• No surveillance — No monitoring beyond the action
• No tracking — No cross-action data collection
• No profiling — No user behavior analysis
• No persistence — No stored verification state

​

Related Concepts

• Human Presence — What BotShield verifies and the three Census result states
• Webhooks — How anonymous results reach your server
• Device Security — Hardware-backed security requirements
• SDK Overview — Technical API architecture