openintegration200+ connectors
← Attack library · Banking & payments

Stop payout-account fraud when AI agents handle Stripe requests

Change the payout account and the next payout run goes to the attacker. An agent that acts on “urgent” finance emails is the shortest path there.

The workflow

An email asks to move Stripe payouts to a new bank account. The agent checks the current payout setup and prepares the change for review.

The attack hidden in it

A line tells the assistant to make the change today and keep it from the finance team.

How the guardrails handle it

  1. Screening withholds the instruction to act now and stay quiet.
  2. Payout-account changes are writes and always wait for a person.
  3. The approval shows the exact account and the sender, so it can be verified out of band.

Same workflow, every company size

The agent and the guardrails stay the same; only the systems behind them change.

Questions

Can an AI agent change Stripe payout details?

It can prepare the change. A person must approve it, and nothing the agent reads can skip that.

What is payout-account fraud?

An attacker asks for payouts to move to an account they control, often posing as your own finance team.

Which payment providers are supported?

Stripe and Mollie today, with more through native APIs.