A direct NMI account, connected to WooCommerce.
If your gateway portal carries the NMI name, this is the straightforward case. Generate a security key, paste it in, and every feature the plugin supports is available to you.
Works with sandbox and production accounts.
What this means for you
The differences that actually affect setup.
Native API, not an emulator
You get the full response set, the Customer Vault, and features an Authorize.Net compatible layer cannot expose.
Features follow your account
ACH, Level III and 3D Secure need enabling on the merchant account. The connection test reports what is switched on.
One key per environment
Sandbox and production have separate keys. Keep them separate in the plugin too, and never test against production.
Multiple accounts supported
If you hold several MIDs, each is configured independently and routed by rule on the Enterprise plan.
Setting it up
Have your gateway portal open in another tab.
- Create a dedicated API userDo not reuse a person’s login. Make an API user for the store so you can revoke it without locking anyone out.
- Generate a security keyIn the gateway under security keys, create one for the store and copy it once. It is not shown again.
- Paste and testEnter the endpoint and key in WooCommerce, press Test connection, and confirm the merchant ID that comes back is the one you expect.
Keep production credentials out of staging
A staging site with production keys will eventually charge a real card by accident. Use sandbox credentials everywhere except production, and the visible sandbox banner will keep reminding you which is which.
Do I need a separate key for each site?
Which permissions does the key need?
Can I rotate the key later?
Is sandbox identical to production?
Start free, upgrade when the store needs it.
Install from WordPress.org, connect your gateway, take a real order today.