A pre-registration undertaking (PRU) is the bridge product the Canadian Securities Administrators use to let crypto trading platforms continue serving Canadian users while a formal Restricted Dealer registration is assessed. It is binding. It is bilateral. And it is misunderstood often enough that platforms operate under one without fully understanding what they have committed to.
What a PRU is
A PRU is a written undertaking — typically from the platform's senior management and legal counsel — that the platform will operate in compliance with a defined set of conditions while the regulator assesses its application for full registration. The conditions vary by platform but are drawn from a published template that includes:
- Restrictions on which crypto assets can be made available to Canadian users.
- Custody requirements, including segregation, hot-wallet limits, and proof-of-reserves obligations.
- Limits on margin, leverage, derivatives, and yield products.
- Marketing restrictions, particularly around language used in advertising to retail users.
- Reporting obligations — periodic submissions on activity volumes, asset holdings, and incident disclosures.
- A commitment to apply for full Restricted Dealer registration within a defined timeline.
What a PRU is not
A PRU is not a registration. It does not confer the rights of a registrant. It does not satisfy securities laws on its own — it is a regulatory accommodation that recognizes the platform's intent to register, in exchange for operating under conditions in the interim.
A PRU is also not a permanent state. Regulators view the PRU as a stepping stone toward Restricted Dealer registration. Platforms that operate under a PRU for an extended period without progressing toward registration draw scrutiny — and in some cases, an instruction to wind down Canadian operations.
What it commits the platform to
The PRU is enforceable. Breach of a PRU condition is treated similarly to a breach of registration conditions, with consequences ranging from heightened reporting to a formal direction to cease operations. The conditions are not informal best practices — they are the operating perimeter.
Operating outside the perimeter, even temporarily, is the most common reason platforms get into trouble during the PRU period. Common breaches:
- Listing an asset not previously approved under the platform's listing methodology.
- Marketing in a province where the PRU does not extend, or using marketing language inconsistent with the conditions.
- Offering a product (staking, yield, derivative) that the PRU explicitly excludes.
- Exceeding hot-wallet limits during a period of operational stress.
- Missing a reporting deadline.
How PRU conditions evolve toward registration
The Restricted Dealer registration that follows a PRU usually incorporates much of the PRU's perimeter, with several differences:
- The conditions become formal registration terms. They appear in the registration decision and apply on an ongoing basis.
- Reporting cadence may change. Some PRU reports become quarterly; some become annual; new requirements may be added.
- Capital and insurance commitments become firm. What was a stated intention under the PRU becomes a registration condition.
- Asset-listing methodology is reviewed in depth. The PRU period gives the regulator a window to assess how the methodology has been applied in practice — that practice informs the registration terms.
- The "interim" framing falls away. Registration is durable; PRU was transitional.
The transition window
Moving from PRU to registration is rarely a single decision letter. It typically involves several rounds of clarification, an updated business and compliance description, and an in-depth review of the operations that have evolved during the PRU period. Platforms that have grown materially during their PRU — new asset types, new product lines, new jurisdictions — will face deeper review than platforms that have held the line.
If you're considering a PRU
The PRU is a useful tool if the platform's roadmap to full Restricted Dealer registration is concrete and the conditions are operationally workable. It is a poor fit if the platform's commercial model depends on activities the PRU excludes, because operating outside the PRU has more friction than waiting for registration would have caused.
The starting question is not "can we get a PRU." It is "are the standard PRU conditions compatible with our 12-month operating plan." If the answer is yes, the PRU shortens the path. If not, addressing the gaps before requesting one is cheaper than discovering them after signing.