ArmorPay Policy Studio
Customize financial compliance policies with the 9-section editor - member roles, tool config, amount thresholds, velocity limits, and more.
Overview
The ArmorPay Policy Studio at /dashboard/armorpay/studio provides a specialized editor for financial compliance policies. It extends the standard Policy Studio with financial-specific sections.
Editor Sections
The left panel lists 9 sections. Click any to switch:
1. Metadata
| Field | Description |
|---|---|
| Policy Name | Name for this financial policy |
| Description | What this policy controls |
| Target Agent | The financial agent this policy applies to |
2. Member Roles
Assign members to pre-defined financial roles:
| Role | Description |
|---|---|
| Finance | General finance team access |
| AP | Accounts payable operations |
| Payroll | Payroll and HR operations |
| Accountant | Accounting and reporting |
| Finance Manager | Management-level financial oversight |
| CFO | Executive financial access |
3. Tool Configuration
Mark tools with financial metadata:
| Setting | Description |
|---|---|
| Financial Flag | Whether this tool handles financial transactions |
| Amount Fields | Which parameters represent monetary amounts |
| Currency | Default currency for amount fields |
4. Amount Threshold
Set per-transaction limits:
| Setting | Description |
|---|---|
| Per-Transaction Limit | Maximum amount for a single transaction |
| Hold Threshold | Amount above which transactions are held for review |
| Block Threshold | Amount above which transactions are blocked |
| Approval Workflow | Who must approve transactions above the hold threshold |
5. Velocity Limit
Rate-based controls:
| Setting | Description |
|---|---|
| Frequency Cap | Maximum number of transactions per time window |
| Cumulative Cap | Maximum total amount per time window |
| Time Window | The period for counting (e.g., per hour, per day) |
6. Recipient Validation
| Setting | Description |
|---|---|
| Vendor Approval | Whether recipients must be pre-approved vendors |
| Blocked Recipients | List of blocked recipient patterns |
7. Transaction Types
| Setting | Description |
|---|---|
| Allowed Types | Transaction types the agent can execute (e.g., payment, invoice, refund) |
| Blocked Types | Transaction types that are always blocked |
| Read-Only Types | Transaction types the agent can view but not create |
8. Enforcement
| Setting | Description |
|---|---|
| Default Action | What happens when no specific rule matches: block, hold, allow_log, alert, quarantine |
| Rate Limit | Global requests-per-hour limit |
9. YAML Editor
The right panel shows a live YAML preview of the compiled FinancialPolicy document. Changes in the form sections update the YAML in real time, and vice versa.
- Copy - Copy YAML to clipboard
- Download - Download as
.yamlfile
Draft Persistence
Your work is auto-saved to browser localStorage. Come back later to continue editing. Use Clear Draft to start fresh.
Saving
Click Deploy Policy to save and activate the financial policy.