AI Agent Payments for Small Business: Let AI Queue the Bills, Keep the Approve Button

On October 15, Mercury added a feature that makes "AI agent payments" concrete for small businesses. Its release notes say you "can now ask ChatGPT or Claude to move money, pay a recipient, or categorize transactions on your Mercury account," and that "nothing moves until you approve it."

The next day, @TheClaytonR summed up why it matters: "The win isn't faster bookkeeping. It's the owner becoming the approver, not the doer. Start with vendor bills. Then run quote follow-ups the same way."

That is the right reading. The feature is useful, but the design pattern behind it is more useful. Here is how it works, where it fits in a service business, and how to set it up without handing an assistant the keys.

TL;DR

What Mercury actually launched

Mercury's support article and developer docs spell out the boundaries clearly:

The docs are explicit: "Your AI tool creates a payment or transfer request. It cannot approve the request or move money on its own." Even clicking a confirm button in the chat "doesn't authorize the payment. You must approve the request in Mercury before it can be initiated." Approval requests "expire after approximately 5 minutes."

Mercury also notes that its connector "is currently in Beta" and asks users to "double check any responses from the LLM with your Mercury account for any important decisions."

Why the approve button is the whole point

Most of the anxiety about AI agents and money is about one thing: an assistant doing something irreversible because it misunderstood. Mercury's design answers that by splitting the work in two.

The AI does the tedious part: finding the bill, matching the recipient, filling in the amount and account. A person does the decisive part: looking at the finished request and tapping approve or decline. If the AI got it wrong, the cost is a declined request, not a lost payment.

That split is the same rule SpiAI uses in every client workflow, whether the output is a payment, a quote or an email: AI drafts, your team approves. Mercury has simply built it into a bank.

Where this fits in a service business

For a 5 to 75 person service business, the obvious first use is accounts payable. A typical week might include subcontractor invoices, supplier bills, software renewals and rent. Each one involves the same steps: open the email, find the amount, check it against what was agreed, log in to the bank, pay.

With an approval-first setup, the steps become:

1. A bill arrives by email.
2. The assistant reads it, matches it to an existing recipient and prepares the payment request.
3. The request lands in Mercury's Tasks page or as a verification notification.
4. The owner or bookkeeper reviews the recipient, amount and account and approves or declines.

The person who owns the money still makes every decision. They just stop doing the typing.

How to set it up safely

1. Decide who approves. Name the person who approves AI-requested payments. For most small businesses that is the owner or a bookkeeper who already has payment authority.
2. Start with existing recipients only. Mercury already limits AI payments to recipients that exist in your account. Keep adding new vendors a manual, deliberate step.
3. Review the permission screen. When you connect, Mercury shows which organization and which permissions you are granting. Read it, and connect only the business account you mean to.
4. Treat categories differently. Categorization changes apply immediately. If your bookkeeper relies on clean categories, decide whether the assistant should have that permission at all.
5. Check before approving, every time. Recipient, amount, account, payment method. The five-minute expiry is a reason to approve promptly, not a reason to skim.
6. Revoke when not needed. You can disconnect the AI tool at any time. If nobody is using it, remove it.

Mistakes to avoid

• Approving from the chat window. The chat confirmation does nothing on its own. Real approval happens in Mercury, which is where you should look at the details.
• Sharing one login. Every person who requests or approves payments should have their own access, so you can see who did what.
• Skipping your own policies. Mercury says your organization's approval policies still apply. If you require two approvers above a certain amount today, keep that rule.
• Starting with the hardest bills. Begin with recurring, predictable vendors. Leave disputed invoices and new vendors to a person until the routine is solid.

Questions to ask before connecting any AI tool to money

Mercury is the first bank many owners will see this from, but it will not be the last. Before you connect an AI assistant to any financial account, whether a bank, a card platform, a payroll tool or accounting software, ask the vendor five questions:

1. Can the AI move money on its own, or only request it? The answer you want is "only request."
2. Where does approval happen? It should happen inside the financial tool, under your normal login and verification, not in the chat.
3. Which actions apply immediately? Many tools let some changes skip approval, as Mercury does with categories. Know which ones.
4. Can you limit who and what the AI can pay? Restricting payments to existing recipients removes the most damaging class of mistake.
5. How do you revoke access? You should be able to disconnect the assistant in one step, and see what it did while it was connected.

If a vendor cannot answer these clearly, wait. The approval design is not a nice extra. It is the reason this is safe to use at all.

The same pattern beyond payments

@TheClaytonR's suggestion to "run quote follow-ups the same way" is the bigger idea. Any task where a mistake is costly but the preparation is tedious fits the pattern:

• Quotes. AI drafts the quote from your price list and the customer's request. An estimator approves before it goes out.
• Follow-ups. AI drafts the reminder for an unanswered quote. A person approves the wording and timing.
• Collections. AI drafts the overdue-invoice email. The owner approves anything that names a late fee.

In each case, the person stops being the doer and becomes the approver. That is where an owner-led business gets its time back.

Verdict

Verdict: AI agent payments are ready for small businesses when the AI can only request and a person must approve, which is exactly how Mercury built it. Start with recurring vendor bills, keep approval with whoever owns the money today, and copy the same request-then-approve design into the rest of your workflows.

FAQ