dotnetcharge.com

What It Is

.netCHARGE is a real-time credit card processing component from Corporate Web Solutions Ltd. for ASP.NET/.NET. It is not positioned as a standalone acquiring service or payment aggregation platform, but rather as a universal interface for connecting to payment gateways and processors. The website says it supports 50+ processors/gateways, allowing merchants to initiate transactions from their own website backend over SSL, usually without redirecting buyers to the processor’s page, helping keep the checkout experience consistent.

Core Capabilities

Its biggest feature is a “common interface”: when switching between multiple gateways, in many cases only minor code changes are required. It supports ASP.NET 4.0+, .NET Core, and .NET 6/7, and provides NuGet packages, WebForms, WinForms, sample projects, and documentation. Payment features include sale, authorization, post authorization, void, refund, force, eCheck, and more, depending on the specific processor. For risk control and security, it offers AVS, CVV, card-number pre-validation, client-side encryption, database logging, encrypted storage of sensitive fields, and other functions. Historical versions have supported 3D Secure, Stripe.js, Authorize.Net Accept.js, and similar tools to reduce the risk of card data touching the merchant’s server.

Pricing and Compliance

The main text does not disclose .netCHARGE licensing prices. It only states that v9.5 is available for purchase, offers a free trial, and mentions licensing options such as website/server, WinForms, and SaaS. In terms of fees, .netCHARGE itself does not determine transaction charges; merchants still need to contract with a gateway or processor. On compliance, v7 previously passed PCI Council PA-DSS 1.2, and earlier versions also had PABP/Visa CISP-related validation. However, the text also notes that PA-DSS no longer accepts components, and the final application must still meet PCI requirements on its own.

Pros, Cons, and Best Fit

Its strengths are deep integration with the .NET ecosystem, broad gateway coverage, low switching costs, and the possibility of reducing gateway fees by connecting directly to processors. Its drawbacks are that pricing, service SLA, and settlement cycles are not transparent; it is also not an out-of-the-box payment account service, so it requires a solid understanding of development and PCI responsibilities. It is best suited for teams with existing ASP.NET e-commerce sites, SaaS products, or WinForms applications that want to integrate multiple gateways or preserve flexibility for future processor migration.

Access from China and Alternatives

The source text does not provide information on accessibility from mainland China, so it should be considered unknown. For Chinese merchants or local payment scenarios, alternatives worth evaluating include Stripe, PayPal/Braintree, Authorize.Net, Adyen, Worldpay, or more cross-border/localized options such as Oceanpayment and PingPong Checkout.