DEFS Learn · AI agents and online banking

Agentic commerce fraud readiness checklist for credit unions

Last updated October 26, 2026 · DEFS Agent Defense (defs.ai)

Short answer

A credit union is ready for agentic commerce when it can answer five questions about any agent request: which agent is this, which member sent it, what was it allowed to do, who approved anything new, and how do we stop it right now. The checklist below turns those questions into concrete items for fraud, digital banking, compliance and member service teams.

Use this as a working list. Each item is something your team can confirm or assign an owner to this quarter.

1. Visibility

We can tell agent sessions apart from member sessions in online banking.
We know which aggregators and apps hold member connections, and whether each is read-only or can move money.
We can report agent activity by agent, by operation and by outcome (allowed, held, stopped).

2. Agent identity

Money movement by agents requires an agent credential, not a shared password.
We can verify the major credentials: Cloudflare Web Bot Auth, Visa Trusted Agent Protocol, Mastercard Agent Pay and Google AP2. See how to verify an AI agent.
Expired, replayed and tampered requests are rejected.

3. Authority and limits

Each agent has an explicit list of allowed operations; everything else is denied.
Per-payment, daily and rolling limits are counted across all of a member's agents.
External transfers, ACH and moving deposits out have their own, stricter rules. See setting agent limits.

4. Member control

New payees and new destinations are approved on the member's enrolled device, never inside the agent's session.
Members can see their connected agents and revoke any of them in one step.
Members can set tighter limits than the institution's defaults.

5. Fraud operations

We have a kill switch that stops all agent money movement at once, and we know who can use it.
We can block or limit a single agent without affecting others.
We receive alerts on suspected rogue-agent campaigns and new agent types, and we can share and receive blocklist information with other institutions.
Someone reviews held requests, including nights and weekends, and unclear cases are held rather than allowed.

6. Disputes and evidence

For every agent transaction we can show what the member allowed, what limits applied, what the agent did and when the member was notified. Quavo calls this the "chain of intent" evidence that agent disputes will need (Quavo).
The audit trail is tamper-evident and exportable for examiners and auditors.
Our member agreement and dispute procedures address agent-initiated transactions (reviewed with counsel).

7. Governance and vendors

We have a written AI agent access policy approved by management.
We know what our digital banking provider, card processor and core provider offer for agents, and where the gaps are. FIS, for example, offers card issuers an agentic commerce capability built with Visa and Mastercard (FIS).
Any agent-security vendor has delivered a full due-diligence package and starts on test data in a sandbox.

Comparing vendors? See how to evaluate AI agent security for credit unions.

How DEFS handles it

DEFS covers the identity, authority, member-control, operations and evidence items above for non-card money movement, and sends your team real-time alerts and a monthly outcome report you can take to the board.

One checkpoint before money moves. Every agent request for bill pay, transfers, ACH, disputes or moving deposits out passes through DEFS before your core or payments engine sees it.
Accepts the credentials agents already carry. DEFS checks Cloudflare Web Bot Auth, Visa Trusted Agent Protocol and Google AP2 credentials today, and is adding Mastercard Agent Pay, Prove and World ID. Members and agent makers don't adopt anything new.
Your scopes and the member's, enforced together. For example: bill pay up to $500 to existing payees, no external transfers. The strictest rule wins.
Members stay in charge. New payees and new destinations go to the member's own device for approval. A "connected agents" page lets members see every agent and revoke it with one tap.
Your fraud team keeps the controls. A live decision log, approve, limit or block for any agent, a kill switch that stops all agent money movement at once, and a tamper-evident audit trail. DEFS reviewers run it day to day; your team can step in any time.
Shared protection. A rogue agent blocked at one participating institution is flagged for yours, on your terms.

The demo results

We tested DEFS in a model credit union built from public information, using test data. OpenAI and Claude agents sent it 3,259 requests: everyday member tasks mixed with deliberate attacks.

1,490 of 1,491attack attempts stopped by DEFS. The one remaining request moved $0 because the core system rejected it.
0 of 807legitimate requests wrongly blocked: zero false positives.
3,259requests from OpenAI and Claude agents, decided in a median of 7 ms.

"Stopped" means DEFS denied the request outright or held it until the member or a reviewer decided. No attack attempt moved any money.

Attack type in the test	Result
Requests sent after the kill switch was turned on	71 of 71 stopped
Agents flagged at another institution (shared blocklist)	101 of 101 stopped
Requests from agents a member had revoked	57 of 57 stopped
New-payee attempts	90 of 90 stopped or held for the member

See it for yourself in the live demo environment (test data only), or book a 30-minute walkthrough.

See DEFS stop a rogue AI agent before it moves money, live, in 30 minutes.

Book a demo

Frequently asked questions

Who should own agentic commerce fraud readiness at a credit union?

Usually the fraud or risk lead, working with digital banking, compliance and member service. Agent traffic crosses all four, so one named owner with a short cross-team checklist works better than splitting it up.

Where should a credit union start?

Start with visibility and member control: find out which agents are already active, make new payees a member decision on the member's own device, and make sure you can stop all agent money movement at once.

Is agentic commerce only about card purchases?

No. Card purchases by agents get a lot of attention, but members also ask agents to pay bills, move money between accounts, send ACH transfers and file disputes. Those non-card actions run through your online banking and need their own controls.

How does this checklist relate to existing fraud programs?

It extends them to a new channel. Most items reuse existing practices, such as limits, out-of-band approval and audit trails, and apply them to agents specifically.

Sources

Quavo: What credit unions must do about the agentic commerce storm
FIS: FIS launches industry-first offering enabling banks to lead and scale in agentic commerce (Jan 12, 2026)
DEFS demo results: model credit union built from public information, using test data (3,259 agent requests from OpenAI and Claude agents).