Trade finance platforms and payment infrastructure
Trade finance platforms that layer fintech infrastructure onto documentary and structured trade payment flows face fund flow and MSB questions that traditional trade finance did not require.
TaaS products that hold, move, or convert client funds on a managed basis can engage MSB registration requirements that technology framing does not resolve.
Treasury-as-a-Service products — platforms that manage cash, liquidity, or payment operations for business clients — occupy an interesting position in the Canadian regulatory framework. The product is framed as a service, the client retains the cash, and the platform provides the technology and operational infrastructure. Whether that framing resolves the MSB analysis depends on what the platform actually does with client money.
Treasury-as-a-Service products vary considerably in their structure. At one end, a TaaS platform may provide reporting tools, cash flow forecasting, and payment initiation interfaces that connect to a client’s existing bank accounts, without ever holding client funds. At the other end, a TaaS platform may receive client funds, hold them in a platform account, allocate them across multiple currencies or yield-generating instruments, and disburse them on client instruction.
The MSB analysis concentrates on the second type. A platform that receives client funds, holds them in a commingled or segregated account under the platform’s control, and disburses them based on client instructions is holding funds on behalf of others and transmitting them at direction. Those activities engage the fund transmission and, where foreign exchange is involved, the foreign exchange dealing definitions under the PCMLTFA.
The technology framing — that the platform is a software system rather than a financial intermediary — does not resolve the analysis. The question is what activity is performed, not how it is described.
TaaS products that receive client payments before passing them to their ultimate destination create a float position. During the period the platform holds those funds, the platform is in a custodial position relative to the client.
Whether that custody period is brief, as in a same-day settlement model, or extended, as in a model where the platform holds funds pending instruction, affects the risk profile of the product but not the basic regulatory analysis. Custody of client funds pending disbursement is the activity that engages the MSB framework, regardless of the duration.
The basis on which the platform holds client funds during the custody period also matters. Holding client funds as agent, as custodian, or commingled with platform funds each raises different legal issues. The agreements between the platform and its clients should accurately reflect the legal basis for the custody arrangement.
TaaS products with foreign exchange or cross-border functionality add the foreign exchange dealing analysis to the fund transmission analysis. A platform that holds client funds in multiple currencies, that converts between currencies on client instruction, or that facilitates cross-border payments by coordinating between local and foreign bank accounts is performing foreign exchange dealing activity in the course of its operations.
Even where the exchange itself is performed by a banking partner, the platform’s role in facilitating that exchange, quoting rates, or aggregating client positions for exchange purposes needs to be assessed. The distinction between providing access to exchange services and performing exchange activity is not always clear in TaaS product designs.
A TaaS operator should map the fund flow for its product in the same way any payment platform should: identify every step at which funds are received, held, moved, or converted, and identify every entity that performs those steps. The regulatory analysis then follows from the map.
Where the analysis indicates that the platform is performing regulated activity, the appropriate next steps depend on the specific activity and structure. Registration as an MSB may be required. Partner agreements may need to be structured to allocate compliance responsibilities clearly. Banking relationships need to be established on the basis of the platform’s actual regulated status.
Trade finance platforms that layer fintech infrastructure onto documentary and structured trade payment flows face fund flow and MSB questions that traditional trade finance did not require.
PaaS platforms that enable clients to offer payment functionality need to define clearly whether the platform or the client bears the regulatory obligations that follow from the payment activity.
Supply chain finance platforms move funds in patterns that can engage MSB registration requirements depending on who holds money and how it flows between buyers, sellers, and capital providers.
Companies building at the intersection of trade, treasury, supply chain, and fintech payment infrastructure face legal questions that arise earlier than they expect.