One licence, twenty five client stores.
Agencies do not want a different gateway plugin per client. They want one they know well, that configures in five minutes, and that a client can be handed without a training session.
Agency covers 25 production domains. Staging and local installs do not count.
What usually hurts
The problems merchants in this category describe, and what answers each one.
A different gateway on every build
Learning each client’s plugin is unbillable time. One plugin that covers every NMI reseller means one thing to know.
Licences scattered across client accounts
Manage all 25 from one dashboard, and move a licence when a client leaves rather than losing the slot.
Staging sites burning licence slots
Staging, local and development installs are detected and excluded, so a copied database does not consume a domain.
Handover that generates support calls
Two credential fields and a test button. Most clients never need to open the settings screen again after launch.
How to set it up
The configuration that fits this kind of store.
- Activate on the production domainStaging is free, so activate when the site goes live rather than during the build.
- Store client credentials properlyEach site gets its own API user and key. Never share one key across clients, and rotate when staff change.
- Set the checkout styling onceHosted field styling is configurable, so the card inputs inherit each client’s theme rather than looking bolted on.
- Document the handoverPoint the client at the docs and the sandbox guide. Most support questions are answered there before they reach you.
Our processor resells NMI under a different name. I pasted the gateway URL, ran a test order, and it worked on the first try.
What counts as a site?
Can I move a licence between clients?
Do clients need their own account with you?
Is there a reseller arrangement?
Related
Features that matter most here.
Start free, upgrade when the store needs it.
Install from WordPress.org, connect your gateway, take a real order today.