The Clock Is Running
September 2026 is not a soft target. It is the date the FCA's authorisation gateway opens for cryptoasset businesses — and for stablecoin issuers specifically, it marks the point at which operating without authorisation becomes unlawful. The regulatory framework that governs that gateway has now been substantially set out across two consultation papers: CP25/14 (conduct requirements for stablecoin issuance and custody) and CP25/15 (the CRYPTOPRU prudential sourcebook).
If you are building a stablecoin — or advising one — you need to understand both. This article gives you a practical summary of what each paper requires, what they mean for your balance sheet, and what the September 2026 deadline actually demands of your finance function.
What Qualifies as a Stablecoin Under This Regime?
The FCA's regime focuses on fiat-referenced tokens — cryptoassets designed to maintain a stable value by reference to a single fiat currency (e.g. GBP, USD, EUR). This means:
- Algorithmic stablecoins (those without asset backing) are not in scope for authorisation — they are effectively prohibited from being used as a means of payment in the UK.
- Multi-currency or commodity-backed tokens may be in scope but are treated differently.
- If your coin is backed 1:1 by fiat-denominated assets and marketed as a stable store of value or payment instrument, you are almost certainly in scope.
Issuers of in-scope stablecoins must obtain FCA authorisation before they can issue tokens to UK persons or allow their tokens to be used as a means of payment in the UK. Custodians holding backing assets on behalf of issuers are separately in scope and must meet their own conduct requirements.
The 1:1 Backing Requirement: The Floor, Not the Ceiling
The single most important structural requirement is the mandatory 1:1 backing of all tokens in issuance at all times. Every qualifying stablecoin must be fully backed by a pool of eligible assets equal in value to the total supply of tokens outstanding.
This sounds simple. It is not. The 1:1 backing requirement has four hard constraints attached to it:
A statutory trust is imposed over the backing asset pool by operation of law. This means that in the event of issuer insolvency, the backing assets sit outside the general estate and are ring-fenced for the benefit of token holders. It is not optional — it is a legal consequence of the regulatory structure.
"1:1 backing is the floor, not the complete picture. Once you layer in the ODDR, BACR, ILAR and OFR requirements, total capital and liquidity commitments for a material issuance can run to 3–5% of outstanding coins — in addition to the 100% backing pool."
What Can You Hold in the Backing Pool?
The FCA draws a clear distinction between core backing assets and expanded backing assets. All issuers can use core assets by default. Expanded assets require notification to the FCA and trigger additional requirements.
Core Backing Assets (default, all issuers)
- On-demand bank deposits at regulated credit institutions
- Government debt instruments maturing within one year (e.g. UK Treasury bills, gilts)
Expanded Backing Assets (notification required)
- Longer-duration government bonds (e.g. 5-year gilts)
- Public Debt Constant Net Asset Value (PDCNAV) money market funds
- Repo and reverse repo instruments
Issuers using expanded assets must comply with the Backing Asset Composition Ratio (BACR) — a dynamic, rolling calculation that sets a floor on how much of your pool must remain in core (liquid) assets at all times. This prevents issuers from chasing yield through duration extension without holding adequate liquidity to meet redemptions.
The Five Reserve Layers: A CFO's View
Here is where founders typically underestimate the capital commitment. The 1:1 backing pool is just the first of five distinct layers of reserves and capital that the regime requires. Each layer serves a different purpose and sits in a different place on your balance sheet.
Layers 1–3 sit inside the backing pool and are counted toward the 1:1 ratio. Layers 4 and 5 sit on the issuer's own balance sheet, funded by equity or retained earnings, and are entirely separate from — and additional to — the pool.
Layer 2: The ODDR
Regardless of what you hold in the rest of your pool, at least 5% must be held in on-demand bank deposits at all times. This is not a rolling average or a target — it is a hard floor that applies to every issuer on every day.
The purpose is straightforward: the FCA wants to ensure you can meet a redemption wave without needing to access markets. A 5% ODDR means that if you have £100m of tokens in issuance, £5m must be sitting in same-day accessible bank accounts at all times, regardless of what the rest of your portfolio looks like.
Layer 3: The BACR
If you use expanded backing assets, you must maintain a minimum proportion of your pool in core assets. This proportion is not fixed — it is calculated from your own redemption data:
- Peak DRA: your peak estimated daily redemption amount over the next 14 redemption days
- CBAR: a calibration buffer derived from 180 days of forecast versus actual redemption variance
- Minimum core asset % = (Peak DRA + CBAR) ÷ total pool value
This calculation is recalculated every 14 redemption days. In practice, it means you need a robust redemption forecasting model from day one — this is not something you can build retrospectively. The 180-day CBAR means the FCA expects you to have at least six months of operational data before the ratio stabilises.
Layer 4: The ILAR
This is the requirement that most founders miss entirely — and the one that is most likely to be a material gap in your financial model.
Non-cash backing assets carry mark-to-market price risk. If a gilt in your pool falls in value overnight, you have a shortfall against your 1:1 requirement. The FCA requires you to top that up by T+1 using your own resources. The ILAR is the liquidity buffer you must hold on your own balance sheet to fund that top-up.
The ILAR is calculated by applying haircut rates to each non-cash asset in the pool:
The ILAR is held in on-demand deposits on the issuer's own balance sheet, in the reference currency. It is not counted toward the 1:1 pool. It is equity at risk.
Pool: £3m on-demand deposits + £5m 3-month gilts + £2m 5-year gilts
ILAR = (£5m × 0.2%) + (£2m × 3.5%) = £10,000 + £70,000 = £80,000
This £80,000 sits on your own balance sheet, in cash, at all times — not in the pool, not earning yield, and not counted toward authorisation capital.
Layer 5: The Own Funds Requirement
CP25/15 sets out the CRYPTOPRU prudential sourcebook, which governs the issuer's own capital position — entirely separate from the backing pool. The Own Funds Requirement (OFR) is the highest of three components:
Component 1 — Permanent Minimum Requirement (PMR)
A flat capital floor of £350,000 for stablecoin issuers, regardless of size. This aligns with existing e-money issuer minimums and is binding only for very small or new issuers.
Component 2 — Fixed Overheads Requirement (FOR)
One quarter of your previous year's relevant annual expenditure — roughly three months of operating costs. This is your wind-down buffer: enough capital to keep the firm operating while an orderly exit is executed. For a firm with £2m annual opex, the FOR is £500,000.
Component 3 — K-SII: Stablecoin in Issuance Factor
2% of the rolling 6-month average of stablecoin in issuance, calculated monthly with a 3-month lag. This is the binding constraint for any issuer of material size:
PMR of £350k binds
FOR may bind depending on opex
KFR binds
One further constraint: cryptoassets held by the firm on its own account are deducted from own funds. You cannot hold large crypto positions on your balance sheet and count them toward your OFR. Your capital must be in qualifying instruments — predominantly equity and retained earnings.
Redemption Rights and T+1 Settlement
Token holders have a statutory right of redemption at par. Operationally, this means:
- Valid redemption requests must be settled by the end of the next business day (T+1)
- Any shortfall identified in daily reconciliation must be topped up within one business day from the issuer's own resources
- Gating — suspending or limiting redemptions — is not permitted under normal operating conditions
- You must maintain a Contingency Funding Plan, tested annually, covering a range of stress scenarios
The T+1 requirement has direct implications for custody and settlement infrastructure. Your custodian arrangement must support same-day or next-morning liquidation of backing assets where necessary.
The September 2026 Timeline
The FCA's crypto roadmap sets out a clear sequence of events. Understanding where each element falls is essential for planning your authorisation programme:
The implication is stark: all three regulatory pillars — CP25/14 conduct, CP25/15 prudential, and SMCR governance — are simultaneous pre-conditions for authorisation. You cannot apply with partial compliance. You will need all three in place on day one of the gateway.
Watch for CP2: The ICARA Process
CP25/15 confirms that an Internal Capital Adequacy and Risk Assessment (ICARA) process — analogous to the ICAAP in banking — will be consulted on in CP2. This process may require issuers to hold capital and liquidity above the OFR minimums, based on their specific risk profile and wind-down plan.
In practice, this means your financial model must stress-test your capital position under a range of scenarios — rapid redemption events, asset price shocks, custodian failures — and demonstrate that you hold sufficient buffers above the regulatory floor in each case. The ICARA is where the FCA moves from prescriptive minimums to supervisory judgement, and it is where underprepared firms will be exposed.
What Founders Need to Do Now
If you are building toward the September 2026 gateway, the following are the highest-priority items for your finance function:
- Model all five capital layers — not just the backing pool. ILAR and OFR sit on your own balance sheet and must be funded by equity. Build them into your capital requirement projections from day one.
- Build your redemption forecasting model — you need 180 days of forecast versus actual data to calibrate the BACR. If you are not live yet, begin building the methodology now so it is ready on launch.
- Select your custodian early — the custody arrangement is a conduct requirement, not an operational preference. The FCA requires independence, segregation, and T+1 liquidation capability. This takes longer to structure than most founders expect.
- Stress-test your funding structure — model what happens to your ILAR and OFR if (i) gilts fall 3% overnight, (ii) a single large holder redeems 15% of supply, or (iii) your custodian bank fails. These are the scenarios the ICARA will require you to cover.
- Engage your CFO function now — the finance complexity of this regime is material. The BACR, ILAR and ICARA all require ongoing CFO-level input, not a one-time implementation. If you do not have that capacity in-house, build it before you apply.
Key Takeaways
- The September 2026 authorisation gateway is a hard deadline. All three pillars — conduct, prudential, SMCR — must be met simultaneously at application.
- The 1:1 backing requirement is the floor. Five distinct layers of capital and liquidity are required on top of it.
- The ODDR (minimum 5% on-demand) and BACR (dynamic core asset floor) live inside the pool. The ILAR and OFR live on your own balance sheet, funded by equity.
- No yield pass-through is permitted. Your business model is the spread between backing asset yield and operating costs — not income shared with holders.
- The ILAR is the most commonly missing element in stablecoin financial models. Fix this early.
- CP2 will introduce the ICARA process, which may impose capital requirements above the OFR minimums. Plan for this in your stress scenarios.
