Financial Policies

Managed Mode reference. You do not configure these policies. They are enforced automatically for applicable ActionKinds.

Trigger example (derived from the managed catalog)

Financial policies typically trigger when the request includes amount/velocity context and crosses a managed threshold. They may emit WARN (approval required) or BLOCK.

Example ActionKind where financial policies apply: money.refund

Common required context fields: amount_usd, authz_decision, case_id, destination_id, destination_verified, invoice_id, recent_actions_count, time_window_minutes, transaction_id

Example threshold shapes used by these policies: {"maxAmountUsd":200} | {"maxActionsPerHour":25,"maxActionsPerMinute":5}

Example decision

WARN responses include an approval_token. BLOCK responses do not.

json

{
  "status": "WARN",
  "decision_id": "dec_...",
  "approval_token": "appr_...",
  "reasons": [
    "Warn and require approval for high-value refunds/credits."
  ]
}

json

{
  "status": "BLOCK",
  "decision_id": "dec_...",
  "reasons": [
    "Block refunds/credits/payouts without verified evidence and authorization."
  ]
}

Resolution

Apply the remediation specified by the policy that fired, then re-validate.

Summary	Severity	Applies to	Required context	Approval	Remediation
Block refunds/credits/payouts without verified evidence and authorization.	BLOCK	money.refund, money.credit, money.payout, billing.change	invoice_id, transaction_id, case_id, authz_decision	—	Require support ticket/case, validated transaction reference, and server-side authz before executing.
Warn and require approval for high-value refunds/credits.	WARN	money.refund, money.credit	amount_usd, invoice_id, case_id	WARN requires approval	Approve only with case evidence. Consider dual approval for unusually large amounts.
Block payouts to unverified or new destinations.	BLOCK	money.payout, money.move	destination_id, destination_verified, amount_usd	—	Verify destination ownership and risk checks. Use allowlisted payout destinations per account.
Warn when financial actions exceed safe velocity thresholds.	WARN	money.refund, money.credit, money.payout, money.move	recent_actions_count, time_window_minutes	WARN requires approval	Investigate automation loop or abuse. Rate-limit and require manual review temporarily.

Legal & Responsibility Notice

Summary

Informational only

Provided for general guidance. Not legal, compliance, security, or professional advice.

You control implementation

You are responsible for policies, prompts, integrations, workflows, and regulatory requirements.

Liability limitation

To the maximum extent permitted by law, the company disclaims liability for losses arising from use of this documentation or implementations based on it.