Who decides a held wire, and how quickly? Without a named owner, exceptions sit in a shared mailbox.
Banking and payments
Let your payments agent release more wires on its own
Routine wires go out without waiting in a queue. A wire that trips a bank rule stops, or goes to compliance with the facts attached. When someone asks why, the record answers.
Connecting the agent? See the developer guide for Banking & Financial Services
What keeps a payments agent in pilot
The agent is often ready before the bank is. Approval tends to stall on three questions from risk, model risk, and internal audit.
Can the risk team change a threshold without a code release, and see its effect before it applies?
What does internal audit get when it samples a quarter of releases?
One wire rule, four people
How a new release rule moves from idea to evidence without an engineering ticket.
Risk officer
Writes the rule: wires of $250,000 or more to a higher-risk destination need compliance review, even when screening is clear.
Payments operations owner
Watches the share of wires released without a person, and how long held wires wait, from the business owner portal.
Compliance analyst
Gets the held $310,000 wire in the VeriProof Inbox with the amount, destination, and rule, and releases or rejects it.
Internal audit
Opens an engagement scoped to the payments agent and the quarter, and pulls the evidence pack.
Getting model risk to sign off
SR 26-2 wasn’t written for agents
SR 26-2 replaced SR 11-7 and covers “non-generative, non-agentic AI models.” Agents fall to your own governance, and model risk needs evidence before one goes live.
Behavior validators can sample
Each recorded decision keeps the facts, the rule version, and the outcome, so validators test what the agent did, not a design document.
Canadian banks and OSFI E-23
OSFI’s E-23 guideline on model risk takes effect May 1, 2027. The same decision history supports that review.
Built-in handoff
A tighter wire rule gets a second pair of eyes
Compliance officer
The new threshold can run in Shadow first, so payments operations sees which wires it would have held. A governance engineer’s change to the production agent waits for a compliance officer to approve it.
See the six role portals and how work moves between themWhere banks start
Most banks connect one agent first, where volume is high and the rules are already written down.
Wire and payment release
The agent proposes a release. Bank rules decide whether it goes, waits for compliance, or stops, before any money moves.
Credit decisions
An agent recommends approve or decline. Each decline keeps its reason and rule version for an adverse-action question.
Alert triage
The agent clears low-risk screening alerts and passes the rest to an investigator with the facts it used.
Test your release rules on one agent
Developer is free for 60 days, with unlimited users and agents, 1,000 recorded decisions per month, and 14-day retention. Use test or sample data to evaluate your release rules.