FINTRAC MSB Registration: When to Register and Keeping It Current

The sequencing rule is the part founders most often get backwards. If your business falls within the money services business definition — PCMLTFA s. 5(h) for domestic businesses, s. 5(h.1) for foreign businesses directing services at people in Canada — the registration obligation under PCMLTFA s. 11.1 applies before you begin operating, not within some grace period after launch. Soft-launching a regulated service — including a beta that handles real customer funds — can already amount to operating, so the safe habit is to treat registration as a pre-launch dependency and check current FINTRAC guidance on when a service is being offered, rather than assuming a quiet launch sits outside the rule.

The practical consequence is that the scope review has to happen early in the product timeline. Deciding whether a planned feature amounts to an MSB service takes time, and if the answer is yes, both registration and the supporting compliance program — the reasonably designed, risk-based program required by PCMLTFA s. 9.6, with the elements set out in PCMLTFR ss. 156–157 — need to exist before the service goes live. Teams that leave the analysis until the launch checklist usually discover the dependency too late to fix cheaply.

Part of keeping a registration current is recognizing that the perimeter itself moves. PCMLTFR s. 29.1 prescribes additional services for the MSB and FMSB definitions — cheque-cashing services and crowdfunding platform services are prescribed under it. Transporting currency or negotiable instruments (armoured car services) became a reporting-entity obligation in force July 1, 2024, and acquirer services for private automated banking machines (private or white-label ATMs) became a registerable MSB/FMSB obligation in force October 1, 2025.

This cuts the other way too: positions can be withdrawn. FINTRAC withdrew its PI-7670 policy interpretations on merchant servicing and payment processing effective April 27, 2022, so an old interpretation letter in a data room may describe a position that no longer exists. A scope memo written against the rules as they stood two years ago is evidence of diligence at that time, not an answer for today — re-run the analysis against current FINTRAC guidance when the rules change or when a re-registration cycle comes around.

Registration is not a one-time launch task. FINTRAC's registration reflects the services you told it you provide, and adding or changing a service line means re-checking whether that record still matches the actual business. A common pattern: a company registers for foreign exchange dealing, later adds virtual currency transfer, and never revisits the registration because the company itself is already registered. The entity was registered; the new service was not reflected. That gap is exactly what an update exists to close.

The same check applies inside the compliance program. The risk assessment, policies, and training required under PCMLTFR ss. 156–157 were built around the original services; a new service line brings new typologies, new customer profiles, and often new reporting obligations that the existing documents do not address. In practice, businesses treat any material product change as a two-part task: confirm the registration record still describes the business, and confirm the program documents cover the new activity before it launches.

Some provinces license money-services activity under their own statutes. Those regimes serve provincial purposes and run on their own applications, fees, and renewal cycles — they are not a federal AML registration. Holding a provincial money-services licence does not remove the requirement to register with FINTRAC before operating an MSB service, and being registered with FINTRAC does not satisfy a provincial licensing requirement either. The two are cumulative: a business in a licensing province typically needs both.

The confusion usually starts with vocabulary. A team that has just finished a demanding provincial application reasonably feels licensed, and the federal registration gets mentally filed as done. The safer habit is to track them as separate line items with separate owners, renewal dates, and update triggers, so that a change reported to one regulator prompts the question of whether the other needs it too.

The paper trail for registration mechanics is short but valuable. Keep a dated scope memo recording which services you concluded are MSB services and why, referencing the guidance you relied on. Keep a snapshot of what the FINTRAC registration says at any given time. Maintain a plain trigger list — new service line, new corridor, new delivery channel, a regulatory change like the 2024 and 2025 additions — that forces the question of whether the registration and program need updating, and name the person who owns that question. When someone later asks why the registration looked the way it did on a given date, the answer should be a document, not a memory.