The latest articles on DEV Community by Giorgio Di Rosa (@giorgiodirosa). https://dev.to/giorgiodirosa https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4140232%2Fb9915ed1-5974-41b4-b7ae-41f770bfa002.png https://dev.to/giorgiodirosa en Giorgio Di Rosa Thu, 24 Sep 2026 01:24:56 +0000 https://dev.to/giorgiodirosa/how-i-built-a-stripe-billing-health-audit-for-saas-3ja7 https://dev.to/giorgiodirosa/how-i-built-a-stripe-billing-health-audit-for-saas-3ja7 <p>If you run a subscription SaaS on Stripe, a successful checkout does not necessarily mean your billing state will stay healthy forever.</p> <p>Subscriptions can become <code>past_due</code>, payments can remain incomplete, invoices can stay open after collection attempts, and customers can sometimes end up with more than one current subscription.</p> <p>I built Tresvio to make these states easier to spot.</p> <h2> What I wanted to monitor </h2> <p>The first version focuses on Stripe billing states such as:</p> <ul> <li> <code>past_due</code> subscriptions</li> <li> <code>unpaid</code> subscriptions</li> <li> <code>incomplete</code> subscriptions</li> <li>recent <code>incomplete_expired</code> subscriptions</li> <li>open invoices with an amount remaining after attempted collection</li> <li>multiple active or trialing subscriptions for the same customer</li> </ul> <p>The goal is not to automatically change anything in Stripe.</p> <p>Tresvio is designed as a monitoring and audit layer. It shows the state that deserves attention, while Stripe remains responsible for payment collection, retries, invoices, and subscription management.</p> <h2> Why I separated monitoring from recovery </h2> <p>I didn't want the tool to automatically cancel subscriptions, retry charges, issue refunds, or make billing decisions.</p> <p>Those decisions depend on each SaaS company's own policies.</p> <p>Instead, the workflow is:</p> <ol> <li>Connect Stripe</li> <li>Run an audit</li> <li>Review the findings</li> <li>Open the relevant customer, subscription, or invoice in Stripe</li> <li>Enable continuous monitoring if useful</li> </ol> <p>This also keeps the Stripe integration read-only for the monitoring workflow.</p> <h2> Stripe state is only half of the problem </h2> <p>There is another class of billing problems that Stripe alone cannot see.</p> <p>For example:</p> <ul> <li>Stripe says a customer is paying, but the app gives them no access</li> <li>the app gives premium access without a paid subscription</li> <li>the plan in Stripe does not match the plan stored by the application</li> </ul> <p>For that reason I also built an optional App Probe integration.</p> <p>It is not required for the normal Stripe audit. It is only there for SaaS teams that want to compare billing state with application access.</p> <h2> The free audit </h2> <p>I wanted the first step to be low-friction, so Tresvio starts with a free Stripe billing audit.</p> <p>The current flow is:</p> <p><strong>Connect Stripe → Run free audit → Review findings → Enable monitoring</strong></p> <p>No card is required for the initial audit.</p> <p>I'm currently looking for feedback from developers and SaaS founders using Stripe Billing.</p> <p>If you want to try it:</p> <p><a href="https://tresvio.com" rel="noopener noreferrer">https://tresvio.com</a></p> <p>I'd also be interested to know: what Stripe billing issue has caused you the most trouble in a SaaS project?</p> stripe saas webdev payments