ACH is the default B2B payment rail. It processes the majority of domestic B2B transactions. It's cheap, widely supported, and deeply embedded in AP workflows across every industry. It's also the lowest-revenue rail, the slowest rail, and the most data-constrained rail available for B2B payments in 2026.
A well-designed multi-rail payment program doesn't replace ACH — it adds rails above and below it in a delivery cascade that routes transactions based on payee capability, transaction economics, and program requirements. The result is higher average revenue per transaction, better delivery coverage, and more product surface area for monetization.
This guide covers every major domestic payment rail, what it's good for, what it costs, and where it fits in a multi-rail architecture.
ACH — Standard and Same-Day
ACH is the baseline. For B2B programs, standard ACH is the default fallback in any cascade — it reaches the most accounts at the lowest cost. The data constraint (80 characters) is the primary limitation for complex B2B remittance. CTX format extends this to 200 characters and multiple addenda records, which helps for multi-invoice payments but still falls short of what ISO 20022 rails carry.
Same-day ACH unlocks three settlement windows per day and is the right answer when RTP isn't available and the payer needs same-day confirmation. The NACHA return code framework — R01 through R85 — is the compliance risk. Programs with high return rates face escalating scrutiny. Return rate management is an operations discipline that needs to be designed into the program from the start.
Revenue opportunity: Speed tier spread — charge more for same-day delivery than standard. Programs that don't price the difference are leaving margin on the table.
RTP — Real-Time Payments
RTP is the highest-value domestic rail for B2B payments. The 9,000-character ISO 20022 data field is the key differentiator — full invoice-level detail, line-item data, PO references, and structured remittance can all travel with the payment. For buyers and suppliers with complex multi-invoice transactions, RTP remittance data can eliminate the manual reconciliation step entirely.
The Request for Payment (RfP) capability is underutilized. It enables pull-payment workflows — the supplier sends a payment request to the buyer's bank, the buyer approves, and the bank initiates the RTP. This is the closest domestic equivalent to a SEPA direct debit for B2B. For programs with a network of known buyer-supplier relationships, RfP creates a receivables collection product that doesn't require the supplier to chase the payer.
Coverage gaps (30–35% of US DDA accounts are not on RTP-participating banks) are the limiting factor. The cascade needs to route around non-participating banks, not fail the payment.
FedNow
FedNow is the Federal Reserve's answer to RTP. Launched in July 2023, adoption has accelerated significantly. The key insight for program design: RTP and FedNow are not competing rails — they serve different bank populations. Combined instant coverage is meaningfully higher than either rail alone. A routing engine that detects which instant rail a receiving bank participates in, and routes accordingly, can approach ACH-level coverage for instant payments as adoption matures.
Push-to-Debit (Visa Direct / Mastercard Send)
Push-to-Debit is the broad-coverage near-instant option. It reaches payees who don't have accounts at RTP- or FedNow-participating banks, and it reaches consumer-adjacent payees (gig workers, contractors, insurance claimants) who are more likely to have a debit card than a business bank account at an instant-rail-participating institution.
The higher per-transaction cost relative to ACH or RTP warrants a premium delivery tier. Programs that route to push-to-debit but charge ACH prices are paying a premium to deliver a product they're not charging for.
Virtual Credit Card (VCC)
Virtual card is the highest interchange-potential rail for B2B programs. The commercial interchange rates available for VCC — particularly when Level 2 and Level 3 data is transmitted — significantly exceed anything available on ACH or instant rails. For AP programs with high supplier acceptance rates, VCC revenue can exceed the total revenue from all other rails combined.
The design variables that determine VCC revenue: card network and BIN structure (determines interchange category), Level 2/3 data transmission (determines whether enhanced interchange rates apply), supplier delivery format (electronic, email, or manual), and STP rate (determines what percentage of VCC payments actually process electronically versus manually). Programs operating at 30–50% STP are leaving significant interchange on the table.
Check Printing
Check printing is a cost center — but it's a cost center that, in a well-designed program, doubles as a conversion engine. Every check printed to a supplier who could accept VCC or ACH is revenue left unrealized. Programs that treat check printing as a passive service rather than an active conversion opportunity accept a permanently higher check volume than necessary.
Check displacement programs — active campaigns to convert check-paying suppliers to electronic — are a separate product that directly improves both cost and revenue. The design question is whether check conversion is a one-time campaign or a continuous workflow embedded in the AP process.
Electronic Lockbox (eLockbox)
eLockbox is the AR-side counterpart to outbound payment rails. For programs that also manage receivables — or that serve AR teams in addition to AP — eLockbox architecture determines how many inbound check payments process automatically versus require manual handling. The three tiers of eLockbox capability represent genuinely different product architectures, not incremental feature additions. Moving from basic lockbox to intelligent lockbox requires AR workflow integration changes, not just a vendor upgrade.
Building the cascade
A multi-rail cascade for a B2B AP program looks like this, for each payee transaction: first, attempt RTP (if receiving bank participates). If not: attempt FedNow. If not: route to push-to-debit (if payee is consumer/SMB with debit card). If not: ACH same-day (if same-day timing is required) or ACH standard. Overlay: VCC (if payee is enrolled in supplier acceptance network). Fallback: check.
The cascade isn't just a routing decision — it's a revenue architecture. Each branch of the cascade has a different cost structure and a different price potential. The programs that model the revenue per branch, optimize pricing at each tier, and actively manage payee enrollment into higher-revenue rails generate significantly higher revenue per transaction than programs running ACH with occasional check fallback.
The infrastructure selection question
Multi-rail architecture requires infrastructure partners with direct access to each rail. Indirect access — routing through a processor that routes through a bank that participates — adds cost and latency at every intermediary. Evaluating infrastructure for multi-rail capability before building the program is the correct sequence. Discovering that your BaaS provider doesn't have direct RTP access after launch is a costly retrofit.
The infrastructure selection decision is downstream from the rail architecture decision. Define the rails the program needs. Then evaluate infrastructure against that requirement. Not the other way around.