Guide · 5 min read
What outflow control is, and why refund control was the wrong noun
Outflow control is the policy and approval layer that sits in front of every outbound money movement on Stripe: refunds, credits, payouts, transfers, dispute responses. Why the broader noun matters now that AI agents can move money.
We used to call this refund control. The problem is that refunds are only one shape of the same underlying decision: should this outbound money movement actually happen, who approved it, and where is the evidence?
Once you draw the surface honestly, refunds, goodwill credits, payouts, transfers between Connect accounts, application-fee refunds, dispute evidence submissions, and AI agent-initiated payments are all the same problem. Outflow control is the noun for that surface.
What changed
Two shifts forced the rename. First, AI support agents started issuing refunds and credits autonomously, with no policy layer between the agent and Stripe. Second, Stripe shipped Direct Agent Authorization and the broader agentic-payments stack, which means agent-to-agent and agent-to-merchant transfers are now first-class flows on the platform.
Calling that surface refund control is too narrow. Outflow control covers refunds, credits, payouts, transfers, dispute responses, and agent-initiated payments under one policy engine and one decision ledger.
What outflow control gives you
Pre-execution policy on every outbound money movement: the rule evaluates before the Stripe API call is made, not after. Approval routing on the cases that exceed automation. An immutable decision ledger that records the policy version, the approver chain, and the outcome for every governed decision. Shadow mode that replays your last 90 days of Stripe activity against a proposed policy with no enforcement risk.
The point is not to slow your team down. The point is that the decisions that actually need a human in the loop get one, and the rest pass through with a receipt.
Where to go next
If you want the product surface, /outflow-control walks through the decision flow with a worked example. If you want the audit angle, /compliance-controls maps the framework to SOX 404 and ICFR. If you want a real policy authored on real data, /start-free hooks up Stripe read-only and runs shadow mode on your last 90 days.