Trust posture for Sharia-aware controlled wallets used by AI agents.
Vicera is designed for bounded wallet authority, institution-approved Sharia policies, separated approval paths, and audit receipt evidence before financial actions advance.
Posture statement
The trust boundary is the controlled-wallet authorization decision.
- Designed for finance teams that need clear boundaries before agents touch AP, treasury, or payment workflows.
- Enforces institution-approved Sharia and compliance policies; Vicera does not decide halal or replace scholars, Sharia boards, or compliance teams.
- Supports existing approval paths instead of replacing ERP, AP, treasury, or payment systems.
- Records audit receipts in operational language so reviewers can understand the authority check before money moves without decoding a model trace.
A practical trust posture for controlled-wallet agent finance.
Designed for
Explicit bounded wallet authority
Wallet mandates describe which agent may request which finance action, with scope for counterparties, resources, currency, wallet limits, and expiry.
Supports
Approval separation
Threshold exceptions can route to a distinct approver before a downstream finance system receives execution authority.
Records
Decision evidence and audit receipts
Each authorization result can carry agent identity, wallet mandate id, request context, institution-approved Sharia policy reason, approval evidence, and audit receipt timestamp.
Supports
Revocation and expiry
Inactive, expired, or revoked authority can stop an otherwise valid request at the mandate boundary.
Review record
What Vicera records for later inspection.
The record is intentionally operational: who requested what, which mandate applied, what the decision was, and why the boundary responded that way.
- Authority state
- Designed for active, expired, revoked, and inactive mandate states.
- Approval posture
- Supports maker-checker and Sharia/compliance review for requests that exceed a configured threshold.
- Policy reason
- Records the institution-approved Sharia and compliance reason attached to approved, approval-required, or denied decisions.
- Review context
- Records request metadata so finance, risk, and platform owners can inspect what happened later.