GoldcoteGOLDCOTE
Invest
Playbook · Money

AI agents and money: a refunds and disputes playbook

Agents are good at the slow part of money work: finding the payment, reading the history, drafting the change. The last step, moving the money, should stay with a person.

Updated October 2026

In short

Let AI agents prepare money actions but not execute them alone. Separate proposing from doing, so the agent never holds a key that can refund. Cap amounts, require the evidence on every proposal (the charge, the reason, earlier refunds), and treat irreversible actions (refunds, submitting dispute evidence, accepting a dispute, reporting fraud, voiding an invoice) as explicit approvals. Let unanswered proposals expire, keep a record, and start in test mode.

What an agent can prepare, and what needs extra care

Most payment work is lookup and judgment, which agents do well. A few actions can’t be undone and deserve a deliberate yes.

  • Good to prepare: refunds, dispute evidence, invoices and credit notes, subscription changes, coupons and payment links.
  • Irreversible: refunds, submitting dispute evidence, accepting a dispute, reporting fraud, voiding an invoice.
  • Customer-visible: anything that emails the customer, such as sending an invoice.

Write a refund policy the agent can cite

An agent follows written rules better than vibes. Write down when you refund in full, when partially, and what always needs you. Then ask the agent to quote the rule it applied in every proposal, so a decision takes seconds.

  • Full refund: duplicate charges, items never shipped.
  • Partial refund: late delivery, damaged packaging.
  • Always ask: anything above an amount you choose, repeat refunds to one customer, anything after a dispute opened.

Disputes: evidence beats speed

Disputes are decided on evidence: the order, proof of delivery, the customer’s own messages. An agent connected to your store and shipping tools can gather these in minutes. Save the evidence as a draft first, read it, and submit only when it’s right; submitted evidence can’t be changed, and accepting a dispute means you lose it.

Start in test mode

Run a week of proposals against test-mode keys before using live ones. Compare each proposal with what you would have done, tighten the written rules where the agent guessed, and only then switch to live.

Checklist

Before an agent touches payments

  • The agent holds no key that can move money; a broker sends approved changes.
  • Every proposal shows the amount, the reason and the evidence.
  • Irreversible actions need an explicit approval, every time.
  • Unanswered proposals expire instead of piling up.
  • You ran it in test mode first, and every decision is recorded.

How MoltenRock Connect does it today

MoltenRock Connect’s Human Queue is live for Stripe: the agent proposes, you approve with Touch ID on your Mac, and only then does Connect send the change. Money is capped at 1,000.00 per proposal, and unanswered proposals expire after 72 hours.

Questions

Can small refunds run automatically?

Some businesses allow that below a threshold. MoltenRock Connect asks for your approval on every Stripe change today; starting strict and loosening with evidence is the safer path.

Who should approve?

Whoever owns the money decision today. Team queues, where approvals go up to a manager, are on MoltenRock’s roadmap.

What if nobody answers?

Nothing happens. A proposal that isn’t decided expires; it never defaults to yes.

Does this replace Stripe Radar?

No. Radar scores payments; an agent adds context from your other tools and prepares a recommendation for you.

More guides