Policy Engine

Set the rules. Credian enforces them.

The Policy Engine is the core of Credian. It evaluates every agent transaction in real time against the guardrails you set, and blocks anything that violates the rules before money moves.

Explore docs
3D illustration of a policy shield checking transaction paths

Product thesis

Approval should be embedded in the rules, not asked for every time.

Traditional payments require a human to approve or decline. That does not work when agents need to act fast and autonomously. Credian flips the model: you define the rules up front, and the agent operates freely inside them.

The Policy Engine sits between the agent and money. It checks every transaction against your guardrails in milliseconds. No human in the loop. No delay. If the transaction is within rules, it goes through. If not, it is stopped.

Rules

Limits and categories

Set budgets, merchants, time windows, and task controls before money moves.

Decision

Milliseconds to approve

The policy layer evaluates every request without slowing down the agent experience.

Visibility

Blocked with reason

Users see the exact rule that approved or rejected the transaction.

Hierarchy

Stacked policy levels

User, agent, wallet, business, and program policies all work together.

3D illustration of stacked policy layers and guardrail controls for agent finance

Policy hierarchy

Stack user, agent, wallet, business, and program rules.

Policies compose across every level so each agent operates inside the right financial boundary.

3D illustration of approved and blocked transaction decision logs with a policy shield

Decision logs

Explain every approval and every block.

Every transaction is recorded with the rule result, giving users and operators clear visibility.

Guardrails

Every rule you need to keep agents in bounds

Spend Limits

Set maximum amounts per transaction, per day, per week, or per month. The agent cannot exceed what you authorize.

Merchant Category Controls

Allow or block specific merchant categories. Let the agent buy groceries but not gamble. Allow SaaS tools but not luxury goods.

Velocity Controls

Limit how fast an agent can spend. Prevent rapid transaction bursts and suspicious spending patterns.

Time Window Rules

Restrict when the agent can transact. Business hours only, weekdays only, or custom time windows.

Task Budgets

Allocate budgets per task or goal. A grocery run gets $100. A software purchase gets $50. Each task has its own ceiling.

Wallet Pause & Kill Switch

Freeze or shut off the wallet instantly. The agent loses access to money in one click, no delay, no exceptions.

Policy hierarchy

Policies at every level of the stack

User Policies

Individual users set personal guardrails for their own agents. Maximum daily spend, allowed merchants, task budgets.

Agent Policies

Each agent can have its own policy set. A shopping agent gets different rules than a subscription management agent.

Wallet Policies

Policies can be attached directly to a wallet. Useful when one user has multiple wallets for different purposes.

Business Policies

For B2B customers, company policies set the outer boundary. Individual agents operate within the company's macro rules.

Program Policies

Card program partners can set program limits and controls that apply across every wallet in the program.

How it works

Transaction, rules check, decision in milliseconds

01

Agent initiates transaction

The agent attempts to spend, transfer, or pay using the wallet.

02

Policy engine evaluates

Credian checks the transaction against every active guardrail: limits, categories, velocity, time, and balance.

03

Decision in milliseconds

If all rules pass, the transaction proceeds. If any rule fails, Credian blocks the transaction instantly.

04

Outcome recorded

Every decision is logged with the rule that triggered it. Users see exactly why a transaction was approved or blocked.

Blocked transaction visibility

Example: Transaction blocked. Your agent tried to purchase from an electronics retailer, but your policy only allows groceries and software.

Agent activity explanations

Example: Your agent spent $42.19 at Instacart because it was completing your grocery task and the transaction was within your weekly grocery budget.

Control how your agents spend. Down to the dollar.

Join the private beta. Build agent payment flows where every transaction is checked before money moves.