Wire release simulator

A payment app proposes an outbound wire. VeriProof checks the bank’s rules before release. Try a fictional payment to see what proceeds, stops, or needs review.

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 outgoing payment

Each wire is set up to end differently. Pick one, or change the payment facts below.

Sender profile
Avery Chen · business treasury
Beneficiary
Kaspar Novik Holdings
Beneficiary country
Türkiye, higher-risk destination
Wire amount
$480,000
Payment purpose
Real estate
Change scenario details

This wire is $480,000. Including earlier wires today, the sender reaches $700,000.

The app approves release. VeriProof blocks the wire because the screening result still shows an unresolved potential match.

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
Banking & Financial Services
Application
AML Transaction Monitor
Environment
Public demo workspace
Rule enforcement
On, rules can stop wire releases
Rule set
Wire release and sanctions guardrails

Related frameworks

Industry context: FinCEN SAR obligations · FATF Recommendation 16 · Fedwire / Regulation J

The app's own checks

The payment app makes the initial release decision. VeriProof then checks the proposed action against company rules.

  • Stop a wire when the screening feed confirms a sanctions match.
  • Send a wire above $1 million to payment operations for review.
  • Propose release for wires of $1 million or less, including unresolved potential matches.

The company rules VeriProof enforces

The bank owns these release rules. In this demo, a policy stop prevents release, while a review decision holds the wire.

  • Block a proposed wire release when a potential watchlist match remains unresolved.
  • Stop a wire to a higher-risk destination when its payment purpose is missing.
  • Require compliance review for wires of $250,000 or more to a higher-risk destination, even when screening is clear.
  • Require review before release when customer information is more than 12 months old.
  • Flag wires below $10,000 when the combined daily volume reaches $900,000. This warning does not itself stop release.
Review the details saved with each run

A saved record brings the payment facts and both decisions together. Reviewers can trace the outcome to the rule check.

originator_name / originator_id

The sender identity saved with the wire for follow-up and review.

beneficiary_name / beneficiary_country

The payment destination and country used in the screening decision.

amount_usd / daily_wire_volume_usd

The wire amount and running daily total used by the rules.

purpose_code / sanctions_disposition

The payment purpose and screening result that explain the release or stop.

high_risk_corridor / kyc_refresh_age_months

The derived corridor flag and customer-information age used by the rules.

local_decision / governance_action / final_decision

The app decision, rule check, and final outcome saved as separate facts.