How does the daily billing sweep invoice due cycles?

A daily background job (a Hangfire recurring sweep) looks for subscription cycles that are due and processes them: it generates the cycle's invoice/charge, and in Stored mode attempts payment against the saved card; in Manual mode it raises the invoice for the customer to pay. Each subscription is broken into SubscriptionCycles (one per period), so the sweep can track exactly which…

A daily background job (a Hangfire recurring sweep) looks for subscription cycles that are due and processes them: it generates the cycle's invoice/charge, and in Stored mode attempts payment against the saved card; in Manual mode it raises the invoice for the customer to pay. Each subscription is broken into SubscriptionCycles (one per period), so the sweep can track exactly which periods are scheduled, invoiced, paid, or failed. The job is idempotent and safe to re-run, so a missed or retried run doesn't double-bill. It also drives dunning and lifecycle transitions on failure.