Agencies / Multisite Networks
Multisite-Compatible Network Payment Gateway
A payment gateway engineered for WordPress Multisite (WPMU), centralising billing across hundreds of sub-sites instead of configuring payments per site.
Project Overview
Industry
Agencies / Multisite Networks
Solution
Multisite-Compatible Network Payment Gateway
Services
Technologies
The Challenge
Where This Started.
Before
- Gateway configured individually, site by site
- Billing reconciled per sub-site across hundreds of sites
- One misconfigured sub-site easy to miss until a transaction failed
After
- Gateway configuration centralized at the network level
- One centralized billing dashboard for the whole network
- Consistent checkout behavior across every sub-site
Business Impact
Why It Mattered
At network scale, per-site payment configuration isn't just tedious — it's an operational risk. A misconfigured gateway on one sub-site among hundreds is easy to miss until a transaction fails.
Engineering Approach
How We Approached It
Engineered a gateway plugin at the network level rather than the site level, so payment configuration and billing data are centralized once and inherited across every sub-site instead of duplicated hundreds of times.
Architecture
How It's Wired Together.
A network-activated plugin stores gateway credentials and billing configuration in network-wide options, with each sub-site's checkout resolving against the shared network configuration rather than its own local copy.
Implementation
What We Built
Built the plugin against WPMU's network-activation and network-options APIs, added a centralized billing dashboard visible at the network admin level, and validated checkout behavior across a representative sample of sub-sites.
Technical Highlights
What Made This Work.
-
Network-wide gateway configuration instead of per-site setup
-
Centralized billing dashboard for the whole multisite network
-
Consistent checkout behavior across every sub-site
Results
The Outcome.
Payment gateway configuration and billing reconciliation moved from a per-site task repeated hundreds of times to a single network-level setup.
Lessons Learned
What This Taught Us
Most WooCommerce payment plugins are built with the assumption of one site, one store — multisite agencies need that assumption engineered out from the start, not patched in after hundreds of sub-sites already exist.
Facing a Similar Challenge?
Let's talk about what your store or system actually needs — no template pitch, just an engineering conversation.