Canadian bank regulations: why fintechs and PSPs face debanking

The rapid processing of funds by Payment Service Providers (PSPs), specifically when float moves quickly through a bank, creates significant challenges for financial institutions. This velocity negatively impacts:

• 01Liquidity provisions.
• 02Financial stability parameters.
• 03The bank's capacity to maintain compliant deposit levels.

This is a critical, yet under-discussed, mechanism behind Canadian debanking. The regulatory framework effectively renders fast-moving PSP float as low-value, and sometimes negative-value, assets on a bank's balance sheet.

How OSFI's Liquidity regime classifies PSP Deposits.

The Office of the Superintendent of Financial Institutions (OSFI) Liquidity Adequacy Requirements (LAR) Guideline implements Basel III’s Liquidity Coverage Ratio (LCR) and Net Stable Funding Ratio (NSFR), alongside the Canada-specific Net Cumulative Cash Flow (NCCF) metric. A critical variable across all three is deposit classification, and PSP float is typically categorised in the most restrictive bucket.

• 01LCR (Liquidity Coverage Ratio): Deposits from non-financial corporations face a 20 to 40% assumed 30-day runoff, while retail deposits face 3 to 10%. Deposits from non-operational financial institutions, however, are assigned up to a 100% runoff rate. This requires the bank to hold high-quality liquid assets (HQLA) against essentially the entire balance.
• 02The Velocity Problem: PSPs are financial-sector entities. While there is an 'operational deposit' carve-out (25% runoff), this requires funds to be tied to clearing, custody, or cash-management services, demonstrating that the balance is stable and necessary for operations. Float that moves in hours or days fails this test. The faster the money moves, the more decisively it is classified as 'non-operational.' This classification effectively applies Little's Law to regulation: balance equals throughput multiplied by dwell time. When dwell time collapses, the balance is viewed as 'hot money.'
• 03NSFR (Net Stable Funding Ratio) Impact: Funding from financial institutions with a residual maturity under six months receives a 0% Available Stable Funding factor. The deposit contributes nothing to the bank's stable funding position, yet the assets it funds still require stable funding. Consequently, PSP float is a liability that expands the bank's balance sheet without providing stable funding.
• 04NCCF (Net Cumulative Cash Flow) Metric: OSFI’s supervisory metric tracks the survival horizon month-by-month, allowing for tailored assumptions. High-velocity, concentrated PSP balances shorten the measured survival horizon. A weakening NCCF often invites direct intervention and pressure from OSFI, which is a significant concern for bank treasurers.
• 05Intraday Exposure: Fast-moving float creates intraday and settlement exposure. The bank clears the PSP's outflows through Lynx/ACSS against balances that may not yet be funded, consuming intraday liquidity and collateral capacity, an unpriced cost that remains invisible in the deposit spread.

Financial consequences for banks.

Does fintech float velocity impact bank liquidity regulations? Yes, mechanically. A $500 million PSP deposit that turns over daily forces the bank to hold nearly $500 million in HQLA to satisfy LCR requirements, provides no stable-funding credit under NSFR, and incurs NCCF and intraday consequences.

The bank earns a deposit spread on a balance it must fully collateralise with low-yield liquid assets. The net economics can be negative; the bank may lose money holding the float even before accounting for risk or compliance costs. This converts a bank's 'ability' to service fintechs into a question of 'willingness.' Debanking becomes the arithmetic conclusion when combined with AML burdens and competitive dynamics.

Strategies for managing PSP float.

The goal for trustees is to change the nature of the balance so that dwell time becomes a result of purpose rather than rail mechanics.

• 01Tranche the Pool by Function: Decompose the aggregate float into functional layers. Keep same-day settlement working balances (the 'hot' money) in a separate settlement layer or master account. Only place slower, stable layers (prefunding buffers, collateral, core float) with the bank as deposits.
• 02Convert Buffers to Rule-Sized Requirements: Replace demand-based buffers with buffers sized by documented formulas (e.g., peak historical net outflow plus stress multipliers). By formalizing these buffers in trust deeds and correspondent agreements, the balance becomes a contractual requirement rather than a convenience.
• 03Utilise Term and Notice Structures: For the statistically permanent core of the float, use term deposits or notice accounts (e.g., 31-day or 95-day notice). Because the trustee aggregates funds, it can offer stability that individual PSPs cannot.
• 04Structure as Collateral: Where buffers secure intraday extensions or zero-net-debit positions, structure them as pledged collateral. This legally restricts withdrawals, effectively reducing the runoff rate.
• 05Achieve Genuine Operational-Deposit Treatment: If the deposit is tied to essential clearing or custody services provided by the bank, argue for the 25% operational runoff rate. This is most defensible when the banking relationship is deeply integrated, making migration difficult.
• 06Provide Transparency to Banks: Furnish bank treasurers with detailed reports, including historical balance floors, sizing rules, and composition schedules. Transparency allows banks to classify deposits accurately rather than defaulting to the most conservative (100% runoff) category.

Conclusion: The Trustee's role.

A trustee cannot promise PSPs full same-day access to all funds while simultaneously promising the bank stability. The honest approach is to provide same-day liquidity from the trustee’s own settlement layer, while placing tranches with defined access terms at the bank. The trustee’s value lies in absorbing this maturity transformation, effectively managing the mismatch that individual PSPs cannot safely perform.