Authorize.Net Integration for Saleor Commerce
A production-grade Authorize.Net integration for Saleor: cards, ACH and eCheck, Apple Pay and Google Pay, customer vaulting, fraud controls, recurring billing, and auth-capture workflows. Web Shop Manager hardened Saleor's community example app into a supported integration we deploy and operate for merchants.
Saleor publishes an Authorize.Net app, but it ships as a community-supported example: a developer reference you would need to productionize, host, and maintain yourself. Web Shop Manager took that foundation and hardened it into a production-grade Authorize.Net integration, then deploys, configures, and operates it for merchants. You get a supported, operated Authorize.Net option instead of a sandbox example to finish on your own.
A WSM-hardened Authorize.Net integration, deployed and operated for you
Authorize.Net has been in operation since 1996 and is one of the most established payment gateways in North America. Web Shop Manager hardened Saleor's community Authorize.Net reference app and runs it as a production integration for merchants. Authorize.Net is one of the most widely deployed gateways across WSM's merchant base. Web Shop Manager deploys, configures, and operates this integration as part of your store.
Because we maintain and operate the integration, it is not a hosted app you inherit from a third party. It is a WSM-maintained connection between your Saleor checkout and Authorize.Net's payment gateway, running on your own Authorize.Net merchant account.
Saleor example app vs. WSM-operated Authorize.Net integration
| Saleor community example app | WSM-operated Authorize.Net integration |
|---|---|
| Developer reference starting point | Production-hardened payment workflow |
| Requires hosting, security, and maintenance | Deployed, configured, and operated by WSM |
| No official production support | Supported as part of WSM's Saleor commerce stack |
| Merchant team owns updates and troubleshooting | WSM maintains updates as Saleor and Authorize.Net APIs evolve |
| Good technical foundation | Ready for real merchant checkout operations |
What the Authorize.Net integration covers
- Credit and debit cards: Visa, Mastercard, American Express, and Discover, processed through Authorize.Net.
- ACH and eCheck: bank-direct payments for customers who prefer to pay from a checking account.
- Apple Pay and Google Pay: one-tap wallet payments at checkout on supported devices and browsers.
- Customer vault (CIM): stored payment methods so returning shoppers check out faster without re-entering card data.
- Authorize-only and auth-capture: separate authorize and capture calls, so you can hold a card at order time and capture funds only when the part ships.
- Fraud Detection Suite: Authorize.Net's built-in velocity filters, address verification, and card security code checks.
- Recurring billing: for stores running subscription or repeat-order programs.
Why Authorize.Net matters for parts and automotive merchants
Parts buyers hesitate at checkout when they are not sure the part fits. That hesitation is already part of the buying decision before they reach payment. What matters on the payment side is that the gateway is rock-solid, the checkout adds no friction, and your payment flow handles the downstream complexity of a parts order: backorders, split shipments, and the window between “we confirmed the fitment” and “the part shipped.”
The auth-capture split is where that plays out. Authorize.Net lets you authorize a card at order time (holding funds without charging) and capture only when you are ready to ship. For parts merchants managing supplier lead times or confirming fitment before charging, that distinction is real and operationally useful.
Does Saleor have a built-in Authorize.Net integration?
Saleor offers an Authorize.Net app, but it ships as a community-supported example implementation: a reference for developers that needs work to reach production, with no official support behind it. Web Shop Manager started from that foundation and hardened it. We revamped and improved the integration, run it in production across our merchant base, and maintain it. When Authorize.Net or Saleor update their APIs, we update the integration. There is no third-party vendor between you and the fix, and the team that runs your commerce stack maintains the code.
How do you add Authorize.Net to a Saleor store?
With a self-hosted Saleor build, your starting point is Saleor's Authorize.Net example app, a community-supported reference you would need to productionize, host, secure, and maintain yourself. Web Shop Manager removes that work. When you run Saleor through WSM, a WSM-hardened Authorize.Net integration is built in. We connect it to your Authorize.Net merchant account, configure your gateway credentials, set up fraud-detection rules, and handle ongoing API updates. For merchants migrating from a platform already using Authorize.Net, the merchant account carries over, so you do not need a new gateway relationship.
Is the Authorize.Net integration PCI compliant?
Authorize.Net is a PCI DSS Level 1 service provider, the highest certification tier. Web Shop Manager configures the integration to keep card processing inside Authorize.Net's secured, tokenized flow and sets up its fraud controls as part of deployment, so payment handling stays on the gateway side rather than something your team has to build and certify. We handle the Saleor side and keep it current as Authorize.Net and Saleor update their APIs.
Operated for you
As with every integration we operate, you do not stand this up or maintain it yourself. We deploy it, configure it for your store, connect it to your Authorize.Net merchant account, keep it current, and support it as part of running your commerce on an open headless Saleor core. Web Shop Manager is also an Authorize.Net partner. The Partners section explains WSM's payment ecosystem relationships; this page focuses on how WSM operates Authorize.Net inside production Saleor commerce.
Related resources
Frequently asked questions
Practical questions about Authorize.Net Integration for Saleor Commerce.
It is ours to support, built on Saleor's example app. Saleor publishes an Authorize.Net app as a community-supported example, and Web Shop Manager hardened and improved it into a production-grade integration. WSM deploys, runs, and maintains it for production Saleor merchants. Authorize.Net is one of the most widely deployed gateways across WSM's merchant base.
Saleor's Authorize.Net app is a community-supported developer example. It gives technical teams a starting point, but it still needs to be productionized, hosted, secured, monitored, maintained, and updated. WSM hardens that foundation into a production-operated integration, connects it to the merchant's Authorize.Net account, configures gateway and fraud settings, and maintains it as Saleor and Authorize.Net APIs evolve.
Cards (Visa, Mastercard, American Express, Discover), ACH and eCheck for bank-direct payments, Apple Pay and Google Pay wallets, and customer-vaulted saved cards for returning shoppers. Fraud detection, recurring billing, and separate auth-capture calls are all part of the same integration.
Yes, but only as a community-supported example app, a developer reference that is not production-ready or officially supported. Saleor's production-grade payment app is Stripe. Web Shop Manager took the Authorize.Net example and hardened it into a supported integration we operate in production across our merchant base.
Authorize.Net supports separate authorize and capture calls. You authorize a card at order time, holding the funds without charging, and capture only when the part ships or is confirmed in stock. For parts merchants managing backorders, fitment checks, or supplier lead times, that window between order and ship is where auth-capture earns its keep.
Yes, in many cases. Merchants already using Authorize.Net can often keep their existing Authorize.Net merchant account when moving to WSM's Saleor environment. WSM connects the Saleor checkout to the merchant's Authorize.Net account and configures the payment workflows around the store's operational needs.
Authorize.Net is a PCI DSS Level 1 service provider. WSM configures the Saleor integration so sensitive payment data is routed through Authorize.Net's secured, tokenized payment flow rather than being stored on the merchant storefront. WSM also configures supported fraud controls and keeps the Saleor-side integration current as Authorize.Net and Saleor update their APIs.
No. Web Shop Manager deploys, configures, maintains, and supports the Authorize.Net integration as part of operating your commerce on Saleor.
See it running on Saleor
Web Shop Manager builds, deploys, and operates this integration on a real, open, headless Saleor commerce core.