Oct 1st, 2026

Instant Payments Have a Send Problem. Does FedNow Solve It?

TL;DR

FedNow is growing fast, but the Federal Reserve is now offering 2027 discounts specifically designed to encourage more financial institutions to turn on sending. That raises a fair question: is FedNow solving an instant-payments problem, or entering a market where Visa Direct, Mastercard Move, and The Clearing House RTP network already move money quickly? The answer depends on the use case. Push-to-card products already solve many payout experiences extremely well, while FedNow offers a different bank-to-bank model with 24/7 settlement, ISO 20022 messaging, and support for higher-value transfers. The opportunity isn't to declare one rail the winner. It's to understand which rail actually solves the customer's problem, then build the fraud controls, reconciliation, support, and routing logic around it.

A payment can be instant and still be the wrong payment product.

That is the part of the U.S. instant-payments conversation that gets lost when every new rail, network feature, and payout product is described with some version of the same promise: money moves faster.

The Federal Reserve recently gave us a useful reason to revisit that assumption. Beginning January 1, 2027, Federal Reserve Financial Services is introducing a FedNow discount program aimed at encouraging more financial institutions to enable and scale both receiving and sending. The sender side is especially interesting. The Fed says industry feedback showed that more support for send enablement could accelerate adoption.

In other words, after three years of FedNow growth, getting institutions comfortable receiving instant payments is not the whole challenge. They need to be comfortable sending them too.

And that raises a question payments people should be willing to ask:

Is FedNow solving a problem that does not exist?

After all, Visa Direct has been pushing funds to eligible cards and accounts for years. Mastercard Move supports money movement to cards, accounts, wallets, and other endpoints. The Clearing House RTP network already processes substantial U.S. bank-to-bank instant-payment volume.

The U.S. was not sitting around waiting for someone to invent fast money.

So the real question is not whether FedNow is faster than yesterday's ACH file. It is where FedNow fits in a market that already has multiple ways to make money arrive quickly.

"Instant" is not a use case

This is where the conversation gets cleaner.

A gig worker asking for today's earnings now is not necessarily solving the same problem as a corporate treasury team moving $2 million between accounts on a Saturday night.

Neither is an insurance payout, marketplace seller disbursement, wallet withdrawal, loan funding, supplier payment, P2P transfer, or emergency government payment.

They can all benefit from speed. That does not mean they all need the same rail.

Visa Direct for Card, for example, uses VisaNet and card credentials to support push payments to eligible accounts linked to debit or prepaid cards. Visa also offers account and wallet capabilities that can route payouts across account and faster-payment networks. Mastercard Move similarly spans multiple payment types and endpoints, including cards, bank accounts, wallets, and cash-out locations. Those products can be especially compelling when the experience is fundamentally about getting funds to a recipient quickly using an endpoint the recipient already has.

FedNow is different. It is domestic U.S. instant-payment infrastructure for participating banks and credit unions, moving account-to-account credit transfers with settlement through the Federal Reserve. It operates 24/7 and uses ISO 20022 messaging. Its customer credit transfer network limit is currently up to $10 million, although individual institutions can set lower limits.

And FedNow is not the only bank-to-bank instant rail. The Clearing House RTP network has been live since 2017 and, according to The Clearing House, processed more than 371 million transactions through August 2026.

That is why "which instant-payment product is best?" is usually the wrong question.

The better question is: What payment are you actually trying to make?

Visa Direct and Mastercard Move already solved a lot of the visible problem

If the customer problem is, "I need this person to get paid now," card-network money movement products are hard to ignore.

Cards are already familiar endpoints. Consumers already carry them. Platforms already understand card credentials. The networks have spent years building reach, connectivity, fraud capabilities, APIs, and payout use cases around them.

A marketplace can use a fast payout as a seller-retention feature. A gig platform can offer workers quicker access to earnings. An insurer can reduce the frustration of waiting for a claim check. A gaming or investment platform can let customers access funds without waiting through a traditional bank-transfer cycle.

From the end user's perspective, that can look a lot like the instant-payments problem has already been solved.

Tap a button. Money shows up.

That is a very high bar for FedNow to compete against if we frame the competition only around consumer-visible speed.

But that framing misses what FedNow is actually adding.

FedNow is more interesting when the bank account is the product

FedNow starts making more sense when the destination is not "whatever gets money there fastest," but the bank account itself.

Think corporate treasury, supplier payments, payroll funding, account-to-account transfers, loan disbursements, real estate-related funding, or other higher-value domestic flows where immediate clearing and settlement, structured data, and direct bank-account movement matter.

The Federal Reserve increased FedNow's network transaction limit to $10 million in November 2025 specifically to support more high-value use cases. Federal Reserve Financial Services has pointed to corporate treasury, payroll, vendor payments, and real estate transactions as examples.

That is not the same problem as pushing $180 of gig earnings to a debit card.

It is still instant payments. It is just a different job.

This distinction matters for ISVs because payments teams have a habit of starting with a rail name.

"We need FedNow."

"We need push to card."

"We need RTP."

Maybe. But first answer the boring questions:

  • Where does the recipient expect the money to land?
  • Is this domestic or cross-border?
  • What is the typical and maximum transaction size?
  • Does immediate settlement matter, or only immediate availability to the recipient?
  • What data needs to travel with the payment?
  • What happens if the recipient cannot receive on the preferred rail?
  • How much does the payment cost at the volumes you expect?
  • Who owns fraud losses, customer errors, exceptions, and support?

Once you answer those, the rail decision gets a lot less ideological.

The Fed's send discount tells us where the hard part is

The most revealing part of the new FedNow discount program is that it separates receive and send incentives.

For 2027, eligible institutions can receive statement credits for enabling FedNow receive capabilities and participating in specified supporting services. The send discount can be significantly larger and requires institutions to enable sending and meet volume thresholds.

That makes sense operationally.

Receiving an instant payment is one thing. Sending one is where risk gets uncomfortable.

When an institution lets a customer originate a payment that can settle in seconds, the fraud decision needs to happen before the money leaves. There is not much room for "we will review that tomorrow morning."

That means send enablement is not just a connectivity project. It touches:

  • authentication and account takeover controls;
  • transaction and velocity limits;
  • receiver-account intelligence;
  • sanctions and compliance screening;
  • customer behavior monitoring;
  • exception and return processes;
  • reconciliation;
  • customer support; and
  • clear ownership when someone sends money to the wrong place.

The Federal Reserve has been building more risk tooling around this reality. In April 2026, it launched a network intelligence API for early adopters that provides receiver account-level information observed over FedNow to help participants assess risk before sending a payment.

That is an important clue about the real adoption problem.

The challenge is not convincing banks that customers like fast money. The challenge is giving institutions enough confidence to originate more of it.

Is FedNow solving a problem that does not exist?

If the problem is simply "make payouts feel instant," then sometimes, yes, there are already mature products that solve that job very well.

FedNow does not need to replace Visa Direct. It does not need to replace Mastercard Move. It does not need to pretend RTP never happened.

Those systems overlap, but they are not interchangeable.

Visa and Mastercard are also becoming increasingly multi-rail themselves. Visa Direct's account and wallet products can use account-based and faster-payment networks. Mastercard Move is explicitly positioned as a portfolio spanning payment types and endpoints. Even the card networks are telling us that the future of money movement is bigger than a single rail.

That may be the more useful way to think about FedNow too.

It is another route in an increasingly multi-rail U.S. payments stack.

And for software platforms, that can be valuable even when another rail could technically make the payment instant.

The future may be routing, not choosing

The best payment architecture for an ISV may eventually look less like picking a winner and more like building routing logic.

A payout to a consumer debit card may go one way. A high-value supplier payment may go another. A bank-account transfer might use FedNow when both institutions are reachable, RTP in another case, and ACH when instant delivery is unnecessary or unavailable.

The customer does not need to understand any of that.

They need to understand what the payment will cost, when it will arrive, what information they need to provide, and what happens if something goes wrong.

That is where the ISV's job gets harder.

More rails can create better payment experiences. They can also create more integration logic, more reconciliation paths, more exception handling, more pricing models, and more ways for support teams to have no idea what happened to a transaction.

A multi-rail strategy without operational discipline is just a more sophisticated version of final_final_recon_v7.xlsx.

Speed is the easy part to market

FedNow's growth is real. Federal Reserve data shows nearly 5 million settled FedNow payments in the second quarter of 2026, up 83.2% from the first quarter. The service has also expanded into higher-value payments and continues to add risk capabilities.

But compare that with the established scale of other options and it becomes obvious why the Fed is focused on adoption rather than simply declaring victory. The Clearing House says RTP processed more than 1.5 million payments per day on average through August 2026. Visa and Mastercard bring enormous existing endpoint reach through their money-movement products.

FedNow does not have to make those alternatives obsolete to matter.

It has to solve the right payment problems well enough that banks, software platforms, and businesses choose to use it.

For ISVs, that means the conversation should not start with whether FedNow is the future.

Start with the payment.

Who is sending it? Who is receiving it? Where does the money need to land? How much is moving? How quickly does it actually need to arrive? What does "final" mean for this use case? What happens when the customer makes a mistake? And can your risk and operations teams support the experience you are promising?

If FedNow is the best route, use it.

If push to card is better, use that.

If RTP fits, use RTP.

If the payment can wait until tomorrow and ACH is cheaper and easier, instant may not be a feature worth paying for at all.

The interesting future is not one where every payment becomes FedNow.

It is one where the customer gets the right payment experience and never has to know which rail made it happen.

Want to get featured on the CentsChat podcast? Complete our survey.

Featuring
  • Steve
    The Fixer