Let an AI agent touch Stripe without letting it move money

Refunds, payouts, and disputes are irreversible the moment they fire. Cap the amounts, gate the approvals, and close the raw-API back door.

For: Finance and RevOps teams giving an agent access to payments

Payment actions are the rare agent write with no undo. A refund is money out the door; a dispute submission is a decision you can't recall; a payout goes where it goes. An agent that drafts a customer email is low-stakes — an agent that can call the refund tool is not.

The controls gate money movement at ingress. gate-money-movement-refund-cap caps refund and payment amounts and denies anything above the ceiling unless the caller is in the finance group. require-human-approval-dispute-submit keeps the agent from consummating a dispute on its own. role-gate-writes-billing restricts billing writes to authorized identities, and deny-escape-hatches-api-write blocks the raw pass-through tool that would otherwise let an agent route around every per-tool rule. On the way back, redact-pii-egress-customer masks customer PII in responses.

The posture is simple to state: the agent can read, reconcile, and draft, but it cannot move money past a threshold or bypass the controls to try.