Library
PublishedMSB & FMSB ScopeLast reviewed 2026-07-09 · 7 min read

White-Label, Embedded Finance and Group Structures: Who Has the Obligation?

In white-label and embedded-finance programs, MSB status follows the entity actually engaged in the business of providing the service — traced through contracts, funds custody and settlement instructions — while agents and reliance under PCMLTFR ss. 106–107 delegate the work, never the obligation. The article also covers why the program partner is itself a client from service-agreement signature (s. 4.1(d)), why group companies are scoped one entity at a time, and how to document a no-MSB conclusion without overstating it.

Reader question

In a white-label or embedded-finance program — or a corporate group — which entity carries the MSB obligations?

The obligation follows the service provider, not the brand

Canadian AML obligations are assigned by legal entity, not by brand. The money-services-business paragraphs of the PCMLTFA — s. 5(h) for domestic businesses and s. 5(h.1) for foreign ones — catch a person or entity "engaged in the business of providing" the listed services; the newest listing, acquirer services in relation to a private automated banking machine at s. 5(h)(iv.1), uses exactly that wording. In a white-label or embedded-finance program the end user sees one name on the interface, but the scoping question is which entity actually provides the service under subparagraphs 5(h)(i)–(v): who contracts to move or exchange the funds, who holds them in flight, who gives the settlement instruction on the rail. Whichever entity that is carries the full package — registration with FINTRAC, the identification triggers in PCMLTFR s. 95(1) (for example, a request to initiate an electronic funds transfer of $1,000 or more), record-keeping and reporting. A trademark licence, by itself, moves none of that.

White-label programs: delegate the work, keep the status

What a program can delegate is execution. Under PCMLTFR s. 106, a reporting entity "may rely on an agent or mandatary to take the measures" to verify identity under s. 105(1) — which is how a front-end partner typically collects and checks ID for the provider behind it. Under s. 107, an entity may instead rely on verification already performed by another person or entity referred to in s. 5 of the Act, or by an affiliated foreign entity with similar identification and record-keeping requirements; within corporate groups, s. 105(1)(e) also offers an affiliate-or-member method. None of these move the obligation. The reporting entity remains the one required to verify, and it must hold the s. 108 records — paragraphs (a) to (i), keyed to the method used — even when a partner performed the steps. Set out the mandate in the program agreement, and check the current FINTRAC guidance on methods to verify identity for what the arrangement itself must cover.

In embedded finance, the distribution partner is usually also a client

The brand partner is not only the MSB's distributor — it is typically the MSB's client. Under PCMLTFR s. 4.1(d), an MSB whose client is an entity enters a business relationship when it enters into a service agreement for services under subparagraphs 5(h)(i)–(v) of the Act (s. 4.1(e) is the foreign-MSB equivalent). Signature day therefore starts real work: verify the partner entity against its certificate of incorporation or equivalent records (ss. 109 and 112); obtain the names of its directors and the names and addresses of everyone owning or controlling 25% or more, plus information on ownership, control and structure (s. 138(1)), and take reasonable measures to confirm accuracy (s. 138(2)); where an information record must be kept, make the third-party determination under s. 137.

If beneficial ownership cannot be obtained or confirmed, s. 138(4) requires reasonable measures to verify the identity of the entity's chief executive officer and application of the special measures under s. 157. The relationship then sits under ongoing monitoring per s. 123.1 — detecting reportable transactions, keeping client information current, reassessing risk, and checking that activity matches what is known. Since October 1, 2025, material discrepancies with the Corporations Canada individuals-with-significant-control database, for CBCA corporations assessed as high risk, must be reported to the CBCA Director within 30 days (s. 138.1).

Group structures: scope each legal entity on its own

Corporate groups get scoped one entity at a time, and the last two years show why. Cheque-cashing services became an MSB-prescribed service under PCMLTFR s. 29.1 — alongside crowdfunding platform services — with obligations in force April 1, 2025. Factoring did not: a factor is a separate reporting-entity class under PCMLTFA s. 5(i) and PCMLTFR s. 24.1, also from April 1, 2025. Financing or leasing entities are another class again under s. 5(j) and s. 24.15, covering among other things business-purpose financing or leasing of property other than real property, and passenger vehicles in Canada. Private-ABM acquirer services sit inside the MSB definition itself at s. 5(h)(iv.1), in force October 1, 2025 — the same date title insurers came in as their own class; the mortgage sector arrived earlier, on October 11, 2024.

A group with a payments subsidiary, a factoring arm and a leasing arm can therefore hold three different obligation sets, and an analysis done for one entity does not answer for its siblings. A non-Canadian group entity serving the same program raises the separate foreign-MSB question under s. 5(h.1) — check the current FINTRAC guidance before assuming it falls outside.

The facts that usually decide a scoping review

A defensible scoping file typically turns on about a dozen facts, established with evidence rather than intentions: which entity contracts with the end user; which entity holds funds, even briefly; who instructs settlement; whose name appears on the rail (Interac e-Transfer or SWIFT records are useful evidence); the full flow of funds, including refund and failure paths; which entity earns the fee; whether any activity matches the subparagraph 5(h)(i)–(v) categories or a prescribed service under s. 29.1; whether the activity is better characterized as factoring or financing/leasing, which points to a different class entirely; where each entity is incorporated; what the partner agreement assigns to each party; and when each product launched relative to the in-force dates above.

How to document a no-MSB conclusion without overstating it

Write the conclusion narrowly: a dated memo stating the facts relied on, the provisions considered, and the answer for each named entity on those facts as of that date — with listed re-review triggers such as new products, new rails, new group entities and new in-force dates. Avoid a standing "we are not regulated" declaration. The October 2024, April 2025 and October 2025 waves each moved the perimeter, and a conclusion that was sound when the program agreement was signed can be stale by launch. A memo that says exactly what was decided, on what facts, and when it must be revisited is worth more in a FINTRAC examination — and to a bank or partner doing diligence — than a broad assurance no one can trace.

At a glance

  • MSB obligations attach to the legal entity "engaged in the business of providing" the listed services (PCMLTFA s. 5(h)/(h.1)) — trace contracts, funds custody and settlement instructions, not the logo on the interface.
  • A white-label partner can execute identity verification as an agent or mandatary (PCMLTFR s. 106), and reliance on another s. 5 entity's prior verification is available (s. 107) — but the obligation and the s. 108 records stay with the reporting entity.
  • For an MSB with an entity client, signing the service agreement itself forms a business relationship (s. 4.1(d)), pulling in entity verification (ss. 109/112), beneficial ownership (s. 138), third-party determination (s. 137) and ongoing monitoring (s. 123.1).
  • Group companies are scoped one by one: cheque-cashing is an MSB-prescribed service (s. 29.1, in force April 1, 2025), but factors (s. 24.1) and financing or leasing entities (s. 24.15) are separate non-MSB classes, and PABM acquirer services entered the MSB definition itself on October 1, 2025.
  • A no-MSB conclusion should be a dated memo — facts relied on, provisions considered, entity-by-entity answer, named re-review triggers — not a standing declaration.

Common mistakes

  • Reading the brand on the app as the reporting entity: obligations attach to whichever legal entity is engaged in the business of providing the s. 5(h) service, traced through contracts and the flow of funds.
  • Treating an agent or reliance arrangement as transferring the obligation — PCMLTFR ss. 106–107 delegate the verification steps only; the reporting entity still owns the requirement and must hold the s. 108 records.
  • Scoping the group as one unit: factors (s. 24.1) and financing or leasing entities (s. 24.15) are separate reporting-entity classes, not MSB-prescribed services, so an MSB analysis for the payments subsidiary says nothing about its siblings.
  • Missing that signing the program service agreement itself forms a business relationship with the entity client (s. 4.1(d)) — beneficial ownership, third-party determination and ongoing monitoring start then, not at the first transaction.
  • Writing an undated, unconditional "we are not an MSB" position — the perimeter moved on October 11, 2024, April 1, 2025 and October 1, 2025, and a conclusion without stated facts and re-review triggers overstates what was decided.
  • Ignoring the foreign-MSB paragraph (s. 5(h.1)) when a non-Canadian group entity participates in the same program.

Sources

Regulatory anchor: PCMLTFA s. 5(h), (h)(iv.1), (h.1), (i), (j); PCMLTFR ss. 4.1, 24.1, 24.15, 29.1, 95(1), 105–108, 109, 112, 123.1, 134–137, 138–138.1

This content is general education and industry perspective. It is not legal advice, does not create a solicitor-client relationship, and does not replace the PCMLTFA, the PCMLTFR, FINTRAC guidance, or advice from qualified legal counsel. It does not guarantee regulatory or bank acceptance. Confirm current law, current FINTRAC guidance, and the full facts before relying on it for a business decision.