
Policy hierarchy
Stack user, agent, wallet, business, and program rules.
Policies compose across every level so each agent operates inside the right financial boundary.
Policy Engine
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.

Product thesis
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
Set budgets, merchants, time windows, and task controls before money moves.
Decision
The policy layer evaluates every request without slowing down the agent experience.
Visibility
Users see the exact rule that approved or rejected the transaction.
Hierarchy
User, agent, wallet, business, and program policies all work together.

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

Decision logs
Every transaction is recorded with the rule result, giving users and operators clear visibility.
Guardrails
Set maximum amounts per transaction, per day, per week, or per month. The agent cannot exceed what you authorize.
Allow or block specific merchant categories. Let the agent buy groceries but not gamble. Allow SaaS tools but not luxury goods.
Limit how fast an agent can spend. Prevent rapid transaction bursts and suspicious spending patterns.
Restrict when the agent can transact. Business hours only, weekdays only, or custom time windows.
Allocate budgets per task or goal. A grocery run gets $100. A software purchase gets $50. Each task has its own ceiling.
Freeze or shut off the wallet instantly. The agent loses access to money in one click, no delay, no exceptions.
Policy hierarchy
Individual users set personal guardrails for their own agents. Maximum daily spend, allowed merchants, task budgets.
Each agent can have its own policy set. A shopping agent gets different rules than a subscription management agent.
Policies can be attached directly to a wallet. Useful when one user has multiple wallets for different purposes.
For B2B customers, company policies set the outer boundary. Individual agents operate within the company's macro rules.
Card program partners can set program limits and controls that apply across every wallet in the program.
How it works
01
The agent attempts to spend, transfer, or pay using the wallet.
02
Credian checks the transaction against every active guardrail: limits, categories, velocity, time, and balance.
03
If all rules pass, the transaction proceeds. If any rule fails, Credian blocks the transaction instantly.
04
Every decision is logged with the rule that triggered it. Users see exactly why a transaction was approved or blocked.
Example: Transaction blocked. Your agent tried to purchase from an electronics retailer, but your policy only allows groceries and software.
Example: Your agent spent $42.19 at Instacart because it was completing your grocery task and the transaction was within your weekly grocery budget.
Join the private beta. Build agent payment flows where every transaction is checked before money moves.