<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Giuseppe Falcetta</title>
    <description>The latest articles on DEV Community by Giuseppe Falcetta (@peppe98).</description>
    <link>https://dev.to/peppe98</link>
    <image>
      <url>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%2F4247697%2F56b01e9d-7319-4f1f-a822-207b898d721a.png</url>
      <title>DEV Community: Giuseppe Falcetta</title>
      <link>https://dev.to/peppe98</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/peppe98"/>
    <language>en</language>
    <item>
      <title>Making Stripe subscription Checkout checks repeatable</title>
      <dc:creator>Giuseppe Falcetta</dc:creator>
      <pubDate>Mon, 16 Nov 2026 12:15:01 +0000</pubDate>
      <link>https://dev.to/peppe98/making-stripe-subscription-checkout-checks-repeatable-4li5</link>
      <guid>https://dev.to/peppe98/making-stripe-subscription-checkout-checks-repeatable-4li5</guid>
      <description>&lt;p&gt;When a subscription checkout changes, there are several things to check: did the app create a subscription-mode Checkout Session, did it use the expected recurring Price, did Stripe create the subscription, and did the app process the related events?&lt;/p&gt;

&lt;p&gt;Those checks are related, but they are not the same test. Treating them as one all-or-nothing browser script can make failures hard to interpret—especially when the hosted payment page itself is difficult to automate.&lt;/p&gt;

&lt;p&gt;I’m building &lt;strong&gt;SubTest&lt;/strong&gt;, an open-source local CLI for repeatable Stripe subscription checks.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Check the Checkout Session contract
&lt;/h2&gt;

&lt;p&gt;SubTest follows browser steps that you configure for your application, captures the test Checkout Session your app creates, then checks that Session through Stripe’s API. The default check verifies the subscription mode and expected recurring Price without filling in the payment form or claiming a payment succeeded.&lt;/p&gt;

&lt;p&gt;This is useful when you want a repeatable check that your app is creating the intended Stripe Session after a code or configuration change.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Exercise lifecycle and webhook evidence separately
&lt;/h2&gt;

&lt;p&gt;A Test Clock scenario creates its own test customer and subscription directly through Stripe, advances simulated time, and checks Stripe-side subscription and invoice state. If you configure a local evidence endpoint, SubTest can also check whether your app reports processing the expected Stripe event IDs.&lt;/p&gt;

&lt;p&gt;That endpoint is application-provided evidence. SubTest does not inspect an arbitrary app database or infer that the app updated its internal business state correctly.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Treat the hosted browser attempt as optional
&lt;/h2&gt;

&lt;p&gt;The &lt;code&gt;--browser-smoke&lt;/code&gt; option attempts the hosted Checkout UI with configured test payment details. Browser automation can be blocked or the UI can change, so this is a best-effort check. If it blocks, SubTest keeps the Session checks and reports a partial result with the browser evidence it observed; it cannot always identify the exact cause.&lt;/p&gt;

&lt;p&gt;The tool runs locally, stores history in SQLite, and includes a local dashboard. It accepts Stripe test-mode keys only. To try it, you’ll need Node.js 22.13+, pnpm, your own Stripe test account, a recurring test Price, and an app checkout flow to configure.&lt;/p&gt;

&lt;p&gt;The repository and quick start are at &lt;a href="https://github.com/pepito1198/subtest" rel="noopener noreferrer"&gt;github.com/pepito1198/subtest&lt;/a&gt;. If you try it, I’d value feedback on where setup is unclear and which subscription checks you need most.&lt;/p&gt;

</description>
      <category>opensource</category>
      <category>testing</category>
      <category>webdev</category>
      <category>stripe</category>
    </item>
  </channel>
</rss>
