
For a US logistics and income-tools company, I wired Stripe Checkout, one-tap cancel and the subscription webhook. Each event writes membership status, subscription ID and period end back to the member record.
It fails closed: while a dependency is missing, it refuses to write rather than guessing. Stripe's extra subscription states are mapped, in code, onto the four the business actually uses, so no schema change was needed and no write is ever lost to an unknown value.
Alongside billing, I built and proved the data wall: one member can never read another member's rates, costs or net. It's enforced server-side on every read, with dispatcher and broker access scoped to explicit grants.
Stack: Node.js, Netlify serverless functions, Stripe, Airtable API.
0 likes · 0 views · Nov 17, 2026
Stripe checkout, cancel and webhooks that fail closed and never lose a write, plus a server-side data wall between members.