Safeguarding end-user funds under the RPAA: the three routes

The statute is short and the choice is real. Route one, s. 20(1)(a): funds held in trust in a trust account used for no other purpose. Route two, s. 20(1)(b): funds held in a prescribed account or manner, subject to prescribed measures - a limb whose content depends on what the Regulations prescribe, so check the current SOR/2023-229 text before building on it. Route three, s. 20(1)(c): funds in a dedicated account, plus insurance or a guarantee in respect of them at least equal to the amount held. In practice the working decision runs between the trust route and the insurance-or-guarantee route.

Two further points sit in the statute itself. Section 20(3) bars set-off: safeguarded funds cannot be netted against amounts an end user may owe the provider. And the obligation is not aspirational - it has applied to every registered PSP since 8 September 2025, when the RPAA's operational provisions came into force, and it feeds two standing reporting rails.

The statute names the routes; SOR/2023-229 makes them hard to fake. Section 13 disciplines where the money sits: the provider holding safeguarded funds must meet the Regulations' comparable-prudential-standards test, so end-user money cannot simply be parked with an entity outside prudential supervision.

Section 14 disciplines the insurance-or-guarantee route. The insurer or guarantor must be a regulated entity not affiliated with the PSP, and the proceeds must be insolvency-remote: they "will not form part of the payment service provider's estate" and must be "payable for the benefit of end users as soon as feasible". An intra-group guarantee fails the non-affiliation condition by construction; a policy whose proceeds flow back through the PSP's own accounts fails the estate-remoteness one.

Section 15 is the operational core: a written safeguarding framework covering ledgering, identification of end users, procedures for returning funds, and mitigation of legal risks to the funds. It is the document that turns a compliant account into a compliant system - anyone reading it should be able to reconstruct which funds belong to which end user and how they get them back.

A recurring assumption in scoping conversations is that an insured deposit account settles the matter. The Bank of Canada's FAQ on retail payments supervision (January 2026) is explicit that deposit insurance alone "is not sufficient". The logic follows from the statutory wording: deposit insurance protects depositors against the failure of the account provider, while the s. 20(1)(c) insurance or guarantee must respond to the failure of the PSP itself, with proceeds that bypass its estate and reach end users. Different risk, different beneficiaries, different trigger - and only the second discharges the obligation. A provider that wants a dedicated account with an insurance wrapper still has to procure a policy or guarantee purpose-built to the s. 14 conditions.

Safeguarding is not a one-time setup; two reporting rails watch it continuously. The annual report under s. 21, due by 31 March each year, must cover - among the items prescribed by SOR/2023-229 s. 19 - the safeguarding arrangements themselves plus value, volume and end-user-funds metrics. The first reports of the full supervisory era fell due on 31 March 2026, so registered PSPs have now attested to their stack once - and will every year.

The significant-change notice under s. 22 is the sharper rail. A change that "could reasonably be expected to have a material impact on operational risks or the manner in which end-user funds are safeguarded" must be notified to the Bank at least 5 business days before implementation (SOR/2023-229 s. 20(1)). Read that literally: switching account providers, replacing a guarantee with a trust structure, or re-papering the safeguarding framework is a notify-first event.

Two adjacent clocks complete the calendar. An incident that materially affects end users must be notified to them and to the Bank "without delay" under s. 18 - the Act sets no fixed hour window, whatever secondary summaries claim. And registration-information changes carry their own windows: notice within 30 days after most changes, some requiring 30 days in advance, data-location changes 60 days before effect (SOR/2023-229 ss. 35-36).

Now run the same requirements through an acquisition. Under RPAA s. 24(1), if anyone plans to acquire control of a registered PSP - one third of the votes or more, per SOR/2023-229 s. 21 - the registered PSP must submit a new registration application that takes the planned acquisition into account, and be registered on that basis before the acquisition happens. Once control passes, the prior registration can be revoked under s. 52(f). Buying does not skip the queue: the acquisition-adjusted application faces the same completeness review and Minister of Finance national-security screening, whose only statutory clocks are 60 days to decide whether to review, extendable by 60, and 180 days for a full review, also extendable. No end-to-end service standard is published.

Safeguarding is where that application gets concrete. The s. 29(1) application content includes end-user funds information and the safeguarding arrangements, so the buyer is effectively re-filing the target's safeguarding stack under the new ownership structure. Three items deserve day-one attention. The insurance or guarantee: s. 14's non-affiliation condition should be re-tested against the post-closing group, because a guarantor independent of the seller may not be independent of the buyer - a diligence question to resolve, not a settled reading. The written framework: the s. 15 ledgering, end-user identification and fund-return procedures must describe the business as the buyer will actually run it. And the notice calendar: any post-closing change to how funds are safeguarded is a s. 22 significant change carrying the 5-business-day advance notice.

This is the rail on which SKY7's live Canadian lot sits: a FINTRAC-registered MSB whose Bank of Canada RPAA application has been submitted - an application in review, not a registered PSP. The honest version of that asset is a head start on the paperwork plus a FINTRAC registration that the Bank's refusal grounds under s. 48 take into account, not a licence that changes hands at closing. For the wider mechanics, see our Canadian MSB acquisition pillar. For scale: the Bank's registry listed 1,463 registered PSPs and 486 applications in review on 11 July 2026, with 40 refusals and 14 revocations published with reasons - counts that drift, so verify them on the registry before relying on them.