Agent-initiated payment simulator

A procurement agent authorizes a sample stablecoin payment. VeriProof checks the wallet and transfer against treasury rules before signature. Select a payment to review the outcome.

How the simulation works

The website proposes approval. VeriProof checks the rules.

  1. The website simulates the agent

    Every prepared scenario starts with the website acting as an AI agent and proposing approval.

  2. VeriProof enforces the business rules

    VeriProof checks the proposed approval against the rules prepared for this demo.

  3. The website applies the result

    VeriProof returns one of five outcomes: Allow, Warn, Transform, Escalate, or Deny. The website applies that outcome to the simulated action.

In a real integration, your application applies VeriProof's result before the proposed action proceeds.

  1. Choose what the agent approvesEvery prepared scenario starts with simulated agent approval
  2. See VeriProof's decisionPass, escalate, or stop based on the business rules

Choose a scenario

The agent payment

Each sample payment ends differently. Pick one, or change the payment facts below.

Counterparty wallet
Wallet on restricted list
Payment amount
$48,000
Stablecoin asset
USD stablecoin
Earlier agent spend today
$22,000
Per-payment cap
$50,000
Change scenario details

The payment agent proposes to sign this transfer.

The procurement agent approves the transfer, but VeriProof stops it before signature because the wallet appears in the restricted-wallet list.

Records created in this public demo can be seen by other visitors, so use the sample data rather than your own.

Configuration details

How this demo is set up

Review the application settings, rules, and evidence fields used in this simulator.

VeriProof setup

Industry
Agentic Payments & Stablecoins
Application
Payment Authorization Chat
Environment
Public demo workspace
Rule enforcement
On, rules can stop transfers before signature
Rule set
Agent spend, counterparty, and treasury guardrails

Related frameworks

NIST AI RMFEU AI ActPCI DSSOFAC / BSA

Industry context: GENIUS Act · EU MiCA · FinCEN travel rule

The payment agent's own checks

The sample procurement agent checks spending limits first. VeriProof then evaluates the proposed transfer against treasury rules.

  • Propose a transfer when the payment and daily totals fit within the agent’s caps.
  • Send a cap exception with human preapproval to the treasurer.
  • Refuse a cap exception without preapproval.

The company rules VeriProof enforces

Before signature, VeriProof checks rules the treasury team wrote.

  • Stop a transfer to a wallet that appears in the restricted-wallet list.
  • Send a first payment of $5,000 or more to a new counterparty for treasury review.
  • Send cross-border transfers of $10,000 or more for treasury review.
  • Warn when earlier spending has reached 80% of the daily cap. This check excludes the proposed payment.
Review the details saved with each run

The decision record connects the sample payment with its rule check. Each outcome shows whether the record was saved.

agent_name / payment_id

The sample agent and payment references.

counterparty_wallet / wallet_flagged / counterparty_new

The wallet facts used by counterparty rules.

amount_usd / asset

The requested transfer amount and stablecoin asset.

agent_daily_spend_usd / per_transaction_cap_usd / daily_cap_usd

The spend totals and governed caps.

human_preapproval_present / cross_border

The approval and routing facts.

local_decision / governance_action / final_decision

The agent decision, rule check, and actual outcome as separate facts.