Demo mode active: Cleanverse calls use live API when credentials exist; audit + Monad receipt are simulated.
Demo flow
Step 3 of 5
Step 3
Compliance Rule Engine
Define and enforce payment logic for autonomous agents, then validate A-Token and validator eligibility through server-side Cleanverse routes.
A-Pass Verification
Real Cleanverse API CallA-Token Rules
Real Cleanverse API CallValidator
Real Cleanverse API CallMonad Transaction
Demo MockActive Policies
14 enforcedDaily Spend Limit
Hard cap on aggregate 24h outgoing transactions per agent cluster.
Restricted Recipient List
Prevents transfers to known OFAC sanctioned wallets and entities.
Mandatory 2FA for >$1k
Requires human-in-the-loop cryptographic signature for high-value operations.
Weekend Velocity Check
Limits transaction frequency outside standard banking hours.
Rule Editor: Daily Spend Limit
Configure logical conditions and enforcement actions.
Visible Compliance Checklist
Payment approval stays blocked until every required control passes.
Query A-Token rules
Read compliance rules for 0xA700000000000000000000000000000000000123 on Monad.
Check paused status
Confirm the A-Token has not been paused before authorizing payment.
Verify validator compliance
Verify wallet 0x8E6B0C8E05C7A5fA7aF0a3Bcb7844B9747622E91 against payment contract 0xC000000000000000000000000000000000000321.
Failure Simulation
Test cases prove the system blocks payments that fail identity, risk, or limit checks.
Payment Authorized
AgentPay Guardian approved this transaction after identity, rule, and risk checks.