Yes, for scheduled payouts to a verified bank account that has not changed. An AI agent can release a merchant's routine payout at depth 4 when the amount is within the merchant's normal range and no risk hold applies. First payouts, payouts after a change of bank details, early payouts and unusual amounts go to a named person.
What is the real risk in a merchant payout?
The money itself is usually not in question. The merchant sold goods, the cards were charged, and the balance belongs to them, less fees and any reserve. The risk is where the money goes.
The most damaging attack on a payments company is not stealing card data; it is changing a merchant's payout account. A fraudster who takes over a merchant's dashboard, or persuades support to update the bank details, can redirect weeks of takings. Once a payout lands in the wrong account, getting it back is slow and often fails. That is why the deciding factor is the destination, not the amount.
What conditions let the agent release a payout?
All of these must hold:
- the payout follows the merchant's agreed schedule;
- the destination account was verified at onboarding or at its last change, and has not changed within the cooling-off period the payments company sets;
- the amount is within the merchant's usual range, given their history;
- no risk hold, reserve shortfall or open investigation applies to the merchant;
- the balance has been reconciled against settled transactions, less fees and refunds.
When any condition fails, the agent prepares the payout and holds it.
What may the agent do, and what stays with a person?
| Payout type | The agent | Stays with a person |
|---|---|---|
| Scheduled payout, unchanged account, normal amount | Releases at depth 4 within bounds | Nothing routine |
| First payout to a new merchant | Prepares and holds | Release after onboarding checks |
| Payout after bank details change | Prepares and holds | Confirming the change through a second channel |
| Early or instant payout request | Checks eligibility and drafts | Approving it |
| Unusually large payout | Holds with the comparison to history | Deciding whether to release |
| Payout from a balance with a pending reserve | Calculates the releasable amount | Deciding the reserve |
| Updating the merchant's bank details | Never | A person, after verification |
Payout amounts should also respect the merchant's limits, which is its own question: see whether an AI agent can set a merchant's transaction limits.
An example: a bakery chain with new bank details
Take a small bakery chain that receives a payout of about 8,000 every Monday. On Saturday, someone logs into its dashboard from a new device and changes the payout account. On Monday the agent prepares the payout.
The amount is normal, but the destination changed two days ago, inside the cooling-off period. The agent holds the payout and opens a case. A person on the merchant risk team calls the bakery's owner on the number recorded at onboarding. The owner did not change anything. The team restores the original account, locks the dashboard and releases the payout to the correct destination on Tuesday.
The record shows the change, the device it came from, the hold and the bound that decided it: the merchant's own account-change rule.
What controls make it safe?
- Destination verified from the system of record. The agent reads payout details from the merchant database. An email from the "merchant" with new details is external and cannot change a destination.
- Cooling-off after changes. Any change to payout details holds the next payout for a person.
- Amount bands from history. Each merchant has a normal range; payouts outside it are held.
- Reconciliation before release. The payout balance must agree with settled transactions and refunds before money moves.
- Separation of duties. The agent that releases payouts cannot change payout details, and no agent can approve another agent's change.
Payouts are the end of a chain that begins with merchant onboarding for card acquiring. Money also flows the other way through refunds, which have their own controls in letting an AI agent issue refunds through your payment gateway. The general rules are in AI agents in banking: what they may and may not do.
Questions people ask
Can the agent pause a merchant's payouts?
Yes, where the risk policy defines when payouts may be paused, because a pause protects funds and can be lifted. A person should review any pause quickly, since merchants depend on regular payouts.
What if a payout fails because the bank rejects it?
The agent records the rejection reason and tells the merchant what happened. It does not resend to a different account; the merchant must correct the details through the verified process.
Can the agent issue a payout to a marketplace seller?
The same rules apply, with one addition: marketplace sellers are often small and newly onboarded. The cooling-off and first-payout holds matter even more there.