What the emulator is
NMI provides an endpoint that accepts Authorize.Net formatted requests and translates them into its own API. It exists so that merchants moving to the platform do not have to rebuild every integration. Shopping carts, billing systems and plugins written for Authorize.Net keep working, unchanged, against an NMI account.
As a migration tool it is excellent. As a permanent arrangement it costs you more than most merchants realise, because the limitations are invisible. Nothing breaks. Payments go through. You simply never see the features that were not expressible in the older API.
What you lose
The Customer Vault
This is the big one. Native vault records support one click reorder, customer managed payment methods and reliable subscription renewals. Emulated stored profiles are more limited, and the gap shows up exactly where it hurts, on renewal night.
Decline reasons worth reading
The gateway returns detailed response data. The emulator flattens it onto a smaller legacy set, so a decline that had a specific cause arrives as a generic code. That turns a two minute diagnosis into a support ticket.
Anything added since
Level III line item data, current 3D Secure flows and multiple merchant account routing have no equivalent in the legacy format. They are not disabled, they are simply not reachable through that door.
How to tell if this is you
Two signs. Your credentials are an API login ID and a transaction key rather than a security key. And your gateway portal looks nothing like the Authorize.Net interface your plugin claims to be talking to.
What switching involves
Ask your processor for native API credentials for the merchant account you already have. It is a routine request and usually answered the same day. Then install a plugin that speaks the native API, test in sandbox, and switch the gateway over.
The card path migrates in an afternoon. The part that needs planning is stored cards and active subscriptions, because tokens created through the emulator may not map to native vault records. If you have subscribers, plan the payment method update email before you change any settings. That email is the whole project.
When to leave it alone
If you take one off card payments, store nothing, and have never had a support problem, the emulator is fine. Switching buys you very little. The case for moving appears the moment stored cards, subscriptions or B2B card acceptance matter to your revenue.
Our migration guide sets out the full sequence, and support will review your plan before you touch production.