Payment Infrastructure for Zero Deliverables

Payment infrastructure handles money. Checkout flows, subscription management, webhook handlers, customer portals. The systems exist to collect payment for goods or services. Project Nothing needed the same infrastructure to collect payment for neither goods nor services. Real money. Zero deliverables. Full Stripe integration.

The Absurdity of Real Payments

Stripe's documentation assumes you're selling something. Product descriptions. SKU management. Fulfillment webhooks. The API expects post-payment actions: ship product, grant access, deliver service. Project Nothing's post-payment action: do nothing.

Yet the technical requirements remain identical. Secure checkout sessions. PCI-compliant payment processing. Subscription lifecycle management. Failed payment handling. The infrastructure complexity doesn't decrease because the product is nothing. If anything, ensuring reliable delivery of nothing requires robust systems.

The checkout flow needed special attention. Standard flows minimize friction — fewer steps means higher conversion. Project Nothing added friction deliberately: confirmation screens explaining you'll receive nothing, cancel options at multiple points, explicit disclaimers before payment. The goal wasn't maximizing conversions but ensuring conscious participation.

Webhook Handlers for Nothing

Stripe sends webhooks for subscription events. `checkout.session.completed` signals successful payment. `customer.subscription.updated` tracks changes. `invoice.payment_failed` indicates declined charges. Each webhook expects handler logic: provision access, send confirmations, trigger fulfillment.

Project Nothing's handlers do the minimum: record subscription, update counts, log events. No access provisioning (nothing to access). No fulfillment triggers (nothing to fulfill). No welcome emails (stated policy: zero emails). The handlers exist to maintain accurate subscriber tracking — the only metric that matters when the product is nothing.

Failed payment handling follows standard patterns: retry logic, notification systems, eventual cancellation. The irony: sophisticated infrastructure ensuring payment processing succeeds for delivering nothing. But the integrity of the experiment requires this — if payments fail silently, the subscription isn't genuinely nothing. It's broken nothing.

Customer Portal for Void Management

Stripe's customer portal lets subscribers manage subscriptions: update payment methods, change plans, cancel service. Project Nothing enables full portal access. Subscribers can upgrade from The Void to The Singularity (still receiving nothing, just paying more). They can cancel anytime (stop paying for nothing). They can view billing history (documentation of payments for nothing).

The portal transparency reinforces the broader commitment: complete control, zero lock-in, honest presentation. You're paying for nothing, but you have full power to manage that payment however you choose. No dark patterns. No difficult cancellations. The subscription serves you, even while delivering nothing.

Building payment infrastructure for zero deliverables required all the technical sophistication of standard e-commerce plus additional ethical considerations. The systems had to work flawlessly while delivering nothing. The infrastructure had to enable commerce while being transparent about absence. Stripe doesn't care what you sell. The API handles nothing the same as something — which perfectly suits Project Nothing's needs.