SaaS subscription refunds
Mid-market SaaS with self-serve and assisted billing, mixing prorated cancellations, goodwill credits, and the occasional six-figure annual refund.
Read the scenarioAxiru is pre-revenue, so we do not publish made-up customer logos or fabricated savings figures. Instead, here is how Axiru is configured for the patterns we see most often in conversations with finance and ops teams. Numbers are clearly labeled as illustrative or cited to public sources.
Mid-market SaaS with self-serve and assisted billing, mixing prorated cancellations, goodwill credits, and the occasional six-figure annual refund.
Read the scenarioTwo-sided marketplace on Stripe Connect, where a buyer refund has to claw money back from the seller and possibly from the platform fee at the same time.
Read the scenarioDirect-to-consumer digital goods where the product is delivered the moment payment authorizes, and where refund-after-consumption is the dominant fraud pattern.
Read the scenarioLate-stage or public company where every refund over a control threshold needs two named approvers, an evidence chain, and an audit-ready export at quarter end.
Read the scenarioMost early-stage vendors paper over the absence of real customers with composite stories that read as real. We do not. Each page below describes a configuration we actually recommend, and a set of signals we actually watch. When real, named, opt-in customers exist we will publish them with their own numbers. Until then, you get the playbook.
Upload the last 90 days of refund history and Axiru will simulate these policies against your real data, with no enforcement, before you change anything.
Start in shadow mode first. Move to live enforcement later.