Customer Billing

1. 1

   Start from local history

   Customer and operator pages read projected subscriptions, orders, invoices, charges, refunds, disputes, and entitlements from local tables.

   Relevant Product code

   • src/features/billing/server/queries/current-profile-history.ts
   • src/features/billing/server/queries/customer-history.ts
2. 2

   Use portal for customer changes

   The portal service resolves the active provider and customer before returning a provider-hosted URL.

   Relevant Product code

   • src/features/billing/server/services/portal.ts
3. 3

   Sync provider state deliberately

   Provider refresh and refunds stay behind admin services so support actions remain auditable and provider-aware.

   Relevant Product code

   • src/features/billing/server/services/customer-sync.ts
   • src/features/billing/server/services/admin-refund.ts
4. 4

   Export from local projections

   CSV exports are assembled from local customer and invoice rows after authorization checks.

   Relevant Product code

   • src/features/billing/server/export/request/auth.ts
   • src/features/billing/server/export/service.ts

Use this example as a starting point, then adapt it to your product's rules and configuration.

Portal requests accept only relative return paths so provider redirects stay inside the app.

const PortalBodySchema = z.object({
  return_path: z
    .string()
    .trim()
    .max(300)
    .refine((value) => value.startsWith("/") && !value.startsWith("//"), {
      message: "return_path must be a relative path",
    })
    .optional(),
  source: z.string().trim().max(80).optional().default("dashboard_billing_hub"),
});