CPMC-5
CPMC-5
Safeguarding of customer funds (e-money/stored value/payment institutions) heading
Safeguarding of customer funds (e-money/stored value/payment institutions)
Whether customer funds are protected via mandatory segregation, property right or a spe…
Whether customer funds are protected via mandatory segregation, property right or a special insolvency regime
No meaningful safeguarding framework. No binding legal or regulatory provisions require…
No meaningful safeguarding framework. No binding legal or regulatory provisions require relevant non-bank financial providers holding customer funds to safeguard those funds through segregation, trust, escrow, insurance, guarantees, or an equivalent mechanism. No binding framework clearly addresses the treatment or return of customer funds if the provider fails or becomes insolvent. Digital Applicability Test: No safeguarding requirements clearly apply to customer funds held through digital wallets, e-money accounts, payment applications, or comparable digital financial products.
No regulated fintech provider is subject to binding customer-fund safeguarding requirem…
No regulated fintech provider is subject to binding customer-fund safeguarding requirements.
Customer funds are not subject to clear safeguarding or insolvency protections.
Customer funds are not subject to clear safeguarding or insolvency protections.
Limited or unclear safeguarding framework. Safeguarding requirements exist, but they ar…
Limited or unclear safeguarding framework. Safeguarding requirements exist, but they are narrow, fragmented, or unclear. They may apply only to specified products, providers, or account structures, or rely on general prudential, fiduciary, or licensing obligations without clearly establishing how customer funds must be protected. Requirements concerning segregation, reconciliation, eligible safeguarding assets, custodial arrangements, or treatment upon provider failure are limited or uncertain. Digital Applicability Test: Safeguarding requirements apply to selected providers or digital products, but their application to significant categories such as non-bank payment service providers, e-money issuers, digital wallets, or embedded-finance arrangements remains unclear or inconsistent.
Evidence is found only at Level 4, or Levels 1–3 contain limited provisions applying on…
Evidence is found only at Level 4, or Levels 1–3 contain limited provisions applying only to specific products, providers, safeguarding methods, or customer-fund arrangements.
Safeguarding requirements apply primarily to banks or to only one provider category, ex…
Safeguarding requirements apply primarily to banks or to only one provider category, excluding most non-bank fintech providers that hold or control customer funds.
Some safeguards exist, but their application, coverage, or effectiveness remains limite…
Some safeguards exist, but their application, coverage, or effectiveness remains limited or uncertain.
Established safeguarding framework with identifiable gaps. Binding rules require the pr…
Established safeguarding framework with identifiable gaps. Binding rules require the principal categories of regulated non-bank providers holding customer funds to protect those funds through segregation, trust, escrow, insurance, guarantees, or legally effective equivalent arrangements. The framework addresses core operational requirements, including reconciliation and restrictions on the use of safeguarded funds. However, identifiable gaps remain in provider coverage, the legal effectiveness or protective quality of permitted safeguarding mechanisms, eligible safeguarding mechanisms or assets, audit and reporting requirements, intermediary arrangements, or funds-in-transit coverage, legal protection upon provider failure, or procedures for returning funds to customers. Digital Applicability Test: Safeguarding requirements clearly apply to major categories of digital financial products or providers, but coverage or implementation is not consistent across all relevant payment service providers, e-money issuers, digital wallets, embedded-finance arrangements, or other regulated entities holding customer funds.
Binding requirements are found at Levels 1–3, but they remain incomplete in provider co…
Binding requirements are found at Levels 1–3, but they remain incomplete in provider coverage, requirements governing the applicable safeguarding mechanism or reconciliation, eligible safeguarding methods, audit and reporting obligations, intermediary responsibility, insolvency treatment, or procedures for returning customer funds.
Safeguarding requirements apply to several major regulated provider categories but excl…
Safeguarding requirements apply to several major regulated provider categories but exclude one or more significant types, or apply inconsistently across provider models, without a documented or otherwise verifiable risk-based justification.
Customer funds are generally protected under established safeguarding arrangements, but…
Customer funds are generally protected under established safeguarding arrangements, but important gaps remain in provider coverage, operational requirements, oversight, or insolvency treatment.
Comprehensive and operational safeguarding framework. Binding rules require all relevan…
Comprehensive and operational safeguarding framework. Binding rules require all relevant regulated non-bank providers holding customer funds to maintain clear and effective safeguarding arrangements. The framework establishes: separation of customer funds from the provider’s own assets through segregation, trust, escrow, insurance, guarantees, or another legally effective mechanism; where multiple safeguarding mechanisms are permitted, the framework establishes requirements sufficient to ensure that each provides substantively effective protection against the relevant risks, including shortfall, misuse, creditor claims, third-party failure, and delay in returning customer funds; requirements that account for material differences in provider legal status, regulated activity, and custodial structure, without allowing differences in entity form, custody model, or accounting treatment to create gaps in the identification, safeguarding, or return of customer funds; regular reconciliation of customer liabilities against safeguarded assets; restrictions on the use, investment, transfer, encumbrance, or commingling of safeguarded funds; requirements governing eligible safeguarding assets, accounts, custodians, insurers, guarantors, or equivalent arrangements; with proportionate treatment of materially different safeguarding risks where supported by a documented risk-based rationale; requirements addressing the failure of a bank, custodian, or other third party holding safeguarded funds, including where appropriate eligibility standards, concentration or diversification controls, legal segregation, and applicable deposit-protection, compensation, or recovery arrangements; clear allocation of responsibility among providers, custodians, partner banks, fintech interfaces, and other intermediaries; clear rules specifying when safeguarding obligations attach and cease as customer funds move through a payment chain, including which entity bears responsibility at each stage from receipt or control of the funds through delivery to the payee or transfer to another regulated provider subject to applicable safeguarding obligations, so that intermediary arrangements do not create material gaps in protection; governance, audit, reporting, recordkeeping, and supervisory requirements; clear requirements, where relevant, for providers to disclose to customers the nature and material limitations of applicable safeguarding arrangements, including whether customer funds are protected by safeguarding, deposit insurance, compensation arrangements, or another mechanism, and any material conditions or exclusions affecting recovery; and legally effective protection upon provider failure or insolvency, including a clear basis for identifying affected customers, determining their entitlements, protecting safeguarded assets from general creditor claims where applicable, and returning funds without unreasonable delay. The framework may use different legal mechanisms depending on the jurisdiction, provided those mechanisms offer substantively equivalent protection. Digital Applicability Test: Customer funds held through relevant digital products—including e-money accounts, digital wallets, payment applications, and embedded-finance arrangements—receive equivalent safeguarding protection regardless of the interface, distribution arrangement, or provider structure. Compliance is subject to supervisory oversight or enforcement. Operationalisation Requirement: A score of 3 requires publicly available or otherwise verifiable evidence that the safeguarding framework has been applied in practice to regulated providers holding customer funds. Evidence may include supervisory reviews, enforcement actions, thematic inspections, required independent audits, remediation of safeguarding shortfalls, insolvency guidance, tested customer-fund return procedures, or equivalent evidence. The evidence should demonstrate that supervisory authorities assess compliance with safeguarding, reconciliation, asset sufficiency, use restrictions, and arrangements for protecting and returning funds upon provider failure. A framework that establishes safeguarding requirements but lacks verifiable evidence of implementation should receive no more than a score of 2.
Comprehensive and enforceable safeguarding requirements are established through Levels…
Comprehensive and enforceable safeguarding requirements are established through Levels 1–3 and supported, where appropriate, by supervisory guidance. Pathways note: A Level 4 source alone cannot justify a score of 3. A score of 3 additionally requires evidence that the framework operates in practice through publicly available or otherwise verifiable supervisory reviews, enforcement actions, required safeguarding audits, shortfall-remediation findings, insolvency guidance, fund-return procedures, or equivalent operational evidence.
Safeguarding requirements apply consistently across all relevant regulated provider cat…
Safeguarding requirements apply consistently across all relevant regulated provider categories holding customer funds, including PSPs, e-money issuers, digital wallets, remittance providers, prepaid providers, and applicable embedded-finance arrangements. Any exclusions are explicitly documented, proportionate, and supported by a documented or otherwise verifiable risk-based rationale. Coder note - common applicability gaps: Common sources of below-3 scores include non-bank PSPs, e-money issuers, general-purpose digital wallets, remittance providers, prepaid products, crypto-asset or stablecoin arrangements where applicable, and embedded-finance or BaaS models where responsibility is unclear between the fintech frontend, bank partner, and custodian. Where one of these is the binding constraint, identify it in the evidence log. Risk-based exclusion: A score of 3 requires more than a formal carve-out. Coders should verify that any exclusion is supported by a documented or otherwise verifiable rationale tied to whether the provider holds customer funds, the nature of the safeguarding risk, or the availability of an equivalent protection mechanism. An exclusion lacking a documented or otherwise verifiable rationale, or a legacy omission, is an unexplained coverage gap and should receive a score of 2, not 3.
Customer funds are consistently protected through comprehensive safeguarding arrangemen…
Customer funds are consistently protected through comprehensive safeguarding arrangements, effective supervisory oversight, and clear rules governing the applicable safeguarding mechanism, reconciliation, protection upon provider failure, and the timely return of funds.
Primary Legislation: Payment services acts, e-money legislation, financial services act…
Primary Legislation: Payment services acts, e-money legislation, financial services acts, insolvency statutes, trust laws, and other primary legislation establishing requirements for the protection or preferential treatment of customer funds.
Binding Subordinate Legislation: E-money and payment regulations, legally binding safeg…
Binding Subordinate Legislation: E-money and payment regulations, legally binding safeguarding rules, licensing conditions, mandatory segregation and reconciliation requirements, eligible-asset restrictions, audit and reporting requirements, and binding rules governing the treatment of customer funds in insolvency.
Binding Supervisory Requirements: Enforceable regulatory directives, notices, circulars…
Binding Supervisory Requirements: Enforceable regulatory directives, notices, circulars, safeguarding standards, supervisory codes, or guidelines incorporated into regulation or otherwise subject to supervisory enforcement, including requirements concerning custodians, safeguarding accounts, shortfall remediation, audits, and fund-return procedures.
Non-Binding Guidance: Regulator guidance, supervisory expectations, safeguarding FAQs,…
Non-Binding Guidance: Regulator guidance, supervisory expectations, safeguarding FAQs, best-practice materials, thematic review findings, insolvency guidance, and other non-binding explanations of expected safeguarding arrangements.
protection, legal certainty, and operational coverage—not whether providers appear fina…
protection, legal certainty, and operational coverage—not whether providers appear financially stable.
Scope Note – Narrower Approach (Proposal):
Scope Note – Narrower Approach (Proposal):
This indicator assesses customer funds held or controlled by regulated non-bank financi…
This indicator assesses customer funds held or controlled by regulated non-bank financial providers. It does not independently assess custody of securities, crypto-assets, investment assets, or other customer property. Providers such as custodians, trust entities, or digital-asset service providers should be assessed only to the extent that they hold, receive, control, or safeguard customer funds. Broader customer-asset protections could be addressed through a separate indicator or future expansion of the framework.
Objective requirements:
Objective requirements:
Replace subjective descriptions such as “strong safeguarding” with objective requiremen…
Replace subjective descriptions such as “strong safeguarding” with objective requirements, including segregation or an equivalent protection mechanism, regular reconciliation, restrictions on the use of customer funds, eligible custodian or asset requirements, clear insolvency treatment, procedures for returning funds, and publicly available or otherwise verifiable supervisory or enforcement evidence.
Entity Structure and Accounting Treatment:
Entity Structure and Accounting Treatment:
Assessors should account for differences in provider legal status, regulated activity,…
Assessors should account for differences in provider legal status, regulated activity, and custodial structure, including payment institutions, e-money issuers, money transmitters, trust entities, custodians, wallet providers, and comparable entities. Neither regulatory classification nor accounting presentation should independently determine the score. Whether customer funds are treated as a provider liability, trust property, custodial property, client money, or another legally recognized interest, assessors should focus on the substantive protections provided, including customer entitlement, segregation, reconciliation, restrictions on use, creditor protection, and return upon provider failure.
Provider and product gaps:
Provider and product gaps:
Common sources of below-3 scores include non-bank PSPs, e-money issuers, general-purpos…
Common sources of below-3 scores include non-bank PSPs, e-money issuers, general-purpose digital wallets, remittance providers, prepaid products, crypto-asset or stablecoin arrangements where applicable, and embedded-finance or BaaS models. In embedded arrangements, coders should determine which entity is legally responsible for safeguarding and whether customers retain protection if the fintech frontend, bank partner, or custodian fails. Identify the binding coverage gap in the evidence log.
Funds-in-Transit / Payment-Chain Coverage:
Funds-in-Transit / Payment-Chain Coverage:
In multi-entity payment arrangements, assess whether binding rules identify when custom…
In multi-entity payment arrangements, assess whether binding rules identify when customer funds become subject to safeguarding, which entity is responsible while the funds are in transit, and when that responsibility legally terminates or passes to another entity. A framework should not receive comprehensive credit where transfers between PSPs, banks, custodians, processors, or other intermediaries create an identifiable period in which no entity bears clear responsibility for safeguarding the customer funds.
Safeguarding Mechanism- Effectiveness:
Safeguarding Mechanism- Effectiveness:
Safeguarding mechanisms should not receive equivalent credit solely because they are le…
Safeguarding mechanisms should not receive equivalent credit solely because they are legally permitted. Assess the substantive protection provided by the mechanism, including whether it covers the full customer-fund liability, limits shortfall and counterparty risk, prevents unauthorized use or encumbrance, remains legally effective upon failure or insolvency, and permits timely return of customer funds. Different mechanisms may receive equivalent treatment where they demonstrably achieve substantively equivalent protection.
Safeguarding Mechanisms and Insolvency:
Safeguarding Mechanisms and Insolvency:
Segregation, trust accounts, escrow, insurance, guarantees, and comparable mechanisms s…
Segregation, trust accounts, escrow, insurance, guarantees, and comparable mechanisms should not automatically be treated as equivalent. Assess whether the arrangement covers the full customer-fund liability, prevents use for the provider’s own purposes, is regularly reconciled, and remains legally effective upon failure or insolvency. This assessment should distinguish failure of the regulated provider from failure of a bank, custodian, or other third party holding or administering the safeguarded funds. A general safeguarding obligation is insufficient for a comprehensive score if customer entitlements, creditor protection, administration of the return process, or the treatment of shortfalls, fees, and delays remains unclear. No particular legal mechanism is required where another arrangement provides substantively equivalent protection.
Risk-Proportionate Safeguarding:
Risk-Proportionate Safeguarding:
Safeguarding requirements may vary according to the nature and duration of the provider…
Safeguarding requirements may vary according to the nature and duration of the provider’s control over customer funds and the risks presented by the relevant product, transaction, or intermediary arrangement. The indicator does not require identical safeguarding measures for all categories of customer funds. Where a jurisdiction applies less intensive requirements, exemptions, or alternative mechanisms to particular categories of funds, assessors should determine whether the distinction is supported by a documented or otherwise verifiable risk-based rationale and whether the resulting arrangement continues to provide protection proportionate to the customer’s exposure. Product labels alone should not determine the score.
Consumer Transparency:
Consumer Transparency:
Assess whether binding rules require customers to receive clear and accurate informatio…
Assess whether binding rules require customers to receive clear and accurate information concerning the protection applicable to their funds, including the nature of the safeguarding arrangement, material limitations or exclusions, the applicability or non-applicability of deposit insurance or compensation schemes, and relevant procedures for recovering funds following provider or safeguarding-institution failure. Disclosure should complement, rather than substitute for, substantive safeguarding protections. A provider should not receive additional safeguarding credit merely because risks are disclosed where the underlying protections are inadequate.
Where a jurisdiction scores below 3, distinguish between: (a) a regulatory-design gap,…
Where a jurisdiction scores below 3, distinguish between: (a) a regulatory-design gap, where binding rules do not cover a provider, product, safeguarding method, intermediary arrangement, or insolvency issue; and (b) an operational gap, where rules formally require safeguarding but reconciliation, audits, shortfall remediation, supervisory monitoring, or fund-return procedures are inconsistent in practice. Record which failure mode applies in the evidence log.
Operational evidence:
Operational evidence:
A score of 3 should be supported by evidence that safeguarding requirements are activel…
A score of 3 should be supported by evidence that safeguarding requirements are actively implemented, such as supervisory reviews, enforcement actions, required independent audits, publicly available or otherwise verifiable shortfall findings, insolvency guidance, or documented customer-fund return procedures. The absence of provider failure should not itself establish that the framework is operational.
AI-enabled safeguarding and fund management:
AI-enabled safeguarding and fund management:
Existing safeguarding frameworks generally apply regardless of whether providers use AI…
Existing safeguarding frameworks generally apply regardless of whether providers use AI to monitor balances, reconcile accounts, detect shortfalls, select safeguarding assets, or manage fund movements. Coders should assess whether providers remain legally accountable for the applicable safeguarding mechanism, reconciliation, asset sufficiency, shortfall remediation, and protection upon provider failure when these functions are automated or outsourced to AI-enabled systems. Do not penalize jurisdictions solely for lacking AI-specific safeguarding rules at this stage, but flag silence on automated control failures, human oversight, auditability, third-party accountability, and operational resilience as a v1.1 improvement item.
Safeguarding: CPMC scores the substantive adequacy of customer-fund protection; RCC sco…
Safeguarding: CPMC scores the substantive adequacy of customer-fund protection; RCC scores the clarity and findability of the safeguarding rulebook; RI scores the operational resilience of safeguarding arrangements. (CPMC module, Section 8 — section borrowed from the RI module pending a CPMC-drafted version.)