NMI Resolves Payment Settlement Delays That Could Have Affected Merchant Funding

Payments technology provider NMI said batch settlement processing was operating normally again on Saturday, October 17, after a delay that had raised the possibility of slower merchant funding. Its Gateway Services status page marked the issue resolved at 4:58 a.m. Central Daylight Time, with engineers confirming that payment batches were settling as expected.

An update at 2:54 a.m. CDT said the company had identified the cause of the delay and was working to fix it. NMI warned at that point that some customers might continue to experience delays in settlement and associated funding. The warning described a potential consequence for merchants, not a confirmed count of late deposits.

The incident was listed as affecting the Credit Card Processing component. NMI did not disclose how many merchants were affected, the value of any delayed batches or which processing partners were involved. Its October 17 incident report also gives no time for the initial onset, so the interval between the two published updates should not be treated as the full duration of the problem.

A settlement delay does not necessarily stop checkout

For merchants, card approval and payment settlement are different stages. An approval at a checkout tells the business that the issuer has authorized a payment; it does not mean the proceeds have already been deposited in the merchant’s bank account. After eligible payments are captured, their details move through clearing and settlement before funds reach the acquiring side and, ultimately, the merchant.

This distinction matters when interpreting NMI’s notice. The company identified a problem with batch settlement, but did not report that all card authorizations had failed or that every merchant had lost the ability to accept payments. A business could therefore see approved sales on its records and still be waiting for the corresponding batch to complete processing. Whether that occurred for any particular merchant cannot be determined from the public notice alone.

NMI uses different settlement arrangements depending on the processor. Under terminal capture, its gateway stores eligible card activity and sends it for settlement in a batch based on the merchant’s configured cut-off time. NMI’s support guidance says batch files normally enter a queue and can appear as settled hours after the cut-off. An unsettled status immediately after a merchant closes for the day is not, on its own, proof of an incident.

Host capture works differently. The processor or acquirer stores and handles the settlement batch, and NMI says it has less visibility once the relevant information has left the gateway. Merchants using host-capture processors also cannot change their settlement time through the gateway’s settlement-schedule setting. Those differences mean the timing and information available to merchants can vary even when a status notice concerns a common processing function.

The cut-off time is another potential source of confusion. It determines which payments fall into a particular batch, rather than guaranteeing that money will arrive in a bank account at that hour. Activity after the cut-off generally moves into the next batch. NMI cautions that delivery of a closed batch to the processor depends on processing queues and operating conditions, which are separate from the merchant’s chosen cut-off.

Even after a batch moves through the gateway successfully, funding may depend on the acquirer, card network, issuing bank and the merchant’s account arrangements. In its explanation of card processing, NMI says clearing and funding often take two to three business days, although some providers offer faster access. The October 17 resolution notice therefore establishes that normal batch processing resumed; it does not certify that every potentially delayed bank deposit had already arrived.

How merchants can check for outstanding batches

NMI provides a settlement-batch view in its Merchant Portal for users with the required reporting permissions. Its Transaction Reports guidance explains that merchants can open Transaction Snapshot, group results by Settlement Batch and choose a date range. The report groups sales and captured authorizations by the processor’s settlement cut-off, allowing businesses to review batches rather than relying only on a total sales figure.

The same guidance explains that the report may show a “Not Settled” row for payments taken during the current day, or for earlier activity that missed a previous cut-off. That label can reflect normal timing. It should be assessed against the merchant’s configured schedule, the processor in use and the dates of the underlying card payments before being treated as evidence of a lingering problem.

A merchant working with more than one card processor may see separate batches for each processor on the same day. NMI says users can inspect the individual payments within a reported batch and use processor-specific filters in their reporting. For a funding question, that level of detail is more useful than assuming every payment accepted on October 17 was affected by the same delay.

Individual payment statuses help narrow the check. NMI distinguishes approved payments awaiting settlement from those marked complete, and its reporting tools also identify failed items. These categories describe the payment’s recorded processing state within the gateway. They are not a substitute for checking whether the processor has sent the expected proceeds to the merchant’s bank account.

NMI also documents a separate process for failed settlement batches. Its help materials say the gateway may attempt to correct some failures automatically, while other failures require the merchant to contact the processor before resubmitting a batch. The October 17 notice described delays, not a blanket failure of every affected batch. It did not instruct all merchants to resubmit payments, and a general resettlement procedure should not be read as such an instruction.

For merchants whose expected funding has not appeared, the useful distinction is between a payment still awaiting batch settlement and a batch already recorded as settled but awaiting downstream funding. The public status page addresses the first part of that process. Account-level reporting and the merchant’s processor or acquirer are needed to clarify the second, especially where a normal funding timetable has already passed.

Earlier October notices involved specific processors

The October 17 notice followed other settlement disruptions recorded on the same NMI status service. On October 15, NMI investigated delays involving Worldpay APACS and AIB APACS, warning that affected merchants could receive their funding later than expected. That incident was first posted at 2:13 a.m. CDT. NMI reported that it was monitoring the fix at 8:19 a.m. and marked the incident resolved at 8:30 a.m.

Another incident, on October 8, concerned settlement processing for First Data Merchant Solutions (Rapid Connect). The company warned at 4:30 a.m. CDT that some merchants might experience funding delays, then reported a resolution at 9:01 a.m. The notices for October 8 and October 15 named particular processor arrangements. By contrast, the October 17 incident report identified Credit Card Processing as the affected component without naming a processor.

Those earlier entries provide context for the type of issue NMI has been reporting, but they do not establish a common technical cause or show that the same merchants were affected multiple times. NMI did not publicly connect the October 17 event to either earlier incident in the notices reviewed. The company also did not publish a merchant count, delayed-payment total or estimated financial impact for the latest event.

The Gateway Services dashboard displayed its listed systems as operational following the October 17 resolution, including Credit Card Processing and other gateway functions. That is a current service-status statement, not a record of every individual funding outcome. NMI’s published confirmation is limited to settlement batches processing as expected again, leaving merchant-specific deposit timing to be checked through the relevant account and payment processor.