The key question is what was tested, not how long it was called a trial operation
If a client has already handed real funds or stablecoins to the platform, and the platform is responsible for exchange, custody or delivery, the test label does not change the fact that assets and responsibility have already shifted. By contrast, simulated orders, test-network assets, internal technical demonstrations and user interviews that do not collect client funds can be used to validate processes. The two should be designed separately; in particular, do not casually complete a real payment on behalf of a prospective client during the demonstration stage and then conclude that no business is being conducted because no fee was charged. Signing a confidentiality agreement, inviting only familiar enterprises, or having participants bear the risk themselves does not automatically change the nature of the activity; a testing contract cannot replace the licensing or registration basis required by law.
Whether to register first or operate first depends on the specific regime
Canada's FINTRAC expressly requires the relevant MSBs to register before commencing operations; this is not an arrangement under which a business reports retroactively once it reaches a certain scale. The form and timing of market access may differ in other markets, and the filing deadline in one jurisdiction cannot be used to explain the prior authorization requirement in another. Even where the registration procedure differs from licensing approval, anti-money laundering, record-keeping and other applicable obligations should not be treated as matters that may be deferred during a trial operation stage.
Formal sandboxes still have market-access boundaries
The UK FCA's regulatory sandbox guidance emphasizes that testing involving regulated activities still requires appropriate authorization or registration first, and may be subject to restrictions such as the number of clients, duration and scope of activities. The fact that a payment project is approved to test within a designated client scope does not mean the same product can be opened globally. Written approval or legally applicable arrangements should govern; verify who the approved entity is, which functions are being tested, and how the project will exit or transition to formal operations after testing ends.
Break the launch threshold into verifiable milestones
It is advisable to divide the launch plan into three stages: technical validation, partner integration testing and real business, with each stage clearly specifying what assets may be accessed and who bears the service obligations. Before real transactions, check the client agreement, qualification status, fund segregation, transaction monitoring and incident handling, rather than merely checking whether the interface is available. If unlicensed operations have already occurred, it is inadvisable to continue accumulating transaction volume while waiting for approval; historical records should be preserved, new risks should be limited, and options for cessation, client exit and subsequent filings should be assessed.
Recommended actions
- Determine whether the test environment involves client assets with real value, and close any unreviewed channels for real deposits.
- Retain the applicable market-access basis or sandbox approval documents, and verify the entity, duration, client and product restrictions.
- Add sign-off on qualifications, client protection and exception handling to the launch acceptance checklist; the technical lead alone should not be able to clear the launch.
Information note: This article provides general information only and does not replace legal advice based on specific facts.
References
- Register your MSB or FMSB — FINTRAC
- Regulatory Sandbox — FCA
