Instant payment rails have reached genuine scale in the US. FedNow had attracted 1,725 banks and credit unions by the first quarter of 2026 — about 19.7 per cent of US financial institutions — processing roughly 2.73 million transactions worth $271.25 billion per quarter. The RTP network averages more than 1.5 million payments per day and approaches $500 billion in quarterly value. Both settle in seconds with immediate finality.
Parking operators keep being asked whether this changes anything for them. The honest answer, for most operators today, is less than the coverage implies — but the places where it does matter are specific and worth identifying.
What the two rails are
FedNow settles directly in each participating bank’s Federal Reserve master account, using central bank money, with intraday liquidity management tools. RTP, operated by The Clearing House, settles through a prefunded joint account at the Fed, with participating institutions committing commercial bank money in advance. Both achieve instant settlement; RTP’s prefunding model creates liquidity costs and requires active position management, while FedNow places a lighter liquidity burden on smaller participants.
For a merchant, the relevant properties of both are the same: seconds to settle, irrevocable once sent, and available outside banking hours.
Why it does not change your card revenue
The overwhelming majority of parking revenue arrives by card, and instant rails do not touch card transactions.
A card payment’s settlement timing is governed by the card networks and your acquirer, not by interbank rails. Whether funds reach your account in one day or three is a function of your merchant agreement and your acquirer’s funding schedule. FedNow existing does not change that, because the card transaction never travels on FedNow.
It is possible for an acquirer to use an instant rail for the final leg of funding a merchant, and some do offer faster or same-day funding as a product. But that is an acquirer service decision with its own pricing, not a consequence of instant rails being available. If faster card funding matters to you, the conversation is with your acquirer, and it is about their funding schedule and what it costs — not about FedNow.
Where instant rails genuinely apply to parking
Four areas are real.
Payouts to landowners and revenue-share partners. Operators managing facilities on behalf of property owners typically remit on a monthly cycle, partly because the payment mechanics are slow and batch-oriented. Instant rails remove that constraint. Whether more frequent remittance is desirable is a commercial question, but it becomes technically trivial.
Refunds. Parking generates small refunds constantly — overpayments, machine faults, disputed sessions, cancelled reservations. Card refunds take days to appear and generate a second customer contact when they do not appear fast enough. An instant credit to a bank account resolves the issue while the customer is still paying attention. The obstacle is that you need their bank details, which most parking transactions do not provide, so this is realistically limited to account-holding customers: monthly parkers, permit holders, corporate accounts.
Monthly parker and permit collections. This is the clearest fit. Recurring monthly payments currently run on ACH or on stored cards. ACH is cheap but slow and carries return risk for days. Cards cost interchange and fail on expiry. An instant credit push from the customer’s bank settles with finality immediately, at low cost, with no expiry problem and no chargeback. For operators with substantial monthly-parker bases, this is the use case worth piloting.
B2B receivables. Event parking contracts, validation programme billing, and corporate account invoicing all involve larger, less frequent payments between businesses, which is where instant rails have found their strongest adoption generally.
The irrevocability point
Instant settlement means final settlement. There is no chargeback mechanism on FedNow or RTP; a completed credit transfer cannot be pulled back by the sender.
For a merchant, that is straightforwardly good — it eliminates dispute risk on any revenue collected this way. It also means the burden shifts entirely to fraud prevention before authorisation rather than dispute resolution afterwards, and that any error in your own outbound payments is unrecoverable by mechanism. Payouts to the wrong account number stay at the wrong account number, subject to the receiving bank’s goodwill.
Operators adopting instant rails for outbound payments should tighten beneficiary verification before they increase payment speed, not after.
What to actually do
For most parking operators the sensible posture is: no change to card acceptance, and a specific look at the monthly-parker and permit-collection use case.
Ask your bank whether it participates in FedNow, RTP, or both, and whether request-for-payment is supported — the ability to send a payment request the customer approves in their banking app is what makes this workable for recurring collections. Ask what it costs per transaction and compare it against your current blended cost for monthly collections, including ACH return handling and card decline recovery.
If the numbers work on your monthly base, pilot there. The transient, small-ticket, card-dominated transaction that makes up most parking volume is not the place instant rails will show up, and there is no reason to wait for it to.
