Now booking Q3 FINTRAC MSB filings. Reserve a scope call →
Explainer · Provincial

When Québec's AMF overlay applies to your filing.

If you have customers in Québec, the Autorité des marchés financiers likely has a view — even on a federal registration. The triggers, the timing, and what to file in parallel.

6 min read Updated May 2026 Series Provincial overlays

Most Canadian fintech registrations are federal. FINTRAC, the Bank of Canada, the CSA — these are federal or pan-Canadian regimes. But for any platform serving Québec users, the Autorité des marchés financiers (AMF) often has its own view, and the provincial overlay can change the timeline and the scope of the filing materially.

Why Québec is different

Québec maintains a parallel financial-services regulator with jurisdiction that overlaps several federal regimes. The AMF supervises money services businesses operating in Québec under the Money-Services Businesses Act (Loi sur les entreprises de services monétaires), enforces provincial securities law alongside the CSA, and applies consumer-protection oversight that doesn't exist in other provinces in the same form.

The effect: a federal registration does not automatically clear the Québec layer. An MSB registered with FINTRAC and serving Québec customers needs a separate Québec MSB licence. A crypto platform working through CSA registration also engages the AMF where Québec users are involved.

What triggers the overlay

  • Money-services activities offered to Québec residents. Currency exchange, money transferring, cheque cashing, ATM operations, virtual-currency dealing — all caught by the Québec MSB framework if performed for users in Québec.
  • Crypto trading activities involving Québec users. The AMF participates in the CSA process, and the registration terms may include Québec-specific conditions.
  • Marketing or advertising directed at Québec users. Provincial consumer-protection and advertising rules apply, including specific requirements around language (French) and disclosure.
  • Establishing a physical or operational presence in Québec. Beyond purely customer-facing activity, having staff, offices, or operational infrastructure in Québec triggers additional engagement.

What it adds to a federal filing

Separate licensing

The Québec MSB licence is a parallel application, not a notification. It requires its own form, supporting documentation, fees, and review process — typically several months, sometimes running in parallel with the FINTRAC review but on a different timeline.

Personnel and ownership disclosure

The AMF's disclosure expectations for directors, officers, and beneficial owners are similar in spirit to FINTRAC's but distinct in form. Document the federal disclosures with Québec in mind, and the parallel filing is much faster.

French-language obligations

Québec's Charter of the French Language (Bill 96, as amended) creates language obligations that apply to customer-facing materials, contracts, and marketing. For a fintech serving Québec users, this is operational, not theoretical — terms of service, onboarding flows, transactional emails, and complaint-handling materials all engage the rules.

Complaint handling

The AMF applies a structured complaint-handling expectation, with specific timelines and escalation paths to the regulator itself. The complaint policy and operational practice need to reflect this — generic customer-support workflows often do not.

Timing

The most common mistake: treating Québec as a stage-two project. Federal registration takes precedence, the federal application gets filed, and the AMF engagement is deferred until the federal side is settled. The result: a launch into Canada that excludes Québec, or a launch that quietly serves Québec users without the licence, which creates a problem that compounds the longer it runs.

The cleaner approach: scope the Québec filing alongside the federal one, file in parallel where possible, and treat the AMF timeline as part of the project plan rather than a follow-on.

"We'll launch in the rest of Canada first" is a decision, not a default Excluding Québec users at launch is operationally workable — but it requires real geo-restriction at signup and in payment flows, not just a footnote in the terms of service. Half-measures here are a finding waiting to happen.

What to bring to a Québec-aware scope

  • A clear yes/no on whether you intend to onboard Québec users at launch.
  • If yes: a plan for French-language customer-facing materials and complaint handling.
  • If yes: budget for the parallel Québec licence application alongside the federal filing.
  • If no: a real geo-restriction approach, not just a passive disclaimer.
  • An understanding that "in Canada" is rarely uniform — provincial overlays exist in other provinces too, but Québec's is the most distinct.

Operating in Québec? Plan the AMF layer in.

We map federal and Québec filings together so the provincial overlay doesn't surface as a surprise late in the process.