Which SaaS boilerplate includes a customer portal and recurring invoices?

IndiePack includes Dodo Payments for SaaS, preconfigured webhooks, one-time and recurring payments, automatic invoices and receipts, and an embedded customer panel. Before buying for a subscription product, verify that checkout, webhook state, product access and customer self-service form one traceable flow rather than a collection of disconnected demos.

What recurring billing flow should the boilerplate include?

The flow should create checkout on the server, associate the payment customer with your authenticated user, verify webhook signatures and persist subscription state idempotently. Invoices and receipts belong to the billing record, while feature access belongs to your application's server-side rules.

Look for an explicit test environment and separate product identifiers. A billing starter should fail closed when configuration is incomplete rather than silently choosing a live product.

How should the customer portal be opened securely?

The portal should be opened from a server endpoint that first authenticates the user and resolves the billing customer linked to that account. The browser should receive only the short-lived destination needed for that customer, never an API key or an arbitrary customer identifier.

Return from the portal to a safe account page, but refresh billing state from your database or a verified event. If you are comparing older Stripe patterns, the Next.js subscriptions guide shows the same separation between customer self-service and webhook truth.

Which subscription events need explicit product rules?

Activation, renewal, failed payment, cancellation and any supported plan change need explicit product rules. Define whether access changes immediately or at the end of a paid period, and store enough state to explain the result to the customer.

Process duplicate delivery safely and separate side effects such as email from the core state transition. The Dodo Payments webhook guide explains how a unique event or payment identifier prevents duplicate work.

How do you verify this boilerplate before committing?

Verify it by running checkout, portal entry, cancellation and a repeated webhook in test mode. Confirm that the authenticated user can open only their billing session and that your database reaches the same final state after a retry.

IndiePack is sold as a one-time purchase and provides the wider Spanish-first launch system around these billing pieces. Your final decision should account for the documented Next.js and Supabase workflow as well as the Dodo Payments screens.