Opening Bank Account for Canadian PSP Under RPAA

Canada's payments landscape changed fundamentally on September 8, 2025. That was the date the Retail Payment Activities Act (RPAA) came fully into force — and with it, a new category of regulated financial entity was born: the Canadian Payment Service Provider (PSP), supervised directly by the Bank of Canada. For businesses operating under this new framework, banking has become both more important and more complex.

What Is a Canadian PSP Under RPAA and How Is It Different from an MSB?

The confusion between a Canadian Money Services Business (MSB) and a Payment Service Provider (PSP) under the RPAA is one of the most common questions new entrants face. They are not the same thing and critically, most fintechs need both registrations.

The MSB is registered with FINTRAC — Canada's financial intelligence and AML regulator — under the Proceeds of Crime (Money Laundering) and Terrorist Financing Act (PCMLTFA). An MSB registration covers businesses engaged in foreign exchange, money transfers, issuing or redeeming negotiable instruments, and virtual currency transactions. FINTRAC registration is free, focused entirely on anti-money laundering and counter-terrorist financing, and has been in place since 2000.

The PSP under RPAA is registered with the Bank of Canada and covers a fundamentally different set of obligations. The RPAA defines five core payment functions that trigger PSP registration: holding end-user funds, initiating electronic funds transfers, authorising payment transactions, maintaining payment accounts, and providing clearing and settlement services. The RPAA's focus is not AML — it is operational resilience, consumer protection, and the safeguarding of end-user funds if a PSP becomes insolvent.

The key differences in plain terms:

	MSB (FINTRAC)	PSP (Bank of Canada / RPAA)
Regulator	FINTRAC	Bank of Canada
Focus	AML/CTF compliance	Operational risk & fund safeguarding
Registration fee	Free	Application fee + annual assessment
Reporting	STRs, LCTRs, EFTRs, LVCTRs	Annual reports, incident reports
Fund safeguarding required	No	Yes — if holding end-user funds
Covers crypto only	Yes (if no fiat functions)	No — fiat functions trigger RPAA
Renewal	Every 2 years	Annual reporting

Crucially, an MSB operating exclusively in virtual currency with no fiat account issuance or fiat fund holding is exempt from RPAA registration. The moment fiat payment functions are introduced, RPAA registration is required in addition to the existing FINTRAC registration.

As of January 2026, the RPAA transition period has ended. Any PSP operating without a Bank of Canada registration is now in violation of the Act and faces administrative monetary penalties potentially exceeding CAD $100,000 per violation.

Pros and Cons of Operating as a Canadian PSP Under RPAA

Understanding the commercial and operational trade-offs of the RPAA framework is essential before making banking decisions, because the framework directly shapes what accounts you need and how much they will cost to maintain.

Advantages

Registration under RPAA gives your business a significant credibility signal. Banks — both Canadian and international — recognise Bank of Canada supervision as a meaningful standard. This opens doors to banking relationships that would otherwise be closed to unregistered payment companies. It also positions RPAA-registered PSPs for future membership in Payments Canada, which would give direct access to Canada's Real-Time Rail (RTR) — a significant competitive advantage over non-registered competitors.

The framework also creates a cleaner relationship with end users. By mandating fund safeguarding, the RPAA essentially forces PSPs to build trust infrastructure that strengthens client retention. Being able to demonstrate to clients that their funds are legally ringfenced in trust or insured accounts is a meaningful commercial differentiator.

Disadvantages

The compliance cost is real and material. First-year costs for dual PSP and MSB compliance typically range from CAD $100,000 to $300,000 or more, depending on business complexity, including legal counsel, compliance officer appointment, risk management framework development, technology systems, and banking setup. Annual ongoing compliance costs typically run CAD $75,000 to $200,000 or more.

The Bank of Canada PSP registration process itself is complex and can take six to twelve months depending on application completeness and national security screening timelines. This is a longer timeline than most founders anticipate.

Banking access remains a genuine friction point. Canadian chartered banks — the Big Five — apply rigorous due diligence to PSP clients, and newly registered PSPs without established operating history face slow onboarding and, in some cases, outright refusal. This is the central challenge the rest of this guide addresses.

Operational Bank Account for a Canadian PSP

Every RPAA-registered PSP needs a dedicated operational account — the account where the firm's own money lives. This is separate from any client money and is used for payroll, technology costs, office expenses, regulatory fees, and any other business expenditure that belongs to the PSP itself.

The challenge for Canadian PSPs is that the Big Five banks — Royal Bank of Canada (RBC), TD Bank, Scotiabank, BMO, and CIBC — treat payment companies as elevated-risk corporate clients. Their financial institutions desks require extensive documentation, onboarding timelines of four to twelve weeks are common, and many PSPs report being declined without detailed explanation.

In practice, the most accessible routes are Canadian digital banks and challenger banking providers with CDIC membership, provincially regulated credit unions with fintech-friendly onboarding, and — for PSPs with cross-border operations or non-Canadian ownership — international EMI-licensed providers offering multi-currency operational accounts as a complement while a domestic bank relationship is being established. The Epico Finance team maintains an updated list of digital banking providers currently open to onboarding Canadian PSPs — get in touch directly to receive it.

When opening the operational account, present your RPAA registration certificate, FINTRAC MSB registration, corporate documents, beneficial ownership structure, and a clear explanation of your business model and fund flows. Being RPAA-registered is an asset — use it prominently in your bank application to distinguish yourself from unregulated payment companies.

Client Money Accounts for a Canadian PSP

If your PSP holds funds on behalf of end users — even temporarily, before transfer or withdrawal — the RPAA mandates specific safeguarding obligations (covered in the next section). Separate from the technical safeguarding requirement, you also need accounts structured to clearly separate client funds from the firm's own operational capital.

Client money accounts must be:

• Titled to clearly identify them as accounts holding end-user funds

• Held at an eligible financial institution in Canada or another reputable jurisdiction

• Kept entirely separate from the PSP's own assets under all circumstances

• Reconciled daily against your internal client money records

For PSPs handling client funds in multiple currencies such as CAD, USD, EUR, GBP, and others — separate accounts per currency are the cleaner operational structure, both for reconciliation purposes and for presenting a clear audit trail to the Bank of Canada during supervisory reviews.

Practically, securing dedicated multi-currency client money accounts at a Canadian bank is one of the harder steps in PSP setup. RBC and TD have financial institutions desks that handle these structures, but onboarding requirements are stringent.

International providers, especially under the BaaS framework, are increasingly used as practical solutions for the non-CAD legs of a client money operation — EUR, GBP, and USD — while a Canadian bank handles CAD client money. Get in touch if you would like to receive an up to date list of BaaS providers that can support Canadian PSPs.

Safeguarding Account for a Canadian PSP

The RPAA's safeguarding requirement is one of its most operationally significant provisions and came fully into force on September 8, 2025. If your PSP holds end-user funds, you must protect those funds through one of two prescribed methods:

Option 1 — Trust Account: End-user funds are held in a designated trust account that is separate from the PSP's own assets and not available to the PSP's creditors in the event of insolvency. This is typically the simpler option for most PSPs. The trust account must be held with an eligible financial institution, and it is recommended — and in many cases required by banks — that a third-party trustee is appointed to ensure the legal separation is clear and enforceable.

If you act as your own trustee, consult Canadian legal counsel before proceeding. The trust relationship must be documented in a formal trust agreement that explicitly describes the PSP's obligations, the trustee's role, and the rights of end users to the funds held.

Option 2 — Insurance or Guarantee: Rather than segregating funds in a trust account, the PSP obtains an insurance policy or guarantee from an eligible provider that would cover the full value of end-user funds held at any given time. This is a less common approach in practice because the insurance market for this type of coverage is limited in Canada and pricing can be significant for PSPs holding material client balances.

For most RPAA-registered PSPs, Option 1 — a dedicated trust account at a Schedule I Canadian bank or credit union — is the practical default. The account must be titled as a trust account, the trust deed must reference the RPAA obligations, and the account must be reconciled to your client money ledger no less than daily.

Keep detailed records of all safeguarding arrangements. The Bank of Canada can and will request documentation of your safeguarding framework during supervisory reviews, and failing to demonstrate adequate end-user fund protection is one of the most serious compliance failures under the RPAA.

Crypto OTC and On/Off Ramps for a Canadian PSP

The RPAA explicitly covers fiat payment functions — it does not directly regulate virtual currency activities, which remain under FINTRAC's MSB framework. However, the two frameworks interact meaningfully when a PSP provides both fiat and crypto services, which is an increasingly common business model.

For RPAA-registered PSPs that also hold FINTRAC MSB registration covering virtual currency, crypto OTC and on/off ramp operations require careful structural separation. Client funds held for fiat payment functions fall under RPAA safeguarding requirements. Crypto assets held on behalf of clients are governed by FINTRAC's virtual currency reporting requirements — Large Virtual Currency Transaction Reports (LVCTRs) for transactions of CAD $10,000 or more within a 24-hour period.

Practically, Canadian PSPs seeking crypto OTC and on/off ramp capability have several banking and infrastructure options:

Domestic crypto-friendly banking: banks and some credit unions will work with FINTRAC-registered MSBs on crypto-adjacent banking, though fiat-to-crypto settlement flows require clear documentation of the counterparty and transaction purpose.

International OTC providers: PSPs frequently partner with established OTC desks for institutional crypto liquidity, settling the fiat leg through their PSP bank account and the crypto leg through a custodial relationship.

Stablecoin rails: USDT and USDC have become practical settlement instruments for Canadian PSPs serving international counterparties.

Any on/off ramp arrangement must be documented in your RPAA risk management framework and reviewed by your compliance officer. The Bank of Canada's October 2024 guidance explicitly added cryptocurrency-backed service providers to its case scenario library, confirming that PSPs offering services backed by cryptocurrencies are captured by the RPAA when fiat functions are involved.

If you would like to explore providers that support crypto payment flows and OTC transactions on behalf of Canadian PSPs and MSBs, send us a message requesting the list.

Yield on Cash Balances for a Canadian PSP

One of the less-discussed commercial considerations for RPAA-registered PSPs is the question of yield on client money balances. The RPAA is clear that client money cannot be used for the PSP's own benefit — it cannot be invested speculatively, commingled with firm assets, or used as collateral for the PSP's obligations.

However, yield on safeguarded client balances is not categorically prohibited, provided it is structured correctly. The key considerations are:

Who does the yield belong to? If your PSP's terms of service with end users specify that interest or yield on held balances accrues to the end user, you can pass that yield through. Several Canadian PSPs are building this as a product feature — offering end users a modest return on their payment account balances, similar to what neobanks offer on savings accounts.

High-quality liquid instruments: For larger PSPs holding material client balances, some of the safeguarded funds may be held in high-quality liquid assets rather than purely in cash deposit accounts, provided the investment structure is consistent with the trust account framework and the funds remain immediately available for client withdrawals. Government of Canada treasury bills and short-term money market instruments are the most commonly used instruments for this purpose.

Operational yield: The PSP's own operational account balance can of course earn standard business deposit interest from its Canadian bank or credit union, which is entirely unrestricted.

How a Canadian PSP Can Partner with BaaS Providers

Banking-as-a-Service (BaaS) is a natural fit for RPAA-registered PSPs that want to offer branded financial products — payment accounts, virtual IBANs, card programs, or embedded payments — without building the full banking infrastructure themselves.

The RPAA is compatible with BaaS partnerships. The PSP remains the regulated entity responsible for compliance with the Bank of Canada, while the BaaS provider supplies the underlying infrastructure. The critical requirement is that the third-party BaaS arrangement is documented within the PSP's operational risk management framework, which must address third-party risk explicitly.

Relevant BaaS and embedded banking providers with Canadian or North American reach worth considering include:

Galileo Financial Technologies (a SoFi company) — provides payment infrastructure, virtual account issuance, and card program management used by North American fintechs. Integrates well with Canadian PSP structures needing USD and CAD payment accounts for end users.

Marqeta — card-issuing infrastructure used by global fintechs. Allows RPAA-registered PSPs to issue branded Visa or Mastercard debit cards to their end users with real-time spend controls.

Peoples Group (Canada) — a Canadian trust company and CDIC member increasingly acting as a banking partner for fintech and payment companies in Canada. Provides trust account infrastructure well-suited to RPAA safeguarding requirements, and offers API-based account issuance for PSP clients.

When structuring a BaaS partnership, your RPAA risk management framework must document the third-party provider's role, the data flows, the resilience measures in place if the BaaS provider experiences an incident, and the controls ensuring end-user fund protection is maintained throughout. The Bank of Canada will review third-party arrangements during supervisory assessments.

Risks of Serving Clients Based Outside Canada and Banking Implications

The RPAA has extraterritorial reach — it applies to any entity performing retail payment activities for end users in Canada, regardless of where the PSP is incorporated. The reverse is also true: a Canadian-incorporated PSP serving predominantly non-Canadian clients still falls under the RPAA, and the banking implications of that cross-border client base are significant.

AML and correspondent banking risk: Canadian banks assess the jurisdictions of a PSP's end users as part of their ongoing due diligence. A Canadian PSP with a predominantly Canadian client base is a lower-risk banking client than one where most clients are in high-risk jurisdictions — sanctioned countries, FATF grey-listed jurisdictions, or markets with weak AML frameworks. If your client base includes end users in jurisdictions that Canadian banks consider elevated-risk, expect your bank to apply enhanced due diligence, request additional documentation about your AML controls, and potentially restrict certain transaction types or corridors.

FINTRAC reporting on international flows: Electronic funds transfers of CAD $10,000 or more sent internationally trigger Electronic Funds Transfer Reports (EFTRs) with FINTRAC within five business days. For PSPs with large volumes of international outbound payments, this creates a continuous reporting obligation that requires robust transaction monitoring infrastructure.

Banking derisking: This is the most acute practical risk. If a Canadian PSP's international client base shifts toward jurisdictions that a Canadian bank considers too risky, the bank may choose to exit the relationship — a phenomenon known as derisking. This has been a significant issue for MSBs and PSPs globally, and Canada is not immune. Maintain your banking relationship proactively: provide your bank with regular transaction volume reporting, demonstrate that your AML controls are working, and flag any material changes in your client base before your bank discovers them through transaction monitoring.

Cross-border fund safeguarding: The RPAA permits end-user funds to be held with foreign financial institutions if those institutions are subject to a comparable regulatory framework. For PSPs serving international clients and holding client funds in multiple currencies at foreign banks, document the regulatory framework of each institution in your safeguarding policies and confirm comparability with your compliance officer.

Currency exposure: Holding client funds in non-CAD currencies creates FX exposure if there is a mismatch between the currency clients deposit and the currency the PSP holds. Currency hedging for client money is operationally complex — ensure your treasury policy, trust deed, and operational risk framework address how FX positions on client balances are managed.

Onboarding Process with a Bank for a Canadian PSP

Understanding what to expect during bank onboarding — and how to prepare — dramatically improves your chances of a successful outcome. Here is what the process typically looks like and what you need to have ready.

Phase 1: Pre-Application Preparation (4–8 weeks)

Before approaching any bank, have the following fully prepared:

• Bank of Canada PSP registration certificate and registration number

• FINTRAC MSB registration number and compliance program documentation

• Certificate of incorporation and corporate registry documents (federal or provincial)

• Beneficial ownership register — documented to the ultimate individual owner for all 25%+ shareholders

• Board resolution authorising account opening and naming authorised signatories

• Passports and proof of address for all directors and beneficial owners

• Audited financial statements or management accounts (if newly registered, a detailed business plan with financial projections)

• Written description of your business model — what payment functions you perform, who your end users are, which jurisdictions you serve, expected monthly transaction volumes and average transaction values

• Your RPAA operational risk management framework and safeguarding policy

• Your FINTRAC AML compliance program documentation including your compliance officer appointment letter

• Your transaction monitoring policy and any technology systems used for AML screening

• Your third-party provider agreements (BaaS, banking infrastructure, technology)

Phase 2: Bank Selection and Approach (2–4 weeks)

Do not approach multiple banks simultaneously. In the financial institutions space, parallel applications can become visible and create the impression of a desperate or declined applicant. Identify your primary target bank based on the profile of your business — Canadian Big Five for large, established PSPs with strong operating history; credit unions for mid-sized PSPs with primarily domestic client bases; international EMIs for PSPs needing multi-currency infrastructure quickly alongside a domestic banking application.

Phase 3: Due Diligence and Underwriting (6–16 weeks)

Expect to answer detailed questions about your end users, transaction flows, and compliance controls. Banks will review your website, your terms of service, your privacy policy, and your client-facing documentation. They will assess whether your AML controls are proportionate to the volume and jurisdictional risk of your business.

Be transparent about your international client exposure from the outset. Surprises discovered during due diligence — jurisdictions you failed to disclose, client types not mentioned in the initial application — are a common reason bank onboarding fails at the final stage.

Phase 4: Account Opening and Ongoing Relationship

Once approved, treat the banking relationship as an ongoing compliance relationship, not a one-time transaction. Provide your bank with regular volume reports. Notify them promptly of material changes to your business model, client base, or ownership structure — both the RPAA and your bank's terms require this. A proactive, transparent PSP is a banking client a bank wants to keep. A PSP that surprises its bank with undisclosed changes is at risk of having its account closed.

Conclusion

The RPAA has created a new operating environment for Canadian payment service providers — one with meaningful regulatory obligations but also real commercial benefits. Being a Bank of Canada-registered PSP gives you credibility, future access to Payments Canada membership and Real-Time Rail connectivity, and a framework that protects your end users and your business.

If you are a Canadian PSP registered under the RPAA and need guidance on establishing the right banking relationships — Epico Finance works with regulated payment businesses to structure and secure the banking infrastructure their operations require.