Why B2B Payments Still Break at the Settlement Layer

Key takeaways:

• The B2B payments experience has improved on the surface, but the underlying infrastructure (correspondent banking, pre-funding, delays, and fees) remains largely unchanged and inefficient.
• Stablecoins offer a fundamentally different settlement model — eliminating intermediaries, enabling near-instant settlement, and removing the need for pre-funded accounts.
• Adoption is accelerating (>$150B in 2025 B2B volume), but successful implementation depends on solving compliance, orchestration across chains, and seamless integration into existing systems.

—

The front end of B2B payments is fine. Good, even. Invoicing tools are faster, dashboards are cleaner, and API integrations are more capable than they were five years ago. 

If your customers are happy, that is probably what they see.

What they do not see is everything underneath. The delays you cover with float, the fees you eat in the name of growth, or the capital sitting idle in accounts overseas. None of that is visible from a well-designed payments UI.

The backend infrastructure powering most B2B cross-border payments has not meaningfully changed. It just has better interfaces sitting on top of it.

Here’s why this keeps happening and what’s necessary to fix it.

‍

What the customer sees vs. what is actually happening

‍

When a cross-border payment takes three to five days to settle, the delay is not in your application. It is in the chain of correspondent banks that each hold, verify, and forward the funds before they reach the other side. Each one adds time, takes a cut, and introduces a point of failure.

Some providers have found ways to absorb part of this cost, offering no FX fees or competitive exchange rates as a customer acquisition lever. That is a real improvement in what the customer experiences. But it is a margin decision, not an infrastructure change. 

The capital efficiency problem is still there, just hidden. Old backend infrastructure shows up in three ways: 

1. Fees attached to each transaction
2. Settlement times your treasury team manages around
3. Lack of observability of the payment itself

When something goes wrong in a correspondent chain, tracking down where the funds are and why they stopped moving is slow, manual, and largely opaque.

Proactive finance teams try to solve this with pre-funding accounts in major corridors. But that’s just another instance of covering up an inefficiency versus solving for it, as costs and settlement times have not meaningfully decreased.

‍

How stablecoin settlement addresses the structural problem

‍

The core of the correspondent banking system is trust and compliance between parties; each connecting ledgers to ensure the transaction is tracked appropriately.

Stablecoins, by contrast, work on a single cryptographic ledger. This means near-instant reconciliation and settlement as all parties can trace money flows from sent to received. There is no correspondent chain, no pre-funded account in the destination currency, no intermediary holding period. The liquidity requirement is the payment itself rather than a standing reserve deployed across a dozen accounts in advance, just in case.

This is not a UX improvement on top of the same infrastructure. It is a different settlement mechanism. The pre-funding problem does not exist on stablecoin rails because the settlement model does not require pre-funding.

More importantly, organizations are already using stablecoins for cross border settlement. In 2025 alone, for instance, analysis by Boston Consulting Group found that B2B transactions on stablecoins accounted for over $150 billion in value with a compound annual growth rate of 65 percent.

Image source: Boston Consulting Group

‍

What implementation actually requires 

‍

The first conversation with a stablecoin infrastructure provider is usually about the business case. A company knows it moves money internationally and wants to know if stablecoin rails can make that cheaper and faster. The answer is almost always yes.

Then comes implementation planning. Here are the three keys to watch out for. 

1. Compliance

Licensing alone can take years. KYC and AML obligations apply. The Travel Rule — expanded in June 2025 to cover all cross-border virtual asset transfers — requires originator and beneficiary data on every transaction.

Planning for compliance regulations (or picking a vendor who manages this for you) is critical. 

2. Orchestration

Payments orchestration across chains adds another layer of complexity. Each of these pieces (on-ramps, stablecoin flows, and off-ramps) is non-negotiable. Missing any one of them does not simplify the implementation; it blocks you from going live.

The reason the implementation complexity surprises most companies is that stablecoin payments do not run on one chain. Ethereum, Solana, Base, and others each have different liquidity profiles, settlement speeds, and costs. Routing a payment correctly — optimizing for cost, speed, and compliance across whichever chains are relevant to a given corridor — requires real-time decisions across moving variables.

3. Integration

However you choose to build or partner, it has to fit with your existing systems. That means looking for a vendor with clean API documentation so you can plug into current workflows.

The licensed infrastructure, the compliance stack, and the banking connectivity exist — they just need to be assembled correctly for your specific use case.

‍

What the orchestration layer actually does

‍

Individual companies that invested years into solving the settlement layer built competitive advantages for themselves. The infrastructure that lets any payment business, regardless of size or internal engineering capacity, access those same rails is what changes the economics broadly.

To learn more about how an orchestration layer could look in your business, book a demo with Cybrid.