PayFi — short for payments-finance — is the layer that sits between consumer payments and DeFi liquidity. It is where stablecoin pools, real-time settlement, treasury orchestration, and risk underwriting compose to deliver something correspondent banking cannot: instant, capital-efficient cross-border settlement.
The term is new. The underlying mechanics are not. Every interbank settlement system in the world runs on pre-funded float; PayFi simply replaces opaque, slow, off-chain float with transparent, fast, on-chain float. The implications for capital efficiency are substantial — and once you understand how it works, you can read the architecture of any cross-border payments company in twenty minutes.
What PayFi is, technically
PayFi is a stack composed of three layers. At the bottom: a stablecoin liquidity pool, typically denominated in USDC or USDT, deployed across one or more chains. In the middle: a routing and matching engine that pairs inbound fiat receipts with outbound fiat payouts, using the pool to bridge the timing gap. At the top: a treasury and risk system that prices the bridge, manages the float, and earns yield for liquidity providers.
The float mechanics
Consider a real flow. A merchant in Lisbon accepts payment from a customer in Mumbai, who pays via UPI. The merchant wants euros in their SEPA account today; the customer's UPI rupees take 1–3 days to clear through the underlying banking infrastructure.
A PayFi pool bridges the gap. The pool — sitting on-chain in USDC — converts a slice of itself into euros via a regulated FX partner and credits the merchant's SEPA account same-day. Meanwhile, the rupee receipts flow into the platform over the following 1–3 days, are converted into USDC at the licensed off-ramp, and replenish the pool.
- Day 0: customer in Mumbai sends ₹50,000 via UPI to the platform's local collection account.
- Day 0 (T+0): platform debits its USDC pool, swaps the equivalent ~$600 to EUR via a regulated FX partner, settles to merchant's SEPA account.
- Day 1–3: the rupees clear through the underlying banking system into the platform's INR account.
- Day 1–3 (settlement): platform converts the INR back to USDC via a licensed off-ramp and replenishes the pool.
Why pre-funding works
The pool acts as a settlement buffer. Without it, the merchant waits 1–3 days for the UPI receipts to clear, then another day or two for SEPA settlement, then again for whatever FX desk is involved. With the pool, the merchant is paid in seconds and the pool absorbs the timing risk.
The pool earns the spread between the fiat-to-stablecoin and stablecoin-to-fiat conversions, plus a small platform fee. As long as inbound and outbound flows are roughly balanced over time, the pool sees high capital turnover and high effective yield. If imbalanced, the pool can hedge with an FX desk or rebalance via licensed liquidity partners.
| Mechanism | Correspondent banking | PayFi pool |
|---|---|---|
| Float source | NOSTRO/VOSTRO at multiple banks | Stablecoin pool on-chain |
| Settlement window | 1–4 business days | Seconds |
| Capital turnover/year | ~50–80x | ~300–1,000x (real payment flow) |
| Transparency | Opaque to non-members | Public on-chain ledger |
| Capital efficiency | Reserves must cover end-of-day net | Reserves cover instantaneous net only |
Liquidity pool design
Not all PayFi pools are equal. The well-engineered ones have four properties. Currency mix: balanced across the corridors the platform actually serves, not just USDC. Tenure structure: short-tenor LPs handle daily flow, longer-tenor LPs handle imbalances. Risk policy: drawdown limits, counterparty caps, and live exposure dashboards. And underwriting: every receivable backing the pool is rated, priced, and on-chain.
Credible's pool is non-custodial. LPs deposit USDC into vault contracts that are audited and publicly verifiable. The pool's exposure is visible on a per-corridor basis. LPs earn from real settlement flow — typically 12–18% annualised at current utilisation — not from token emissions or speculative trading.
How it compares to correspondent banking
Correspondent banking is also a pre-funding model. Each member bank holds NOSTRO accounts (its money sitting in another country's bank) and VOSTRO accounts (other banks' money sitting in its books). Settlement happens by debiting and crediting these accounts — exactly the same logic as a stablecoin pool, just slower, more opaque, and confined to bilateral relationships.
The difference is structural. PayFi pools turn capital 300–1,000x per year because they recycle the same dollar across many small payments rather than holding it as a static buffer. They are accessible to anyone with USDC — no bilateral correspondent relationship required. And they are programmable: routing decisions are made by software in milliseconds.
Risk: where it lives, how to think about it
PayFi pools concentrate three risks. Settlement risk: the inbound fiat doesn't clear (counterparty default, regulatory hold). FX risk: the conversion rates move adversely between commitment and settlement. Smart-contract risk: the pool's on-chain code has a vulnerability. Each is manageable with the right insurance, hedging, and audit discipline — but they are real and should be priced into the pool yield.
The right comparison is not to a high-yield savings account or a money-market fund. It is to underwriting a portfolio of short-tenor cross-border receivables, collateralised by real payment flow and managed with institutional risk controls.
Where this is heading
We expect three trends. Pool fragmentation by corridor: rather than a single global pool, dozens of corridor-specific pools each earning the spread on their flow. Institutional LPs: pension funds, treasury teams, and regulated asset managers entering as the regulatory perimeter stabilises. And tighter integration with traditional banking: banks themselves becoming LPs and using their NOSTRO accounts as the off-chain leg of a stablecoin pool.
PayFi is not an alternative to traditional payments. It is the engine that lets traditional payments settle in seconds. Anyone running cross-border payment volume should understand the architecture — and anyone managing treasury should ask whether their bank can provide it.