The latest articles on DEV Community by Dmnadsword Tv (@lightseong). https://dev.to/lightseong 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%2F3970921%2F0d4c323b-8039-4880-b723-d5a2f23e899c.jpg https://dev.to/lightseong en Dmnadsword Tv Sun, 07 Jun 2026 14:00:13 +0000 https://dev.to/lightseong/how-i-built-a-stripe-monitoring-tool-in-my-browser-with-zero-backend-3n7a https://dev.to/lightseong/how-i-built-a-stripe-monitoring-tool-in-my-browser-with-zero-backend-3n7a <p>Most payment monitoring tools work the same way:<br> your API key goes to their server, their server <br> polls Stripe, their server sends you a notification.</p> <p>That means your revenue data, customer patterns, <br> and API credentials are sitting on someone else's <br> infrastructure. Forever.</p> <p>I built Stripe Alerts differently.</p> <p><strong>The architecture</strong></p> <p>Everything runs in the browser. Here's the full flow:</p> <ol> <li>User pastes a read-only Stripe API key</li> <li>Key is stored in chrome.storage.local — never synced, never transmitted</li> <li>A Chrome Manifest V3 service worker polls the Stripe REST API directly on a schedule</li> <li>Response is processed locally in the browser</li> <li>Chrome's native notifications API fires the alert</li> </ol> <p>The request chain is: Browser → Stripe API → Browser.<br> No middleman. No server. No data leakage.</p> <p><strong>Why Manifest V3 matters</strong></p> <p>Chrome's Manifest V3 forced developers to move from <br> persistent background pages to service workers. This <br> actually helped the privacy architecture — service <br> workers are ephemeral, they spin up to do a job and <br> shut down. Nothing persists in memory between checks.</p> <p><strong>What it monitors</strong></p> <ul> <li>Failed payment spike detection</li> <li>Chargeback and dispute activity </li> <li>Subscription cancellation monitoring</li> <li>Refund anomaly detection</li> </ul> <p><strong>The result</strong></p> <p>A monitoring tool that is genuinely privacy-first by <br> architecture, not just by policy. There's no server <br> to breach, no database to leak, no API key to steal.</p> <p>Free to install → <a href="https://chromewebstore.google.com/detail/stripe-alerts/epemeoabcaoifldejoblcknljpgbphao" rel="noopener noreferrer">https://chromewebstore.google.com/detail/stripe-alerts/epemeoabcaoifldejoblcknljpgbphao</a></p> <p>Happy to answer any technical questions below.</p> stripe webdev javascript privacy Dmnadsword Tv Sat, 06 Jun 2026 08:05:38 +0000 https://dev.to/lightseong/real-time-stripe-monitoring-that-never-leaves-your-browser-48oh https://dev.to/lightseong/real-time-stripe-monitoring-that-never-leaves-your-browser-48oh <p>Stripe Alerts is a Chrome extension that monitors <br> your Stripe dashboard and sends instant desktop <br> notifications when something goes wrong — failed <br> payment spikes, chargebacks, subscription <br> cancellations, and refund anomalies.</p> <p>Your read-only Stripe API key is stored locally in <br> Chrome. No external servers, no data transmission, <br> no account required. Free tier available, Pro <br> unlocks all alert types and unlimited checks. <br> </p> <div class="crayons-card c-embed text-styles text-styles--secondary"> <div class="c-embed__content"> <div class="c-embed__body flex items-center justify-between"> <a href="https://www.getstripealerts.com" rel="noopener noreferrer" class="c-link fw-bold flex items-center"> <span class="mr-2">getstripealerts.com</span> </a> </div> </div> </div> / monitoring privacy showdev tooling