Retail Payment Activities Act: Registration and Compliance
The Retail Payment Activities Act requires payment fintechs and other payment service providers to register with the Bank of Canada and meet ongoing risk, safeguarding and reporting rules. This note explains who is in scope, the exclusions, operational risk and incident frameworks, safeguarding of end-user funds, and how supervision and enforcement work.

Key takeaways
- Registration provisions took effect 1 November 2024; operating unregistered was prohibited from 16 November 2024.
- Risk management, incident reporting, safeguarding and annual reporting duties apply from 8 September 2025.
- Banks, credit unions, insurers and trust companies are excluded under s. 9.
- End-user funds must be held in trust, in a prescribed manner, or segregated with insurance or a guarantee.
- The Bank of Canada publishes a PSP registry and enforcement decisions; penalties can reach CAD 10 million.
What the Retail Payment Activities Act requires
The Retail Payment Activities Act (RPAA) creates a federal supervisory regime for payment service providers (PSPs) that are not already regulated as banks, credit unions, insurers or trust companies. It requires in-scope PSPs to register with the Bank of Canada before performing retail payment activities, to maintain a risk management and incident response framework, to safeguard end-user funds they hold, to report incidents and file annual reports, and to submit to supervision and enforcement by the Bank. The Retail Payment Activities Act is the foundation for the federal approach to payment fintechs, digital wallets, payment processors and money transfer apps.

Implementation was staged. According to the Act's coming-into-force note, the registration provisions (ss. 28 to 44) came into force on 1 November 2024, the prohibition on performing retail payment activities without registration (s. 23) on 16 November 2024, and the substantive requirements on risk management, incident reporting, safeguarding and annual reporting (ss. 17 to 22) on 8 September 2025. Since that date the Bank of Canada has been supervising registered PSPs.
Who must register under the Retail Payment Activities Act
The Act applies to a "payment service provider", meaning an individual or entity that performs payment functions as a service or business activity that is not incidental to another service or business activity. A "retail payment activity" is a payment function performed in relation to an electronic funds transfer in Canadian or foreign currency, or using a unit that meets prescribed criteria. The five payment functions are:
- providing or maintaining an account held on behalf of end users for electronic funds transfers;
- holding funds on behalf of an end user until withdrawn or transferred;
- initiating an electronic funds transfer at an end user's request;
- authorizing an electronic funds transfer, or transmitting, receiving or facilitating an instruction in relation to one; and
- providing clearing or settlement services.
PSPs with a place of business in Canada are covered, as are foreign PSPs that perform retail payment activities for end users in Canada and direct those activities at Canada. Foreign PSPs therefore need to analyse their Canadian activities even without a Canadian office.
Exclusions
Several categories fall outside the regime:
- Prudentially regulated institutions listed in s. 9, including banks, authorized foreign banks, provincially regulated credit unions and caisses, insurers, trust and loan companies, Payments Canada and the Bank of Canada itself.
- Incidental activities. A business that performs payment functions only incidentally to another service or business, such as a property manager collecting rent or a marketplace that processes payments only for its own sales, may not be a PSP. The line is fact-specific and the Bank has published guidance.
- Excluded activities under s. 6, such as closed-loop gift cards issued by a merchant or group of merchants, transfers to settle eligible financial contracts and prescribed securities transactions, and ATM cash withdrawals.
- Designated systems under the Payment Clearing and Settlement Act (s. 7) and certain internal transactions between affiliates (s. 8).
- Agents and mandataries of registered PSPs, which are covered through their principal's registration.
| Obligation | Provision | Key content |
|---|---|---|
| Registration | ss. 23 and 29 | Register before performing retail payment activities; disclose ownership, agents, activities and safeguarding approach |
| Risk management and incident response | s. 17 | Framework meeting prescribed requirements; Bank may assess and require corrective measures |
| Incident notification | s. 18 | Notify affected end users, PSPs, clearing houses and the Bank without delay of incidents with material impact |
| Safeguarding | s. 20 | Hold end-user funds in trust, in a prescribed manner, or in a segregated account with insurance or a guarantee |
| Annual report | s. 21 | Report on the framework, safeguarding accounts and other prescribed information |
| Changes and acquisitions | s. 24 | New application before an acquisition of control or significant changes |
Operational risk and incident response frameworks
Section 17 requires every PSP that performs retail payment activities to establish, implement and maintain a risk management and incident response framework, in accordance with the Retail Payment Activities Regulations, to identify and mitigate operational risks and respond to incidents. The Bank or a person it designates may assess the framework and provide a list of corrective measures. The regulations set requirements covering governance, objectives, risk identification and mitigation, testing, third-party service providers, business continuity and independent review.
Under s. 18, if a PSP becomes aware of an incident that has a material impact on an end user, another PSP or a clearing house, it must notify them and the Bank without delay. Incidents include cyberattacks, outages, fraud events and third-party failures. The Act's definition of operational risk is broad, covering deficiencies in information systems or internal processes, human error, management failure and disruptions caused by external events, so the framework should not be limited to cybersecurity. In practice PSPs need an incident classification process that decides quickly whether the materiality threshold is met, templates for notices, and a record of every incident and decision.
Many PSPs outsource core functions to cloud providers, card processors and banking-as-a-service partners. The RPAA framework must cover those third-party service providers. Contracts should give the PSP the information, audit rights and incident notification it needs to meet its own obligations to the Bank of Canada.
Safeguarding end-user funds
If a PSP holds end-user funds until they are withdrawn or transferred, s. 20 requires it to protect them in one of the permitted ways:
- holding them in trust in a trust account not used for any other purpose;
- holding them in a prescribed account or manner and taking prescribed measures; or
- holding them in an account not used for any other purpose and maintaining insurance or a guarantee for an amount at least equal to the funds held, as prescribed.
Safeguarding is meant to ensure that end users get their money back if the PSP fails. PSPs must also reconcile funds, keep records and describe their safeguarding approach in the annual report under s. 21. For PSPs that hold funds in bank accounts, the account documentation should clearly reflect the trust or segregated status, and the bank should acknowledge that it has no set-off rights against those funds.
Supervision, enforcement and the first decisions
The Bank of Canada describes its role on its retail payments supervision page: it assesses applications and registers PSPs; maintains and publishes a registry of PSPs, lists of applicants and a list of refused or revoked registrations; supervises registered PSPs and applicants on operational risk, incident response, safeguarding and reporting; and takes enforcement action where necessary. The Bank publishes enforcement decisions and prescribed review decisions, and recovers its costs through a one-time application fee and annual assessment fees. The Bank also notes that it does not handle disputes between PSPs and end users, fee complaints or privacy complaints.
Enforcement tools include compliance agreements, administrative monetary penalties and, in serious cases, refusal or revocation of registration. The Act allows regulations to set penalties up to CAD 10 million per violation. Registration can also be refused or revoked on national security grounds, after review by the Minister of Finance. PSPs should therefore treat registration as a privilege that depends on continued compliance, not a one-time filing.
Retail Payment Activities Act issues in M&A and investment
The Retail Payment Activities Act affects transactions as well as operations. Under s. 24, if a person plans to acquire control of a registered PSP, the PSP must submit a new application for registration that reflects the planned acquisition, and be registered on that basis, before the acquisition. Buyers of payment fintechs therefore need to build the Bank of Canada process into their timetable and conditions precedent, alongside any FINTRAC, Investment Canada Act or competition filings. The application can attract national security review, which may lengthen timelines for foreign acquirers.
Due diligence on a Canadian PSP should confirm its registration status and the activities described in its application, review the risk management and incident response framework and any Bank of Canada assessments or corrective measures, test safeguarding arrangements and reconciliations, and check incident and annual reporting history. Investors taking minority stakes should consider whether their rights could amount to control, and lenders should check whether security over a PSP's shares or assets could trigger a filing on enforcement.
Interaction with other regimes
The Retail Payment Activities Act does not replace other obligations. Many PSPs are also money services businesses that must register with FINTRAC and comply with anti-money laundering rules under the Proceeds of Crime (Money Laundering) and Terrorist Financing Act, which was strengthened in 2026 (see FINTRAC's summary of changes). Quebec has its own money services business licensing. Privacy laws apply to end-user data. And the federal Stablecoin Act, not yet in force, would interact with the RPAA: draft Stablecoin Regulations published in the Canada Gazette, Part I on 24 October 2026 would bring stablecoin payment providers within the RPAA.
Practical compliance steps
- Scope analysis. Map each product against the five payment functions and the exclusions, and document the conclusion, especially for incidental activity arguments.
- Registration maintenance. Keep registration information current, and file a new application before an acquisition of control or other significant change under s. 24.
- Framework. Adopt a board-approved risk management and incident response framework, test it, and arrange an independent review as required by the regulations.
- Safeguarding. Choose and document the safeguarding method, put account documentation in place and reconcile daily.
- Reporting. Calendar the annual report and incident notification processes.
- Agents and partners. List agents and mandataries, and review contracts with third-party service providers for audit, information and incident notification rights.
- Training. Train operations and customer support staff to recognize and escalate incidents quickly.
Illustration (hypothetical): a UK-based payment app lets Canadian users store funds in a wallet and send money to friends. It has no Canadian office but markets to Canadians. It performs at least three payment functions for end users in Canada, so it registers with the Bank of Canada, holds wallet balances in a trust account at a Canadian bank, adopts a framework that covers its cloud and card processing vendors, and also registers with FINTRAC as a foreign money services business.
How TRW & Co helps with the Retail Payment Activities Act
We advise payment fintechs, foreign PSPs, marketplaces and banks on the Retail Payment Activities Act. That includes scope and exclusion analysis, registration and change-of-control filings, risk management and incident response frameworks, safeguarding structures and bank account documentation, vendor contracts, and responses to Bank of Canada supervisory and enforcement action. Where a filing or opinion requires a Canadian-licensed lawyer, we work with licensed counsel. Our fintech and payments and AML and FINTRAC work covers related issues; see also our notes on MSB registration and stablecoins in Canada. To discuss your payment business, contact us. This note is general information, not legal advice.
Frequently asked questions
Who must register under the RPAA?
Payment service providers that perform payment functions as a service or business activity not incidental to another business, in relation to electronic funds transfers, unless excluded. Covered PSPs include those with a place of business in Canada and foreign PSPs that perform retail payment activities for end users in Canada and direct them at Canada.
When did RPAA obligations start?
Registration provisions came into force on 1 November 2024, and the prohibition on performing retail payment activities without registration on 16 November 2024. The ongoing requirements on risk management and incident response, incident notification, safeguarding and annual reports came into force on 8 September 2025.
Are banks and credit unions subject to the RPAA?
No. Section 9 excludes banks, authorized foreign banks, provincially regulated credit unions and caisses, insurers, federal and provincial trust and loan companies, certain provincial Crown deposit-takers, Payments Canada and the Bank of Canada. Their payment activities are covered by other regimes.
How must end-user funds be safeguarded?
Under s. 20, a PSP that holds end-user funds must hold them in trust in a dedicated trust account, hold them in a prescribed account or manner with prescribed measures, or hold them in a dedicated account backed by insurance or a guarantee, as prescribed by the regulations.
Does the Bank of Canada resolve customer complaints about PSPs?
No. The Bank states that its retail payments supervision mandate does not include dispute resolution between PSPs and end users, complaints about fees or privacy complaints. It focuses on operational risk, incident response, safeguarding of funds and reporting, and can take enforcement action for violations.
Sources
General information only, not legal advice. References to statutes, courts and authorities describe published law and practice at the date shown.


