NMI Payment Gateway: Pricing, Setup and Support
The NMI Payment Gateway connects a business’s checkout, software or payment device to supported payment processors. It can support online and in-person payments, a virtual terminal and optional services such as stored payment methods and recurring billing. Available features depend on the account, processor connection and integration.
Swipesum helps businesses select, configure and support NMI-based payment setups as part of the wider payment stack. For an existing setup, call (844) 356-9905 or email support@swipesum.com. Swipesum is an independent payments provider and support team; account changes require the appropriate provider relationship and authorization.
NMI gateway versus payment processing
A gateway handles payment information and communication with the connected payment infrastructure. The processing and acquiring arrangement determines matters such as underwriting, merchant-account terms and funding. A gateway transaction result is not the same as a bank deposit.
NMI also offers NMI Payments, so “NMI is never a payment processor” is too broad. Identify which services your proposal actually includes. If you already have a merchant account, check whether its processing connection is supported and what configuration information is required. Gateway compatibility alone does not approve a merchant account or guarantee funding terms. See the NMI payment gateway FAQ.
NMI pricing and gateway fees
There is no single retail NMI price that applies to every merchant. A provider or reseller sets the merchant’s gateway offer, and a bundled quote may combine several services. Separate gateway charges from card-processing fees before comparing proposals.
Ask for a written schedule covering:
- Setup or activation, monthly gateway charges and account minimums.
- What counts as a billable gateway event: a sale, authorization, capture, refund, void or other request may be treated differently.
- Customer Vault, recurring billing, fraud tools, account updating, accounting extensions and other optional services.
- Processor fees, interchange, network assessments, provider markup and conditional account charges.
- Integration, support, cancellation and migration costs.
NMI’s merchant gateway onboarding documentation describes partner-configured merchant fees. Do not treat one reseller’s monthly or per-event price as NMI’s universal rate.
For a hypothetical gateway quote of $20 monthly plus 10 cents per billable event, 1,000 events would cost $120 for the month: $20 + (1,000 × $0.10). That excludes payment processing and optional services. If the agreement bills multiple events for a payment, the event count can exceed the number of successful sales. Use the written definitions and your actual workflow.
Swipesum can review the complete setup and fee schedule alongside your statements. Request a new NMI setup or pricing review at (844) 312-0589 or save@swipesum.com. The comparison should establish fit and total cost; a lower price is not guaranteed.
Features to verify for your account
Virtual terminal and reporting. Confirm which staff can enter payments, issue refunds, view transactions and change settings. Give each user the permissions needed for their role. NMI’s merchant user account guide distinguishes transaction, reporting, vault and administrative permissions.
Customer Vault. This service stores payment details through NMI-issued tokens so an application can reference a saved payment method instead of retaining the underlying card data. A saved vault record and a recurring billing schedule are different things. Confirm the enabled service, consent workflow and how your application references customers. See NMI Customer Vault documentation.
Recurring payments. Determine whether NMI or your billing software owns the schedule. Test renewals, failures, cancellations, refunds and customer notifications. Avoid configuring two systems to charge the same subscription. Confirm which update or retry services are enabled rather than assuming a stored card guarantees successful collection.
Fraud controls. NMI offers configurable fraud tools, but configuration, review and monitoring still matter. Test rules against legitimate customer behavior and assign someone to review flagged activity. Fraud tools do not guarantee that a transaction will avoid a dispute. Review the NMI Fraud Prevention guide.
Payment methods and devices. Verify cards, ACH, wallets and in-person devices against the specific connector and account. A gateway supporting a capability does not mean every shopping-cart plug-in exposes it. Chargebee’s NMI documentation, for example, describes that particular integration’s capabilities and limitations.
How to set up an NMI payment gateway
- Map the payment workflow. List online, in-person, invoicing and recurring needs. Identify the software, accounting system, device models and payment methods.
- Confirm the commercial arrangement. Establish the gateway provider, processor or acquiring arrangement, pricing, underwriting requirements and support owner.
- Configure the supported connection. Have the provider validate merchant-account details and any processor configuration document, often called a VAR sheet. A sandbox account is not approval for live payments.
- Choose the integration path. An existing supported connector may meet the requirement. A hosted checkout or custom integration may be appropriate when it does not. Verify the exact software version and supported functions.
- Set permissions and security. Restrict administrative access and use the authentication method documented for your integration. Keep private API credentials on the server and out of browser code, shared documents and support emails.
- Test before launch. Check approvals, declines, duplicate submissions, authorization and capture where relevant, voids, refunds, saved payment methods and subscription events.
- Verify the money flow. Match payment records to the application, settlement reports and the bank deposit. Confirm funding timing and deductions with the processing provider.
Swipesum can coordinate gateway, processor and software requirements through its payment gateway and implementation services. Agree on the acceptance checklist and escalation responsibilities before cutover.
Swipesum NMI setup walkthrough
This recorded walkthrough shows an earlier gateway interface. Interface labels, available services and commercial terms can change; use the current documentation and your written agreement alongside the video.
Integrating NMI into software
NMI’s current developer guide recommends its Payment Component with the NMI REST API for a new custom online checkout. The component tokenizes payment details; the backend processes the token. Hosted checkout and other integration paths are also available. Follow the current quick-start documentation and Payment Component guide for the chosen environment.
Existing integrations may use different interfaces. Assess support status, required features and migration testing before replacing one. Keep sandbox and production credentials and endpoints separate, and verify production configuration before the first live payment.
For a software platform serving merchants, also define onboarding, account ownership, reporting access, support responsibilities and payment-data migration terms. The integrated payments selection guide covers that broader platform decision.
QuickBooks integration after SyncPay
QuickBooks SyncPay is no longer a supported recommendation. NMI states that support ended March 31, 2026 and recommends Bill Connect as the supported gateway extension. See NMI’s SyncPay end-of-life notice.
NMI documents Bill Connect by Biller Genie for QuickBooks Desktop, QuickBooks Online and Xero. Availability and activation depend on the merchant’s offered services, and Customer Vault is required. Confirm the accounting version, required workflow and complete fee schedule.
For card-present payments, NMI says gateway-initiated transactions sync as Sales Receipts, rather than automatically paying a specific open invoice. A business expecting terminal payments to close individual invoices should validate the matching process before deployment. See Bill Connect documentation and card-present limitations.
Security and payment data portability
Tokenization and hosted payment collection can reduce exposure to sensitive payment data. They do not remove every merchant PCI DSS obligation. Confirm applicable validation requirements with your provider and security team, including your website, staff access and any devices involved.
Gateway tokens are not automatically portable to every other provider. Before changing gateways or processors, confirm ownership, export permissions, supported destination, secure transfer process, cost and timing. A multi-processor gateway configuration is different from transferring stored credentials between unrelated vaults.
A higher-risk business still needs a suitable approved processing relationship. Multiple merchant IDs and routing tools are not a workaround for underwriting conditions or dispute obligations. Agree on permitted use and monitoring before enabling routing.
How Swipesum supports payment implementation
A gateway launch needs an owner for the wider payment operation. In one published 56-location retail payment migration, Swipesum coordinated merchant accounts, hardware and store implementation, then continued statement review and fee escalation after launch. For an NMI project, define the same responsibilities: configuration, software testing, reconciliation and provider escalation. The team should remain accountable after the first successful transaction.
NMI login and Swipesum support
Use the official NMI merchant login or the branded portal supplied by your account provider. Check that you are using the correct gateway account and authorized user. Login recovery and changes to the primary user can require the existing merchant services provider.
Start with Swipesum when you need help identifying the issue, reviewing fees, checking gateway and software behavior or coordinating the provider escalation. Call (844) 356-9905 or email support@swipesum.com.
Prepare the gateway or merchant ID, affected transaction IDs, timestamps, exact error text, software version and the steps that produced the problem. For a missing deposit, include the batch reference and expected funding date. Share redacted examples through the agreed support channel; do not email full card numbers, card security codes, passwords or private API keys. Account-specific changes depend on access and authorization.
NMI gateway questions
Is an NMI gateway fee the full cost of accepting cards?
No. Gateway charges are one part of the arrangement. Card processing, network costs, optional services and account charges may be separate or bundled. Compare the full written offer.
Can I keep my processor when using NMI?
Possibly. Confirm that the processor connection, merchant-account configuration and required software features are supported.
Does NMI work with QuickBooks?
NMI now recommends Bill Connect rather than the retired SyncPay product. Validate your accounting edition, activation requirements and how invoice payments differ from card-present Sales Receipt synchronization.
Can Swipesum help with NMI support?
Yes. Contact Swipesum at (844) 356-9905 or support@swipesum.com for gateway, integration and payment-operations assistance. Account changes depend on the provider relationship and your authorization.
