Skip to main content

Policies

Policies define the rules governing how cards can be used. They control spending limits, merchant restrictions, approval workflows, and more.

Policy Cascade

Policies are applied in a cascading hierarchy. Settings at lower levels override those at higher levels:
Default policies for all agents and cards owned by the customer.

Cascade Example

Intent Controls

requireIntent

When true, agents must declare an intent before accessing card details. Transactions without a matching intent are flagged.
Use case: Audit trail and compliance. Ensures every transaction has a documented purpose.

requireAttestation

When true, agents must attest to their intent before each card access. Creates an access event record.

requireApproval

When true, intents require human approval before becoming active.
Flow with approval required:

Spending Limits

Control maximum spend amounts at different time intervals.

Limit Enforcement

Limits are checked at authorization time. If a transaction would exceed any limit, it is declined.

MCC Restrictions

Merchant Category Codes (MCCs) classify the type of business. Use MCC restrictions to control where cards can be used.

allowedMccs

Whitelist specific merchant categories. Only transactions at merchants with these MCCs are allowed.

blockedMccs

Blacklist specific merchant categories. Transactions at these MCCs are declined.
If both allowedMccs and blockedMccs are specified, allowedMccs takes precedence. A transaction is allowed only if the MCC is in the allowed list and not in the blocked list.

Merchant Controls

allowedMerchants

Whitelist specific merchants by name. Only transactions at these merchants are allowed.
Merchant matching uses fuzzy matching to handle variations in merchant names.

lockToFirstMerchant

After the first transaction, lock the card to that specific merchant. All subsequent transactions must be at the same merchant.
Use case: Subscription payments. Issue a card for a specific service and prevent misuse at other merchants.

Cooldown Periods

Prevent rapid consecutive transactions by enforcing a wait period between card uses.
Use case: Prevent runaway spending by AI agents. If an agent makes a purchase, it must wait before making another.

Card Expiration

Control how long cards remain active.

Example Configurations

Minimal restrictions for a trusted automation.

Setting Policies

On Customer Creation

On Agent Creation

On Card Creation

Updating Policies

Policy Reference

Next Steps

Agents

Configure agent policies

Cards

Apply card-level controls

Intents

Understand intent workflows

Transactions

View transaction history