MIDs and gateways
Configure NMI, Authorize.net, Stripe, and the built-in Dry Run MID.
Updated July 17, 2026On this page
- Gateway credentials for NMI, Authorize.net, or Stripe when adding a live MID
- An understanding of whether the credentials are sandbox or live
In Recurrify, a MID is a gateway connection. MID pools and routers decide which connection handles a transaction; checkout pages never assign a gateway directly.
Add a gateway MID
Choose the provider and environment
Open MIDs and choose Add MID. Select NMI, Authorize.net, or Stripe, then choose Sandbox or Live. Provider-specific credential fields appear in the same modal.
Save encrypted credentials
Give the connection a clear operational name, enter its credentials, and save. Recurrify stores an encrypted credential payload and only returns configuration status to the portal.
Confirm health and 3D Secure capability
The MID list shows health, environment, configured state, and provider 3D Secure support. Stripe and NMI can initiate supported 3D Secure flows; Authorize.net does not initiate challenges through this integration.
Provider reference
| Provider | Required credentials | 3D Secure |
|---|---|---|
| Dry Run | None | Not applicable |
| NMI | Security key and tokenization key | Supported when configured by the provider |
| Authorize.net | API login ID and transaction key | Does not initiate challenges |
| Stripe | Secret key and publishable key | Supported |
Dry Run behaves as a system MID inside pools and routers, but payment outcomes are simulated from the checkout's enabled test cards.