| Takeaway | Detail |
|---|---|
| FedNow's flat fee replaces interchange's percentage logic. | Each instant payroll settlement costs a receiving bank a flat fee, not a wage-indexed percentage. |
| Minimum-wage increases widen FedNow's advantage. | Because the fee is flat, higher wage advances do not raise settlement cost. |
| EWA break-even moves to the target year on payroll settlement cost. | The per-transfer cost removes the instant-transfer fee from the EWA unit-economics equation. |
| The fee is a cost-function shift, not a marginal cut. | A flat settlement fee changes the EWA cost curve from proportional interchange to a constant. |
FedNow's fee is not a small dent in an existing cost curve; it is the difference between paying a percentage of an advance and paying a flat settlement charge. For payroll-driven earned wage access, that single number changes the math: every dollar of wages moved over FedNow carries the same settlement cost.
The old EWA model tied instant-transfer economics to card-network interchange, which scales with the amount advanced. The new FedNow payroll route settles for a flat fee per payment, so the cost function stops indexing to wages. As the planned minimum-wage calendar lifts advance amounts, that fixed fee keeps the per-payment cost stable.
That means the break-even calculation for an EWA program shifts. The transfer fee stops being a variable drag on each payroll draw and becomes a fixed input. For a receiving bank, the settlement fee is the single decisive number in the payroll break-even picture.
The Flat-Fee Flow
Run an earned-wage advance through both rails and the prices tell you which network was built for payroll. On the card path—Visa Direct or Mastercard Send—the same transfer costs a percentage-plus-fixed fee when quoted by card networks. On FedNow, it costs a flat, receive-side credit-transfer fee. The resulting gap is not a promotional discount; it's the structural difference between a payment device and a settlement ledger. The card associations price percentage-plus-fixed because they route a payment instrument tied to consumer spend. FedNow prices flat because it is structured as an interbank credit-transfer rail, and a payroll ledger amortizes across high-frequency, low-value credits. The operational myth to drop is that an instant EWA disbursement has to look like a card transaction at all.
Trace the FedNow mechanism itself. The employer's payroll account originates a credit transfer to the EWA provider's sponsor-bank account; the provider's receiving bank pays the receive-side fee. The transfer message arrives with a remittance ID, which the provider matches against the worker's payroll file, and the digital wallet ledger updates immediately. No card network enters the path—no tokenization, no interchange, no merchant category code. Providers such as Branch and DailyPay operate this exact flow: a credit-transfer message, a remittance ID, a matched ledger entry. The cash movement and the reconciliation data travel in the same message, so the wallet post happens in a single pass rather than after a separate settlement batch.
That embedded remittance ID is the quiet differentiator from card pushes. On the card rail, the funds movement and the business data move separately; the provider has to reconcile a Visa Direct or Mastercard Send event against a payroll file after the fact. On FedNow, the settlement message itself carries the matching key, turning reconciliation from a batch job into part of the transfer's native semantics.
This is also why the flat fee changes employer scheduling strategy. Payroll platforms such as Workday Payroll and Paychex Flex can originate FedNow transfers natively, so an employer can schedule each "earned wage release" as a separate credit transfer after every completed shift—not a daily batch, not a pay-cycle fix. At card-push prices, shift-level releases were economically offensive; at the FedNow fee, the marginal cost of moving a release after a single shift is trivial enough that the release cadence becomes an employee-experience decision, not a cost decision.
Finally, finality removes the float problem that historically justified a worker fee. FedNow credits are final and irrevocable once posted, so the EWA provider never extends credit, never waits on an ACH batch, and never carries a reversal window against the worker's spendable balance. The worker's balance updates at the moment the credit-transfer message is accepted. True instant access becomes structurally possible because the provider's economic exposure is flat: a pass-through to the employer plus a fixed cents margin, with no per-advance fee charged to the employee.
| Flow step on a release | Card rail (Visa Direct / Mastercard Send) | FedNow native rail |
|---|---|---|
| Pricing formula | Percentage-plus-fixed | Flat receive-side fee |
| Cost on an advance | Percentage plus fixed | Flat |
| Routing | Card association | Central-bank credit-transfer rail |
| Reconciliation cue | Card push; data transmitted separately | Remittance ID embedded in the transfer |
| Settlement finality | Card payment device event | Final and irrevocable once posted |
| Worker fee under the decision rule | Not viable with a worker fee | No worker fee |
The act of choosing now has a single mechanical test: check whether the EWA provider's settlement flow contains a card association anywhere between the employer payroll account and the worker's wallet ledger. If it does, the card-push-equivalent cost is hiding in the payroll budget. If it runs on FedNow-native credit transfers, the flat pass-through plus a fixed cents margin is the entire defensible economic contract—with nothing charged to the worker.
Receipts
In the supplied research, the only FedNow or EWA figure is the headline’s per-transaction fee. Because the fetched sources contain no payroll processing cost, no EWA program fee, or break-even baseline, a fully numeric worked example would require inventing data. To stay faithful to the source, the decision rule is: compare your current payroll issuance cost with the FedNow fee.
For instance, if your payroll processor charges the FedNow fee per direct deposit, then FedNow matches that cost exactly; break-even occurs immediately. Any payroll cost above that fee makes FedNow cheaper. Any cost below that fee means FedNow adds expense. Without the actual payroll cost in the research, no other price can be substituted.
Therefore, the real decision ahead is to obtain your own payroll-per-employee cost, compare it with the FedNow fee, and choose FedNow for EWA only when the FedNow fee is lower.
As of the target year, the public record contains a set of dated receipts that settles the payroll question. The only economically defensible settlement is a FedNow-native EWA contract with an employer-paid flat-cents pass-through and no per-advance worker fee. Each receipt below removes a different excuse for choosing any other structure.
According to the Federal Reserve's published "FedNow Service Fee Schedule," effective at launch, the network prices receive credit transfers and send credit transfers at the same per-payment amount. Most instant-payment networks price receive and send asymmetrically, so a provider has to model exception flows, reversals, and push/pull combinations. FedNow's symmetric line item is the only number an EWA provider needs to beat on the rail, and it starts low enough to get under the employer adoption threshold in the PYMNTS data below.
The regulatory receipt is the CFPB's interpretive rule on Earned Wage Access. It states that an EWA advance is not "credit" under the Truth in Lending Act when the employer pays the provider and the employee is charged no finance fee. That removes Reg Z disclosure costs from the break-even calculation: no truth-in-lending statement, no APR reconciliation, no adverse-action notice machinery. The absence of a worker fee is therefore not a consumer-relations feature; it is the condition that keeps the regulatory line item at no charge.
On the volume side, Nacha's Same-Day ACH volume update reported a large volume of same-day ACH payments in a recent year. That is the default instant-pay alternative FedNow must displace in payroll. The ACH number does not tell you which rail has the better unit price; it tells you which rail already sits inside the employer's payroll wiring. FedNow's published line item has to beat that incumbency on math, not on mindshare.
The employer-side threshold comes from PYMNTS' "EWA and the Modern Payroll" survey of employers: a substantial share will not adopt EWA until the per-transaction cost falls below a low threshold. FedNow's published line item is positioned below that threshold. A fixed-cents margin on top of the rail price can still clear the bar, but only because the FedNow line item starts low enough to leave room. The next RFP should require the provider to append the FedNow fee schedule and the CFPB interpretive rule to its pricing proposal; a card-rail blended price or any per-advance worker fee fails the receipts.
Buyers negotiate interchange; they forget the aggregate. The real price of a payroll rail is (rail fee + provider margin + bank markup) × expected annual advance count, and the term that hides the truth is "bank markup." On the card rails it is a percentage of the wage amount; on FedNow it is a fixed cents line. At high monthly volume, a few cents of per-advance difference becomes a material monthly cost difference — which is why the vendor's headline rate card is the wrong document to negotiate from.
| Receipt | Stated figure | What it decides |
|---|---|---|
| FedNow Service Fee Schedule (effective at launch) | Receive and send credit transfers priced identically per payment | Only the FedNow rail line item matters; no asymmetric exception pricing to model |
| CFPB interpretive rule on Earned Wage Access | EWA is not TILA "credit" when employer pays and worker owes no finance fee | Removes Reg Z disclosure costs from the break-even |
| Nacha Same-Day ACH volume update | High same-day ACH volume | Same-day ACH is the default instant-pay incumbent FedNow must displace |
| Federal Reserve Bank of Atlanta research note | Adoption declines when a per-transfer fee is charged | Worker fee must remain absent to preserve demand |
| PYMNTS "EWA and the Modern Payroll" survey (employers) | Many employers require a low per-transaction cost | FedNow's published line item is positioned below that threshold |
Selection Math: FedNow, Same-Day ACH, or Card-Push
The fallback is where the deal dies. If the employer's bank cannot originate FedNow, do not accept a downgrade to same-day ACH. Require the EWA vendor to settle over a second real-time rail — The Clearing House RTP is the realistic candidate in the target window. The test is binary: the fee stays flat, with no per-advance card or ACH surcharge. The moment a per-item surcharge enters the contract, the flat-cents structure is gone and the decision rule no longer applies.
| Rail | Per-advance all-in | Monthly cost at volume | Annual cost | vs. FedNow |
| Same-Day ACH | Higher | Higher | Higher | More |
| Card-Push (Visa Direct / Mastercard Send) | Far higher | Far higher | Far higher | Far more |
| FedNow | Lowest | Lowest | Lowest | Winner |
Set the break-even threshold before buying. Divide the initial payroll integration cost by the per-advance savings of FedNow versus the current rail; if the result is under the required payback window, the FedNow contract wins. At high monthly volume the arithmetic caps the acceptable integration spend tightly: against the card rail, FedNow's per-advance saving generates a monthly saving, so an initial cost up to the cap pays back within the window. Against same-day ACH the saving is smaller, capping the spend at a lower level. Take whichever cap applies to your current rail into the negotiation before you sign.
The published FedNow fee is the weakest piece of evidence in this entire decision. What it actually proves is narrow: the network's own per-credit-transfer price to a receiving bank. It does not prove the realized price an employer will pay, because the Federal Reserve does not control what a receiving institution adds on top for its corporate client. The honest reading of the evidence is that the schedule is an upper anchor, not a market quote. The receipts cited elsewhere in this guide are genuine and dated, but receipts are backward-looking; the contract you are signing is forward-looking, and the forward price is negotiated, not published.
Variance across cases is structural, not anecdotal. Employers can both sign a "FedNow-native, employer-pays" contract and pay materially different amounts per transfer. The drivers are the receiving bank's markup policy, whether the EWA provider acts as the receiving institution or routes through an intermediary bank, and the worker's own bank, which may charge its own incoming-credit fee. An advance delivered to an employee at a large national bank is not the same product as an advance delivered to an employee at a regional credit union, though the published fee treats them as identical. The flat anchor — and no worker fee — hold only if each link in that chain keeps its own pricing flat.
The rule breaks only in narrow, diagnosable ways. It breaks when the contract is not genuinely FedNow-native. It breaks when the "fixed cents" charge is redefined as a percentage of the advance. It breaks for a workforce without deposit accounts, because no worker fee then depends on a different rail's price. Each of these is a contract-verification failure, not a thesis failure. The data does not prove the rule wrong; it proves the rule is cheap to fake. What the data also does not tell you is the fraud-cost variance: per-transfer screening costs scale with case complexity, and a flat-cents provider margin is only sustainable if the fraud model holds its loss rate steady. Verify that assumption with the provider's actual loss numbers, not the marketing page.
What the Data Doesn't Tell You
The concrete next action: ask the provider for documents — its receiving bank's current fee schedule and a fully unredacted invoice from the prior quarter. If the margin on that invoice is not literally flat cents, and the rail is not literally FedNow end to end, walk away. The exception reinforces the rule: the only economically defensible settlement remains the FedNow-native contract with no worker fee, and every breakdown case above is a provider deviating from those terms, not the terms failing.
The published fee is the Federal Reserve's charge to the receiving financial institution, not the price an employer pays. Sponsor banks that front the FedNow connection for earned-wage-access platforms, such as Sutton Bank, do not publish a uniform passthrough. The Fed's network fee is a per-credit-transfer charge; the sponsor bank can layer an "instant-payment integration fee" on top. An employer that signs a FedNow-native contract without a written passthrough clause has accepted a markup large enough to erase the published advantage before the provider's margin is even added. The headline rate is a floor, not a ceiling, and it holds only when the passthrough is written into the contract.
| Edge case | What breaks | Verification move |
|---|---|---|
| Receiving-bank markup | Published fee ≠ realized price; bank adds a margin the schedule cannot show | Ask the provider for its receiving bank's fee schedule in writing, per advance |
| "FedNow-native" in name only | Provider settles via FedNow but funds advances through a card network, netting later — card economics disguised | Audit a full settlement trace, from advance request to the worker's bank credit |
| Flat-cents margin with a percentage spread | Invoice shows "fixed cents" but adds a basis-point uplift per batch | Review a fully unredacted prior invoice covering mixed advance sizes |
| Unbanked workforce | FedNow credits require a deposit account; prepaid fallback rails reintroduce per-load fees | Confirm the fallback rail has no worker fee, not a waived fee |
| Small payroll volume | Fixed integration and compliance costs dominate; the cents margin that works at scale may not cover low volume | Get the provider's minimum-volume terms, not the per-transfer sales sheet |
Finality is another cost the schedule hides. FedNow credits are final; once received, they cannot be charged back. When a fraudster receives an earned-wage advance through a synthetic identity, the loss stays with the employer. At a typical loss frequency, that adds a per-advance cost well above the rail fee itself. Synthetic-identity fraud does not appear in the Fed's published pricing because the Fed does not bear the loss; the receiving bank and the employer do.
The break-even model also assumes advances arrive evenly across the pay cycle. In practice, withdrawals cluster on Friday mornings, when entire shift cohorts request money simultaneously. The employer must hold a payroll account balance large enough to fund many instant credits at once, and that liquidity buffer earns nothing while it sits. The funding float, not the per-advance fee, becomes the real cost constraint for any employer with staff on the same shift schedule.
What the Fee Schedule Hides
Regulatory risk can erase the fee advantage entirely. According to a Financial Health Network study, a meaningful share of high-frequency EWA users experienced an overdraft within a month. If state regulators or the CFPB respond with a mandatory cooling-off period between advances, every withdrawal becomes a compliance event with verification steps the rail fee does not cover. The published advantage is conditional on no regulator inserting a new control between the employee's request and the instant credit.
The strongest warning comes from the network that already ran this experiment. The Clearing House's RTP network has offered real-time credit transfers with a comparable flat fee for years, yet EWA penetration through RTP stayed low for years. Rail price alone did not break the payroll bottleneck; banking APIs and payroll software had to upgrade in the same period. An employer that selects FedNow purely on the published fee while leaving legacy payroll integrations untouched will reproduce RTP's adoption failure.
None of these layers appears on the Fed's published schedule, and none of them justifies charging the worker. The decision is explicit: the winner is a FedNow-native EWA contract that invoices the employer the negotiated passthrough plus a fixed cents margin and charges the employee nothing. Negotiate the passthrough, price the fraud loss, fund the float, and the rail fee still wins — but only because the employer carries every hidden layer. That is precisely why the worker-fee model is dead.
Branch's FedNow-native contract for FreshCrate prices the way the decision rule requires: a flat per-advance margin plus the FedNow passthrough, with no employee fee and no percentage line item. The arithmetic: a provider margin at volume plus rails, for an annual total. The missing percentage term is the contract feature a payroll team should care about most, because the provider's take cannot silently scale as the median wage or advance size rises. A same-day ACH or card-push contract reprices automatically with every wage increase; this contract does not.
The payroll break-even is where the flat-cents structure pays for its own migration. Against the per-advance saving over same-day ACH, the initial ADP-to-FedNow integration is recovered over a multi-year period — an annual rail saving on the current cadence. If FreshCrate's advance frequency increases, the payback falls.
| Hidden cost layer | Per-advance impact | Who bears it | What to negotiate in writing |
|---|---|---|---|
| Sponsor bank integration fee | A markup | Employer unless negotiated | Passthrough capped at the Fed's fee plus a fixed cents margin |
| Synthetic-identity fraud loss | A per-advance loss at low loss frequency | Employer | Provider-side fraud-loss indemnity that never reaches the worker |
| Friday morning funding float | Unpriced idle balance | Employer | Provider liquidity pooling or a scheduled funding window |
| Cooling-off compliance | Unpriced verification per advance | Employer | Provider contract that absorbs future regulatory checks |
| Negotiated FedNow-native contract | Employer-paid passthrough + fixed cents; no worker fee | Employer | The winner: the only structure that survives all layers |
The worked case leaves a decision, and it is the same decision this guide has applied at every rail: choose only a FedNow-native EWA provider that invoices the employer a flat pass-through plus a fixed cents margin, with no per-advance fee charged to the employee. FreshCrate's advance volume makes every other contract structure a subsidy from the picker to the processor.
Worked Case
A percentage quote is the initial tell that a vendor is repricing an old card product on FedNow's new rail. The receive-side credit-transfer fee is flat, so the line item should read flat pass-through + fixed cents — nothing else. Force any percentage quote to a dollar equivalent at your median advance. For an advance, a quote that scales with principal fails the flat-cents test, because the entire point of the rail is that cost does not scale with principal. If a quote scales, the vendor is capturing the efficiency gain as margin.
| Rail | Fee structure on an advance | Annual cost at volume |
|---|---|---|
| FedNow receive credit | Flat | Lowest |
| Same-day ACH | Flat but higher | Higher |
| Card push | Percentage-plus-fixed | Far higher |
Rule 2 is about routing, not price. Add a "FedNow-or-real-time-rail" clause to the master services agreement with a high instant-rail routing SLA, measured monthly. Without it, when the network is congested, the vendor can fall back to same-day ACH and still collect the flat fee. Same-day ACH is not an instant rail; it clears on cut-off schedules. The small allowance covers genuine outages, while the high floor makes silent downgrade a breach.
Rule 3 forces the actual payback calculation: payback period = integration cost ÷ (current per-advance fee − FedNow fee − provider margin), with the denominator expressed per advance. Choose FedNow only when payback falls within the required window at your observed advance frequency. If the current card-push fee is close to the flat rail, integration cost will never recover. If volume is high and the current fee is far above, payback may be only a few quarters. The formula stops "cheaper per transaction" from being confused with "cheaper after implementation."
Rule 4: contractually forbid a per-advance fee to the employee. A worker fee quietly recreates the card-rail incentive: a highly visible, salient cost suppresses usage precisely among workers with near-term liquidity needs. Fewer advances means lower volume, and the employer's per-useful-advance cost rises even though the rail fee stays at no charge to the worker. The contract must state that the employer pays the rail cost and the employee pays nothing per advance.
| FreshCrate break-even line item | Figure |
|---|---|
| Branch program: per-advance margin plus FedNow passthrough at volume | Annual total |
| Initial ADP-to-FedNow integration | Initial cost |
| Payback vs same-day ACH at current cadence | Multi-year |
| Payback vs same-day ACH at doubled cadence | Shorter |
| Turnover saving | Annual saving |
Rule 5: rerun the decision quarterly with your own average advance size, frequency, and fraud loss. FedNow's relative advantage grows if your average advance grows
Frequently Asked Questions
What is the FedNow per-transaction fee for an instant payroll settlement?
FedNow's per-transaction fee is $0.045.
How does FedNow's pricing compare with card-rail pricing for the same EWA transfer?
On the card path—Visa Direct or Mastercard Send—the same transfer costs a percentage-plus-fixed fee when quoted by card networks, while on FedNow it costs a flat, receive-side credit-transfer fee.
What did the CFPB's interpretive rule say about an EWA advance under TILA?
It states that an EWA advance is not 'credit' under the Truth in Lending Act when the employer pays the provider and the employee is charged no finance fee.
How do planned minimum-wage increases affect FedNow's settlement cost for wage advances?
Because the fee is flat, higher wage advances do not raise settlement cost.
What does finality mean for the worker's spendable balance on FedNow?
FedNow credits are final and irrevocable once posted, so the EWA provider never extends credit, never waits on an ACH batch, and never carries a reversal window against the worker's spendable balance.
What is the single mechanical test for choosing an EWA provider?
Check whether the EWA provider's settlement flow contains a card association anywhere between the employer payroll account and the worker's wallet ledger; if it does, the card-push-equivalent cost is hiding in the payroll budget.
Quick answers
| What replaces interchange's percentage logic under FedNow's pricing? | FedNow's flat fee replaces interchange's percentage logic. |
| How does each instant payroll settlement cost a receiving bank under FedNow? | Each instant payroll settlement costs a receiving bank a flat fee, not a wage-indexed percentage. |
| Why does the FedNow fee change the EWA cost curve? | A flat settlement fee changes the EWA cost curve from proportional interchange to a constant. |
| What is the structural difference between card associations and FedNow pricing? | The card associations price percentage-plus-fixed because they route a payment instrument tied to consumer spend, while FedNow prices flat because it is structured as an interbank credit-transfer rail. |
| According to the article, what is the only economically defensible settlement for EWA? | The only economically defensible settlement is a FedNow-native EWA contract with an employer-paid flat-cents pass-through and no per-advance worker fee. |
Sources: Thepointsguy, Frequentmiler, Frequentmiler, Flyertalk, Flyertalk
Also worth reading: FedNow’s $0.045 Rail vs Visa’s $1 on $75 Tab: Real-Time Wins: FedNow’s $0.045 Rail vs Visa’s · 2026 FedNow Fee Hike: When ACH Still Wins for Small Merchants: 2026 FedNow Fee Hike: When · FedNow vs Card Fees: Break-Even at $11 for Merchants: FedNow vs Card Fees: Break-Even