Setting Up a Payment Processor

Direct Ordering works with the NMI payment gateway (formerly Network Merchants) to connect with a range of payment processors. This article lists the supported processors and explains how payment processing credentials are configured.

The following payment processors support the features most clients require and are available options:

• TSYS
• Elavon viaConex
• EPX (North American Bancard, or NAB)
• First Data
• Worldpay (FIS), with SMB and enterprise options
• Chase Paymentech
• Global Payments

During onboarding, the restaurant completes a questionnaire describing its payment processing preferences, and the Direct Ordering team uses it to recommend an approach based on best practices. A restaurant can continue using its existing processor across channels or choose a different one, as long as NMI supports it. While a POS company can act as a payment processor by building processing into its POS system, Direct Ordering cannot support a POS company acting as the merchant processor.

Levels of Configuration

Payment processing credentials can be configured at three levels. The first two are required:

• Brand level (required)
• Store level (required)
• Revenue center level (optional)

A restaurant can establish merchant credentials at the revenue center level. Doing so offers advantages such as more granular reporting and analytics, risk mitigation, and scalability. When all revenue centers use the same processor, it is easier to integrate payment data with other systems such as inventory management, accounting, and CRM software, and reporting stays consistent. The choice of merchant processor rests with the restaurant operator, provided Direct Ordering can support it.