Stripe Integration for ASP.NET Core

Stripe.net integrates cleanly with ASP.NET Core's conventions when it's configured as a typed, dependency-injected service rather than instantiated ad hoc inside controllers — the latter pattern works in a demo and becomes a testing and configuration headache the moment you need to mock Stripe calls or support multiple environments.

DI, Async, and Webhook Patterns for .NET

• Register the Stripe client as a typed service in `Program.cs`, configured once from environment-scoped options
• Use Stripe.net's async methods throughout — mixing sync and async Stripe calls in an ASP.NET Core app risks thread-pool starvation under load
• Webhook endpoints need to respect the framework's middleware pipeline (raw body access before any body-consuming middleware runs), the .NET equivalent of the Express raw-body issue
• Minimal APIs or MVC controllers both work — the DI and async patterns matter more than which routing style you choose

We focus on ASP.NET Core (.NET 6+) as the default target; legacy .NET Framework projects are evaluated case by case since Stripe.net's async patterns and DI conventions assume the Core-era hosting model.