For standing orders, yes; for direct debits, usually not, because the collecting company sets them up. An AI agent can create a standing order to a verified payee on the customer's instruction at depth 3, and explain the direct debit process. Pressured requests, or new payees that fail checks, go to a named person.
Why are the two so different?
They point in opposite directions. A standing order is an instruction from the customer to their bank: pay this amount to this account on this schedule. The customer controls it completely. The bank's agent can set it up, change it or cancel it on the customer's instruction.
A direct debit is permission for a company to take money from the customer's account. The mandate is usually created by the company that collects, with the customer's agreement, and lodged with the customer's bank through the scheme. In most markets the customer's bank does not originate it. So the agent's role is to explain, confirm and protect, not to set it up on the customer's behalf.
What conditions decide a standing order?
The agent may set one up when:
- the customer gave the instruction in an authenticated session;
- the payee is already on the customer's payee list, or is added through the bank's payee process with name checks where available;
- the amount, start date, frequency and end date are confirmed back to the customer;
- the first payment and the schedule fit within the customer's limits;
- there are no scam signals, such as a third party telling the customer to set up regular payments.
New payees are the risk point, as with any payment. A standing order to a fraudster's account is a repeating loss.
What may the agent do, and where must it stop?
| Request | The agent | Where it stops |
|---|---|---|
| Standing order to an existing payee | Creates it after confirming details, depth 3 | Nothing routine |
| Standing order to a new payee | Runs the payee process, then creates on confirmation | Payee checks that fail or warn |
| Changing an amount or date | Changes on instruction, depth 3 | Nothing routine |
| Setting up a direct debit | Explains how the company sets it up | Originating the mandate itself |
| Confirming a new direct debit has arrived | Shows the mandate and first collection | Disputes about its terms |
| Customer told to set up regular payments by a caller | Pauses and asks | Fraud team |
| Business account mandates | Checks the signing rules | Requests outside the mandate |
Stopping payments is the reverse action, with its own risks; see whether an AI agent can cancel a direct debit.
An example: rent and a "debt collector"
Take a customer who moves into a new flat and asks the agent to pay rent of 900 on the first of each month to the landlord, whose details are on the tenancy agreement. The agent adds the landlord as a payee through the bank's process; the name check returns a match. It confirms the amount, start date and frequency, and the customer approves in the app. The standing order is created.
A month later, the same customer messages: a debt collection firm called and told them to set up a direct debit for an old phone bill, and asked for their account details and the security code from their card. The agent tells the customer not to share the card code with anyone, explains that genuine collectors send written details and that a direct debit is set up through the company's own process, and suggests checking the debt by calling the phone company on a number the customer already has. It flags the contact to the fraud team, which looks for any new mandate in the following days.
What controls make it safe?
- Authenticated instructions only. Standing orders are created or changed from the customer's own session.
- Payee checks before the first order. New payees pass the same name checks and warnings as a one-off payment.
- Confirmation of every detail. Amount, dates and frequency are shown back to the customer and recorded with their approval.
- No origination of direct debits. The agent has no capability to create a mandate in the customer's name.
- New mandates surfaced. When a direct debit is lodged against the account, the agent can show the customer so they can query anything unexpected.
Agreeing payment plans with borrowers is a different setting, where the lender is the collector; see letting an AI agent set up payment plans in your collections system. The general limits are in AI agents in banking: what they may and may not do.
Where Pryme fits
In Pryme, creating a standing order and adding a payee are separate capabilities, so an agent certified for the first does not inherit the second. The payee's details arrive sealed from the core banking system once added. Details pasted from a tenancy agreement or an email are external, and an external claim cannot authorise a payment.
Questions people ask
Can the agent set up a standing order for a variable amount?
No. A standing order is for a fixed amount. For variable bills, a direct debit with the company, or a rule-based bill payment, is the better fit.
Can the agent set up a standing order from a joint account?
Yes, if the account mandate lets either holder instruct payments. Where both must sign, the agent waits for the second holder's approval.
Can the agent pause a standing order?
Where the bank's system supports skipping a payment, yes, on the customer's instruction. Otherwise it can cancel and set up a new one later.