Approve every Stripe refund before it moves money.
An AI agent with Stripe access can issue refunds, cancel subscriptions, delete customers and trigger payouts on its own. mild.run puts a human approval gate in front of all four — nothing executes until you say yes.
What mild.run gates on Stripe
Approve or block a refund by charge ID and amount before it's issued.
Confirm a cancellation before a customer's subscription actually ends.
A second pair of eyes before a customer record is permanently removed.
Sign off on payouts before funds leave your Stripe balance.
Set up in one MCP call
Your agent calls stripe_refund as an MCP tool. mild.run intercepts it, notifies you, and only lets it run once you approve.
// Your agent calls the MCP tool directly — no webhook server, no SDK.
stripe_refund(
charge_id="ch_3Qx8a...",
amount_cents=24000,
reason="requested_by_customer"
)
// mild.run pauses execution, notifies you via Telegram/email/Slack,
// and only calls the real Stripe API after you tap Approve.Stripe + mild.run FAQ
Does mild.run see my Stripe secret key?
Your Stripe key is stored encrypted (AES-256) and used only server-side to execute an approved action — it is never exposed to the agent or logged in plaintext.
What happens if I don't respond?
Every request has a 24-hour approval window. If you don't respond in time, the action is treated as blocked, not approved — mild.run fails closed.
Which Stripe actions does mild.run gate?
Refunds, subscription cancellations, customer deletions, and payouts — the four highest-risk write actions an agent could take against a Stripe account.