Why is pre-funding so expensive for a PSP?

Because it is capital parked against uncertainty. To pay out quickly in a corridor, a PSP holds balances in destination accounts before payments arrive, sized for peak volume plus a buffer. That money earns little, cannot be deployed, and is multiplied by every corridor and currency served. As corridors grow, pre-funded float grows faster than revenue, because each new market needs its own buffer against its own peaks.

What is any-to-any settlement?

The ability to accept value on one rail and pay out on another through a single integration: fiat in, stablecoin across, local fiat out, or any other combination the corridor and counterparty require. Without it, a PSP builds and maintains a separate integration for every rail and market pair it serves, and each pair carries its own reconciliation, cut-offs, and float.

Do stablecoin rails actually lower corridor costs?

For the settlement leg, often yes: transfer is fast, final, and cheap compared with a chain of correspondents. The honest caveat is the edges. On-ramps and off-ramps charge their own fees, and on thin-margin corridors a stacked set of ramp costs can erase the saving. The economics have to be evaluated corridor by corridor, which is itself an argument for infrastructure that can choose the rail per payment rather than commit to one.

What should a PSP evaluate in settlement infrastructure?

Four things: corridor and rail coverage (not just how many, but whether routing between them is policy-driven); the compliance model, since the PSP carries the regulatory relationship and needs screening enforced on every payment; reconciliation and evidence, because ops headcount scales with exceptions; and neutrality, to avoid locking the business to one coin, one chain, or one network's roadmap.

Solutions

Settlement infrastructure for PSPs and processors

Why settlement is the margin problem for PSPs and processors: pre-funding costs, corridor sprawl, integration debt, and how to evaluate the alternatives.

For a payment service provider, settlement is where the margin goes. The client-facing product is priced in basis points; the cost base underneath is priced in trapped capital, correspondent fees, integration projects, and reconciliation headcount. McKinsey’s 2025 Global Payments Report counts $2.5 trillion in global payments revenue, and the competition for every slice of it means a PSP’s economics are decided less by what it charges and more by what its settlement stack costs. This page is about that stack: why it is expensive, and what the alternatives look like.

The three costs that compound

Trapped capital. Fast payouts in a corridor mean pre-funded balances waiting in that corridor, sized for peaks. Every new market adds another float, every float is capital that cannot work, and the sum is liquidity fragmented across accounts that exist only to absorb settlement delay. The delay itself comes from the correspondent chain: while a payment spends days in transit, someone has to have already provided the money at the far end, and that someone is the PSP.

Corridor sprawl. Each corridor arrives with its own local partners, cut-off times, formats, and failure modes. The BIS has documented a roughly 22% decline in active correspondent relationships between 2011 and 2019, which makes the long tail of corridors harder to serve, not easier: fewer routes, more intermediaries on the routes that remain, and thicker fees where competition thinned. Meanwhile the official improvement program is behind its own schedule; the FSB concluded in October 2025 that the G20’s end-2027 targets for cross-border payments are unlikely to be met at the global level, and the World Bank still measures average remittance cost at 6.36%.

Integration debt. The rails multiplied. Instant schemes, stablecoin networks, wallet payouts, local ACH equivalents: each is an opportunity in a pitch deck and a project in the roadmap. A PSP that connects rail by rail accumulates integrations the way old banks accumulated correspondents, and every one must be maintained, reconciled, and staffed.

What any-to-any changes

The structural fix is to stop owning the pairs. An any-to-any settlement layer accepts value on whichever rail the payer uses and delivers it on whichever rail the payee needs, through one integration: fiat in, stablecoin across, local fiat out, or fiat end to end where that wins. Three consequences follow.

Floats shrink, because settlement in seconds needs a fraction of the buffer that settlement in days demands. Corridors become configuration, because adding a market means adding a route and a policy rather than a project. And rail choice becomes reversible: when a corridor’s economics shift, when a coin’s regulatory status changes, when a new instant scheme opens, routing policy changes and the integration does not.

The honest caveat belongs in the evaluation: rails have edges. On thin-margin corridors, stacked on-ramp and off-ramp costs can eat the gains of a faster middle leg, which is precisely why the routing decision should be per payment and per corridor, made by policy against live economics rather than fixed by whichever rail the infrastructure happens to be.

What to evaluate

Coverage is the obvious question and the least decisive one. The harder questions: Is routing policy-driven, so the PSP’s own rules decide the rail per payment? Where is compliance enforced, given the PSP carries the regulatory relationship and cannot outsource the obligation? What evidence does settlement produce, since exceptions and reconciliation are where ops cost actually lives? And is the layer neutral, or does it quietly anchor the business to one coin, one chain, or one network whose roadmap the PSP does not control?

Where Frame fits

Frame is the settlement layer for global finance: one integration to orchestrate payments at scale across fiat rails, stablecoins, and tokenized deposits, with compliance enforced on every transaction and settlement in seconds instead of days.

For PSPs and processors, that is the any-to-any model described above. Frame is rail-neutral, so each payment routes across whichever rail fits the corridor, the counterparty, and the policy that governs it, and the choice stays reversible as corridor economics move. Compliance runs inside settlement: Frame’s Rules Engine evaluates every transaction against its governing policies, a transfer that cannot satisfy them does not settle, and every settled transaction produces verifiable evidence that its conditions were met. Frame serves banks and financial institutions, payment providers and processors, exchanges and trading venues, SaaS and ERP platforms, and enterprises; for a PSP, the practical translation is fewer floats, fewer integrations, and settlement economics decided by policy instead of by inheritance.

See how a rail-neutral settlement layer is designed: the Frame Blueprint.

Common questions

Why is pre-funding so expensive for a PSP?: Because it is capital parked against uncertainty. To pay out quickly in a corridor, a PSP holds balances in destination accounts before payments arrive, sized for peak volume plus a buffer. That money earns little, cannot be deployed, and is multiplied by every corridor and currency served. As corridors grow, pre-funded float grows faster than revenue, because each new market needs its own buffer against its own peaks.
What is any-to-any settlement?: The ability to accept value on one rail and pay out on another through a single integration: fiat in, stablecoin across, local fiat out, or any other combination the corridor and counterparty require. Without it, a PSP builds and maintains a separate integration for every rail and market pair it serves, and each pair carries its own reconciliation, cut-offs, and float.
Do stablecoin rails actually lower corridor costs?: For the settlement leg, often yes: transfer is fast, final, and cheap compared with a chain of correspondents. The honest caveat is the edges. On-ramps and off-ramps charge their own fees, and on thin-margin corridors a stacked set of ramp costs can erase the saving. The economics have to be evaluated corridor by corridor, which is itself an argument for infrastructure that can choose the rail per payment rather than commit to one.
What should a PSP evaluate in settlement infrastructure?: Four things: corridor and rail coverage (not just how many, but whether routing between them is policy-driven); the compliance model, since the PSP carries the regulatory relationship and needs screening enforced on every payment; reconciliation and evidence, because ops headcount scales with exceptions; and neutrality, to avoid locking the business to one coin, one chain, or one network's roadmap.

Sources

Last reviewed 2026-07-16