Home / Compare / vs AuthNet plugins
Native NMI, or an Authorize.Net plugin on the emulator?
Plenty of NMI merchants run a generic Authorize.Net plugin pointed at the emulator. It works. It also hides most of what your gateway can do.
The fair summary
If you take simple card payments and nothing else, the emulator is fine and switching buys you little. The difference appears the moment you want stored cards that behave properly, reliable subscription renewals, or a decline you can actually diagnose.
Side by side
Written to be accurate rather than flattering. Tell us if something here has changed.
| Consideration | AuthNet plugin | NMIWP |
|---|---|---|
| API | ||
| Connection | Emulated legacy API | Native NMI API |
| Response detailDiagnosing declines | Flattened to legacy codes | Full gateway response |
| New gateway features | Not exposed | Available as released |
| Stored credentials | ||
| Customer Vault | Partial through emulation | Yes |
| One click reorder | Unreliable | Yes |
| Customer managed cards | No | Yes |
| Capability | ||
| Subscription renewals | Fragile on tokens | Yes |
| Level II and Level III | No | Yes |
| 3D Secure 2 | Legacy flows only | Yes |
| Multiple merchant IDs | No | Yes |
| Operations | ||
| Partial capture and void | Yes | Yes |
| Redacted logging | Varies | Built in |
| Support | Generic plugin author | People who know NMI |
Stay where you are if
- You take one off card payments and nothing more
- You have no stored cards and no subscriptions
- Your current setup has never caused you a support problem
- You are not planning to add ACH or B2B card acceptance
Move to NMIWP if
- Saved cards or subscriptions matter to your revenue
- You are tired of declines that say nothing useful
- You want Level III, multiple MIDs or current 3D Secure
- You would rather ask a question of someone who knows the platform
Questions
The card path migrates in an afternoon. Stored cards and subscriptions are what need a plan.
Ask us directlyIs the migration risky?
The card path is straightforward. Stored cards and active subscriptions are the part that needs planning, which the migration guide covers step by step.
Can I run both plugins during a transition?
Yes, that is the recommended approach. Enable the new gateway, leave the old one installed but inactive for a week.
Will old orders still refund?
Refunds route through the gateway that took the payment. Keep the old plugin installed until historical orders are outside your refund window.
Do I need new credentials?
Yes, native ones. Ask your processor for a security key and the direct endpoint for the account you already have.
Start free, upgrade when the store needs it.
Install from WordPress.org, connect your gateway, take a real order today.