Canada โ€” Bank of Canada PSP Registration (Retail Payment Activities Act)

Canada's Retail Payment Activities Act requires payment service providers to register with the Bank of Canada before performing retail payment activities. Full compliance obligations took effect on 8 September 2025. The regime catches far more businesses than most operators expect โ€” including foreign companies with no Canadian incorporation, no Canadian office, and no FINTRAC registration โ€” and the Bank began publishing notices of violation in June 2026.

REGULATOR
Bank of Canada
FRAMEWORK
Retail Payment Activities Act
FULL OBLIGATIONS IN FORCE
8 September 2025
PORTAL
PSP Connect

โ€” Last updated: August 2026 ยท 12 min read

In short

The Retail Payment Activities Act requires payment service providers to register with the Bank of Canada before performing retail payment activities in Canada. Full compliance obligations took effect on 8 September 2025. Registration applies to domestic and foreign PSPs, including companies with no Canadian incorporation or office. The RPAA is separate from FINTRAC MSB registration, and neither regime satisfies the other.

The four-step scope test

The Bank of Canada's guidance sets a four-part test for determining whether an entity must register. All four must be true.

  1. 1
    You are a payment service provider: You perform one or more of the five statutory payment functions as a service or business activity that is not incidental to another service or business activity.
  2. 2
    You perform retail payment activities: A payment function performed in relation to an electronic funds transfer made in Canadian currency, foreign currency, or a prescribed unit.
  3. 3
    You fall within the geographic scope: Either you have a place of business in Canada, or you both perform retail payment activities for end users in Canada and direct those activities at persons in Canada.
  4. 4
    Neither you nor your activities are excluded: The RPAA contains both entity-based and activity-based exclusions, each of which must be checked against your specific circumstances.

The Bank publishes a self-assessment tool for this determination, together with a large library of case scenarios covering acquirers, card program managers, marketplaces, payroll services, remittance providers, point-of-sale terminals, lending, e-commerce gateways, and providers of services backed by cryptocurrencies.

The five payment functions

Precision matters here. Each function is defined narrowly in the legislation and the Bank's guidance, and paraphrasing them introduces error.

Provision or maintenance of an account

You store end-user personal or financial information in relation to future electronic funds transfers. Storing information for a single transaction without retaining it is likely not covered. Two points catch people: end users need not have direct access to the account, and you do not need to hold funds in order to maintain an account.

Holding funds on behalf of an end user

You keep a payer's or payee's funds at rest, available for future withdrawal or transfer, and you are indebted to the end user in respect of those funds. Funds are in transit โ€” and therefore not held โ€” from the moment you receive an instruction for immediate transfer.

Initiation of an electronic funds transfer

You launch the first payment instruction enabling an EFT requested by a payer or payee. This covers both push and pull payments. The distinguishing feature is capturing and packaging the data into the first instruction โ€” for any given transaction, only one entity performs initiation.

Authorization of an EFT, or transmission, reception or facilitation of an instruction

Deliberately broad. Authorisation includes enabling an end user to consent, confirming sufficiency of funds, debiting or crediting an account per instruction, and pre-authorised payment arrangements. The second limb captures sending or receiving payment instructions and providing the network, platform, or interface through which instructions flow. Multiple entities can perform this function within a single transaction.

Provision of clearing or settlement services

Clearing covers calculating final positions, format transformation for settlement, integrity checks, transaction sorting, transmitting position information, and confirming funds availability for settlement. Settlement covers posting credits and debits in another entity's accounts, and account adjustments. Both apply where you provide the service to another entity.

On holding funds โ€” two clarifications from the Bank

Processing delays for fraud or AML screening, including overnight delays, do not make funds โ€œheldโ€. And where funds move between end-user accounts via intermediary PSPs, only the first and last PSP in the chain are holding funds.

The incidental test

This is the hardest judgement in the regime and where most self-assessments go wrong. If your only business activity is performing payment functions, you are a PSP. Where you perform both payment and non-payment activities, the question is whether the payment functions exist only to directly support the non-payment activity.

The Bank applies three indicators:

  • โ€ขRevenue or commercial advantage โ€” a payment function is likely not incidental if it directly generates revenue or a commercial advantage. The Bank reads this broadly: it includes less tangible benefits, such as generating data that may be monetised later.
  • โ€ขEnd-user expectations โ€” if a substantial number of end users reasonably expect to be receiving a payment service, the function is likely not incidental.
  • โ€ขMarketing and advertising โ€” advertising payment features, using payment-related branding or trade names, or allocating budget to promoting payment services all indicate a distinct service.

The Bank's own worked example: a company processing payments for merchants and producing promotional material for those merchants cannot treat the payment business as incidental, because the payment function does not support the promotional business โ€” even where the two are packaged and sold together.

A contextual analysis, not a checklist

The Bank is explicit that the indicators are not weighted equally and that an assessment may rest on a single indicator. A payment function previously assessed as incidental can also stop being incidental when the business model changes โ€” so reassessment is a standing obligation, not a one-off exercise.

Foreign PSPs: registration without a Canadian entity

Foreign PSPs subject to the RPAA must register with the Bank of Canada even if they are not incorporated in Canada and not registered with FINTRAC as a foreign money services business. Once registered, they are supervised and treated in the same manner as domestic PSPs, and are subject to the same enforcement actions.

You have a place of business in Canada if any one of the following is true:

  • โ€ขA physical location in Canada, including a home office.
  • โ€ขIncorporation under federal or provincial legislation.
  • โ€ขEmployees, agents, or mandataries in Canada.

Without a place of business in Canada, you must still register if you both perform retail payment activities for an end user in Canada and direct those activities at persons in Canada. You are considered to be directing activities at Canada if any one of these applies:

  • โ€ขMarketing or advertising directed at persons in Canada.
  • โ€ขOperating a .ca domain.
  • โ€ขListing in a Canadian business directory.
  • โ€ขHaving a retail-payments agreement, working relationship, representative, agent, or mandatary in Canada.

The Bank may also consider: describing your activities as offered in Canada, offering them in Canadian dollars, providing end-user support to persons in Canada, seeking feedback from Canadian users, having Canadian staff or third parties promoting your activities, having a high proportion of Canadian end users, or operating in multiple countries and being well known in Canada.

Planning to expand into Canada

Marketing to assess demand is only directing activities and does not itself trigger registration. But you must register before you begin performing retail payment activities for end users in Canada.

Exclusions

Entity-based exclusions: banks and authorized foreign banks under Schedules I, II and III of the Bank Act; insurance companies and fraternal benefit societies; trust and loan companies; provincially regulated deposit-taking institutions including credit unions and caisses populaires; the Bank of Canada; the Canadian Payments Association; the Provincial Crown and its agents accepting deposits transferable by order; and the SWIFT messaging network.

Activity-based exclusions: merchant instruments and group-of-merchants instruments; eligible financial contracts under the CDIC Act; prescribed securities transactions where the entity is regulated or exempt under Canadian securities legislation; cash withdrawals at ATMs including white-label machines; payment functions performed using a designated financial market infrastructure; and internal transactions between affiliated entities where no other PSP performs payment functions.

Three traps in the exclusions

Agents and mandataries are excluded when acting within the scope of their authority for a registered PSP โ€” but the registered PSP is liable for their violations. An agent of an excluded PSP, such as a bank, must register in its own right, and an agent performing activities outside the agency relationship may need to register for those activities.

Third-party service providers are not excluded. They must be disclosed in the registration application, and the PSP is liable for them acting within the scope of their contract.

Affiliated entities register separately. A subsidiary may need its own registration even where its parent is already registered.

The registration process

  1. 1
    Scope assessment: The four-step test, the incidental analysis, and identification of the specific payment functions performed. This is Zitadelle AG's starting point on every engagement.
  2. 2
    PSP Connect account: Registration is impossible without one. PSP Connect is the Bank's registration and communication portal.
  3. 3
    Application preparation: Required content includes contact details for the applicant and any third parties, agents, mandataries and affiliated entities; business structure, ownership, debtholders and key staff; the retail payment functions performed or planned, including those performed by agents or affiliates; actual or projected values and volumes of end-user funds held inside and outside Canada; actual or projected end-user numbers inside and outside Canada; the methods used to safeguard end-user funds; whether a risk management and incident response framework is in place or planned; and any existing registrations with FINTRAC or under other federal, provincial or territorial legislation.
  4. 4
    Pay the registration application fee: One-time and non-refundable, payable by credit card or EFT. Assessment does not begin until the fee is paid in full. Amount: {{Amount TO VERIFY}}.
  5. 5
    Review: Applicants may need to respond to requests for information. The Bank shares qualifying applications with the Department of Finance Canada for national security screening, and with FINTRAC.
  6. 6
    Decision and publication: Registration decisions are published as national security screenings complete. Foreign PSPs must identify any Canadian agents or mandataries, who will receive notices and orders on their behalf.
  7. 7
    Ongoing: Comply with the RPAA, pay the annual assessment fee, and keep registration information current.

Two things to know before you submit

Applications cannot be cancelled once submitted. The Bank also publishes a list of applicants, including legal and trade names, head office country and city, website, and application date โ€” so a submission is public before any decision is made.

Ongoing obligations

Operational risk and incident response framework. Identify operational risks, assets and business processes; protect activities and assets from those risks; detect, respond to and recover from incidents; assign roles and responsibilities; maintain adequate resources; review and test the framework; and manage risks arising from third-party service providers, agents and mandataries. The framework must be proportionate to the nature of the business, the services offered, and the organisational structure.

Safeguarding end-user funds. PSPs holding end-user funds must either hold them in trust in a trust account, or hold them in a segregated account with insurance or a guarantee. A written framework is required, setting out how end users retain reliable and timely access to their funds and how funds are paid out on insolvency.

The three mandatory RPAA reports.
ReportTriggerDeadline
Annual reportRegistration information, operational risk, incident response, safeguarding practicesNo later than 31 March of the year following the reporting year
Significant change or new activity noticeMaterial change to how retail payment activities are performed, or a new retail payment activityAt least five business days before the change or new activity
Incident noticeIncident with material impact on end users, other PSPs, or certain clearing and settlement systemsWithout delay

Requests for information. Typically 15 days to respond, but 24 hours in specific circumstances. PSP Connect is the primary communication channel, and entities on the applicant list โ€” not only registered PSPs โ€” must respond.

Assessment methods. The Bank uses desk assessments, on-site assessments, and special audits with a scope the Bank defines.

Change of control. A registered PSP must submit a new registration application where a person plans to acquire control, or where a state-owned enterprise plans to acquire the right to appoint the CEO or senior management, elect board members, or acquire an ownership interest. The new registration must be approved before the change takes place.

Enforcement is live and public

  • โ€ข12 June 2026 โ€” the Bank announced it would begin publishing Notices of Violation issued to payment service providers.
  • โ€ข27 February 2026 โ€” the Bank issued a revised compliance order to XTM Inc.
  • โ€ขRegistration may be refused or revoked for failing to meet the registration criteria, failing to provide requested information, providing false or misleading information, ceasing to perform retail payment activities, committing a violation, or failing to pay the annual assessment fee. The Bank may also act on information provided by FINTRAC, and must refuse or revoke under a directive from the Minister of Finance on national security grounds.
  • โ€ขOperating without having submitted an application may violate section 104 of the RPAA. The Bank describes this as a serious violation that could carry a notice of violation with a substantial administrative monetary penalty. Maximum AMP amounts: {{Maximum AMP amounts TO VERIFY}}.

Enforcement tools escalate in the following order: warning letter, compliance agreement, notice of violation with an administrative monetary penalty, compliance order, and application to a superior court.

The compliance agreement trade-off

The AMP is cut by half where the party enters a compliance agreement offered as part of the notice of violation. But a PSP that enters such an agreement and then fails to meet its terms owes the remaining half plus an additional prescribed penalty equal to the original AMP.

Reviews and appeals. A refused or revoked registration, a notice of violation, or a notice of default may be reviewed on request within 30 days of receipt. The Governor's delegate must decide within 90 days, and decisions may be appealed to the Federal Court. Separately, where the Minister of Finance issued the directive, review is by the Minister and is also appealable to the Federal Court.

RPAA registration vs FINTRAC MSB registration

Bank of Canada PSP registrationFINTRAC MSB registration
StatuteRetail Payment Activities ActPCMLTFA
RegulatorBank of CanadaFINTRAC
PurposeOperational risk, end-user fund safeguardingAnti-money laundering and terrorist financing
Core obligationsRisk and incident framework, safeguarding, three mandatory reportsAML/CTF programme, compliance officer, STR/LCTR/EFTR reporting, recordkeeping
Public registryYes, plus refused and revoked listsYes
Triggered byPerforming payment functions in relation to EFTsFX dealing, remittance, money orders, virtual currency dealing, crowdfunding

Neither regime satisfies the other

These are separate regimes. Many businesses need both. Some need only one. The determination is made by applying each test independently โ€” see our Canada MSB Registration (FINTRAC) page for the anti-money laundering side of the analysis.

Who needs to look at this

Payment gateways and e-commerce payment processors

Typically perform initiation, authorisation, or transmission functions, and provide the interface through which payment instructions flow.

Merchant acquirers and card program managers

Authorisation, clearing and settlement functions are common, and both categories are covered by the Bank's published case scenarios.

Remittance and money transfer operators

Initiation and transmission functions, frequently combined with holding funds โ€” and frequently in scope for FINTRAC MSB registration in parallel.

Digital wallet and neobank services

Account provision and holding funds are the core of the product, which places them squarely within the payment functions.

Marketplaces holding or routing funds

Holding buyer or seller funds, or maintaining accounts in relation to future transfers, can bring a marketplace into scope even where payments are not the headline business.

Payroll service providers

Initiating and transmitting electronic funds transfers on behalf of employers, with the incidental test often the deciding question.

Point-of-sale terminal providers

Transmission, reception or facilitation of payment instructions through the terminal network and interface.

Providers of services backed by cryptocurrencies

Where the service involves electronic funds transfers in fiat or a prescribed unit, RPAA payment functions can be engaged alongside virtual currency obligations.

Foreign payment companies serving Canadian customers

In scope without any Canadian incorporation or office where activities are performed for Canadian end users and directed at persons in Canada.

Lending platforms with payment functions

Disbursement and repayment flows can involve initiation, authorisation, or holding funds โ€” and the incidental test is rarely straightforward.

The Bank has published case scenarios covering most of these categories, which is the most reliable starting point for a business-model-specific read.

How Zitadelle AG assists

  • โ€ขScope assessment against the four-step test and the incidental analysis.
  • โ€ขPayment function mapping across your transaction flows.
  • โ€ขPSP Connect application preparation.
  • โ€ขSafeguarding framework design, including trust versus segregated-account structuring.
  • โ€ขOperational risk and incident response framework development.
  • โ€ขAnnual report, significant change notice, and incident notice processes.
  • โ€ขResponses to requests for information within the applicable deadlines.
  • โ€ขCoordination with parallel FINTRAC MSB registration where both regimes apply.
  • โ€ขOngoing compliance support and reassessment when the business model changes.

Related services: Compliance & Advisory, Legal, and Company Formation. For a European footprint see the EU EMI License, and for an offshore payment intermediary structure see the Mauritius PIS License.

Primary sources

Regulatory positions on this page are verified against the Bank of Canada's published supervisory framework and its registration criteria policy for payment service providers.

Frequently Asked Questions

Any entity that satisfies the Bank's four-part test: it performs one or more of the five statutory payment functions as a service or business activity that is not incidental to another business activity; it performs those functions in relation to electronic funds transfers; it either has a place of business in Canada or performs retail payment activities for end users in Canada while directing those activities at persons in Canada; and neither the entity nor its activities are excluded. Full compliance obligations took effect on 8 September 2025.

Is your business caught by the RPAA?

Scope is the first question and the one that determines everything that follows. Zitadelle AG assesses your business against the four-step test and the incidental analysis, maps the specific payment functions performed, and confirms whether Bank of Canada registration, FINTRAC MSB registration, or both apply.

Quick Facts

Regulator
Bank of Canada
Framework
Retail Payment Activities Act (RPAA)
Full obligations in force
8 September 2025
Registration
Mandatory before performing activities
Portal
PSP Connect
Public registry
Yes โ€” plus refused and revoked lists
Foreign PSPs
In scope โ€” no Canadian incorporation required
Registration fee
One-time, non-refundable {{Amount TO VERIFY}}
Annual report
Due by 31 March
Separate from FINTRAC MSB
Yes โ€” neither satisfies the other

Disclaimer: This page is for informational purposes only and does not constitute legal or regulatory advice. Requirements, timelines, and fees are subject to change. Always consult directly with the relevant regulatory authority or a qualified professional for the most current information. Zitadelle Advisory Group LTD is not a law firm and does not provide legal representation.