Payment Instructions and Consent: the Small Facts That Change Scope

Whether a platform must register as a money services business for transferring funds is governed by PCMLTFA s. 5(h)(ii) for domestic businesses and s. 5(h.1)(ii) for foreign businesses directing services at Canadians, read with the definitions in PCMLTFR s. 1(2). None of those provisions asks what the company calls itself. A business that describes itself as a software layer, a checkout tool, or a technology provider gets no distance from the test by the description alone.

FINTRAC's analysis works from the actual payment arrangement: what service is performed, how money moves, and who touches the instructions that move it. Payer consent language and payee agreements are part of that fact pattern — they are evidence to be weighed, not conclusions that settle the question either way.

The transfer analysis leans heavily on whether a business receives instructions for the transfer of funds. That short phrase does a lot of work, and it is where thin scope analyses usually fail. The operative questions are concrete: who receives the instruction, who forwards it, and who has the authority to change, hold, or reject it before funds move.

Consider a marketplace that receives payment instructions from buyers at checkout and forwards settlement instructions to a payout partner. It is tempting to argue that because the instructions are passed along, the platform never really 'received' them. That reasoning does not hold: forwarding an instruction is downstream of receiving it, not a substitute for it. The more useful distinction is between a party that merely transmits a message it cannot act on and a party that stands in the chain with authority over the instruction or the funds. Where a business sits on that line is exactly what the documentation should establish — and where the line falls in a specific arrangement is a question for the current FINTRAC guidance, not intuition.

Founders often reach for consent as a shield: the buyer agreed to pay through the platform, the merchant signed an agreement accepting payment that way, so surely the platform is just executing the parties' wishes. But a buyer choosing to pay 'through' a platform is a description of the arrangement, not a legal characterization of it. Consent tells you the parties agreed to a funds-flow; it does not tell you whether that funds-flow is a transfer service under the Act.

These clauses can even point the other way. A payee agreement authorizing the platform to accept payment on the merchant's behalf, or payer terms routing money through a platform-controlled account, are facts that tend to show the platform stands inside the flow of funds rather than beside it. The honest way to use these documents is as inputs: read them for what they say about who controls funds and instructions at each step, and let that drive the conclusion.

Scope memos in this area often cite FINTRAC's historical policy interpretations on merchant servicing and payment processing, grouped under PI-7670. FINTRAC withdrew those positions effective April 27, 2022, and confirmed the change in notices dated April 27 and July 21, 2022. Anything reasoned from PI-7670 is historical context only.

A practical consequence: if a platform's scope position was written before mid-2022, or borrows language from an older opinion or a competitor's terms of service, it needs to be reassessed against the current FINTRAC MSB guidance and the 2022 notices rather than assumed to still hold.

A defensible scope file for a payments platform typically contains four things. First, a funds-flow diagram showing every hop money takes, including any moment funds sit in an account the platform controls — a payroll platform that briefly holds employer funds before disbursing wages has a materially different diagram than one whose processor settles directly to employees. Second, the contracts: payer-facing terms, the payee agreement, and settlement-partner agreements, annotated for who can amend, hold, or reject an instruction. Third, a written scope conclusion that states the reasoning, cites the current guidance relied on, and records the date of the analysis. Fourth, a trigger list — new corridors, new settlement partners, a change to who holds funds — that prompts a re-analysis.

Businesses that conclude they are in scope register under PCMLTFA s. 11.1 and build the compliance program required by PCMLTFA s. 9.6 and PCMLTFR ss. 156–157. Businesses that conclude they are out of scope keep the same file: the documented reasoning is what shows the conclusion was reached carefully if the facts are ever questioned.