NMI for Magento Setup Guide How to Buy Configure and Test Before Launch

Introduction

Table of Contents

Introduction
1. Verify NMI fit before add-to-cart
2. License, pricing, and guarantees
3. Purchase and download workflow
4. Install on staging first
5. Configure sandbox credentials
6. Sandbox test matrix
7. Go-live procedure
8. Post-launch maintenance
Red flags before purchase
FAQ
Related reading

Network Merchants merchants often arrive at checkout integration with API keys in hand and a launch date already printed on a project plan. The gap is usually Magento-specific: store scope, payment method visibility, capture timing, and refund behavior in admin.

This is the transactional companion to why buy NMI Gateway for Magento—a pre-purchase and setup checklist before you click Buy Now on the PatSaTECH product page.

1. Verify NMI fit before add-to-cart

Check	Action
Processor	Merchant agreement says Network Merchants Inc. (not a different gateway product)
Integration	Collect.js / Payment API features enabled on MID
Magento version	2.4.x, verified against 2.4.7 support note on product page
SSL	Valid certificate on checkout hostname
Workflow	Auth+capture vs sale; partial shipments; refund policy

Unclear processor naming? Read PymtPro vs NMI for Magento or ask PatSaTECH before payment.

Product URL: Network Merchants Inc. Gateway for Magento

2. License, pricing, and guarantees

From the listing:

Pricing from $241/year
Single site license options (verify multi-site needs on product page)
Support and updates for 1 or 5 years
Satisfaction guarantee if the extension cannot meet documented requirements
Support guarantee for installation and troubleshooting assistance

Document who owns the license (client vs agency) so renewals do not lapse silently.

3. Purchase and download workflow

Select license and support term on the product page.
Complete checkout on patsatech.com (confirm domain authenticity).
Store invoice, license key (if applicable), and download package securely.
Optional: add plugin installation support for scoped setup on staging or production.

4. Install on staging first

Do not experiment with payment methods on production during business hours.

Clone staging with matching Magento minor version.
Install extension via Composer or upload per PatSaTECH documentation in the package.
Enable module, flush caches, verify payment method registration.
Confirm website / store / currency scope in Magento admin.

If checkout uses a ** heavily customized theme**, verify Collect.js loads without CSP or minification stripping required scripts.

5. Configure sandbox credentials

In Magento payment settings:

Set mode to sandbox.
Enter NMI sandbox credentials from your processor portal.
Set custom title shoppers will see.
Enable logging during setup.
Configure payment action (authorize vs capture) to match operations.
Require CVV (extension default aligns with processor best practice).
Enable 3-D Secure 2 only after baseline sandbox passes—then retest.

6. Sandbox test matrix

Scenario	Expected outcome
Approved card	Order processing / correct state; gateway transaction ID stored
Declined card	Graceful error; no false “paid” state
Insufficient funds	Same as decline—CS script documented
Auth + delayed capture	Capture from admin succeeds; totals reconcile
Partial refund	Credit memo matches gateway partial amount
Full refund	Order and gateway both closed consistently
3DS challenge (if on)	Mobile + desktop completion
Abandoned 3DS	Manual reconciliation procedure documented

Cross-check with how to test your payment gateway like a pro.

7. Go-live procedure

Maintenance window communicated to stakeholders.
Swap sandbox → live credentials; double-check no staging URLs in NMI portal callbacks if used.
One small live transaction with finance watching settlement.
Disable verbose logging in production.
Monitor auth failures and capture errors for 48 hours.
Train CS on refund steps in Magento admin vs NMI virtual terminal.

8. Post-launch maintenance

Renew support/updates on schedule.
Read changelog when upgrading Magento minor versions.
After Adobe security patches, smoke-test checkout even if “nothing changed in payments.”
Link internally to Magento hub for sibling products across brands.

Red flags before purchase

Magento below supported 2.4.x line with no upgrade budget.
Headless checkout without scoping JS integration—consider custom integration.
Processor portal shows different API product than NMI Payment API.
No staging environment and no rollback plan.