Mercury Lets ChatGPT and Claude Queue Payments. Approve in Mercury First.

On October 15, 2026, Mercury released write actions for its Model Context Protocol (MCP) connection so ChatGPT, Claude and other supported AI tools can request payments, internal transfers and category changes on a Mercury account. (Mercury release notes)

Payments and transfers still move only after a human approves them in Mercury. A confirmation in the chat is not that approval. Category and note edits apply immediately, with no Mercury approval queue.

What shipped

Mercury's docs list five write tools (supported tools):

• `requestSendMoney`: queues a payment to an existing recipient. Needs approval in Mercury before money is sent.
• `requestTransferMoney`: queues a transfer between your own Mercury accounts. Needs approval in Mercury before money moves.
• `createCategory`: creates a custom expense category immediately. No separate Mercury approval.
• `editCategory`: updates a custom expense category immediately. No separate Mercury approval.
• `updateTransaction`: updates or clears a transaction's note or category immediately. No separate Mercury approval.

Existing read-only connections must reauthorize before these write tools work. Mercury's support article also states that AI tools cannot add new recipients: you can only request payments to recipients already in Mercury. (Connecting Mercury to AI tools)

Chat Confirm is not Mercury Approve

Mercury's support page is explicit: selecting Confirm Request in the AI tool does not authorize the payment. You still open Mercury, find the request under Needs approval in Tasks or Payments, and approve or decline there.

Approval requests expire after approximately five minutes. If one expires, you start again from the AI tool.

Mercury's docs add that your organization's approval policies still apply. If those policies would otherwise skip an approval step, the requester must still approve the request in Mercury. The AI tool cannot approve the request or move money on its own. "Request created" does not mean "payment sent."

The six-line payment approval ledger

Before anyone taps Approve in Mercury, put these six lines on the request. One row per payment or transfer.

1. Task and recipient. What the payment is for, and which existing recipient or destination account is named. If the recipient is new, stop: add them in Mercury first, outside the AI tool.
2. Amount and method. The dollar amount, the payment method, and the timing Mercury shows.
3. Requester and AI tool. Who asked, which AI client queued it (ChatGPT, Claude, Cursor or another supported MCP client), and which Mercury user will approve.
4. Policy and eligibility. Whether the amount sits inside the org's approval policy, and whether the approver is an eligible approver for that request.
5. Outcome or purpose. The business reason in one line a CFO or RevOps lead can audit later (vendor invoice, partner payout, internal float move).
6. Keep, cut or expiry. Approve, decline, or let the ~5 minute window expire and restart with a corrected request.

Who owns which line

• CFO or finance ops: owns lines 2, 4 and 6. Money leaves only after Mercury Approve, and the receipt has to match policy.
• RevOps or GTM ops: owns lines 1, 3 and 5 when the payment is a vendor, partner or campaign cost that sits next to revenue work.
• CRO or founder on Mercury: sets which AI tools may connect, which users may request, and who is an eligible approver.
• Anyone connecting an AI tool: treats category and note edits as live edits. They skip the approval queue, so a wrong category can overwrite a correct one without a second look.

This is the same receipt pattern whether you run payments for a manufacturer, an insurer, a regional bank, a hospital system or a software company. The bank product is Mercury; the ledger is for the humans who still have to tap Approve.

What to do this week

1. List every AI tool connected to Mercury in your org, and confirm each one reauthorized after the Oct 15 write tools shipped.
2. Confirm no workflow assumes chat Confirm equals bank approval.
3. Add the six ledger lines to your Mercury approval checklist for `requestSendMoney` and `requestTransferMoney`.
4. Decide who may create or edit categories through AI, since those changes apply now.

Related

• Accenture's $29 Claude Allowance: A Six-Line Ledger Before You Approve Overage
• AI Credit Index: Price the Task, Not the Credit
• Sales AI Just Moved Into ChatGPT and Claude. What Can It Read, Write, and Prove?
• Who Audits the Meter on Our AI Agents?
• Reversal Ledger

Sources

1. Mercury release notes, "Take action on your Mercury account from ChatGPT and Claude," Oct 15, 2026: mercury.com/releases
2. Mercury Support, "Connecting Mercury to ChatGPT, Claude, and other AI tools": support.mercury.com
3. Mercury docs, "Supported tools on Mercury's MCP": docs.mercury.com

If you want the next bank or agent payment control checked the same way, subscribe.