Small merchant payment routing in 2026: FedNow $0.045 vs card fees — when cards still win?

In 2026, cards still win when the full FedNow-side cost exceeds the blended card cost.

That answer changes when the payer's balance is verified up front and the sale is final.

How a FedNow payment actually settles

FedNow is a Federal Reserve credit-transfer rail, not a card-network alternative that lives inside your existing gateway. You do not route a card authorization onto it; you replace the card-entry form with a pay-by-bank button, which makes the decision a checkout redesign with its own conversion cost. When a customer chooses that button, the settlement chain involves four parties: the payer, the payer’s financial institution, the Federal Reserve’s FedNow Service, and the merchant’s receiving financial institution. The payer’s bank sends a credit transfer through the FedNow Service, and the merchant’s bank receives and posts the funds to the merchant’s account.

That structure differs from a card payment, where an authorization request travels across card-network and issuer systems before funds are later captured and settled. With FedNow, the customer initiates a push payment from their account rather than granting the merchant permission to pull funds on a card credential. For a small merchant, the practical check is whether your checkout, banking relationship, and reconciliation process can support a separate pay-by-bank flow, not whether your current card processor can “turn on” FedNow as another routing path.

Speed cannot be the argument for choosing it. A 2026 RTP-versus-ACH comparison for accounts-receivable teams (July 15, 2026) states that both RTP and FedNow settle in seconds, 24 hours a day, 7 days a week, 365 days a year. Because that latency is identical, a merchant evaluating FedNow should treat settlement speed as a baseline capability and focus instead on the live variables that differ by implementation: price, finality, and who absorbs the cost and risk of a failed or abandoned payment attempt.

Before adding the button, confirm with your provider how a FedNow payment is presented at checkout, how the customer authenticates with their bank, and how your system receives confirmation that the receiving institution has credited the funds. Because the rail settles in real time, your order-release logic should wait for that confirmation rather than assuming success from a customer’s click. This is especially important for digital goods, pickup orders, or any sale you fulfill immediately.

Treat the change as an operational test: place the pay-by-bank option beside, not in place of, the card form, then measure whether customers complete it at the same rate. The settlement chain may be simpler than a card authorization, but the merchant still owns the checkout experience, the timing of fulfillment, and the reconciliation of each credited transfer against the corresponding order.

The three figures only your bank can price

The Federal Reserve’s 2026 Fee Schedule can tell you what the Fed charges to move a FedNow payment, but it cannot price what your bank or payment service provider charges you to access that rail. A sound comparison rests on only three statement figures: the FedNow network fee, your provider’s written per-item access fee, and the measured per-transaction cost your provider documents for handling the payment on your side.

Figure 1 — Network fee. Pull the per-item FedNow billing code from the Federal Reserve’s 2026 Fee Schedule and its 2026 price-and-product-changes summary, then confirm the line item appears the same way on your provider’s billing statement. The $0.045 used in this guide is a headline premise to verify against those Federal Reserve documents, not a number to copy into a model unpriced. If your statement shows a different network amount, or bundles it into another code, use the billed figure and keep the source document on file.

Figure 2 — Access fee. Your bank or PSP layers its own per-transaction price on top of the Fed’s charge, and the Federal Reserve schedule is silent on that markup. Ask for the written per-item access fee before you change any checkout flow. The arithmetic is direct: a $0.25 access fee converts a $0.045 network charge into $0.295 per transaction. Against a $40 card sale that costs $1.46 (40 × 2.9% + $0.30), that access fee cuts the per-ticket saving from $1.415 ($1.46 − $0.045) to $1.165 ($1.46 − $0.295).

Figure 3 — Measured provider cost. The third input is any additional per-transaction amount your bank or PSP bills for processing, reporting, or integration on your account. Do not estimate it; read it from a written fee schedule or a recent statement and measure it on the same per-item basis as the other two figures. If the cost is bundled, request an itemized breakout so you are comparing like with like.

Card vs FedNow: the winner by ticket size

At a $40 ticket, the price comparison starts with your full card acceptance cost, not an interchange rate in isolation. Using a blended card rate of 2.9% plus a $0.30 per-item fee, the card cost is $1.46 per sale (40 × 0.029 + 0.30 = 1.16 + 0.30). Against that, FedNow carries the Federal Reserve’s $0.045 network fee plus your bank’s written per-item access fee, A. The raw price edge for FedNow is therefore $1.415 − A on every $40 sale (1.46 − 0.045), which means FedNow wins on processing price alone for any A below $1.415.

Price alone is not the decision point. The reader rule is to compare (blended card rate × ticket + per-item fee) against (FedNow network fee + your bank’s written per-item access fee + measured conversion impact). If a pay-by-bank option changes checkout behavior, that measured difference must be treated as a real cost or benefit in the same per-attempt calculation.

Apply that tolerance to a $40 final sale with a 30% gross margin, or $12 in gross profit per completed sale (40 × 0.30). A 5% checkout drop-off on the pay-by-bank button costs $0.60 per attempted sale (12 × 0.05). Subtracting that conversion cost from the raw edge lowers the survivable access fee to $0.815 (1.415 − 0.60). This $0.815 access-fee ceiling is the practical break-even for this ticket and margin profile.

Use the ceiling as a go/no-go check: if your written access fee is below $0.815 and your measured drop-off is no worse than 5%, FedNow can retain a per-attempt advantage on a $40 final sale. If your access fee is above $0.815, cards win even in a final-sale category, because the conversion cost erodes the remaining price edge. Recalculate the same way with your own ticket size, margin, and observed checkout data before changing the payment mix.

What the saving is worth over a year

At a $40 ticket and 2,000 sales a month, card processing at 2.9% plus $0.30 comes to $1.46 per sale ($40 × 2.9% = $1.16 plus $0.30), or $2,920 a month. A FedNow network fee of $0.045 is about 32.4 times smaller than that card cost on the same ticket, which is the ratio that undercuts the idea that “$0.045 is my new rate.”

Annualized, the gap depends on your bank’s written per-item access fee. If that access fee is $0.00 per item, FedNow runs $90 a month (2,000 × $0.045), so you save $2,830 a month and $33,960 a year compared with cards. If the access fee is $0.25 per item, FedNow runs $590 a month (2,000 × ($0.045 + $0.25)), you save $2,330 a month, and the annual spread is $27,960.

The saving is capped by what you can actually move. If only 30% of volume is movable because the rest requires credit, recurring billing, or dispute rights, the best-case $33,960 becomes $10,188 a year. Put that movable-share figure in front of an owner, not the per-transaction headline, and recompute it with your bank’s written per-item access fee before treating any annual number as real.

Where the $0.045 quietly disappears

As priced above, the $0.045 network fee is only a small fraction of the $1.46 card cost on a $40 ticket, so the fee gap is real; the rest of the gap is where conversion, disputes, and access fees live. The quiet loss is operational: a push credit transfer carries no authorization hold, so an insufficient-funds problem can surface only after the customer has left your counter or your page.

That failure mode has three parts: no funds are reserved, discovery happens after the customer is gone, and there is no card-style authorization to reverse. Before you move a sale, confirm in your payee bank's FedNow access agreement whether it offers any pre-transfer balance check, retry, or notice timing, and who bears the loss if the transfer is returned; treat missing language as a reason to keep the card path for that transaction.

Use the table as a gate, not a forecast. "Breaks" means the fee advantage is consumed by friction or risk; "still wins" means the ticket is small, final, and verified.

Apply the triggers in order: verify balance and finality first, then test the access fee, then test ticket size, credit, and delivery timing. If any keep-card condition is true, keep the card even when the fee math favors FedNow, and revisit only when the written fee or delivery terms change.

What to do next

Frequently Asked Questions

Under what conditions should a merchant route a sale to FedNow instead of cards?

A sale should be moved to FedNow only when the payer's balance is verified up front and the sale is final.

What costs must be included when calculating the full FedNow-side total?

The full FedNow-side comparison must include the FedNow network fee, the bank's written per-item access fee, and measured conversion loss.

Why can't a merchant simply route a card authorization onto FedNow?

FedNow is a Federal Reserve credit-transfer rail, not a card-network alternative that lives inside your existing gateway, so you cannot route a card authorization onto it.

What checkout change is required to accept FedNow payments?

Accepting FedNow requires replacing the card-entry form with a pay-by-bank button, which makes the decision a checkout redesign with its own conversion cost.

What common comparison mistake should merchants avoid when evaluating FedNow against cards?

Merchants must not compare the FedNow network fee to an interchange rate when evaluating payment routing options.

Who are the parties involved in a FedNow payment settlement chain?

When a customer chooses the pay-by-bank button, the settlement chain involves four parties: the payer, the payer’s financial institution, the Federal Reserve’s FedNow Service, and the merchant’s receiving financial institution.

Quick answers

Also worth reading: instant payment fees for merchants: FedNow $0.045 vs card networks in 2026: instant payment fees for merchants: · Small business payment fees: Ethereum Layer 2 (L2) vs card interchange — Break-even at 2,500 sales in 2026: Small business payment fees: Ethereum · Merchant payment fees: $2 tap sale push vs swipe in 2026: Merchant payment fees: $2 tap