Refund Eligibility Guardrail on Stripe Refunds

It watches refunds as they happen and checks each one against your refund rules — time since purchase, percentage refunded, and per-agent limits. Compliant refunds pass silently; anything outside the rules is surfaced immediately so a supervisor can question it before it becomes a pattern.

Use it as a backstop when agents can issue refunds directly and you need an after-the-fact compliance check without slowing the team down. It catches the refund that was technically allowed in the tool but not by policy.

1. 1A Stripe `refund.created` webhook triggers the flow with the refund and linked charge.
2. 2The flow retrieves the original charge date, amount, and who initiated the refund from Stripe.
3. 3An OpenAI step evaluates the refund against your written policy window and amount thresholds.
4. 4A logic branch separates compliant refunds from out-of-policy or oversized ones.
5. 5Compliant refunds are logged and the flow ends quietly.
6. 6Violations are posted to a Slack supervisor channel with the charge details, the policy rule broken, and the agent who issued it.