Payment Infrastructure
Payment Infrastructure Must Support More Than Money Movement
Nov 20, 2026

On October 23, the U.S. Faster Payments Council released new guidance on non-value messaging for instant payments. The guide addresses requests for payment, requests for returns, requests for information, remittance details, and administrative messages. It also highlights differences in how the RTP Network and FedNow support these capabilities.

The publication reflects an important development in instant payment operations. As financial institutions expand their use of faster payment networks, the ability to move funds within seconds is only one part of the operational requirement. Institutions must also exchange information, respond to requests, and manage activities associated with a transaction before and after settlement.

That distinction matters because payment settlement does not necessarily complete every operational task. A business may need to request payment from a customer, while a financial institution may need additional transaction information to investigate an issue. A return request or remittance detail may also be required to support subsequent processing.

These activities rely on non-value messaging. Unlike payment messages that initiate the movement of funds, non-value messages support communication and information exchange without directly transferring money. They help institutions manage the wider transaction lifecycle, including activities that take place beyond the initial payment instruction.

The challenge is that different payment networks do not necessarily support identical messaging capabilities.

The RTP Network and FedNow have their own approaches to supporting non-value messages. Differences in supported message types and processing requirements mean that institutions cannot assume the same workflow will apply across every network.

As a result, institutions operating across multiple payment rails may need to manage different messaging processes, system integrations, and operational responsibilities. Without a coordinated approach, it can become harder for teams to understand which messages are supported, where a transaction stands, and what action is required next.

This creates a distinction between payment execution and payment lifecycle management.

A payment network facilitates the movement of funds and supports its own messaging capabilities. The institution's payment infrastructure must then coordinate the relevant instructions, transaction information, and operational workflows around those capabilities. Maintaining a consistent payment lifecycle requires more than tracking when funds settle. It also requires connecting the messages and processes associated with the transaction.

A common orchestration framework can help institutions manage these differences without requiring every payment rail to follow identical processes. Network-specific capabilities and rules can remain distinct, while payment instructions, transaction records, and exception workflows are managed within a consistent operating model.

ModernRails provides that orchestration layer. It uses a canonical payment instruction, transaction identifier, and state machine to establish a consistent structure for managing payment activity across supported settlement methods. Its policy-based routing, limits, and exception rules are explicit, testable, and versioned. Governed, timestamped events also preserve a record of transaction state changes, supporting lifecycle visibility and audit lineage.

For financial institutions, this approach provides several operational benefits:

  • A consistent transaction structure across supported payment methods, reducing the need to manage each rail as an entirely separate operational environment.
  • Clearer visibility into payment states and the progression of transaction activity.
  • Defined, testable, and versioned exception rules to support more controlled operational handling.
  • A governed record of transaction state changes, helping institutions trace payment activity and related decisions.

The Faster Payments Council's guidance highlights how much more instant payment operations involve than the transfer of funds. As institutions expand across payment networks, the ability to coordinate messaging, transaction information, and operational workflows will become increasingly important.

The completeness of a payment operation depends not only on the transfer of funds, but also on the information and processes that support the transaction throughout its lifecycle.