Payment Integration

Payment processing is the backbone of every revenue-generating web application, yet implementing it correctly involves navigating a maze of compliance requirements, security protocols, and edge cases. From handling failed payments to managing subscription lifecycle events, the complexity of a robust payment system extends far beyond a simple checkout button. Fabricate reduces this complexity by writing Stripe code into your app from high-level descriptions.

Stripe has established itself as the industry standard for online payments, supporting 135 currencies and dozens of payment methods. When you tell Fabricate to add payments, the AI writes the integration into your app's server code: checkout session creation, webhook event handling, and customer portal links, using products and prices you define in Stripe. You add your own Stripe keys, and only the published app receives them, so real payments run only in the published app. The generated code follows Stripe's recommended patterns for security and reliability.

Subscription billing introduces additional complexity that many developers underestimate. Plan changes, prorated charges, trial periods, grace periods, failed payment retries, and dunning emails all need proper handling. Fabricate can generate the subscription lifecycle handling you describe, including the UI for plan selection, upgrade and downgrade flows, and a billing portal where customers manage their payment methods and invoices.

The checkout experience is generated to fit your application's design. The AI can send users to Stripe-hosted Checkout, which you brand in Stripe, or build an embedded flow if you ask for one. Custom success and cancellation pages are generated to handle post-checkout scenarios appropriately.

Revenue analytics can be generated into your admin screens on request, providing real-time visibility into monthly recurring revenue, customer lifetime value, churn rates, and payment failure rates. These metrics help SaaS founders make informed decisions about pricing, retention strategies, and growth planning without needing separate analytics tools.

Payments use your own Stripe account. On a paid plan, you connect it under More, Payments by pasting a Stripe secret key; Fabricate checks the key with Stripe and stores it encrypted as an app secret. When you ask for payments, the AI writes server routes that create Stripe Checkout sessions with that key and send customers to Stripe-hosted payment pages, so card data stays within Stripe's infrastructure and your app's server never processes, stores, or transmits card numbers.

A test key (sk_test_) reaches the preview and the published app, so you can pay with Stripe's test card before going live. A live key (sk_live_) reaches only the published app, the next time you publish. Prices are looked up on the app's server, never taken from the browser, and an order is marked paid only after the server asks Stripe whether the checkout was paid.

Subscriptions use Stripe Checkout in subscription mode, and the app checks the subscription status with Stripe before serving members-only content. Money goes straight to your Stripe account; Fabricate takes no share of it.