Consultation · BMA · 29 Aug 2025
The proposed Payment Services Act would repeal the Money Service Business Act 2016 and license payment service providers, including Digital Facility Providers, Payment-Handling Providers and Payment Technology Providers. Existing MSB licence-holders would be grandfathered with a one-year grace period, while firms newly in scope must apply within six months of the Act coming into force. Comments are due by 13 October 2025.
Friday, 29 August, 2025
BMA
BERMUDA MONETARY AUTHORITY
CONSULTATION PAPER
Comments to be received by 13 October 2025
Contents
I. INTRODUCTION ............................................................................................................................... 3
II. BACKGROUND ................................................................................................................................. 4
III. DISCUSSION PAPER FEEDBACK.................................................................................................... 4
IV. KEY PROPOSALS.......................................................................................................................... 8
A. SCOPE OF APPLICABILITY............................................................................................................. 8
B. PSP BUSINESS ACTIVITIES............................................................................................................ 8
Digital Facility Provider (DFP)........................................................................................................... 8
Payment-Handling Provider (PHP).................................................................................................... 9
Payment Technology Providers (PTP)............................................................................................. 10
C. LICENSING................................................................................................................................. 12
D. EXCLUSIONS AND EXEMPTIONS ................................................................................................ 14
E. CONSEQUENTIAL AMENDMENTS .............................................................................................. 15
F. FEES.......................................................................................................................................... 15
G. REGULATORY FRAMEWORK...................................................................................................... 15
H. NEXT STEPS............................................................................................................................... 16
1. In April 2025, the Bermuda Monetary Authority (Authority or BMA) released a Discussion Paper (DP) inviting feedback on proposals to modernise Bermuda's approach to payment services. The primary objective was to introduce a new legislative framework: the Payment Services Act (PSA). The DP aimed to solicit feedback on this regulatory framework to facilitate adequate supervision of this rapidly evolving sector.
2. Stakeholder feedback submitted in response to the prior DP has informed clarifications and revisions to the newly proposed PSA regime. This Consultation Paper (CP) reflects stakeholder input and provides additional technical information to support further industry engagement.
3. Given the significance and complexity of introducing an entirely new legislative and regulatory architecture, it is essential that relevant stakeholders further participate in the consultation process. The aim is to collect feedback and foster a thorough understanding of the range of risks and benefits associated with modern payment systems, ensuring that the proposed legislative framework is robust, balanced and fit for purpose.
4. The proposed framework introduces a spectrum of regulatory requirements that will apply to entities operating under the new regime proportionate to the nature, scale and risk profile of their activities. These requirements are intended to ensure the integrity and resilience of the financial ecosystem. They will include areas such as Anti-Money Laundering and Anti-Terrorist Financing (AML/ATF), conduct of business standards and prudential and cyber risk management. Additional requirements may also apply depending on the entity’s business model, including those relating to operational resilience, safeguarding customer data and governance.
5. The proposed PSA does not require a licence from operators of system-level payment infrastructures, such as interbank messaging networks, card schemes, real-time gross-settlement platforms or base-layer decentralised protocols, where their activities are limited to providing connectivity, messaging, standard-setting, security. They do not: (a) accept, hold, control or settle customer funds; (b) provide payment accounts; or (c) act as payer or payee, or as agent for either party, in a payment transaction.
6. The proposed PSA will repeal the Money Service Business Act 2016 (MBS Act) and establish a new regulatory framework with an expanded scope of licensable activities. Money Service Business (MSB) licence‑holders will be grandfathered into the new PSA regime and granted a one‑year grace period to comply with all applicable statutory and regulatory requirements under the PSA framework. During this transition, each MSB’s licence will be restricted to its existing business line(s). Firms that are currently operating outside the scope of the MSB, but fall within the scope of the PSA, will be required to submit a licence application within six months of the PSA coming into force. Once an application is submitted, these firms may continue to operate pending a decision on their application.
7. Industry and other stakeholders are invited to provide feedback on the proposals outlined in this CP and its attachments by emailing their comments to fintech@bma.bm by the close of business on 13 October 2025.
8. The payments landscape is rapidly transforming as technology integrates with financial services, introducing new business models and enhancing user experiences. This shift necessitates a modern regulatory framework that addresses the complexities of this hybrid sector. Domestically, a unified payments framework can enhance customer protection and enable secure, efficient transactions. Globally, it can foster sustainable practices and innovation aligned with international trends.
9. Accelerated by post-COVID digitisation and changing customer behaviours, demand for seamless, real-time payments is rising, while reliance on cash and cheques declines. New market entrants offering digital wallets and platform-based solutions are improving payment accessibility and convenience. As more financial interactions move online, secure and efficient payment systems, supported by strong governance and risk management, are essential for safe, innovative transactions.
10. Given the rapid pace of technological advancements, the existing MSB Act is no longer fit-for-purpose to address the needs of the dynamic financial services industry. Updating the framework is crucial to support innovation responsibly, strengthen customer protection against new and emerging risks, and establish clear and consistent guidelines for Payment Service Providers (PSPs).
11. By proposing a new framework for PSPs, the Authority aims to balance innovation, trust and safety. The objective is to tailor regulation that considers the current payments industry landscape, protects customers, safeguards the financial systems and improves regulatory efficiency.
12. The feedback underscores the need for a more precise delineation between the scope of the proposed new PSA and the existing DABA, particularly where firms may engage in overlapping activities such as custody or the handling of digital assets used in payments.
13. While some jurisdictions define stored value facilities as money, potentially excluding digital assets, this distinction is blurring with the rise of stablecoins.
The proposed framework will streamline licensing for payment business models and provide exemptions for DABA-licensed firms that conduct issuance or payment activities in relation to the transfer of funds1 . It also allows seamless transitions for firms evolving to require DABA licensing.
14. The Authority confirms that all activities currently regulated under the MSB framework will be brought under the scope of the proposed PSA. This integration is intended to align regulatory requirements, improve clarity for market participants and consolidate the regulation of payment services within a single, coherent legislative framework.
15. Some respondents requested further clarification on the scope of the DWP (subsequently referred to as Digital Facility Providers (DFPs)). This has been further clarified in this CP (refer to the DFPs section of the CP).
16. Some stakeholders suggested that closed-loop payment systems, such as internal corporate treasury operations, payroll systems or affinity/reward programmes should be explicitly excluded or exempted from the proposed regime. In response, the Authority clarifies that payment transactions and related services (including currency conversion and payment aggregation) conducted solely within a corporate group may be exempted, provided these activities are strictly internal group treasury management functions such as ‘self-to-self’ transactions). For example, between a parent company and its subsidiaries or between subsidiaries under common ownership and control.
17. However, this exemption is narrowly drawn and does not extend to intra-group arrangements that, in substance, facilitate payment services for external clients.
18. The Authority may apply a look-through approach to determine the true economic purpose and beneficiary of the arrangement. For instance, if a parent company sets up an internal payment system to process travel reimbursements for its employees across subsidiaries, this may fall within the exemption. However, if the group’s travel subsidiary uses that same system to settle payments on behalf of third-party clients (e.g., corporate customers booking flights through a group travel agency), the Authority may ‘look through’ the intra-group structure and determine that the activity serves external clients. This will bring it within the scope of the regulatory regime. In contrast, other closed-loop or limited network systems, such as retailer gift cards or loyalty point schemes, will be considered on a case-by-case basis, considering factors like:
I. Whether the system has access to or control over customer funds;
II. The volume and value of transactions processed;
III. The interoperability with other payment systems or external merchants; and
[1] Funds in this CP are intended to capture fiat, electronic money and stablecoins.
IV. The potential consumer exposure or reliance on the service.
This approach ensures proportional oversight without unduly capturing low-risk, internal or limited-scope activities.
19. Some feedback suggested refining the definition of PHPs to explicitly exclude decentralised protocols (e.g., blockchain infrastructure), unless a specific legal entity exercises control, custody or discretion over funds, similar to traditional PHPs. The Authority agrees with this proposed refinement of the definition, and further details have been provided in this CP (refer to the PHPs section of the CP).
20. The Authority reaffirms the purpose of the PTPs category as capturing entities that do not hold and/or have access to funds. However, to address the feedback received from the DP, refinements to the scope of the PTP category are being proposed. To provide greater clarity, the Framework will not include decentralised infrastructure providers in its scope, such as blockchain node operators, protocol developers, non-commercial AI-driven agents and smart-contract developers. This is to ensure that these entities are not inadvertently included under the PTP definition solely due to their technical roles. Instead, the PTP category will focus on commercial entities, such as wallet frontends, custodial interfaces and payment APIs, that are integral to payment transactions and/or infrastructure. Additionally, the Framework will follow a technology-neutral approach to applying consistent principles across all payment networks, including blockchain-based infrastructures, thereby avoiding any unintended double standards.
21. While stakeholders generally support the PG licence, concerns were raised about potential barriers for institutional-facing providers, such as FinTech startups, due to disproportionate compliance expectations. The Authority reaffirms its commitment to establishing a fit-for-purpose regulatory framework that recognises the distinct characteristics of certain PSPs (further details in this CP). This applies particularly to those operating at materially higher transaction volumes that serve only institutional or non-retail clients and present a differentiated risk profile. Firms can apply directly for the PG licence without progressing through T and M licences. The Authority welcomes feedback to ensure that the proposed PG licence effectively supports innovation, promotes market efficiency and appropriately manages the associated risks.
22. The Authority intends to establish an AI Payments Hub to respond to stakeholder feedback regarding the appropriate regulatory treatment of DeFi intermediaries, AI-driven payment arrangements and embedded or programmatic payment solutions.
23. The proposed AI Payments Hub builds on and integrates with the Authority’s existing Innovation Hub. This Hub has served as a key platform for supporting early-stage regulatory dialogue and responsible experimentation in insurance, digital assets and RegTech solutions. Like past initiatives facilitated through the Innovation Hub (e.g., the exploration of parametric insurance, embedded supervision and blockchain-enabled compliance tools), the AI Payments Hub will provide a structured yet flexible environment for assessing novel technologies that may fall outside existing regulatory classifications. By leveraging the Authority’s established experience in guiding innovation through pre-licensing engagement and cross-sector collaboration, the AI Payments Hub aims to extend these capabilities into the payments domain, addressing new challenges and opportunities arising from the integration of AI in financial services.
The AI Payments Hub is not envisioned as a sandbox or testbed but as a collaborative platform to support responsible innovation, identify and manage emerging risks, and guide the ethical and secure adoption of AI in the payments sector. Its purpose is to promote a future-ready payments ecosystem by facilitating engagement across regulators, industry and academia. In addition to fostering innovation, the AI Payments Hub will explore mechanisms to enhance user protection in the context of digital payments, including those involving stablecoins. This may include assessing the feasibility of applying controls to mitigate risks such as fraud, error or unauthorised transactions. Examples of such controls include the chargeback-like mechanisms used in traditional card payments.
24. To finalise the scope, structure and priorities of the AI Payments Hub, the Authority will undertake further consultation in the near future. This will ensure that the Hub’s development is informed by broad stakeholder input and aligned with both domestic needs and evolving international standards. The AI Payments Hub would operate as a specialised initiative within the Authority’s existing Innovation Hub framework, leveraging its flexible, pre-licensing environment to support the responsible exploration, testing and development of AI-driven payment solutions in close collaboration with industry stakeholders.
Q1. Do you see value in the establishment of an AI Payments Hub. Do you agree with the proposed scope and objectives?
Q2. What do you think the areas of focus for consumer protection should be in the context of digital payments?
25. The Authority acknowledges the feedback received on the need to distinguish between the commercial services offered by AI-driven payment agents and general-purpose AI tools. Additional input included the suggestion to provide oversight of DeFi intermediaries, such as swap or yield aggregators, without regulating public infrastructure or self-executing smart contracts. Respondents also highlighted the importance of addressing programmable payments, particularly where developers provide enabling infrastructure without retaining control, and called for greater clarity on cross-border remittances, multi-currency payment orchestration and embedded or programmatic payment solutions in support of globally active digital asset firms. These areas of emerging complexity will be further examined through the AI Payments Hub initiative, which aims to support responsible innovation while ensuring appropriate regulatory outcomes.
26. Under the proposed PSA, any person conducting payment services business in or from within Bermuda will be considered to be carrying on PSP business. This includes entities incorporated or formed in Bermuda, as well as foreign entities engaging in PSP activities within Bermuda, as defined under the PSA.
27. Previously referred to in the DP as Digital Wallet Providers (DWPs), DFPs offer payment facilities that store funds, either digitally or on a physical device. Users prepay these funds and use the technology to make purchases for goods or services. These facilities may also include stablecoins2 designed primarily for payments, settlements or serving as a store of value.
28. DFPs encompass entities that provide end-user-facing applications or services, enabling users to store, manage and initiate payments in fiat or stablecoins. DFPs may include issuing payment instruments (e.g., physical/virtual cards or any other device that could be used for payment purposes).
29. The following attributes detail the definition of DFPs in the context of the proposed PSA:
I. DFPs issue and administer payment facilities to make payments, transfer or store pre-paid funds;
II. Customers using DFPs have flexibility in using the stored funds for multiple purposes, such as purchasing goods or services or processing payments and settlements; and
III. Funds stored in DFPs can be held in various forms and platforms. They can be stored in online accounts or embodied in physical or virtual devices (e.g., virtual cards), offering a broad spectrum of service channels to users.
30. For clarity, the following are not considered DFPs under the proposed PSA:
I. Gift and/or loyalty digital facility providers (including gift and store cards/vouchers); and
II. Providers of facilities that store value, such as debentures or interests in managed investment schemes, which are not compatible with payment transactions.
[2] As further referenced above, stablecoins fall within the ‘funds’ definition.
A Digital Facility Provider is any undertaking that issues, maintains and administers a payment facility to end users by receiving funds (stored electronically or on a physical device) used for making payments, transferring funds or withdrawing stored funds at a future point in time, including:
1. Issuing or redeeming stablecoins;
2. Custodial wallet services solely related to a stablecoin issuer’s own stablecoin: in this context, any undertaking that would like to provide custody to third-party stablecoins, or any other digital asset, should seek a digital asset business licence;
3. Issuing of payment instruments;
4. Cashing cheques made payable to customers and guaranteeing cheques;
5. Issuing, selling or redeeming drafts, money orders or traveller’s cheques for funds; and
6. Operating a bureau de change.
Q3. Do you agree with the scope of the ‘DFPs’ activity as it is defined? Are there any services that have not been captured by the definition that should be included (or that are included but, in your view, should not be)?
31. PHPs are entities involved in receiving and transferring funds from payers, primarily for the purpose of transmitting equivalent amounts to designated payees. These providers handle, process or directly manage funds.
32. This category does not apply to businesses for which the receipt of funds is merely incidental to their primary function, such as legal, accounting, courier or delivery services. The following non-exhaustive examples are provided to illustrate cases where the receipt of funds is incidental to a business’s primary function and does not constitute a standalone payment service:
I. Law Firms – holding client funds in trust (or escrow) for settlements (e.g., property transactions);
II. Accountants – receiving tax refunds on behalf of clients in the course of providing tax services;
III. Couriers/Delivery Services – collecting cash on delivery and remitting it to merchants;
IV. Property Managers – collecting rent for landlords as part of property management; and
V. Event Planners – receiving client deposits to secure venues or suppliers.
33. PHPs may hold client funds only for as long as strictly necessary to execute a payment transaction (funds must be moved or returned promptly and not used or retained by PHPs for purposes unrelated to the immediate execution of the payment transaction). Activities falling under the PHP definition inherently involve a short-term holding or temporary control of funds, specifically for the execution and settlement of a payment transaction.
A Payment handling provider means an undertaking that, for the purpose of executing a payment transaction, receives and administers funds on behalf of a payer with the obligation to transmit an equivalent amount to a designated payee. This includes providing one or more of the following services:
1. Enabling funds to be placed on or into, or withdrawn from, a payment account as well as all of the operations required for the administration of a payment account;
2. Execution of payment transactions, including transfer of funds on or into a payment account with the user’s payment service provider or with another payment service provider, including execution of ─
A. Direct debits,
B. Payment transactions through payment cards or similar [device or instrument], and
C. credit transfers, including standing orders;
3. Acquiring of payment transactions; and/or
4. Money remittance services.
Q4. Do you agree with this proposed definition and scope of PHPs? Are there any types of entities or activities you believe should be explicitly included or excluded?
34. PTPs are commercial entities that perform essential technological functions that are critical to PSP activities, such as the initiation or settlement of payment transactions or the functioning of core payment infrastructures. These providers do not hold, access or control customer funds but instead deliver key components of the payment lifecycle, such as transaction routing, payment data aggregation, authentication, encryption or secure user interfaces. The definition explicitly excludes decentralised infrastructure providers, including blockchain node operators, protocol developers, smart contract developers and AI-driven agents, which all conduct activities that are purely technical and do not commercially interface with end users.
35. The Framework does not seek to regulate entities that merely supply general-purpose technology or provide back-end outsourced services to licensed PSPs. However, certain operators will fall within the regulatory perimeter where their activities are commercial in nature and integral to payment flows or infrastructure. Examples of these operators include Account Information Service Providers, Payment Gateways, Checkout Facilitators and Buy-Now-Pay-Later Providers. While these business models may not pose the same prudential risks as traditional PSPs, their operational role can materially affect end users and market integrity. A distinct and proportionate regulatory approach will be applied to such entities that will be tailored to the specific risks and functions they perform to ensure adequate safeguards without stifling innovation.
36. It is essential to differentiate activities, like compliance, data collection or data processing for onboarding or for Know Your Customer (KYC) or AML purposes, from the core functions of payment transactions. These broader services, while potentially supporting payment relationships, are not directly tied to specific transactions or intrinsic to their execution. Unlike PHPs, which handle customer funds, PTPs are technical operators that underpin the payment cycle. They do this by facilitating the secure exchange of payment instructions and safeguarding system security, verification and stability without ever taking possession of funds. Their role is integral to the reliability and integrity of the payment infrastructure yet distinct from system‑level networks that are regulated separately as payment systems.
37. The defining characteristic of PTPs is their role in enabling essential, non-custodial technological functions in support of the execution of payment transactions. However, it is acknowledged that certain operators within this category may also store, whether directly or indirectly through third parties, user credentials such as authentication tokens, encrypted payment details or login information. This is typically done to facilitate secure and seamless payment experiences. For example, entities such as account information service providers that have access to, and consolidate account information across, multiple providers may retain credentials or use tokenised authentication methods as part of their service delivery. The inclusion of such entities within the PTP perimeter reflects their operational significance and the potential risk implications associated with the management of sensitive user data, even in the absence of fund custody. This clarification is intended to ensure that commercially active intermediaries performing credential-related functions integral to payment execution are appropriately captured within the regulatory framework.
38. Entities engaged in this activity typically include, but are not limited to, those providing the following services:
I. Services that are preliminary or necessary for executing payments;
II. User-facing commercial platforms, non-custodial commercially-facing interfaces and similar services; and
III. The provision of consolidated information on a consumer's multiple payment accounts, such as their balance and transaction history.
39. For clarity, the following are not considered PTPs:
I. Persons who have access to or hold financial resources during their operations;
II. Technical services provided to PSPs, such as cloud storage services and e-invoicing services; and
III. System-level payment infrastructures or operators, such as card networks, centralised payment systems or decentralised blockchain networks, which are not commercial user-facing service providers.
A Payment Technology Provider is any commercial undertaking that performs a critical role in the payment chain and performs services such as transaction routing, data aggregation, authentication, encryption (or similar services), forming part of the initiation, execution or settlement of payment transactions or to the functioning of critical payment infrastructure that enables payments to be made, without holding, accessing, or controlling customer funds.
Q5. Do you agree with the proposed definition and scope of PTPs? Please highlight any additional entity types or functions that you feel should be expressly included or excluded, such as those with roles limited to passive, conduit-style data transmission. Please then explain why.
Q6. Are there any current undertakings operating in or from Bermuda that are not presently subject to the MSB Act but would fall within the scope of the proposed new regime, based on the updated definitions?
40. The proposed PSA framework introduces a tiered licensing approach designed to provide a proportionate and risk-based regulatory structure.
41. The licensing process plays a vital role in enabling the Authority to act as a gatekeeper for the financial services sector, safeguarding both consumers and Bermuda’s reputation as a reputable financial centre. No person will be permitted to conduct PSP business in or from within Bermuda unless licensed to do so by the BMA. The PSA will specify that conducting business without the requisite licence is a criminal offence and outline the penalties for doing so.
42. The PSA proposes a tiered licensing regime that balances innovation with robust consumer and data protection. Recognising the range of proposed activities and likely applicants, the regime will scale licensing requirements based on factors such as business maturity, track record and the novelty of the proposed offering, particularly where customer protection risks are heightened. The tiered structure clearly distinguishes between companies in the testing and piloting stages (e.g., Class T or M) and those in whole operation (e.g., Class F, F-PG, F-R) from a public protection perspective. This differentiation empowers potential clients to make informed decisions regarding engagement based on a licensee's class.
43. An application for licensing shall indicate the applicable category and include such information as is necessary to enable the Authority to make an informed assessment.
44. Similar to the approach taken for digital asset businesses, the Authority proposes to implement a tiered licensing structure through the issuance of five licence classes:
| Class | Overview |
|---|
| T (Testing) | • A Class T licence will be an initial licence type designed to facilitate a regulatory sandbox for novelty start-up businesses, particularly for testing a minimum viable product or service via beta testing or piloting. • Applicants would be expected to develop success criteria for the test within their business plan, list their minimal scale of pre-identified or targeted customers or counterparties, and ensure that appropriate risk disclosures for potential counterparties are in place. • The T licence will have an initial duration of 12 months or less and be subject to appropriate regulatory requirements based on proportionality. |
|---|---|
| M (Modified) | • The Class M licence is designed to support businesses scaling up a previously tested model, particularly those building a complete compliance programme within a regulatory sandbox environment. It includes modified requirements and restrictions to ensure consumer protection with the BMA that retains the Authority’s discretion to issue a Class M licence regardless of the previously applied class. • This licence will be typically valid for 12 to 24 months, after which time the holder must either cease operations, apply for an extension, or transition to a full licence. The Authority will determine the initial licence period and any extensions on a case-by-case basis. |
| F (Full) | • The Class F licence will be a full licence and will not be subject to a specified period. It may be subject to restrictions or conditions if the Authority deems it appropriate to do so. |
| F-PG (Professional Grade) | • The Class F-PG licence will be a full licence intended, exclusively, for entities providing advanced payment or financial services to businesses, institutional clients or high-net-worth individuals but not to retail customers. It provides a tailored regulatory framework, ensuring global standards, balanced oversight and market credibility. This licence enables wholesale providers to operate flexibly with proportionate compliance. • Firms may start with a lower-tier licence (e.g., Class T or M) and transition to F-PG status as they develop the required risk profile and client base to support innovation while maintaining financial stability. |
| F-R (Reciprocal) | • The Class F-R licence will be a full licence, designed to operate on the basis of mutual reciprocity. Its objective is to align the requirements applied to payment-service providers operating under reciprocity frameworks in designated foreign jurisdictions (“Reciprocal Jurisdictions”). • The Class F-R licence is intended to: 1. Secure automatic or expedited recognition for domestic licensees seeking to operate in Reciprocal Jurisdictions; 2. Offer a gateway for firms already holding a reciprocity-type licence abroad to conduct business domestically; 3. Position Bermuda’s framework as compatible with emerging reciprocity-based recognition models, including those relating to stablecoins; and 4. Deepen cross-border supervisory cooperation through pre-negotiated information-sharing and enforcement protocols. |
45. While the licensing structure includes Classes T, M, F, F-PG and F-R, it is not obligatory for applicants to advance through each stage sequentially. In fact, if an applicant possesses adequate experience and a well-established business model, it is entirely feasible for them to apply for and obtain a Class F, F-PG or F-R licence right away.
46. The Authority, where it has decided on the application of a licensed undertaking, may extend the defined period of a class M or class T licence for such additional period as it deems appropriate.
Q7. Do you agree with the introduction of a dedicated F-PG licence for wholesale-focused payment service providers? Why or why not?
Q8. In your view, do the separate F-PG and F-R licenses provide clearer benefits compared to using conditional variations within the existing F licence framework?
Q9. What specific features or flexibilities would make the F-PG licence most valuable to firms operating in wholesale, institutional or high-value payment markets?
Q10. Do you agree with the proposed introduction of a bespoke licence class, specifically catering to entities operating under a ‘reciprocal or mutual recognition’ regime? Please highlight any benefits or concerns you may have.
Q11. What specific components, features or regulatory considerations do you believe a bespoke licence class, such as Class F-R, should include?
47. The licensing regime is intended to regulate PSPs but not payment systems overall. Payment activities performed by a designated payment system are typically excluded in other jurisdictions from payment Acts, as these systems are subject to separate oversight and regulatory frameworks.
48. The following undertakings are proposed to fall outside the scope of the proposed Framework:
I. Institutions licensed under the Banks and Deposit Companies Act 1999; and
II. Institutions licensed under the Credit Unions Act 2010.
49. The following activities are not intended to be captured by the proposed Framework:
I. The secure transport and handling of physical currency as a professional service;
II. A payment network or arrangement operated by an undertaking that establishes rules, standards and/or procedures that govern card-based payment transactions and provides the related operational infrastructure but does not directly issue payment cards to customers, hold customer funds or make contracts directly with merchants for acquiring services;
III. Payment transactions and related services (including currency conversion and payment aggregation) conducted exclusively between a parent undertaking and its subsidiaries or between subsidiaries under common control. This exemption shall apply solely to internal group treasury management activities (self-to-self) and does not extend to transactions indirectly servicing external customers. Other closed-loop or limited network activities will be assessed using a risk-based approach, considering factors such as access to customer funds, transaction volume, interoperability and consumer exposure (refer to paragraphs 17-18 of this CP);
IV. Payment transactions carried out within a payment system or securities settlement system between PSPs and settlement agents, central counterparties, clearing houses, central banks or other participants in such a system, including central securities depositories;
V. Payroll services; and
VI. Loyalty schemes.
50. Entities performing PSP activities will, as a general rule, be treated as AML/ATF‑regulated financial institutions and, to the extent required by applicable legislation, be subject to AML, ATF and sanctions obligations. The precise scope of those obligations (including any exemptions or simplified measures) will depend on the nature, scale and risk profile of the activities undertaken. Consequential amendments will include updates to the following legislative instruments: the Bermuda Monetary Authority Act 1969 (Third and Fourth Schedules); the Digital Asset Business Act 2018 and the Digital Asset Business Exemption Order 2023; the Anti-Terrorism (Financial and Other Measures) Act 2004; the Proceeds of Crime Act 1997; the Proceeds of Crime (Anti-Money Laundering and Anti-Terrorist Financing) Regulations 2008; and the Proceeds of Crime (Anti-Money Laundering and Anti-Terrorist Financing Supervision and Enforcement) Act 2008.
51. The Authority proposes the following fee approach to support a proportionate and risk-based supervisory approach. A flat application and licence fee of $1,000 will apply to entities seeking a Class T licence. For Class M, F, F-PG and F-R licenses, the proposed application fee is $2,266. Additionally, the licence fee for Class M, F and PG will be the greater of either $15,000 or 0.0075 of the applicant’s estimated annual client receipts. Entities licensed under Class F, F-PG or F-R will be subject to an annual supervisory fee calculated as the higher of $15,000 or 0.0075 of actual annual client receipts.
52. The Authority intends to issue rules, a statement of principles, codes of practice and guidance under the PSA to further clarify duties, requirements, procedures, standards and sound principles to be observed by PSPs. These encompass critical areas such as conduct, cyber risk, prudential requirements, outsourcing and operational resilience.
53. The Authority welcomes feedback on the proposals presented in this CP and any related topics by the close of business on 13 October 2025. As previously mentioned, the BMA aims to use the feedback received to hone the draft legislative proposals and the wider PSA framework outlined in this CP.
Bermuda Monetary Authority
BMA House
43 Victoria Street
Hamilton HM 12
Bermuda
Tel: (441) 295 5278
Fax: (441) 292 7471
Website: https://www.bma.bm
BMA BERMUDA MONETARY AUTHORITY
Note from RegAlert. AI assistants can read this document in full, and search 70,000+ more, through the RegAlert MCP connector (https://mcp.regalert.today/mcp). Free with an account. How to connect ChatGPT, Claude or Cursor.
The documents this one cites, and the documents that cite it.
“The proposed PSA will repeal the Money Service Business Act 2016 (MBS Act) and establish a new regulatory framework with an expanded scope of licensable activities.”
“Consequential amendments will include updates to the following legislative instruments: ... the Digital Asset Business Exemption Order 2023;”
More like this from BMA
BMA published 5 documents in the last 30 days. We email you each new one the day it's published.
Source: Bermuda Monetary Authority — original document · Summary generated with machine assistance and checked by an AI reviewer before publication; the authoritative text is the regulator's original document. How RegAlert works
In RegAlert: added · updated