Embedded payments in SaaS products: MSB risk
SaaS platforms that embed payment functionality need to assess whether their role in the fund flow creates MSB exposure independent of their payment partners.
Cross-border payment flows into and out of Canada engage MSB registration requirements that depend on where activity occurs and which entities perform it.
Cross-border payment products that touch Canada, or that are operated by entities with a Canadian presence, need to assess MSB registration under FINTRAC’s framework. The Canadian rules apply based on the activity performed, not only on where the company is incorporated.
Dealing in foreign exchange is one of the enumerated activities that trigger MSB registration under the PCMLTFA. An entity deals in foreign exchange when it exchanges one currency for another, whether as the primary product or as an incidental step in a broader payment flow.
For cross-border payment platforms, foreign exchange dealing is almost always present somewhere in the flow. A platform that receives Canadian dollars from a sender and delivers a foreign currency to the recipient is dealing in foreign exchange. A platform that quotes an exchange rate to the user, even if a banking partner performs the actual conversion, may be engaged in foreign exchange dealing depending on the structure.
The registration requirement attaches to the entity performing the dealing, not to the entity that holds the banking relationship. Platform structures that separate the customer-facing exchange function from the underlying bank account do not resolve the registration question for the customer-facing entity.
International money transfer, also described as remittance, is fund transmission activity at the core of the MSB framework. An entity that receives funds in Canada and ensures their delivery to a recipient outside Canada, or that receives funds from a foreign sender for delivery to a Canadian recipient, is performing fund transmission.
The technical mechanism of the transfer does not affect the classification. Whether the platform uses correspondent banking, SWIFT, a network of pre-funded accounts, or a virtual currency rail to effect the transfer, the activity of transmitting funds is what engages the MSB definition.
International platforms that direct their services to Canadian senders or Canadian recipients, or that process transactions through Canadian bank accounts or entities, should assess their Canadian regulatory exposure regardless of where they are headquartered.
FINTRAC asserts jurisdiction based on Canadian nexus, which can arise in several ways for international payment operators. Having a place of business in Canada is the clearest basis. Directing services at Canadian customers, processing transactions involving Canadian bank accounts, or employing Canadian staff can also establish nexus depending on the facts.
International operators that specifically exclude Canadian customers from their service may reduce but not necessarily eliminate Canadian regulatory exposure, particularly if Canadian users access the service anyway or if Canadian entities are involved in the payment infrastructure.
The Canadian nexus question is fact-specific and should be assessed based on the actual operation of the platform, not on the intended scope of the product.
Cross-border payment operators assessing Canadian regulatory exposure should map their fund flows to identify which steps occur in Canada or involve Canadian entities, identify all exchange and transmission activity within those flows, determine which entities in the structure are performing regulated activity, and assess whether any of those entities are registered or need to register.
Banking partner diligence for cross-border payment platforms typically includes questions about MSB registration status, the AML compliance program, transaction monitoring, and the geographic scope of the service. Having the regulatory analysis and compliance documentation ready before beginning that diligence is more efficient than developing it in response to partner questions.
SaaS platforms that embed payment functionality need to assess whether their role in the fund flow creates MSB exposure independent of their payment partners.
Marketplaces that handle funds between buyers and sellers face MSB registration questions that the platform label does not resolve.
The regulatory classification of a payment product follows from how funds actually move, not from how the product is described.
Platforms that disburse wages or contractor payments face fund flow and MSB analysis that depends on who holds money and how it moves.