The official Stripe .NET library for integrating Stripe's payment and financial services into .NET applications.
Stripe.net is the official .NET library for integrating with Stripe's payment processing platform. It provides a strongly-typed, fully-featured client that allows .NET developers to interact with Stripe's APIs to handle payments, subscriptions, customer management, and other financial operations. The library abstracts the complexity of HTTP communication and provides intuitive service classes for all Stripe resources.
.NET developers building applications that require payment processing, e-commerce platforms, SaaS subscriptions, or any financial transaction functionality using Stripe's services.
Developers choose Stripe.net because it's the officially maintained library with guaranteed compatibility with Stripe's API, comprehensive feature coverage, strong typing for better developer experience, and regular updates that keep pace with Stripe's evolving platform.
Stripe.net is a sync/async .NET 4.6.1+ client, and a portable class library for stripe.com.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Provides strongly-typed access to all Stripe resources like customers and payments, ensuring type safety and reducing errors, as highlighted in the key features.
The centralized StripeClient improves discoverability and allows per-client configuration, enhancing the developer experience with better IDE autocompletion.
Built-in retry with configurable counts handles intermittent network failures, making integrations more robust without manual intervention.
Includes mechanisms for public and private preview features via special SDK versions, keeping pace with Stripe's latest offerings, as detailed in the README.
Allows injection of custom HttpClient for proxy support or custom handlers, offering flexibility in network configurations, as shown in advanced usage examples.
The standard List method requires manual iteration with StartingAfter parameter, which is more cumbersome compared to fully automatic pagination in other SDKs.
Beta and alpha SDK versions can have breaking changes without major version bumps, forcing developers to pin versions carefully, as warned in the README.
Using undocumented parameters requires workarounds like AddExtraParam or accessing RawJObject, breaking type safety and adding maintenance overhead.