Goodwill credits
Discretionary credits issued via customer.balance_transaction. Often tighter than refund ceilings because every issuance is policy-discretionary.
- Auto-allow up to
- $10
- Require approval
- > $10
- Hard block above
- > $2,500
Aggressive close-window posture. Non-trivial outflows route to approval, every dispute and high-risk refund reason hard-blocked, dispute evidence due in 12h.
A close-window lockdown profile for the final 5-7 business days of a quarter or fiscal year when finance teams want to minimize unreviewed cash movement that could affect the as-reported numbers. Auto-allow is intentionally crushed to a near-zero ceiling so substantially every outflow is at least logged with an approval signature, and the blocked-reasons list is wider so any credit-issuance with a fraudulent/duplicate/requested_by_customer tag during close is hard-blocked and routed manually. Designed to be activated by the finance lead 1-2 weeks before close and rolled back to the org's everyday template after close certification. Pair this with the dual-approval feature for an explicit second-signer audit trail.
These thresholds apply to refunds and any category that does not have its own override. Amounts are in USD cents in the underlying rule and rendered in USD here.
fraudulentduplicaterequested_by_customerWhen a category has its own ceiling, the typed evaluator consults the override instead of the top-level. Categories without an override fall back to the thresholds above.
Discretionary credits issued via customer.balance_transaction. Often tighter than refund ceilings because every issuance is policy-discretionary.
stripe.payout.create plus the full lifecycle (paid, failed, canceled, reconciliation_completed). Operators with steady payout cadence want a higher ceiling here.
stripe.transfer.create and reversals across Connect platforms. Often the largest movements in marketplace flows.
charge.dispute lifecycle. Always combined with the dispute-window deadline rule below.
Pure threshold projection at common amounts. Live decisions also consult blocked-reason lists (e.g. fraudulent refunds always escalate) and the dispute-window escalation rule, so a real decision may be stricter than what the matrix shows.
Useful when you want to reference this template programmatically, in tests, or in support tickets.
sox-quarterly-close-lockdownSOX quarterly close lockdown policyPOST /api/policies/typed-templates/install with body { slug: "sox-quarterly-close-lockdown" }GET /api/policies/typed-templatesSee also: all templates - full coverage matrix - AI agents brief
Sign in to your Axiru workspace and install 'SOX quarterly close lockdown'. Decisions land on your dashboard within seconds of your next webhook. Move from simulate to enforce when you have the audit trail you want.
Start in shadow mode first. Move to live enforcement later.
We use cookies for analytics and marketing measurement. You can reject non-essential cookies at any time.