Five-layer unbundling of central-banking functions
ConfidenceLikelyUpdated2026-08-14Review by2026-11-12Sources9Machine-translatedOriginal (JA)
On this page
Wiki route
This entry sits under fintech index. Read it against US/EU/Japan stablecoin market-access comparison for peer and contrast context, and Japan’s financial-regulation framework for tokens, cryptoassets, and payments for the broader system and regulatory boundary.
[!info] TL;DR The “five layers” in this entry are an analytical taxonomy that separates a monetary and payment system into (1) the sovereign unit of account and monetary anchor, (2) liabilities and assets used for settlement, (3) messaging, clearing, and settlement infrastructure, (4) identity, access, and compliance operations, and (5) policy, supervision, legal enforcement, and technical controls. It is not a factual claim that central banks historically provided all five layers as one bundle, that four layers have been privatized since 2022, or that they will be replaced by a particular year. In the two-tier monetary system described by the BIS, central bank money, commercial-bank deposits, and private services divide responsibilities; central banks, commercial banks, PSPs, and private networks can overlap within the same function.
Using the five functions as an analytical taxonomy
| # | Function under analysis | Institutional role established by public materials | Evidence boundary |
|---|---|---|---|
| 1 | Unit of account and monetary anchor | The BIS explains that the central bank issues the economy’s unit of account and that trust in central bank money supports the singleness of money | Privately issued deposits, e-money, and stablecoins can also be denominated in a sovereign currency. Do not conflate use of the denomination with the issuer or legal liability |
| 2 | Settlement liability and settlement asset | Central bank reserves, commercial-bank deposits, cash, regulated e-money, and tokenized money give holders claims against different issuers | Do not treat “digital,” “tokenized,” or “1:1” as establishing the same credit risk, redemption right, deposit insurance, or settlement finality |
| 3 | Messaging, clearing, and settlement rails | Central banks, private operators, banks, and PSPs may operate or connect different segments such as RTGS, instant payments, clearing, cards, messaging, and DLT | Separate front-end transfer, message delivery, clearing, and final settlement; do not treat connectivity or an experiment as production adoption |
| 4 | Identity, access, and compliance operations | Banks and regulated PSPs perform onboarding, KYC / AML, transaction monitoring, and permission management according to applicable law and customer relationships | Identity technology, wallet permissions, bank KYC, and legal customer-due-diligence duties are distinct. Do not determine regulatory compliance from protocol specifications alone |
| 5 | Policy, supervision, legal enforcement, and technical controls | Central banks, supervisors, sanctions authorities, law-enforcement agencies, and regulated firms have different legal powers and duties. Private issuers / networks may also have freeze, denylist, and upgrade keys | Do not equate a private technical control with sovereign enforcement power; identify the authority, legal basis, scope, appeal mechanism, and audit trail |
Sources: BIS Annual Economic Report 2023, Chapter III, BIS central banks and payments report, structure and functions of the Federal Reserve System, IMF fintech topic, and BIS CPMI. These sources describe public- and private-sector roles and the scope of payments, market infrastructures, and fintech; they do not establish a historical five-layer “bundle” or the privatization of four layers.
Evidence checklist for testing a claim
| Analytical question | Primary evidence required | Inference to avoid |
|---|---|---|
| Whose liability is it? | Statute, product terms, and issuer financial / reserve disclosures | Treating instruments as the same money merely because they use the same currency denomination or chain |
| Where does final settlement occur? | System rulebook, central-bank / operator materials, and the legal status of the ledger / account | Equating processing speed, block finality, or message completion with legal finality |
| Who operates and changes the infrastructure? | Governance documents, validators / operators, upgrade keys, incident procedures, and SLA | Inferring control of the full workflow or production integration from an acquisition, partnership, or PoC alone |
| Who may use it and who bears compliance duties? | Terms of use, registrations / licenses, customer eligibility, KYC / AML, sanctions, and monitoring procedures | Inferring legal compliance or supervisory approval from a “permissioned” technical label |
| What explains a change over time? | Dated disclosures using consistent definitions and periods, decision materials, and a causal explanation from the parties | Constructing a single 2022 trigger from the co-occurrence of interest rates, sanctions, and an AI release, or stating a 2030 outcome as fact |
Source note: the table is the analytical procedure used in this entry. Refer to the preceding BIS / Federal Reserve / IMF / CPMI materials for institutional roles and add each operator’s primary materials for a specific product.
The years 1944, 1971, 2008, and 2022 may each provide important historical context, but the sources cited here do not establish a linear causal timeline in which five layers were bundled and then separated. Add primary evidence for each event, institution, and function before making a historical claim.
Overlapping roles by type of actor
| Actor | Functions that may overlap | Boundary to verify |
|---|---|---|
| Central bank | Unit of account, central-bank liabilities, RTGS / settlement services, financial stability, and payment-system oversight | The mandate and actual operating scope in each jurisdiction. A central bank does not necessarily perform customer KYC or operate a private network |
| Commercial bank | Deposit issuance, settlement access, customer onboarding, KYC / AML, and payment services | Connection to central bank money, the depositor’s claim, participant eligibility, operating hours, and final settlement |
| PSP / fintech | Customer interface, payment initiation, routing, wallets, and KYC / monitoring for regulated activities | Whether the firm is an issuer or intermediary, whether it holds funds, and which rail and settlement asset it depends on |
| Private network / protocol | Message transport, ledger, validators, smart contracts, and token controls | Legal operator, governance, upgrade / freeze powers, external settlement, and the allocation of responsibility with regulated firms |
This table does not rank actors by strength or prescribe an integration sequence. In practice, one actor may perform several functions, while several actors may jointly provide a single function.
Verification examples using public products
| Product / provider | What official materials establish | Evidence boundary this entry does not cross |
|---|---|---|
| Coinbase / Base | Base is an Ethereum L2 incubated within Coinbase. Coinbase’s official description says ETH is the gas token and that there are no plans to issue a new Base network token. USDC is available on Base but is issued by Circle | Do not equate Coinbase customer verification and regulatory obligations with chain-level enforcement across every application on Base |
| Stripe / Bridge | Stripe announced that it completed the Bridge acquisition on 2025-02-04. This shows integration of stablecoin infrastructure with Stripe’s payment and merchant rails. Related analysis | The acquisition announcement alone does not prove “USDB” issuance, OCC approval, or a uniform KYC / enforcement scope for all users |
| Circle / Arc | Circle issues USDC and announced Arc as an open EVM-compatible L1 in 2025, launching its public testnet in October of that year | Issuer, chain, and regulatory applications are separate questions. Do not infer approval status or a statutory denylist requirement from Arc’s technical description |
| J.P. Morgan / Kinexys | J.P. Morgan’s current official page describes JPM Coin as a USD-denominated bank deposit token issued on Base, an Ethereum Layer 2, for vetted institutional clients and 24/7 settlement. Related JPM Coin / JPMD note | Do not infer from this specific product that every deposit token is issued on a public chain, has the same access conditions, or belongs in the same legal category as a stablecoin |
Sources: Coinbase’s description of Base, Stripe’s announcement that it completed the Bridge acquisition, Circle’s Arc announcement, and J.P. Morgan’s description of JPM Coin. This table is a verification map of public product surfaces, not a ranking or list of regulatory approvals.
“Layer coverage” in this framework is not a score of market control, sovereignty, authorization, legal advantage, or investment attractiveness. For a commercial-bank deposit arrangement such as JPM Coin, identify the issuer liability and access conditions rather than automatically placing it in the same regulatory category as a stablecoin.
Application procedure
- Record the product’s unit of account, issuer liability, and redemption right first
- Do not combine messaging, clearing, settlement, and finality into one “rail”; identify each operator and rulebook
- Track onboarding, KYC / AML, sanctions handling, wallet / key controls, and legal-enforcement authority in separate fields
- Do not treat a PoC, testnet, completed acquisition, commercial launch, and regulatory approval as the same maturity state
- Compare the same reference date, jurisdiction, and user scope; require party materials and additional evidence for causation or forecasts
Related
- five-pole geopolitical conflict
- OCC charter arbitrage
- US/EU/Japan stablecoin market-access comparison
Discovery
Keep reading
Read next
- CFTC vs SEC Crypto Jurisdiction Dispute · Commodity-Security DichotomyImpact on issuers: BTC/ETH ETF issuers (BlackRock / Fidelity) benefit from CFTC pathway clarity; new token issuance no longer necessarily requires navigating SEC registration hell → Atkins'...
- Chain-Level OFAC Freeze = Dollar Chain-Level Hegemony1. Issuer-level blacklist: blacklisted[address] mapping in the USDC contract 2. Chain-level denylist: GENIUS §501 mandatory chain-level denylist — issuers must be able to execute address fre...
- Circle USDC · Compliant White-Circle Benchmark · NYSE-Listed Issuer · CCTP / BUIDL InterlockUSDC's core model = the "white-circle compliance benchmark": 100% short-term Treasury reserves + monthly audit + Reserve Fund segregation + monthly CUSIP-level public report. This contrasts...
Links here
- Commoditization of Agent payment protocols and the upward migration of valueAfter protocol commoditization, take rate cannot be extracted from an open-source standard (one cannot levy an HTTP-protocol fee). Value capture is forced to migrate upward to vertical distr...
- AI Agent payment protocols overview · a 7-protocol surveyThe 7 protocols divide labor by layer. The intent layer (where the user expresses "I want to buy Y for X yen") is handled by AP2 / SPT / ACP, which process the mandate's 3-layer trust chain...
- 2022 年 three-variable cascade1. The end of the zero-interest-rate era (lasting 14 years) — released the suppressed room for financial innovation 2. The end of the post–Cold War order (lasting 30 years) — unlocked politi...
- Apollo ACRED · Private Credit Tokenisation · Independent Strategic Position of a Second-Tier MMFACRED is strictly not a MMF — the tokenised vehicle is the Apollo Diversified Credit Fund, covering corporate direct lending + asset-backed lending + performing/distressed credit + structure...
- BIS Project Agorá OverviewAgorá's architecture is not a single blockchain; rather, the BIS provides a "coordination-layer specification." It experiments with a two-tier structure in parallel: central banks issue whol...