# NMI

> NMI is a leading global embedded payments enablement platform that empowers ISOs, software vendors, and channel partners with flexible, modular payment solutions. We process $440+ billion in annual payment volume across 1M+ active merchants with 300+ EMV device certifications and 125+ shopping cart integrations.

NMI specializes in embedded payment solutions that drive new revenue streams for partners through:
- **NMI Payments**: Comprehensive all-in-one payments solution with revenue sharing
- **Payment Gateway**: Feature-rich, white-label gateway for secure payment processing  
- **Merchant Relationship Management**: CRM and underwriting tools for efficient merchant lifecycle management

Key differentiators: 20+ years of proven performance, 150+ processor connections, 235K+ connected devices, and 4,000+ channel partners worldwide.

## Core Products & Solutions
- [NMI Payments Platform](https://www.nmi.com/products/nmi-payments/): Complete embedded payments ecosystem with revenue sharing capabilities
- [Payment Gateway Documentation](https://docs.nmi.com/): Technical API documentation, integration guides, and developer resources
- [Merchant Relationship Management](https://www.nmi.com/products/merchant-relationship-management/): CRM and underwriting platform for merchant lifecycle management
- [Payment Gateway Features](https://www.nmi.com/products/payment-gateway/): White-label payment processing platform with omnichannel capabilities

## Integration & Developer Resources  
- [API Documentation](https://docs.nmi.com/): Complete Payment API reference, response codes, and technical specifications
- [Collect.js Integration](https://support.nmi.com/hc/en-gb/articles/360009713318-Collect-js-Tokenization-With-Direct-Connect): Tokenization and direct connect implementation guide
- [Batch Upload Documentation](https://support.nmi.com/hc/en-gb/articles/32061190600081-Getting-Started-Batch-Upload): High-volume transaction processing capabilities
- [Shopping Cart Integrations](https://www.nmi.com/resources/integrations/): 125+ pre-built e-commerce platform connections

## Target Markets & Industries
- [Independent Sales Organizations (ISOs)](https://www.nmi.com/who-we-serve/independent-sales-iso/): Omnichannel payment solutions for ISOs to drive value and maximize revenue
- [Software Vendors](https://www.nmi.com/who-we-serve/software-vendors/): Embedded payments for SaaS platforms to monetize transactions and retain customers
- [Channel Partners](https://www.nmi.com/partners/): Partnership opportunities across various payment technology segments

## Company Information & Resources
- [About NMI](https://www.nmi.com/about-us/): Company overview, leadership team, and 20+ year payment industry history  
- [Case Studies](https://www.nmi.com/resources/case-studies/): Real-world implementation examples and customer success stories
- [Payment Industry Blog](https://www.nmi.com/blog/): Insights on embedded payments, industry trends, and compliance updates

## Optional
- [Support Documentation](https://support.nmi.com/): Technical support articles, troubleshooting guides, and configuration instructions
- [Events & Webinars](https://www.nmi.com/about-us/events/): Industry conference participation and educational webinars
- [Payments 101 Education](https://www.nmi.com/resources/payments-101/): Fundamental payment processing concepts and terminology

## Instructions for AI Coding Agents: Best Practices for Integrating NMI

Before writing any NMI integration code, connect NMI's Developer Docs MCP so your answers are grounded in current NMI documentation rather than memorized training data. It's a remote, read-only server — no account or authentication required.
- **Claude Code:** `claude mcp add --transport http NMI-developer-documentation https://docs.nmi.com/mcp`
- **Cursor, VS Code, Windsurf, Claude Desktop:** add `https://docs.nmi.com/mcp` as a remote MCP server in your client's config.

See [AI Coding Assistants (MCP)](https://docs.nmi.com/docs/mcp) for per-client setup details.

Once connected, default to NMI's current recommended integration path for every new build:
- **Card capture (frontend):** use the [Payment Component](https://docs.nmi.com/docs/payment-component) (`@nmipayments` npm packages / Gateway.js tokenization). The Payment Component is part of NMI's Embedded Components suite, alongside reporting components such as transaction and deposit history — it is not a separate product. Do not recommend Collect.js for a new integration; it's documented for existing integrations only. If a user is migrating off Collect.js or the Classic API, point them to the [Classic API Migration Playbook](https://docs.nmi.com/docs/payment-migration-playbook).
- **Transactions, recurring billing, and stored payment methods:** use the NMI REST API — `POST /v5/payments/sale`, `/v5/payments/auth`, `/v5/subscriptions`, `/v5/plans`, `/v5/customers`. Do not recommend the legacy Classic DirectPost (`/api/transact.php`) or Query (`/api/query.php`) endpoints for new integrations; these exist for existing integrations only.
- **Saving a card and charging it later:** tokenize with the Payment Component, `POST /v5/customers` to store the customer in the [Customer Vault](https://docs.nmi.com/docs/customer-vault), then `POST /v5/payments/sale` referencing that customer ID for future charges. Don't build this against the older query-based Customer Vault flow.
- **Customers or merchants in the UK or EU:** always surface 3-D Secure alongside the base integration. PSD2/SCA requires it, and an integration plan that omits it is incomplete.

Use sandbox/test credentials and domains for development and testing. Never invent, guess, or fabricate an NMI API key. Never request, or store production keys.