Virtual-asset services
Covers roles involving exchange, trading, custody, brokerage and other virtual-asset services.
Crypto payments are becoming core financial infrastructure for cross-border trade, internet businesses and digital-asset transactions. Long-term viability depends on a compliance architecture aligned with the business model, funds flow and target markets.
Mankun advises digital-asset platforms, crypto-payment providers, blockchain projects and financial institutions on cross-border structures, global licensing, regulatory engagement and risk controls.We start with the business and funds flow, then translate regulatory requirements into licensing, AML, legal documentation and day-to-day operating arrangements.
Most jurisdictions do not regulate “crypto payments” as a single activity. The applicable rules depend on the business role, funds flow, control of accounts and customer touchpoints, and may include virtual-asset, payment, e-money and anti-money-laundering regimes. A stablecoin-payment product commonly falls within several regulatory frameworks at once.
Covers roles involving exchange, trading, custody, brokerage and other virtual-asset services.
Covers collections, payouts, money transmission, merchant services, settlement and payment-account arrangements.
Covers e-money issuance, stored-value arrangements and related safeguarding requirements.
Covers customer due diligence, transaction monitoring, suspicious-activity response, the Travel Rule and sanctions screening.
From product design through ongoing operations, we provide connected legal support across compliance architecture, licensing, controls, documentation and disputes.
We assess applicable permissions, entity structures and ongoing compliance paths based on the client's role and target markets.
Federal registration commonly relevant to exchange, transmission and related financial services.
State money-transmitter licensing assessed against the states served, funds flow and business role.
Applies to certain virtual-asset exchange and crypto-payment services with continuing AML obligations.
May apply to virtual-asset trading, custody and related financial services, subject to activity classification.
The EU authorisation framework for crypto-asset service providers, classified by the services offered.
Relevant to e-money issuance and related cross-border payment arrangements.
Relevant to money transmission, payment accounts and cross-border payment services.
The Hong Kong licensing route for virtual-asset trading platforms, subject to current law and regulatory policy.
Relevant to money exchange and remittance services where a crypto-payment model includes fiat legs.
A combined assessment of major payment institution and digital payment token services.
Registration and continuing AML obligations for digital-currency exchange services.
Dubai's virtual-asset licensing system, assessed by activity class and operating zone.
Includes routes such as El Salvador DASP and BVI VASP, evaluated against the project's objectives.
We advise digital-asset platforms, crypto-payment providers, payment-technology businesses and related infrastructure projects.










Practical answers for institutions on market entry, licensing, business models, partnerships, customer funds and legal responsibility. 100 questions in total.
There is no single "crypto payment license" that is valid worldwide. The product should first be broken down into receiving tokens, custody, exchange, transfer and fiat settlement, and then assessed according to the actual place of business and the customer market. Both crypto asset service and payment qualifications may be required, and a licensed cooperation model may lawfully be adopted, but cooperation does not automatically exempt a party from its own market-access requirements.
When assessing licensing, the most useful material is not the "Web3 payment" label in a business plan, but the complete process of a single order: to whom the client gives instructions, whose wallet or account the assets first enter, who can sign or freeze, who quotes the price, and to whom the merchant ultimately has recourse for payment. Merely providing a billing page is not the same type of service as undertaking to convert stablecoins into US dollars and pay the merchant. Even if client assets remain for only a few minutes, they should be included in the business analysis. Client funds should also be marked separately from the company's own liquidity: for the same outbound transfer, using client balances to perform instructions and a company disposing of its own assets may require different analyses.
Taking the EU as an example, Article 59 of MiCA ties admission to crypto-asset services to specific operating entities and authorized services, rather than giving a company a pass of unlimited scope. The European Banking Authority's opinion on the interaction between MiCA and PSD2 also indicates that certain e-money token services may simultaneously involve payment regulation. Therefore, after obtaining crypto-asset service qualifications, it is still necessary to separately verify how fiat currency is collected and paid after conversion; the fiat-currency-side analysis cannot be skipped merely because the wallet does not display a fiat-currency balance.
Assume an overseas e-commerce merchant uses the same checkout page. In Solution A, the merchant contracts directly with an institution authorized to provide the relevant services; that institution collects the crypto assets, converts them and settles, and the software company only provides order integration. In Solution B, the software company quotes in its own name, collects the crypto assets and guarantees that the merchant receives a fixed amount in US dollars, and then engages an upstream party to perform. The two appear similar, but the service the client purchases and the entity bearing the risk differ; Solution B cannot be treated as pure technical services merely because the upstream party holds a license.
It is advisable to list the service entity, country, qualifications and contracts corresponding to each stage in a table, identify stages not yet covered, and then compare the costs of applying independently and cooperating. Mainland China cannot directly apply the above overseas models; Yinfa [2026] No. 42 imposes restrictions on domestic virtual-currency-related business and on overseas entities unlawfully providing services to domestic parties. The team's location, the clients' location and the source of funds should be reviewed together; an overseas company registration certificate cannot replace a market-access conclusion.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
It is not necessarily required to apply from scratch, but the scope of the license must be re-examined. A traditional payment qualification does not automatically cover stablecoin custody, exchange and transfer; some institutions may follow a statutory notification or license-variation path, while others require separate authorization. The key factors are the license category held by the existing entity, the proposed new functions, and the local legal classification of stablecoins.
"Payment company" is merely an industry label; the actual qualification may be money remittance, acquiring, e-money issuance or other services. The review should begin with the licensing decision, the attached conditions and the public register, and then compare each item against the new product. A distinction should also be drawn between using stablecoins to settle fiat currency on one's own account and directly providing customers with services to buy, hold and transfer coins: the obligations owed to customers differ between the two products, and the original market-access conclusion cannot simply be carried over merely because both are embedded in the existing payment page. At the same time, check whether the original license is subject to restrictions on business scale, customer type or geographic scope of service. Adding a stablecoin function may change the business and risks described in the original application even if the licensed entity remains unchanged.
Article 60 of MiCA establishes a route for certain financial institutions to provide some crypto-asset services. Among these, the notification arrangement for e-money institutions concerns the custody and transfer of e-money tokens they issue themselves; it does not permit them to operate all third-party stablecoins under their original license. Ordinary payment institutions also cannot assume that they fall within the institutions listed in that article merely because they belong to the financial sector. Whether the applicable route is notification, application for CASP authorization or expansion of an existing authorization should be matched item by item against the entity and the service.
An offshore company that already has a fiat-currency collection business plans to let customers deposit stablecoins into a platform balance and then pay suppliers. The new function does not merely add a payment option; it introduces asset custody, transfer authorization and on-chain exception handling. If a qualified third party instead contracts directly with customers and undertakes these services, the company's role may differ; however, the actual interactions and contracts should be examined, rather than merely adding the partner institution's name at the bottom of the page.
EU EMT services also involve an intersection between MiCA and PSD2, and the EBA continues to address the interface between authorizations in its 2026 opinion; earlier regulatory transition recommendations cannot be understood as a permanent exemption. In practice, the company should also re-obtain confirmation from banks and payment channels regarding the new business, and update customer terms, asset segregation, refunds, wallet permissions and incident response plans. Bank confirmation here is a check of cooperation feasibility and does not mean that a bank can approve a business that is otherwise not permitted by law.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Providing software alone does not necessarily require a financial license, but the fact that one does not touch money cannot by itself prove an exemption. It is necessary to examine whether the interface merely transmits information, or whether it accepts client transaction instructions, arranges conversions, controls transfers, or promises settlement. Different markets may also regulate transaction-arrangement services that do not hold assets, and the determination should be made in light of the product's permissions and the contract.
An API may merely display third-party quotes, or it may receive orders and then select counterparties on the customer's behalf, split orders and initiate transfers. It is necessary to clarify: does the customer establish a service relationship directly with a licensed institution? Who can modify the receiving address, cancel orders or release payments? Who bears responsibility for making up shortfalls if a transaction fails? These questions reveal more clearly than the statement that "the funds did not pass through the company's bank account" whether the company is actually selling software or providing financial services.
When Singapore's MAS expanded the scope of payment services regulation in 2024, it expressly included certain activities facilitating the transfer or exchange of funds or digital payment tokens without holding the funds or tokens. Therefore, the fact that the server merely transmits instructions and assets move directly from the customer's wallet to a third-party wallet is not a globally applicable licence-free structure. By contrast, the US FinCEN guidance on software development distinguishes between merely developing and selling software and using software to operate a money transmission business; that conclusion addresses only its specific regulatory scope and cannot substitute for the assessment of other states or countries.
Suppose a merchant originally placed orders independently on a third-party page, and the software only synchronised order status; later, to "optimise the experience", the team had customers uniformly accept terms on its own page, with the platform automatically selecting the quoting party and guaranteeing the exchange rate and arrival of funds. Even if the underlying payment address remains unchanged, the newly added customer commitments, order control and performance arrangements may also change the legal characterisation. The technical team's permission design, product copy and contracts must be reviewed together, rather than checking only the receiving account after development is complete.
If the intention is to operate on a purely technical model, the company should retain data-flow and instruction-flow descriptions, an interface permission list and division-of-labour contracts with service providers, and confirm that an applicable exclusion or exemption basis genuinely exists locally. Do not describe the real business as a different business in order to reduce regulatory costs; customers should know who provides the exchange, custody and payment services. New features added after launch should also undergo change review, especially features such as unified balances, automatic currency conversion and platform signing on behalf of customers. During review, do not look only at front-end flowcharts; have technical personnel demonstrate administrator permissions, key sharding, contract upgrades and manual release functions, to confirm that the division of labour on paper matches actual capabilities.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
In offshore markets that permit the relevant business, collecting stablecoins and then settling fiat currency to merchants may be carried out under the corresponding licenses and a lawful cooperation structure; it is not lawful merely because "the merchant is willing to accept it." The regulations currently in force in mainland China strictly restrict virtual currency-related business, and an offshore coin-collection and settlement model cannot be used directly as a regular payment solution for merchants in mainland China.
From the customer's payment to the merchant's receipt of US dollars, at a minimum the following questions must be answered: who receives the stablecoin, who holds the assets, who executes the exchange, and who pays the fiat currency. If the platform promises settlement at a fixed exchange rate, it should also specify the point in time at which the rate is locked and who bears the risk of network congestion or upstream refusal to pay. The crypto asset services listed in the EU's MiCA include exchange, custody and transfer on behalf of clients; the specific licence cannot be selected based merely on the word "collection", and the fiat payment stage should also be separately checked against payment regulation. It should also be confirmed whether the merchant statement shows the coins pending exchange, the fiat currency pending payment, or the amount already received, so as to avoid treating upstream operations that have not yet been completed as funds already at the merchant's disposal.
Yinfa [2026] No. 42 of 2026 continues to prohibit the conduct of fiat currency and virtual currency exchange and other related business within the territory, and restricts offshore entities and individuals from unlawfully providing related services to domestic entities. This notice has already replaced the 2021 notice. Therefore, packaging RMB or domestic trade receivables as offshore stablecoin payments, or arranging for an offshore company to sign the contract, does not by itself prove legality; the customer's actual business operations, the provision of services and the use of funds still need to be reviewed.
An offshore hotel that wishes to accept stablecoin payments from guests while receiving local fiat currency can compare two structures: a qualified institution contracting directly with the hotel and responsible for exchange and settlement, or the platform acting as the hotel's settlement obligor and then engaging upstream providers. The latter structure causes the platform to bear more performance risk and makes it more necessary to verify its own qualifications. Even if the former structure is adopted, it should still be confirmed that the currency, network, merchant industry and settlement destination are all within the scope acceptable to the cooperating institution.
The assessment of a solution should not merely demonstrate a successful payment. It is advisable to also design processes for underpayment, overpayment, wrong chain, sanctions screening hits, stablecoin freezing and consumer refunds. For example, whether a refund upon return of goods is made in the original coin quantity or the original fiat amount should be specified before the transaction; this is a matter of contract and risk allocation, not simply "reversing" the original on-chain transaction. Only when the entity, qualifications, transaction purpose and anomaly handling can all be closed off is it suitable to proceed to testing with real merchants.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Possibly, and the fact that "the coins are the company's own" is not a general exemption for operating an exchange business. A distinction should be drawn between the company handling its own investments and a business of continuously quoting prices to customers, executing transactions and delivering fiat currency or stablecoins. The latter may constitute a regulated exchange or money transfer service even if the company does not hold customer balances on their behalf and its profit derives solely from the bid-ask spread.
Who owns the assets before a transaction is a question of asset attribution; whether a company provides financial services to external customers is a question of regulatory characterization. Suppose a company purchases stablecoins in advance as inventory and delivers them after a customer places an order; the fact that it is "selling inventory" does not by itself exclude regulation. Conversely, an ordinary enterprise occasionally disposing of assets to pay its own expenses and a business continuously operating exchange as a customer-acquisition product must be analyzed separately and cannot be covered by the same conclusion. The fact that a company bears inventory price fluctuations does not automatically turn a transaction into an ordinary investment; the key remains whether this transactional capability is offered as a continuous service to customers. External quotation records and customer contracts can both help reconstruct the facts.
Article 3 of the EU's MiCA defines exchange services for buying and selling crypto assets with customers using own capital, which shows that proprietary inventory and operational exchange can coexist. The U.S. FinCEN also distinguishes individuals or enterprises acting as users for their own payments and investments from those conducting business as exchange operators; an interpretation limited to investing for one's own account cannot be expanded into a blanket exemption for providing over-the-counter exchange to customers. These are determinations under their respective regimes, not a globally uniform licensing rule.
Suppose a customer, after selling coins, asks for fiat currency to be paid to its own corporate account, versus asking for payment to multiple suppliers; these are two different delivery methods. The latter may no longer merely complete a bilateral sale but may also involve transferring value on the customer's behalf. Allowing customers to retain balances over the long term, withdraw in installments, or offset receipts and payments among different customers should also be analyzed separately; writing a contract as an asset sale cannot automatically eliminate actual custody and payment functions.
It is advisable to compile the frequency of quotations, external marketing methods, number of customers, sources of funds, and the sequence of execution and delivery, and to explain whether third-party payments and receipts are permitted. The assessment cannot rest solely on the amount being small or the absence of service fees. After completing the jurisdictional analysis, decide whether to merely manage the company's own assets or to establish access, customer due diligence, quotation and abnormal-transaction systems as an exchange business; operational exchange in mainland China must still be separately assessed under the current prohibitory provisions.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Licensing or registration requirements generally still need to be assessed. Corporate clients are not a general exemption: regulators first look at whether the platform operates exchange, custody, transfer or payment services. Some markets apply different rules to specific clients, and those rules must also meet the specific definitions; a registered company does not automatically become a professional investor, and is certainly not automatically exempt from anti-money laundering obligations.
Enterprises paying suppliers, merchants accepting customer payments, and groups managing funds all have different commercial purposes, but whether a platform handles assets on behalf of clients still requires an independent assessment. Taking the EU's MiCA as an example, the definition of client includes natural and legal persons receiving services, and does not protect only individual investors. Therefore, merely closing the registration channel for individual account opening cannot automatically remove from the regulatory scope business that originally constituted CASP services; the specific services and potentially applicable exemptions should still be examined.
Although small trading companies, investment funds and licensed financial institutions are all legal persons, their experience, purposes and applicable rules may differ. If reliance on professional clients, qualified investors or other specific category arrangements is intended, the definitions and corresponding rules of the target jurisdiction must be verified as to exactly what they reduce or exempt. Certain arrangements only change disclosure, marketing or investor protection requirements and do not automatically eliminate business licensing. A sales team cannot complete the legal classification merely by having clients tick "corporate account".
Where a platform receives corporate funds, converts currencies and then delivers them to an overseas supplier, it may still be conducting money or virtual asset transfers. A genuine procurement contract helps explain the purpose of the transaction but cannot replace business qualifications. Conversely, if the platform only provides invoice matching and payment approval software, and the enterprise directly instructs a qualified institution to execute, the role may differ. The two models should be distinguished by actual instructions, asset control and contractual obligations, rather than conflated on the ground that all clients are engaged in trade.
The MAS DPT anti-money laundering notice in Singapore requires identification of clients and beneficial owners and ongoing monitoring of relevant risks. For corporate payments, it is advisable to further verify whether the actual chain of control, authorized payers, business scale and payees match. For batch payments in particular, the link from the corporate client to each ultimate payee must be retained; checking only the first-tier company is insufficient. Focusing on a small number of industries helps deepen the inquiry, but does not mean that all clients holding a business licence may be onboarded. Corporate clients may also change controllers, add operating regions or suddenly change transaction scale, and passing initial onboarding does not mean no further review is needed later. It is advisable to pre-set business changes that trigger re-review.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
The assessment must follow the payment chain rather than looking for a single "cross-border payment license." Collecting funds on behalf of an enterprise, exchanging currencies, transferring tokens and paying fiat currency to suppliers may each involve different market-access requirements; an enterprise paying on its own behalf also differs from a platform paying on behalf of clients. A genuine trade contract can establish the purpose, but it cannot substitute for the service provider's qualifications, and scenarios involving domestic enterprises require a separate review of mainland rules.
When preparing a proposal, the enterprise should specify from which country and which account it pays what assets, and in which country the supplier ultimately receives what assets. An enterprise paying US dollars while the supplier receives stablecoins, versus an enterprise paying stablecoins while the supplier receives local fiat currency, creates different requirements for exchange and payment channels. It should also be stated whether the platform advances funds first, whether it pools funds from multiple enterprises, and who bears the ultimate obligation to ensure receipt; these are not purely technical details, but the basis for determining the content of the service and the allocation of risk. The customer contract should also state whether the supplier's receipt of the specified currency has already discharged the enterprise's payment obligation for the goods. The platform's completion of the technical transfer and the buyer's and seller's confirmation that the debt has been performed should not be conflated in product presentations.
In FinCEN's interpretation, using virtual currency to pay for one's own goods or services differs from operating a business of accepting and transferring value on behalf of others. Assume the enterprise independently controls its wallet and signs payments to the supplier, with the platform only managing invoices; in another model, the platform receives the enterprise's funds, decides on its own to exchange currencies and transfer funds, and delivers a "paid" result to the enterprise. The latter model cannot be regarded as the enterprise's own use merely on the ground of trade payment, and the upstream execution of transactions does not automatically eliminate the platform's liability.
FINTRAC's business guidance in Canada includes virtual currency exchange and transfer within the relevant MSB activities, reflecting that currency transfer itself may also trigger regulation. An actual cross-border product should also be examined end by end: whether the payer side covers the service, whether the receiving side permits the supplier to receive currency, and whether the ultimate fiat currency account accepts that source. The above Canadian definitions cannot be directly applied to all countries, but they are sufficient to show that "using only stablecoins for transit and not touching local currency" is not a universal exemption.
Where Mainland Chinese enterprises, domestic receipts and payments, or services provided to the domestic market are involved, a separate assessment should be made under the 2026 notice and relevant foreign exchange and other rules, and a genuine contract must not be treated as a green channel for stablecoin settlement. For permitted overseas business, it is advisable to agree in advance on confirmation of the receiving address, erroneous payments, exchange rate differences and the handling of supplier refusal, and to retain the linkage among contracts, invoices, customer instructions and final receipt evidence, so as to avoid having only an on-chain hash while being unable to explain the purpose of payment.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
It is not enough to look only at the place of incorporation, nor should "overseas clients" be treated as a single unregulated category. It is necessary to examine simultaneously the place of incorporation and actual management, the places where personnel and service activities are located, and the client markets actively targeted. Some markets regulate local outbound business even without local clients; other markets regulate the provision of services from abroad to local clients.
A company incorporated in jurisdiction A, operated by a team in jurisdiction B, and serving customers in jurisdiction C may need to analyze all three places at the same time. A certificate of incorporation reflects the legal entity, but it cannot fully answer who is taking orders, managing wallets, and making risk decisions. It is advisable to determine the actual place of performance by function, including contracting, marketing, customer onboarding review, transaction execution, asset control, and complaint handling; the mere fact that servers are located abroad does not establish that core operations are also abroad. The existence of cloud services, outsourced customer support, and remote employees should likewise not be mechanically equated with a local licensing obligation, but these facts should be included in the factual inventory so that local rules can determine whether the connection is sufficient, rather than being disregarded at the outset.
In 2025, the Monetary Authority of Singapore (MAS) clarified that a DTSP that falls within the relevant regime and provides digital token services only to customers outside Singapore also requires the corresponding licence, and stated that it would generally not grant such licences. This example shows that “not serving customers in the place of incorporation” does not necessarily reduce the difficulty of market entry and may even make a particular establishment structure unsuitable for the actual business. However, this should be assessed by reference to the specific entity, tokens, and scope of services, and that position should not be extended to all Singapore technology companies.
The FMSB conditions listed by FINTRAC in Canada include having no place of business in Canada but directing and actually providing relevant services to individuals or entities in Canada; both the manner of marketing and customer contact are relevant. Therefore, a website statement that services are provided “only overseas” and the use of a foreign company to sign contracts do not mean that the customer market can be ignored. Active promotion, local agents, and service support for a particular market should be examined together with the actual location of customers; the assessment cannot be completed solely on the basis that a customer provides an overseas address.
Assume that the team originally served only one assessed market, but later had sales personnel continuously solicit customers in another country and had local employees approve large payments. The articles of association have not changed, but new customer and operational connections have been added. It is advisable to establish country admission approval: first confirm the licensing or cross-border service basis, and then open registration, marketing, and transactions, rather than conducting business first and supplementing the research afterward. Where a mainland team is involved, its actual functions and mainland restrictions should also be separately reviewed; an overseas licence cannot replace this step.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Where a business is required by law to obtain prior permission or registration, it may not commence operations merely because it is small in scale, free of charge, or labeled a "closed beta." Technical validation that does not involve regulated activities with real customers may be conducted first; testing with real transactions requires confirmation of authorization, an exemption, or a formal pilot arrangement. A regulatory sandbox is likewise not a license-free zone that a team can declare effective on its own.
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.
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.
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.
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.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
The transition is not merely adding a new currency interface; it requires reworking the alignment of business scope, asset control, risk, and partner channels. Existing customer, order, and reconciliation capabilities can be reused, but stablecoin custody, on-chain transfers, and conversions cannot automatically continue to rely on traditional payment licenses and processes. It is advisable to first select a clearly defined offshore payment corridor and validate the entire chain before expanding.
The team should first answer what commitment it intends to offer to whom: give merchants an additional payment collection method, make payments on behalf of enterprises, or let users hold and transfer out stablecoin balances? For the same payment company to offer these three types of products, the required licenses, wallet permissions and customer terms may differ. The specific financial institution pathway under Article 60 of the EU's MiCA also has service limitations; one cannot presume that all new functions merely require notification simply because traditional payment qualifications are already held.
The original "order success" may have relied mainly on payment channel receipts; after adding on-chain transfers, it is also necessary to define when a transaction is considered finally completed, and how to handle wrong chains, insufficient receipt and incomplete exchanges. It is recommended to distinguish order amount, token holdings, exchange price and final settlement amount, so that customer receivables, platform inventory and on-chain addresses can be reconciled. Do not treat all stablecoins as equivalent US dollar deposits, and do not directly equate on-chain success with receipt into the merchant's bank account. The existing finance and customer service teams also need to understand these statuses in sync, to avoid manual oral explanations of delays after the system marks "completed." A single order can first be used to run through finance, technology and customer service for full-process acceptance testing.
EU MiCA governance requirements include appropriate personnel, continuous operations and secure information technology arrangements; Singapore's 2024 related measures also strengthened DPT customer asset protection. At the product level, the team should clarify private key and signing permissions, wallet backups, on-chain transaction review, and handling when upstream services are suspended. Using third-party custody or on-chain analytics tools can provide capabilities, but the company still needs to know who judges alerts, who can stop payments and who explains to customers.
For example, first provide one stablecoin, one network and one fiat settlement method to specific overseas merchants in markets that permit receiving coins, rather than supporting global wallets and multi-currency balances on day one. When assessing, simultaneously calculate exchange spreads, on-chain fees, exception handling, banking channels and personnel costs, and first obtain confirmation from partners on the nature of the business. If the original customers are mainly located in mainland China, the current restrictions should be assessed first, rather than directly migrating domestic merchant resources under an overseas entity's name.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
There is no single best place of incorporation divorced from the business context. The first batch of customers and the product should be determined first, and only then should the scope of market access, substantive management requirements, banking channels and ongoing operating costs be compared. An inexpensive offshore company does not equal an inexpensive payment business; and the fact that a company can be incorporated in a given place of incorporation does not mean that the company can operate in the markets where its customers are located.
The first table for site selection should be a customer map, not a ranking of tax rates. Identify the countries where the first batch of customers are located, the payment and receipt currencies, the account or wallet functions required, and whether the company will directly hold customer assets. If the main customers are concentrated in the EU, the EU's market access and cross-border service mechanisms should be studied; if the business relates to only one country, there is also no need to first build a complex group structure for a "global footprint." Company registration, financial licensing and market customer acquisition should be verified separately and cannot substitute for one another.
Article 59 of the EU's MiCA sets out clear requirements for the registered office, actual place of management and director residency arrangements of an authorized CASP; Singapore also has a strict licensing position for certain DTSPs that serve only overseas customers. Such conditions directly affect whether an option can be implemented and should not be ranked after registration fees. If the team is unwilling to relocate management functions or bear local personnel costs, the gaps should be identified before applying, rather than registering a shell company first and then looking for a nominee responsible person.
Jurisdiction A is cheap to establish, but cannot support the first batch of customers' market, and the intended bank does not accept the business; Jurisdiction B is more expensive to establish, but has an access pathway that matches the product. What should really be compared at this point is the overall cost of lawfully completing a single transaction, not the price of the company certificate. Whether a bank account can be opened is not determined solely by the place of registration; it is advisable to verify the actual transaction process and customer types with shortlisted banks, exchange and settlement institutions, and avoid treating a service provider's oral assurances as resources already in place.
For each retained candidate jurisdiction, record separately the permitted services, customer coverage, management personnel, application materials, capital or safeguards, tax and exit costs. Tax burden, capital contributions and domestic team arrangements should be analyzed separately in detail; it is not appropriate to draw a total-cost conclusion from any single nominal tax rate. The final choice should be able to answer: which lawful businesses will generate revenue in the first year, which prerequisite failing would make the option unfeasible, and whether future new markets will require a second entity or another type of qualification. For each candidate jurisdiction, an "exit condition" can be listed: for example, key positions cannot be filled, core customers cannot be served, or a bank expressly refuses the corresponding process. Once triggered, the location should be reconsidered rather than continuing to invest sunk costs.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
It is not necessarily required to apply separately in every country, but there should be a clear basis for market access in each market intended to be served. This may be a local licence, a qualifying regional cross-border mechanism, or a lawful cooperation arrangement; a single offshore registration certificate cannot be relied upon to operate globally. The fact that customers can access the website and that partner banks can remit funds does not mean that the company is permitted locally to provide that service.
The EU MiCA regime establishes a cross-member-state service mechanism for CASPs authorized to provide the relevant services and requires the corresponding notifications under Article 65. Its value lies in reducing duplicative authorization within the EU, but it does not mean automatic coverage outside the EU, nor does it expand crypto service permissions into all fiat payment or credit permissions. When planning, the list of countries and the scope of services should be set out together, to avoid promoting "one set of regional rules" as "one global license."
The EU has a narrow arrangement for services requested by clients on their own exclusive initiative, and the ESMA guidance on reverse solicitation emphasizes looking at the facts; contrary marketing conduct cannot be covered by a contractual checkbox. Assuming a company advertises to the EU and then has clients declare that "I found the platform on my own initiative," this cannot establish a compliance basis. Similar rules cannot be directly extended to other countries; absent verification, "clients voluntarily visiting" should not be used as a default reason for opening all markets.
Serving an enterprise in an approved market and paying its suppliers in other countries is a different scenario from directly providing wallets, exchange and account services to those suppliers. The former requires verification of the payment corridor and local delivery conditions; the latter additionally involves new client-market access. Canada's FMSB rules also indicate that an overseas entity targeting and providing services to Canadian clients may trigger local registration requirements; the analysis cannot end merely because formalities have been completed in the place of incorporation.
It is advisable to first open markets for which a clear conclusion has been reached and where the cooperation channels have also confirmed support; for markets requiring new licenses or presenting prohibition risks, retain restrictions and set review conditions. Restrictions should be implemented in marketing, account opening and registration, payment routes and cooperation contracts, not merely as a one-line country list in the terms. Client relocation, agency client acquisition and newly added balance functions may all change the original assessment, so the country list should be maintained together with product versions. Geographic controls should also not rely solely on IP addresses. An enterprise's registered address, actual operations and client relationships may differ; it is advisable to verify by combining account-opening materials with transaction purposes, and to set up manual review for situations suspected of circumventing restrictions.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
MSB, VASP and CASP are not the same global license. MSB is generally a money services business category in specific countries; VASP is a virtual asset service provider concept with differing regimes across jurisdictions; and CASP has a clear authorization framework under the EU's MiCA. One should compare the regulator, services, geographic scope and ongoing obligations, rather than looking only at the abbreviations.
MSB registration with the U.S. FinCEN primarily falls within the federal anti-money laundering framework. FinCEN expressly states that registration is not an operating license, nor is it an endorsement of a business's legality; state-level and other requirements must still be verified. Canada's FINTRAC likewise has an MSB and foreign MSB registration regime, and states that provincial or territorial qualifications cannot substitute for federal registration. The names in the two countries are similar, but the definitions of services, applicable nexus and obligations are not entirely the same. One cannot assume that purchasing an "MSB certificate" means one can serve all of North America.
The FATF uses the concept of VASP to describe entities that, on a commercial basis, provide services to others such as virtual asset exchange, transfer and custody. The FATF sets international anti-money laundering standards, but it does not issue companies a VASP license that permits global operation. Individual countries bring the relevant business within registration, licensing or other regulatory approaches, and local law should be consulted. Promotional materials that state only "holds a VASP" without stating the country, the regulator and the scope provide far from sufficient information.
Under MiCA, a CASP may engage in different services such as custody, exchange and transfer on behalf of clients; the authorization should specify the concrete scope, and qualifying existing financial institutions have a specific pathway as well. Accordingly, obtaining an exchange qualification should not be directly interpreted as also permitting the operation of all wallet or trading platform functions. A CASP is also not equivalent to a stablecoin issuance qualification, and it does not automatically cover fiat payment business; "crypto-asset service provider" and "issuer" are roles that must be kept separate.
Suppose two service providers quote MSB registration and CASP authorization respectively; one cannot compare only the fees and estimated completion dates. Each should be required to explain, using the same product flow: which entity provides which services, which customers it may serve, whether local management personnel are required, and which business is still undertaken by third parties. Then verify the results against the official registers to confirm that what is displayed is a valid status rather than an application receipt, an expired registration or the qualification of another company within the group. It should also be confirmed which legal entity holds the qualification; certificates, training attestations or association memberships produced by agents should not be treated as an operating license granted by a regulator merely because they look similar.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
When the budget is limited, the first step should be to choose the market-entry pathway that can support the first real product and customer market, rather than the cheapest or most easily demonstrated qualification. The scope of functions and countries may be narrowed, or lawful licensed cooperation models may be explored, but registration in an unrelated market must not be used as a substitute for the core operating license. The budget must also cover operations after the qualification is obtained.
First determine what fees the company will charge customers and which regulated functions it must perform itself. Assume the first batch of customers is in a certain European market and the business needs to custody and transfer stablecoins; purchasing an offshore registration unrelated to market access in that market does not solve the core problem. What should really be compared is the complete plan for carrying out this business: the required authorizations, entities and personnel, and qualified alternative partners, rather than the market prices of certificates in various jurisdictions.
Official FinCEN and FINTRAC materials state that the relevant registration procedures do not charge a registration fee, but this does not mean there are no company, personnel, compliance or other licensing costs. FinCEN in the United States also makes clear that MSB registration is not an operating license. Therefore, a low quote should be further broken down: does the fee cover only filing the form, or does it also include business characterization, implementation of policies and procedures, and follow-up support? Are bank account opening, local licensing and customer protection requirements excluded from the scope of delivery? These questions are more worth asking first than "how long until the number is issued."
If custody or exchange capabilities are not to be built in-house in the first phase, consideration can be given to having qualified institutions directly undertake the relevant services. However, it is necessary to verify whether one's own actual functions also trigger regulation; one cannot retain own-brand collection of payments, unified pricing and settlement guarantees while describing oneself as a technology provider. The EU MiCA outsourcing rules also emphasize that a licensed entity cannot transfer responsibility away along with the outsourcing; control over the partner and the ability to exit should be included in the plan, rather than merely comparing interface fees.
It is advisable to first select one customer group, one payment corridor and a limited set of currencies, and then calculate the fixed costs that must still be paid if the expected transaction volume is not reached. Assume the self-licensed plan is more expensive in the first year but has a lower unit transaction cost, while the cooperation plan requires less initial investment but has minimum commitments and exit restrictions; the comparison should be made on conservative business volume, not merely on ideal growth. When funds are insufficient to maintain the necessary team and customer protection, narrowing the business scope is more prudent than obtaining a license first and then looking for operating budget. For capabilities temporarily outsourced, it should also be clarified whether customer and transaction records can be exported if the provider is switched in the future, whose consent is required and how balances are to be migrated. Low upfront costs accompanied by dependencies that are difficult to exit should also be included in the comparison.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
There is no uniform timeline applicable to all crypto payment projects. A distinction should be drawn between document preparation, regulatory processing after a complete application is submitted, and bank and product launch following approval. FINTRAC in Canada currently states that most complete applications are processed within three months after all materials are received, and complex applications may take longer; this is not an overall delivery commitment calculated from the first consultation.
"Three months for the application" and "eight months for the project" may use entirely different starting points. The overall project usually also includes the business plan, entity and equity arrangements, background materials, personnel and policy preparation, and responses to regulatory requests for additional information. Even after a license or registration is obtained, banking and upstream access may not yet be completed. When comparing service proposals, you should require the other party to specify who is responsible for each stage and what the conditions for commencement are, rather than merely providing a fastest-case date.
FINTRAC's registration page states that most complete applications are processed within three months after receipt of a complete application package, and that complex applications may take longer; incomplete materials may be closed and require resubmission. Therefore, this figure cannot be directly applied to a project that has not yet determined its shareholders or prepared its background documents, nor is it a guarantee of approval. It describes the processing of complete applications and does not establish that pre-registration communications, preparation of materials, and subsequent commercial access can all be completed within the same period. Applicants should also keep records of the time when they receive confirmation of completeness or a notice of additional information, so as to avoid mistaking the date on which the pre-registration form was first sent for the date on which review of a complete application began.
For example, the CASP process published by the Austrian FMA distinguishes between the completeness check of an application, supplementary materials, and the substantive assessment once the application is complete, and states that certain supplementary submissions can pause the review clock. It follows that a statutory or published processing period does not mean that approval will be granted on a countdown basis after a service contract is signed. Assume two teams with products of similar complexity: one already has usable policies and management personnel, while the other is still changing its business model. Even if they face the same regulator, their overall preparation paths may differ significantly.
It is advisable to set separate milestones for complete materials, formal submission, confirmation of completeness, regulatory decision, banking readiness, and launch acceptance. For steps that cannot yet be determined, identify dependencies and buffers rather than fabricating industry averages. In particular, do not tie customers' formal deposit of funds, fixed launch publicity, or irrevocable procurement of channels to the most optimistic schedule; where commercial commitments are required, the regulatory and counterparty prerequisites should be clearly stated to avoid timing deviations turning into performance disputes.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Government fees, professional service fees, capital or safeguard requirements, and ongoing operating costs should be calculated separately; they cannot be summarized by a single "total license acquisition price." Different businesses and jurisdictions vary greatly. The relevant MSB registrations in the United States and Canada are themselves free, which does not mean that operating is free; and the prudential safeguard threshold for EU CASPs is certainly not an application fee paid to consultants.
Company formation, translation, legal and application service fees generally constitute project expenditure; salaries, audits, systems and channels constitute ongoing costs; regulatory capital or safeguards are a separate category of requirement. The three should be presented separately, and available operating cash must not be treated simply as the same budget as regulatory requirements, still less may client funds be counted as start-up capital freely usable by the company. Quotations should also state whether taxes and fees, supplementary submissions, business changes and post-failure service arrangements are included. For tools and channels charged by transaction volume, budgets may be presented for low business volume, expected business volume and stress scenarios; a one-off promotional price should not be treated directly as a fixed maintenance cost for future years.
Both FinCEN and FINTRAC have official materials stating that the relevant MSB registration carries no registration fee. This conclusion does not cover fees charged by other competent authorities, nor does it exempt the personnel, policies and systems investment required for operations. Suppose a consultant quotes a very low price but is only responsible for filling in forms; the team must still establish client review, transaction monitoring and record-keeping capabilities itself. Therefore, the price of "completing the filing" should be separated from the budget for "being ready for ongoing operations," to avoid discovering only after obtaining the number that there are no compliance execution resources.
Article 67 of MiCA requires CASPs to maintain prudential safeguards, in principle the higher of the minimum amount applicable by class of service and one quarter of the previous year's fixed expenses; where the business has operated for less than one year, the corresponding forecast is used. The fixed tiers listed in the AMF's official explanation are EUR 50,000, EUR 125,000 and EUR 150,000. Depending on the legal conditions, the safeguards may take the form of own funds, insurance or a comparable guarantee; the three tiers must not all be understood as cash deposits, nor should only the lowest tier be selected while ignoring the actual class of business.
Assume a project falls within the EUR 125,000 tier and its annual fixed expenses calculated under the applicable rules are EUR 800,000; one quarter, i.e. EUR 200,000, is higher than the fixed tier. This merely demonstrates the comparison logic; how actual expense items are included, whether the safeguard form may be used, and how the calculation is made where other licences are also held all require specific verification. The budget should separately reserve the funds required by banks' or channels' commercial conditions and an operating buffer; it must not be assumed that once the minimum safeguard is met, other expenditures will resolve themselves.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Whether approval will be granted cannot be determined on the basis of Chinese nationality alone. A distinction should be drawn between shareholder identity, place of residence, actual control, source of funds and business arrangements, and the specific requirements of the target regime should be verified. The fact that an overseas regulator permits a certain shareholding structure does not mean that the domestic capital contribution and business arrangements are also lawful; borrowing another person's identity or concealing the controller will usually increase, rather than resolve, review risk.
A founder with Chinese nationality may reside outside China for a long period, or may actually manage the business in mainland China; a foreign-national shareholder may also be controlled by a domestic entity. Regulatory applications must disclose the true structure, and a passport cannot substitute for an analysis of actual control. In making the assessment, one should separately list who contributes capital, who enjoys the economic benefits, who holds appointment and veto rights, and who is responsible for operations, and then examine the different conditions that the target market imposes on shareholders, directors and management personnel. Do not mistake director residency requirements for shareholder nationality requirements.
Article 68 of MiCA sets out requirements concerning the reputation, knowledge, experience and time commitment of management, as well as the reputation of qualifying shareholders; these are not a rule that "Chinese shareholders are of course prohibited from applying." It cannot, however, be relied on to promise that all applications with a Chinese background will be approved; sanctions, funds, complex shareholding structures and other applicable reviews must also be examined. Canada's FINTRAC registration materials also require disclosure of the control structure and the submission of background documents for specified persons, which shows that substantive transparency matters more than a superficial packaging of identity.
In addition to prohibiting the relevant domestic business, the 2026 mainland notice imposes restrictions on domestic entities and the overseas entities they control issuing virtual currency overseas without consent, and also sets out provisions on the overseas issuance of RMB-pegged stablecoins. Particular attention should be paid to the fact that issuing virtual currency and providing payment or exchange services to clients are not the same activity, and the provisions must not be expanded or narrowed at will. Projects involving mainland capital contributions, control and teams should be reviewed separately according to their actual business; it should not be assumed that obtaining an overseas licence will resolve mainland issues as well.
If the nominal shareholder is replaced by an overseas friend, but the founder still contributes capital and controls the company, the true control relationship does not thereby disappear. Such an arrangement may also cause the application, bank materials and internal agreements to contradict one another. A more prudent approach is to prepare in advance a complete equity chart, the formation of funds and the capital contribution chain, past regulatory or criminal matters, and the division of management responsibilities; where conditions present obstacles, the actual operating structure should be adjusted in accordance with law, rather than circumventing review through inaccurate application materials. Inconsistencies in the spelling of names, historical addresses and dates of equity changes across different documents should also be explained consistently. Differences that can be explained by original documents should be clarified proactively; true facts should not be altered for the sake of superficial consistency.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Many formal licences require genuine management and operational capacity; renting an address alone is not enough. However, offices, resident personnel and positions that may be outsourced should be assessed on a jurisdiction-specific and licence-specific basis. Lighter registration procedures do not support the inference that banks will accept shell arrangements. Resources required for local governance, compliance and technical controls should be included in the long-term budget, rather than calculating only the cost of a registered address.
A registered address resolves legal nexus and service-of-process issues, whereas actual operations must explain who makes decisions, who understands customer risk, and who can respond swiftly when problems arise. Even if some work can be performed remotely, it is still necessary to verify whether the relevant roles can discharge their duties outside the jurisdiction. Application materials should not contain only a lease contract and an organizational chart; they should also be able to explain how day-to-day approvals, reporting, risk escalation and record access actually operate; otherwise the address itself cannot demonstrate sufficient operational capacity.
Article 59 of MiCA sets out the EU registration, actual management and director residency requirements for authorised CASPs. ESMA's supervisory briefing on CASP authorisation further focuses on local personnel, substantive decision-making authority and the actual performance of duties by management. Accordingly, "at least one director meets the residency condition" does not mean that all other functions may remain outside the jurisdiction, nor does it mean that every company must replicate the same headcount. The specific staffing arrangements must still be determined in light of business scale, key functions and the requirements of the competent authority.
The company engages local personnel to serve as responsible persons, but all customer approvals, transaction suspensions and risk budgets are decided by an overseas headquarters, and the local personnel cannot access system records. Such an arrangement falls short of "local management" in substance. Conversely, a group may provide shared technical or administrative support, but the licensed entity should retain the corresponding professional capabilities, oversight and decision-making resources. The EU MiCA outsourcing rules make clear that outsourcing cannot transfer away the licensed entity's responsibilities to customers and regulators.
It is advisable first to list functions such as business management, compliance, risk, finance, asset control and technical security, then verify which must be performed locally, which may be part-time or outsourced, and what qualifications and backup staffing are required. Do not promise "only one employee is needed" or "no office is required" before verification. The team should also check whether actual office, employment, tax and data access arrangements are consistent; reducing resource requirements through a smaller business scope is more sustainable than maintaining a team on paper. For cross-time-zone teams, it should also be tested whether the local responsible person can promptly access records, approve emergency actions and communicate with regulators when an upstream service outage occurs; key authority must not rest solely with overseas personnel who cannot be reached.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
An acquisition does not mean buying a license that can be used immediately. You should compare the target entity's actual scope of services, the change-of-control procedures, historical risks, and whether its banking channels can continue, rather than comparing only the purchase price and application timeline. Applying on your own is generally more conducive to building around your product, but it likewise requires investment in personnel, systems, and capital.
Financial qualifications generally attach to a specific entity and scope of services. An equity acquisition gives the buyer control of the company, but it does not automatically expand the license, nor should the company's qualifications be treated as an asset that can be independently transferred to another entity. Suppose the target company is licensed only for exchange services, and the buyer plans to launch a customer balance wallet and transfer services on behalf of clients; the new functions would still need to be verified. Registrations or qualifications under legacy regimes that the target previously held should also be checked for their current status, rather than relying solely on historical certificates.
Taking EU CASPs as an example, Article 83 of MiCA establishes notification and regulatory assessment procedures for transactions intended to acquire qualifying holdings or reach the corresponding control thresholds. Transaction documents may set conditions in advance, but signing an agreement should not be equated with being able to immediately complete a change of control or replace management. Which approvals or notifications apply and whether closing can occur first should be confirmed on a jurisdiction-specific basis; in addition, change-of-control clauses in bank, payment channel and material contracts should be reviewed.
It is advisable to review regulatory correspondence, outstanding remediation, consistency between customer assets and ledgers, handling of historical suspicious transactions and complaints, tax matters and material contracts. Wallet control must also be verifiable; obtaining a screenshot of assets is not sufficient. It should also be checked whether the original team and outsourced institutions are willing to continue performing their duties and which key systems cannot be transferred; if the so-called mature company in fact has only certificates and no operational capability, the buyer will still bear most of the cost of rebuilding. If the actual transaction is a purchase of customers, technology and brand rather than equity in the company, customer migration and service continuity must be analyzed separately; an asset transaction does not automatically carry over the original entity's financial qualifications.
The comparison endpoint should be "the ability to continue lawful operations as planned on a sustained basis," not "signing" or "submitting an application." The acquisition option should account for due diligence, approvals, remediation, integration and potential historical liabilities; the new application option should account for preparation, hiring and regulatory engagement. Acquisition documents may set conditions such as the qualifications remaining valid, completion of regulatory procedures, confirmation of key channels and asset handover, as well as liability arrangements for historical issues, but contractual indemnities cannot replace regulatory compliance, nor can they ensure that the seller will have the ability to pay in the future.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
The same licensed entity may operate multiple products within the permitted scope, but different subsidiaries cannot share a qualification merely by virtue of their group relationship. It depends on who contracts with customers, controls assets and bears service obligations. Services purely within the group may fall within a specific scope exclusion, which is distinct from each subsidiary operating for external customers; a unified brand also cannot erase the boundaries of legal entities.
Even if a checkout counter, a corporate payment back office and a mobile wallet have different names, where they are all operated by the same entity, it is still necessary to verify item by item whether their functions fall within the authorised services. Conversely, adding balance custody, currency exchange or credit functions to the same App may already go beyond the original scope. Article 59 of the EU's MiCA requires that authorisation list the services, and newly added crypto services require an application to extend it; therefore, "the same product" and "the same regulated activity" are not the same thing.
Assume Company A holds the relevant authorisation, while Company B independently contracts with customers, quotes prices and collects customer assets, and the terms merely state that "the group holds a licence". Company B's actual role should be re-analysed, and it cannot be deemed authorised merely on the basis of brand affiliation. If Company A is in fact the entity genuinely providing the regulated services, customers should be able to identify Company A's identity, the scope of its services and the party against whom they have recourse; Company B's customer-acquisition or technical role must also comply with the applicable rules, and it is not enough simply to change the contract name to Company A.
Article 2 of MiCA excludes from scope entities that provide crypto-asset services solely to their parent undertaking, their own subsidiaries or other subsidiaries of the same parent undertaking. It addresses a specific purely intra-group relationship; it does not permit any company in a group to conduct business externally without authorisation. A group treasury centre that manages only internal assets and a structure that receives external merchant funds through a subsidiary and then processes them centrally should be assessed separately; nor may this be used to bypass payment, anti-money-laundering or other potentially applicable regimes.
A group may explore shared technology, customer service or risk management, but it should clearly determine how data, assets, permissions and fees are attributed. Article 73 of MiCA indicates that outsourcing cannot transfer the licensed entity's own responsibilities, and intra-group outsourcing cannot cause it to lose its supervisory capability. In practice, it is advisable to set out clearly, for each product, the contracting entity, the customer funds account, wallet control and complaint handling, and to check whether the App, statements, emails and marketing pages are consistent; services provided across countries also require separate review of customer market access. Unified login and group-shared databases should also be able to distinguish each entity's customers, balances and authorisations, so as to avoid customers not knowing that the service provider has changed when switching products, or funds attribution being commingled in internal ledgers.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
US MSB registration is primarily used to fulfill FinCEN anti-money laundering regulatory requirements; it is not a nationwide business license. Stablecoin exchange, payment collection and disbursement on behalf of clients, or transfers may fall within the scope of registration, but whether a business can launch still requires separate examination of each state's market-entry requirements, the specific types of tokens, and other financial regulatory requirements.
Under FinCEN's virtual currency guidance, accepting and transmitting convertible virtual currency as a business, or providing related exchange services, may constitute money transmission. Receiving stablecoins and then converting them to US dollars for payment to merchants cannot be split into two technical steps for which no one is responsible merely because the receipt of coins and the payment of US dollars occur in different systems. Conversely, a business using virtual currency to purchase goods for itself is different from operating an exchange or payment business for third parties. The assessment must list the payee, the quoting party, the wallet controller and the final delivery obligation together.
FinCEN expressly cautions that registration does not mean the government endorses the legality of the business, still less that it reviews or endorses the company's compliance level. Once within the scope of MSB regulation, a business must still establish anti-money laundering systems suited to its business and perform applicable recordkeeping, reporting and other obligations. Purchasing an anti-money laundering template and finding a registration number does not mean these obligations have been fulfilled. Registration also cannot directly resolve bank account opening, customer fund protection or business qualifications in other countries.
Assume a platform collects stablecoins for a New York merchant and then pays US dollars to the merchant. Even if it has registered with FinCEN, the public FAQ of the New York State Department of Financial Services still requires a separate assessment of the BitLicense route or the approved bank or trust company route; if it also operates fiat money transmission, the New York money transmission license may also be involved. This example cannot be used to infer that all states adopt New York's rules, but it is sufficient to show that the state of incorporation and the federal registration location do not mean that all states where customers are located have granted permission.
Using third-party stablecoins for settlement is not the same market-access question as issuing and redeeming one's own stablecoins. As of October 29, 2026, the OCC has issued final rules implementing the GENIUS Act, and the official announcement lists the effective date of the rules and the Act as January 18, 2027; this cannot be written in advance as already fully applicable. Projects preparing to issue coins should separately list the transition work for issuer market access and the reserve and redemption regime; projects that only provide payments should also track changes in the issuance and sale rules of the supported currencies and cannot substitute MSB registration for this.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Whether an MTL is required generally depends on whether a state characterizes your actual receipt and payment activities as money transmission, not on whether the company is registered in that state. The legal characterization of stablecoins, control of funds, and the location of clients may all affect the outcome; state-level virtual asset licensing must also be reviewed separately, and an MTL check alone is not sufficient.
A common risk point is where a platform receives customer funds or assets with monetary value and then undertakes to transfer them to other persons, other accounts or other locations. The analysis must not focus solely on whether a transfer has occurred once on-chain; it must also examine whether the platform accepts payment instructions, bears delivery obligations and holds balances pending settlement. FinCEN's federal money transmission test and state law are not the same checklist, and completing federal registration does not by itself lead to the conclusion that no state-level license is required.
Take the Texas Department of Banking's 2025 revised Supervisory Memorandum 1037 as an example: it distinguishes general non-stablecoin virtual currency from stablecoins that meet the local statutory definition; the latter involves anchoring to a sovereign currency, reserve backing and redemption rights. The Department expressly states that for a transaction involving fiat currency or such stablecoins, whether it constitutes money transmission must be determined by reference to how the asset is handled. Accordingly, the proposition that "a Bitcoin business does not require an MTL in a given state" cannot be directly applied to the same company's U.S. dollar stablecoin payment product.
The New York State Department of Financial Services brings activities such as holding virtual currency on behalf of customers, buying and selling, exchanging and transferring virtual currency within the BitLicense regime, and makes clear that out-of-state companies conducting such business with New York residents may also be subject to regulation. Fiat money transmission may in addition require a separate license. Assume a platform provides only stablecoin custody and transfer to New York enterprises and does not provide U.S. dollar remittance services; even if the MTL analysis reaches a particular conclusion, the platform still cannot skip the assessment of the BitLicense route or the approved bank or trust route.
It is advisable first to select a few states where there is genuine demand, set out the states where customers are located, the business steps, the assets used and the basis, and then decide whether to apply independently or adopt a cooperative arrangement permitted by local law. A licensed partner's ability to complete end-point payments does not necessarily cover the platform's front-end collection of funds or balance management. In states where licensing has not yet been completed, restrictions should be implemented in sales, customer onboarding and transaction review; it is not enough to state in a website footer that "services are not provided to that state" while continuing to accept customers from that state.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Canadian MSB registration may apply to businesses such as commercial virtual currency exchange, transfer and money transmission, but it is only part of anti-money laundering market entry. A distinction must be drawn between Canadian MSBs and foreign MSBs; if a product also performs fiat currency payment functions, the requirements for payment service provider registration with the Bank of Canada and other requirements should be checked separately.
The virtual currency business activities listed by FINTRAC include fiat-to-virtual-currency exchange, virtual-currency-to-virtual-currency exchange, transferring virtual currency at a client's request, and receiving virtual currency for onward transmission to a beneficiary. Where an institution collects virtual currency on behalf of merchants or pays bills for enterprises, the mere fact that the activity is a commercial payment rather than an investment transaction does not exclude its application. The assessment also requires satisfaction of the relevant business and geographic conditions; not every company that holds stablecoins must register. A company paying its own procurement invoices should be analyzed separately from continuous payment on behalf of others.
FINTRAC's interpretation of "having a place of business in Canada" looks beyond physical premises and also includes circumstances such as Canadian registration, local employees, agents or branches. An entity that has no place of business in Canada but targets Canadian clients with the listed services and actually carries them out may qualify as a foreign MSB. Where an offshore platform does not establish an office in Canada but advertises to the Canadian market and accepts local clients for exchange, it is inappropriate to deny a registration obligation solely on the ground that "both the servers and the company are located offshore."
The Bank of Canada examines payment functions, retail payment activities, geographic connections and exclusions under the Retail Payment Activities Act. "Retail" does not mean that only natural-person clients are considered; enterprise payment products must likewise be tested. Where, for example, a platform maintains fiat receipt and payment accounts for clients and initiates or executes electronic funds transfers, it cannot be assumed that no further review is required merely because FINTRAC registration has been completed. Conversely, merely providing virtual currency functions does not mean that fiat payment service requirements can be applied wholesale without analysis.
FINTRAC expressly states that registration does not constitute recognition or licensing of a business, nor does it issue any so-called "certificate of registration" to businesses. For purchasers, it is more useful to verify the entity, status and actual contracting party in the official directory than to rely on certificate images produced by the service provider. For applicants, compliance programs, client identity verification, and recordkeeping and reporting capabilities must still be continuously implemented; bank access and licensing in clients' jurisdictions must be resolved independently.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
A Hong Kong MSO licence cannot serve as a general authorisation for stablecoin exchange or crypto payments. It primarily addresses money-changing and remittance business; where specified stablecoins are offered to customers, the restrictions on "offers" under the Stablecoins Ordinance must also be assessed, and MSO status itself does not constitute the statutory qualification of an approved provider.
The Hong Kong Customs and Excise Department's 2026 MSO licensing guidelines set out access requirements, business information and continuing obligations in relation to money changing and remittance. Accordingly, the fact that a company holds an MSO licence proves only its eligibility under that regime; it does not by extension prove that wallet custody, stablecoin sales or virtual asset platform business are all permitted. Nor is the specific combination a mechanical stacking of licences: the incidental money services of certain regulated institutions benefit from statutory exemptions, and this must be confirmed on the basis of the entity and the actual business.
According to the Hong Kong Monetary Authority's guidance on stablecoin licensing, the permitted providers of specified stablecoins include licensed stablecoin issuers, authorized institutions, licensed SVF licensees, SFC-licensed virtual asset trading platforms and corporations licensed for Type 1 regulated activity. Holding an MSO licence alone does not place a company on this list. The Hong Kong Government's reply to the Legislative Council also makes clear that ordinary over-the-counter virtual asset trading institutions cannot offer specified stablecoins to retail or professional investors merely by virtue of their operating status.
Assume a customer delivers Hong Kong dollars, the platform quotes and undertakes to deliver a certain US dollar stablecoin to the customer's wallet, and the customer then pays a supplier. Here there is not only a remittance narrative; there may also be an arrangement under which the platform sells stablecoins to the customer. The offer analysis under the Stablecoins Ordinance focuses on whether, in the course of business, information on the currency, terms and channel sufficient for the other party to decide to purchase is conveyed; it cannot be assumed that a quote in a private chat, or the customer making the first inquiry, is necessarily unrestricted.
Another assumption is that the customer directly enters into a stablecoin transaction with an institution that meets the requirements, and the MSO undertakes only fiat currency remittance within its lawful scope. The contracts, quotations, asset control and refund liability under the two arrangements should genuinely differ; it is not enough merely to change the name in the agreement. Hong Kong's new regimes for virtual asset trading, custody and the like remain subject to the final legislation and commencement documents; published consultation conclusions cannot be treated as ready-made licences, nor as a reason to disregard the existing stablecoin restrictions. In practice, changes of counterparty, the addition of supported currencies and adjustments to refund paths should also be set as triggers for review, so that an initial review does not permanently cover subsequent products.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Whether an SVF licence is required turns primarily on whether a storable value is created and whether the issuer undertakes to allow customers to pay third parties using that value. Displaying a balance does not necessarily constitute an SVF, but a wallet that accepts top-ups and maintains a consumable or transferable balance should complete an independent analysis of the Hong Kong SVF regime and related business lines before launch.
The HKMA's explanation of SVFs focuses on stored value and payment uses: the customer pays funds first, the instrument stores the corresponding value, and then, in accordance with the issuer's arrangements, pays for goods or services or transfers funds to other persons. Merely displaying an external bank account balance differs from the platform itself accepting top-ups and undertaking commitments in respect of the use of the balance. Even if the funds are actually held at a partner bank, it is still necessary to ascertain who the instrument issuer is, to whom the customer asserts the balance, and who is responsible for refunds; it is not enough to look only at whether the money has entered an account in the platform's name.
The HKMA has made clear that multi-purpose stored-value instruments fall within its licensing regime; single-purpose instruments that can only be used to purchase the issuer's own goods or services, and payment methods without a stored-value function, are treated differently. Suppose a software vendor collects prepayments that can only be used to purchase its own subscription services; this is a different structure from a wallet balance that can be used to pay multiple independent merchants. Calling multiple merchants "ecosystem partners" does not automatically turn a multi-purpose instrument into a single-purpose instrument; where an exemption applies, the statutory conditions must still be checked item by item.
Once stablecoin top-ups, conversions and on-chain withdrawals are supported, the product may raise issues of offers of specified stablecoins, virtual asset trading or custody. Although SVF licensees are included in the category of permitted providers under the Stablecoins Ordinance, this does not mean that their existing product approvals and licensing conditions automatically cover the newly added services, nor does it mean that they may offer any overseas stablecoin to retail customers. Conversely, a stablecoin issuance qualification cannot replace the assessment of the wallet's stored-value structure.
The HKMA's SVF licensing guidance focuses not only on application materials but also on ongoing compliance with licensing conditions and the management of stored-value funds. Teams are advised to set out, at the product design stage, the complete path for top-ups, payments, refunds, incomplete transactions and account termination, and in particular to clarify whether the balance is a fiat currency claim, a token held in custody, or an external asset displayed for information only. If customers believe they can withdraw Hong Kong dollars at any time, while the platform can in fact only return stablecoins whose price or redemption arrangements differ, this is not merely a naming issue; it also affects the contractual and funding arrangements.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Hong Kong permits the design of compliant stablecoin collection and payment services, but a clear distinction must be drawn between issuance, offering to clients, custody and transfer, and fiat currency settlement. Restrictions apply to the eligibility of providers of specified stablecoins and to the types of stablecoins that retail clients may purchase; corporate clients are not automatically equivalent to professional investors, and the B2B label cannot be used to circumvent these requirements.
Stablecoin payment does not mean that every participant is issuing or selling stablecoins. A merchant accepting payment for its own goods, a platform quoting a price to customers for the sale of stablecoins, and a platform controlling a wallet and transferring funds on a customer's behalf are activities that should be analyzed separately. The Hong Kong Monetary Authority's stablecoin licensing guidance states that an offer to provide depends on whether the business communications contain sufficient information about the coin type, terms and channels for the other party to decide to purchase. Payment buttons, quotations and automatic conversion functions should all be included in the review; it is not sufficient to review only the company's business scope.
The Stablecoins Ordinance took effect on 1 August 2025. A 2025 Legislative Council reply by the Hong Kong Government states that permitted providers may provide regulated stablecoins issued under a Hong Kong licence to retail and professional investors; the provision of stablecoins other than such regulated stablecoins is limited to professional investors. "Professional investor" is defined under securities law and does not mean, in ordinary language, a "person who understands coins" or a "corporate client". Accordingly, corporate payment products should verify client eligibility and must not treat a corporate client's ticking a box on the registration page as sufficient.
The Hong Kong Monetary Authority's current register of issuers already lists licensed institutions, so the earlier 2025 statement that "there are not yet any licensed issuers" can no longer be relied on. However, inclusion in the issuer list does not mean that all of an issuer's products, or coins of the same name sold by other institutions, are subject to the same regulation. It is advisable to verify the specific issuing entity, the coin type and the service arrangements, and at the same time to check the seller's own qualifications, business conditions and client onboarding, so as to avoid treating an issuer's licence as a qualification that a platform may borrow.
Assume that a platform receives stablecoins from customers on behalf of a Hong Kong merchant and then undertakes that the merchant will receive Hong Kong dollars. The team must explain item by item: whether the payer first buys coins from the platform; who controls the receiving wallet; who completes the conversion; who remits the Hong Kong dollars; and whether refunds are made in Hong Kong dollars or in the original coin. If the arrangement is changed so that the merchant contracts directly with a permitted institution and the platform only displays orders, the responsibilities and onboarding requirements may differ, but they must be consistent with actual operations. The official consultation conclusions on the new transaction and custody regimes should also be tracked separately and must not be treated in advance as licences already in effect or as existing exemptions.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
When entering the EU now to provide custody, exchange, transfer on behalf of clients, or other services within the scope of MiCA, the relevant CASP authorisation should generally be obtained; certain already-regulated financial institutions may follow a specific procedure under Article 60. The maximum transitional period for legacy national registrations has ended and can no longer serve as an alternative route for launching new business.
MiCA is not a single "European crypto licence" that applies regardless of business line. Article 59 requires the authorisation to specify the crypto-asset services that have been approved; if services are added later, an application to extend the authorisation must be made to the original competent authority. For payment projects, at least the roles of custody on behalf of clients, exchange of funds with clients using own funds, execution or transmission of orders, and transfer on behalf of clients should be verified separately. The classification and issuance eligibility of stablecoins under MiCA must also be checked separately; CASP authorisation does not mean that any token issued by the platform is already compliant.
On 8 October 2026, ESMA published a supervisory opinion requiring competent authorities to supervise CASPs to cease providing services involving stablecoins that do not meet MiCA requirements to EU clients, including transfer and custody, and not only trading. Existing assets may only be subject to necessary, time-limited exit arrangements under supervision, and new business may not be conducted on that basis. This is a supervisory expectation addressed to competent authorities, not a redefinition of every service as a public offering; new projects should treat token compliance review and platform licensing as parallel matters.
The maximum CASP transitional period under Article 143(3) of MiCA ended on 1 July 2026; before that, different Member States could adopt shorter periods. As of October 2026, new entrants cannot rely on the historical transitional treatment of legacy virtual asset registration. Assume an intermediary sells a company that holds a legacy registration, but the company has not completed MiCA authorisation; the buyer cannot directly resume token receipt and settlement business on that basis. Acquisition due diligence should examine the current authorisation, the specific services and the attached conditions, and not only the past registration date.
Under Article 59, an entity applying for CASP authorisation must generally have a registered office in the Member State in which it carries out at least part of its services, have an actual place of management in the EU, and have at least one director resident in the EU. What the regulation requires is a supervisable operating structure, not the purchase of a mailing address. It is advisable, when choosing a location, to determine at the same time who is responsible for client assets, risk-management decisions and outsourcing management; where all core functions are undertaken by an overseas team, the plan should be explained in advance to the competent authority of the intended applicant country, rather than supplementing the structure after obtaining the licence.
Article 65 of MiCA establishes a cross-border notification mechanism, requiring submission of information such as the Member States in which services are to be provided, the services, the start date and other non-MiCA activities. It can reduce the burden of applying repeatedly in each country for the same CASP authorisation, but it should not be promoted as unconditional clearance of the entire product in all countries. If merchant settlement also involves euro accounts or e-money token payments, the payment regime should be checked separately; client contracts, complaints and locally applicable rules should also be included in the launch plan.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Possibly yes. A MiCA authorisation does not automatically cover fiat-currency payments, e-money issuance, or all payment activities carried out using e-money tokens (EMTs). It is necessary to distinguish between "issuing a token", "operating an exchange" and "making payments on behalf of clients", and then to determine whether to obtain payment/e-money authorisation oneself or to have a qualified partner undertake the activity.
CASP authorisation covers the listed crypto-asset services; functions such as fiat-currency accounts, money remittance and acquiring should still be checked against the payments rules. EMTs have an additional specific feature: Article 48 of MiCA treats EMTs as electronic money, and in principle their issuers must hold credit-institution or electronic-money-institution status and complete the white paper procedure, subject to any statutory exceptions. Therefore, a platform that only handles third-party EMT payments and a company preparing to issue its own EMT cannot resolve the matter with the same licence checklist.
The EBA opinion on the interaction between MiCA and PSD2 requires particular attention to EMT transfers on behalf of clients and to custodial wallets that allow clients to receive and make EMT payments to and from third parties. The latter may constitute a payment account. Suppose an enterprise exchanges euros for EMTs on a platform and immediately withdraws them to its own wallet; this is not entirely the same service as the platform maintaining an EMT balance for the enterprise over the long term and paying suppliers on instructions. Each case should be assessed segment by segment: the payment character should not be denied merely because the interface is called “exchange”, nor should all crypto-to-crypto transactions be described across the board as payment services.
The transition period set by the EBA's initial opinion ended on 2 March 2026. The follow-up opinion of 12 February 2026 sets out conditional supervisory treatment arrangements for some CASPs that have applied but not yet obtained payment authorisation, and requires those that do not meet the conditions to cease the relevant EMT payment services. These are supervisory opinions addressed to competent authorities, not an indefinite extension that an enterprise may declare applicable on its own. When planning new products as of October 2026, an enterprise should obtain the applicable qualifications or implement a lawful licensed cooperation arrangement, and cannot rely solely on old news from 2025 as the basis for conducting business.
Article 70(4) of MiCA allows a CASP to provide the relevant payment services itself or through a third party, but the actual provider must hold the qualifications required by PSD2 and must explain to clients the nature of the service and the identity of the provider. If a payment institution directly undertakes EMT payments and the CASP handles exchange within the lawful scope, the parties should clarify with whom the client contracts, who accepts payment instructions, who controls the assets, and who handles unauthorised transactions and refunds. Where a platform connects a licensed service provider in the back end but still promises clients that it itself provides all payment services, the access separation may not have been completed. Budgeting should also include additional client protection, authentication and operational controls, rather than merely comparing the cost of applying for one more licence.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
A non-EU company cannot actively operate in the EU crypto payment market solely on the basis of an offshore licence. The MiCA exception for transactions where the client is the sole initiator is narrow in scope and cannot be created by a mere declaration; where there is a plan to continuously promote and serve EU customers, an EU-authorised entity or a clearly lawful licensed cooperation structure should generally be planned.
MiCA's EU cross-border notification facilitation is built on entities that meet its access requirements; a US MSB or offshore VASP registration cannot be converted into equivalent rights. For the general CASP application route, Article 59 requires, among other conditions, an EU registered office and effective management. Non-EU teams may assess establishing a local operating entity or allocating functions with an authorized institution, but an EU shell alone cannot take orders while all regulated services continue to be directly promised and delivered by an unauthorized overseas company.
The core of MiCA Article 61 is that the client requests the service entirely on its own initiative. Where the company, its affiliates, or persons acting on its behalf have previously promoted to EU clients, contractual terms cannot be used to recast that relationship as client-initiated. ESMA guidance interprets solicitation broadly and in a technology-neutral manner; advertising, emails, social platforms, referral activities, and sponsorships may all be relevant. The fact that a website can be accessed from the EU does not mean every access necessarily constitutes a violation, but the absence of an EU flag on the website does not by itself establish that no solicitation exists.
Suppose a platform buys advertising targeting French companies and pays local promotion partners commission based on successful account openings, and the client ultimately clicks to register on its own and checks "I am contacting you on my own initiative." Such a declaration will not eliminate prior solicitation. Conversely, where a client genuinely approaches the platform on its own initiative without solicitation and requests specific services, the platform still needs to record the client's source, the communication process, and the scope of services. Article 61 does not permit the company to continue actively marketing new types of crypto assets or services on that basis; the exception is not an unlimited sales license for that client.
It is advisable to treat the EU market as a separate product region: who signs clients, which services are authorized, which promotions may be conducted, and where client assets are handled must all be determined before launch. When cooperating with an EU CASP, verify whether its licensed activities cover the actual delivery, rather than assuming that all of the platform's actions are covered once the client is introduced to a licensed party. If not entering the EU for the time being, sales policies, geographic restrictions, and client onboarding should be kept consistent, and arrangements should address clients relocating or changing their business location.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
In Singapore, one should first identify digital payment token services and other payment functions under the Payment Services Act, and then determine the required payment institution licence and permitted business activities. Exchange, transfer, custody and certain arrangements that do not directly handle assets may all be regulated; where services are provided only to overseas customers, the DTSP regime must also be examined separately.
The expanded scope rules published by the Monetary Authority of Singapore (MAS) in 2024 have brought activities such as digital payment token (DPT) custody, facilitating the transfer of tokens, and facilitating exchanges without holding funds or tokens within the regulatory perimeter. Therefore, describing oneself as a "technology platform" or "non-custodial" is not a conclusion. Teams should explain who organizes transactions, accepts instructions, arranges counterparties, and who can alter the path of asset transfers; whether technical services have entered regulated activities depends on actual functions.
Standard Payment Institutions (SPIs) and Major Payment Institutions (MPIs) are licence classes, whereas DPT services and the like are business items. Obtaining a licence in a given class does not mean that functions such as fiat remittance, merchant acquisition, and account issuance are all automatically permitted. The scope of application should be determined according to the applicable thresholds, conditions, and the combination of services intended to be carried on. In 2024, MAS also expanded the scope of cross-border transfer services; certain cross-border arrangements in which funds do not flow through Singapore may still be regulated, and the fund path cannot be treated as the sole criterion for determining geographic scope.
Assume that the platform first collects stablecoins on behalf of the merchant and then remits fiat currency to the merchant's overseas account. The first segment requires an assessment of DPT transfer, exchange, or custody, while the second segment requires a separate review of payment services such as cross-border transfers. If the second segment is completed by a licensed partner, it must still be clear to whom the customer gives instructions, who bears the commitment that funds will be credited, and who handles refunds when they occur. Only where the contract, system permissions, and fund arrangements are consistent with the division of responsibilities can the admissibility of the platform's remaining activities be assessed; pasting a partner's licence on one's own website cannot be regarded as completing licensing.
MAS's licensing page requires verification of matters such as local entity and office arrangements, directors and officers, and compliance and technology risk capabilities. For start-ups, more useful preparation is to enable specific personnel to explain the product and the customer asset flow, rather than to accumulate policy documents. It is advisable to first determine the launch customer regions, core currencies, and minimum service scope, and then allocate customer verification, asset safekeeping, system anomalies, and complaint responsibilities to positions; when adding new services, re-examine the licence scope to avoid developing beyond the perimeter after obtaining a licence.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Possibly yes, and "incorporated in Singapore, serving only overseas clients" is not a light-touch regulatory shortcut. From 30 June 2025, businesses falling within the scope of the overseas digital token service provider (DTSP) regime must hold a licence, and MAS has stated that licences will generally not be granted; institutions already lawfully operating under other regimes cannot, however, be uniformly regarded as having to exit overseas markets.
Section 137 of the Financial Services and Markets Act distinguishes between entities: where a Singapore legal person carries on a business of providing digital token services to places outside Singapore, a licence is not automatically excluded merely because the business is in fact operated elsewhere; for individuals or partnerships, the question is whether the business is carried on from a place of business in Singapore. The exceptions under that section and the application of other financial laws must also be examined. Accordingly, the assessment is not merely whether there are Singapore clients; the place of incorporation, the place of business and the services provided should all be included in the legal analysis.
In its official clarification of June 2025, MAS stated that DTSPs serving only overseas clients and involving DPTs or capital markets product tokens face higher money-laundering risks and supervisory difficulties, that the licensing threshold is high, and that licences will generally not be granted. The relevant regime took effect on 30 June 2025; affected businesses that have not obtained a licence must cease operations, and there is no general grace period that would allow new entrants to wait indefinitely. A business plan should not first assume that a licence can be obtained and then relocate clients and teams to Singapore.
MAS also made clear that licensed service providers serving Singapore clients and already regulated under the Payment Services Act, the Securities and Futures Act or the Financial Advisers Act may also serve overseas clients, and their existing business capabilities do not uniformly disappear because of this regime. However, whether this pathway applies depends on the actual business, the licensed activities and the conditions, and a conclusion cannot be manufactured by arranging a nominal local client. Other tokens with only utility or governance uses should also not all be treated as DTSP tokens without classification.
Assume a Singapore company directly contracts with overseas merchants, quotes prices and collects service fees, while an overseas team operates the wallets. It cannot conclude that Section 137 does not apply merely because "neither the personnel nor the wallets are in Singapore". If the Singapore company genuinely only performs group holding or internal support functions while client services are undertaken by other entities, the assessment should be redone based on the actual functions; at the same time, the overseas operating entities and access to target markets must also be examined. Changing the contracting party while retaining all actual control is not reliable compliance restructuring.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Australia should be assessed at three levels: AUSTRAC VASP or remittance registration, AFSL requirements under existing financial product rules, and the new digital asset platform regime that has been enacted but is not yet in force. The 2026 anti-money laundering reforms have already been implemented, and legacy DCE registration or a single "VASP licence" cannot substitute for a complete business assessment.
The virtual asset services currently specified by AUSTRAC include fiat-to-coin exchange, coin-to-coin exchange, arranging related exchanges, custody, and accepting instructions to transfer on behalf of clients. Whether a service is regulated also depends on the specific service definition and the territorial nexus; an ordinary enterprise merely holding its own coins does not automatically become a VASP on that basis. If a product also remits fiat currency on behalf of clients, the remittance service registration must be checked separately, and it cannot be assumed that on-chain settlement covers the fiat collection and payment leg.
Entities previously registered as DCEs automatically convert to VASPs from 31 March 2026 and do not need to re-register for the name change, but they must still update their information and implement the new obligations. The obligations for some new categories of services are deferred to 1 July, and the application window for eligible applicants closes on 29 July; the official rules state that specified persons who apply on time and have not yet received an approval or refusal decision may continue the relevant business. By October, new entrants cannot use this historical window to "operate first and apply later," nor can it be concluded in the reverse that all historical pending applicants are already in breach. The transitional periods for other obligations must be checked separately.
ASIC's INFO 225 guidance requires determining, on the basis of rights and functions, whether digital assets and related facilities constitute financial products, and non-cash payment facilities are one such category. If a platform allows clients to maintain stablecoin balances and continuously make payments to merchants, it cannot claim that the entire wallet has financial product licensing merely on the strength of AUSTRAC registration. Even if some functions do not involve the platform directly holding assets, it should still be checked whether the specific facilities and services trigger an AFSL, authorised representative status or an applicable exemption, rather than ending the analysis with a "non-custodial" label.
The Corporations Amendment (Digital Assets Framework) Act 2026 received Royal Assent on 8 April 2026, and the Act provides that the entire amending Act commences on 8 April 2027. As of this verification, ASIC has consulted on the implementing rules. Accordingly, this is neither merely a policy proposal that has not yet been passed, nor does it mean that all new platform obligations are in force in October 2026. When designing custody, trading and client asset arrangements now, provision should be made for adjustment to the new digital asset platform and tokenised custody platform regimes, while complying with the rules applicable today.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Joining a Swiss self-regulatory organisation (SRO) recognised by FINMA can be a route to meeting anti-money-laundering requirements for certain crypto exchange, transfer or payment models, but it is not a comprehensive financial operating licence. Whether client funds constitute public deposits, whether assets can be independently returned, and whether other regulated services are provided may all change the qualifications required.
An SRO is a self-regulatory organization recognized by the Swiss Financial Market Supervisory Authority (FINMA) and supervises its members' performance of anti-money-laundering obligations in accordance with the law. FINMA's guidance on fintech lists virtual currency exchange, payment and certain wallet activities as businesses requiring review of anti-money-laundering requirements. Therefore, SRO membership is not devoid of regulatory significance, but it also must not be promoted as FINMA having approved all of the company's products, confirmed the safety of client assets, or guaranteed the company's solvency.
The key to entering the scope of other licenses is not merely whether the wallet is called custody, but what assets the client hands over to whom, how the assets are kept, whether the company may use them, and whether the client obtains a right to return of the original assets or a claim for repayment against the company. FINMA explains that public deposits, custody of certain crypto assets and securities-related business may involve banking, FinTech or other licenses. Recording client funds on the company's internal ledger while holding only an SRO certificate cannot replace this classification.
Assume Model A completes the exchange immediately after confirming the transaction and delivers the agreed assets directly to the client; Model B instead lets the client retain a long-term balance withdrawable at any time, with the company centrally controlling the assets. Both may require anti-money-laundering arrangements, but the fact that Model A's SRO route is viable does not mean Model B requires no other license. If the balance is further invested, lent out or promised a return, the nature changes again. FINMA's existing FinTech license page expressly states that the relevant assets it is permitted to accept may not be invested and bear no interest, showing that a "FinTech license" itself is not an unlimited right to conduct deposit-taking business.
FINMA notes that client assets at FinTech institutions do not automatically enjoy bank deposit protection and requires that clients be informed of the relevant arrangements. SRO membership certainly cannot be used to make an equivalent promise. When choosing a structure, it is advisable to design at the same time the ownership of assets, account or wallet segregation, reconciliation, return and wind-down processes, and to keep them consistent with client contracts. For projects with unclear boundaries, the complete model may be explained to FINMA before applying; when serving overseas clients, the destination rules must also be independently verified, as Swiss status itself does not replace the counterparty's market access requirements.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Usually yes. Registering a BVI or Cayman Islands company merely establishes a legal person; it does not mean the company is authorized to provide virtual asset services. The two jurisdictions each have VASP registration or licensing requirements, and the treatment of custody and trading platforms differs; the fact that all clients are located overseas is not sufficient to establish that local regulation does not apply.
The British Virgin Islands Financial Services Commission (FSC) VASP application guidance requires operators providing virtual asset services in or from within the BVI to apply for registration. Custody and virtual asset exchanges must also satisfy the corresponding additional requirements. Accordingly, the statement that an "offshore company has no local clients" cannot substitute for a business analysis. It should be explained which legal entity contracts, who holds the assets, from where business decisions are made, and who controls the wallets and trading systems, rather than merely asking whether a registered agent can incorporate a company.
The Cayman Islands Monetary Authority (CIMA) states that, with effect from 1 April 2025, virtual asset custody and trading platforms are subject to a licensing regime; other regulated virtual asset services generally follow the registration route, and arrangements lawfully granted an exemption are treated separately. Where a company simultaneously engages in activities requiring registration and activities requiring a licence, the overall route should be determined in accordance with CIMA rules, and "registered VASP" must not be understood to mean that any custody or trading business may be carried on. When purchasing a shelf company, particular attention should be paid to the actual approvals, not merely the licence name used by the seller.
CIMA established a 90-day licence application window for institutions that were already registered and operating custody or trading platforms at the relevant time, and permits institutions that meet the arrangements to continue the relevant business during the licence review. Accordingly, the original draft's statement that "business cannot be carried on on the basis of ordinary registration alone" has cautionary value for new entrants, but it cannot be relied on to conclude that all legacy institutions awaiting approval have no authority to operate. Due diligence should obtain the original registration, the application filed on time and the records of subsequent decisions, and then confirm their current status; newly established projects cannot borrow the transitional experience of others.
A structure in which the group establishes a holding company in the BVI and a licensed subsidiary in another location directly serves clients is different from one in which the BVI company itself contracts and quotes, controls receipt of funds and assumes redemption commitments to clients. Outsourcing custody does not automatically turn the latter into a pure holding company. Even where the local VASP route has been implemented, the target client market, fiat payment and banking access must still be verified separately. When selecting a location, operations, regulation and responsibility for client assets should be placed on the same structure chart, so as to avoid creating an entity that cannot open an account or explain its responsibilities merely for ease of incorporation.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
The actual jurisdiction, assets and services should first be determined before choosing a regulatory pathway. Dubai's VARA does not cover the DIFC, while the ADGM is regulated by the FSRA; stablecoin payments also require attention to the Central Bank of the UAE's payment token rules. A virtual asset transfer licence does not mean that all merchants may accept any stablecoin.
VARA's virtual asset regulatory scope covers mainland Dubai and the relevant free zones, but does not include the Dubai International Financial Centre (DIFC). The Abu Dhabi Global Market (ADGM) is a financial free zone that applies its own financial services regime, and "a company incorporated in Abu Dhabi" cannot automatically be equated with being licensed by ADGM. Accordingly, the specific jurisdiction in which the office, contracting and service provision take place should first be clarified, and the competent authority then identified; the fact that a registered agent can incorporate a company does not mean that the financial regulator has already consented to the conduct of business.
VARA has dedicated rules for the virtual asset transfer and settlement business; other activities such as exchange and custody should be verified separately for authorisation, and all functions cannot be inferred from a single activity. The ADGM requires operation under an FSRA financial services permission and its specific conditions. Its amendments relating to fiat-referenced tokens (FRTs) took effect on 1 January 2026 and cover accepted tokens, regulated activities and client token arrangements. The fact that a certain coin is popular in the market does not mean it already meets the asset admission requirements of the jurisdiction to which the platform belongs.
The Central Bank of the UAE's Payment Token Services Regulation distinguishes issuance, exchange, custody and transfer, and imposes limits on merchants' acceptance of virtual asset payments. Within the scope of application of Article 2 of that Regulation, payment for general goods or services cannot freely accept foreign-currency stablecoins; the payment use of approved foreign-currency payment tokens is mainly limited to the purchase of virtual assets or their derivatives, while dirham payment tokens are handled separately under licensed issuance requirements. That article expressly excludes the financial free zones and cannot be mechanically applied within the ADGM or DIFC, but the provision of services from within a zone to clients outside it requires re-examination.
Assume that Option A serves catering merchants in mainland Dubai, and Option B provides services relating to approved tokens to institutions in the ADGM. The same qualifications and token lists cannot be applied to both merely because both use US dollar stablecoins. For A, it should first be confirmed whether merchant payments are permitted and what central bank and local admissions are required; for B, the FSRA approved activities, tokens and client conditions should be verified. Only then should the team, banking, asset custody and costs be compared; that is an executable choice of location. A licence in any one place should not be promoted as covering the whole of the UAE or the entire Middle East.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Stablecoin exchange, collection followed by foreign-exchange conversion, and similar businesses cannot be treated as ordinary payment services that may be operated simply by registering a company in mainland China. Current regulation prohibits the relevant virtual currency financial businesses and restricts financial institutions from providing supporting services; an offshore license, a technical services contract, or a genuine trade background does not automatically remove these restrictions.
A merchant receiving stablecoins, a platform converting them into RMB, and fiat currency being paid to suppliers may look like a single product, but in practice it may simultaneously involve virtual currency exchange, fund transfers and cross-border foreign exchange. To determine whether such a business may be operated in mainland China, it is not enough to look at whether the product name contains “payment”; instead, it is necessary to confirm item by item whose assets the platform receives, who makes the conversion decision, and who ultimately bears the payment obligation. Merely labeling the revenue as a technical service fee does not change the services actually provided.
Notice Yinfa [2026] No. 42, issued by the People's Bank of China and seven other departments, has replaced the relevant 2021 notice. The new rules continue to prohibit, within mainland China, businesses such as the exchange of fiat currency for virtual currency, and prohibit financial institutions, including non-bank payment institutions, from providing services such as account opening, fund transfers and clearing and settlement for virtual-currency-related business. Stablecoins such as Tether do not acquire legal-tender status merely because their prices are relatively stable. Therefore, this is not a problem that can be solved by “obtaining an ordinary payment license to complete the formalities.”
Assume that an offshore company receives stablecoins from mainland merchants and then arranges for a mainland account to pay RMB to the merchants. Even if the contract chooses foreign law, it is still necessary to examine whether it is illegally providing services to mainland entities. By contrast, arrangements that genuinely take place in offshore markets where the relevant business is permitted and that serve offshore customers require a separate assessment of local market access and China-related factors, and cannot be inferred from this question to be lawful as a matter of course. In particular, where an offshore company controlled by a mainland entity issues virtual currency, the restrictions in the 2026 notice must also be checked separately.
In practice, one should first draw a relationship map of customers, contracting entities, wallets, bank accounts and ultimate payees, and mark out mainland residents, mainland merchants, mainland marketing and fund operations item by item. Where a business is confirmed to be prohibited, it should be excluded from the scope of mainland products, rather than seeking collection accounts, offshore shell companies or a change of contract name. For functions that genuinely constitute ordinary software services, it should also be checked whether they in fact undertake transaction pricing, instruction execution or assistance to illegal business, and it must not be presumed that a “technology company” is naturally exempt.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
An offshore licence alone is not sufficient to provide stablecoin exchange, trading or other services to clients in mainland China. Yinfa [2026] No. 42 expressly prohibits offshore entities and individuals from providing virtual currency-related services to domestic entities in any form. Offshore contracting, servers or payment collection accounts are not sufficient conditions for excluding mainland regulation.
An offshore licence first establishes that a given entity is permitted to carry on specific business in the licensing jurisdiction; it does not equate to global client access. The restrictions in mainland China and whether an entity is licensed offshore are two separate questions: business being lawful in the place of registration does not mean services can be delivered to mainland clients. The wording of the 2026 notice is not limited to exchanges, and it cannot therefore be assumed that payment platforms, merchant collection tools or enterprise-only versions fall outside its scope of review.
A practical review should also examine who actually uses the client account, where the client operates, who issues payment instructions and for whom settlement is ultimately completed. Suppose a mainland trading company opens an account in the name of an affiliated offshore company, but a mainland business team continuously uses that account to arrange exchanges for mainland transactions; in that case, retaining only the offshore registration certificate is insufficient to explain to whom the services are provided. Conversely, a Chinese national genuinely living abroad cannot be treated as a mainland client for the purposes of this question on the basis of nationality alone; it remains necessary to ascertain their location, the substance of the business and any China-related arrangements.
The 2026 notice does not establish a general exemption for offshore licensed institutions permitting them to provide services merely because a client makes a request on its own initiative. The absence of Chinese-language product materials and of a mainland office does not, on its own, prove that no services are being unlawfully provided into the mainland. Where mainland traffic already exists, website application forms, sales chats, referral commissions and payment records should be reviewed to prevent a situation in which the front office claims not to serve the mainland while the back office still manually approves access.
First identify the restricted services and incomplete transactions, and then compliance, legal and operations should jointly determine the path for ceasing new business, communicating with clients and lawfully handling existing assets. Clients must not be asked to use offshore addresses, re-sign with shell companies or change payees in order to continue trading. Whether reporting is required and how frozen funds or refunds should be handled must be confirmed according to the specific account and the status of the matter, so as to avoid simply closing accounts and leaving client assets with no one to deal with them.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Chinese shareholders or Chinese nationality alone are not sufficient to determine whether a particular overseas client can be onboarded; conversely, overseas registration or residence status does not mean the client can necessarily be served. Local market access, genuine business operations and place of use, purpose of funds, and whether the client substantively provides prohibited services to mainland China entities or falls within restrictions on overseas issuance business by domestic entities should all be verified at the same time.
"Chinese background" may mean that the shareholder is a Chinese enterprise, that the founder holds a Chinese passport, or that the customers mainly speak Chinese; it may also mean that operations, employees and funds all remain in the mainland. These situations cannot be conflated. A reasonable onboarding review should not treat nationality directly as a conclusion on the legality of the business; it should first answer: who signs the contract, who uses the service, where the business takes place, and which entity bears the payment or remuneration obligations.
Suppose an enterprise invested in by Chinese shareholders, which genuinely has overseas employees and warehousing, wishes to pay local suppliers: a locally licensed service provider should assess whether the product, currency, customer industry and payment purpose fall within the scope of its licence. For example, the EU's MiCA imposes onboarding requirements on entities providing crypto-asset services, and the relevant fiat-currency payments must also be separately checked for payment qualifications. What is discussed here is the scope for case-by-case assessment, not a compliance endorsement of all overseas enterprises.
The 2026 notice prohibits overseas entities from unlawfully providing virtual-currency services to mainland entities. If an overseas company is merely a shell set up to open accounts, and its real purpose is to buy coins for mainland enterprises, exchange for RMB, or circumvent foreign-exchange administration, the place of registration does not eliminate the risk. Another easily overlooked scenario is where a customer or group intends to issue tokens itself: without the lawful and compliant consent of the relevant authorities, domestic entities and the overseas entities they control may not issue virtual currency overseas, and ordinary payment use cannot be judged together with issuance business.
It is advisable to cross-check registration materials against actual contracts, proof of office operations, payment obligations, sources of funds and beneficial ownership information. If a customer declares overseas operations, but orders, operating personnel and settlement receipts are all concentrated in the mainland, onboarding should be suspended and the inconsistency explained, rather than simply obtaining an overseas address declaration. Periodic review is equally important, because a customer may change its business or the regions it serves after account opening. The above are risk-review recommendations and cannot replace the customer-classification rules of a specific jurisdiction.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Risks exist, but it cannot be concluded that all mainland employees are acting unlawfully merely because the company engages in crypto business, nor can "technical positions" be treated as an exemption. It is necessary to verify what the domestic team actually does, whether it operates prohibited business, and whether it assists an offshore entity in unlawfully providing services to mainland China while knowing or being ought to know of such illegality; employment, tax and data arrangements must also be reviewed separately.
The 2026 notice expressly holds domestic entities and individuals liable where they know or should know that an overseas entity is unlawfully providing relevant services within the PRC and still assist it. Customer service, R&D, sales and finance personnel may all be involved in key steps, and the job title on the labor contract is not the only thing to look at. It is necessary to verify whether an employee handles account-opening approvals, exchange quotations, trading instructions, private-key signing, RMB receipts and payments, or the channeling of mainland clients, and what the employee actually knows about the business risks.
Suppose an employee only maintains general office systems and has no access to clients, orders or assets; the factual basis there differs from that of a team organizing OTC quotations or handling deposits and withdrawals within the mainland. But this is only a distinction in risk analysis; the law contains no rule that "general technical positions are always safe." For products said to serve only overseas clients, the scope of clients and the actual manner of operation must also be verified; where the relevant business itself is unlawful, or an employee continuously handles obviously abnormal requests, an overseas license cannot eliminate the risk on the employee's behalf.
Signing contracts directly with an overseas company, being employed through a domestic affiliate, and engaging independent contractors involve different assessments of entity qualification and labor relations. Where an employee is subject to long-term attendance, performance and day-to-day direction within the mainland, the employment assessment cannot be skipped merely because the contract calls the person a "consultant." Responsibility for remuneration payment, individual income tax filing, social insurance and client data access must be determined separately; whether wage payment is compliant does not mean the business in which the employee participates is lawful.
It is advisable to prepare a position-authority matrix that specifies the data that may be accessed, the instructions that may be executed and the escalation paths. Where problems such as solicitation within the mainland, fictitious trade or collecting payments on behalf of others are discovered, the relevant operations should be suspended and referred for compliance handling, with work orders and review records retained, rather than requiring employees to fill gaps using personal accounts or personal wallets. Contracts, training and access controls should be consistent with actual conduct; a paper policy stating "no service to China" is not enough.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
The fact that a company and its account-opening process are located offshore does not permit it to freely promote stablecoin exchange or related payment services in mainland China. The 2026 regulatory notice restricts related marketing, commercial displays and paid traffic referrals, and imposes liability on those who assist offshore entities in unlawfully providing services to mainland China. Industry research is not the same as customer solicitation; the nature of an activity should be determined by reference to its content, its audience and its conversion pathway.
Whether an event constitutes marketing cannot be determined solely by whether it is labeled a closed-door meeting, a technical exchange, or an investment promotion briefing. Distributing account-opening links after product presentations, inviting deposits, promising conversion into RMB, and paying channel commissions based on completed transactions will all cause the event to be connected to actual business. Suppose the first half of a seminar discusses compliance while the second half instructs mainland merchants to use overseas accounts to receive crypto and settle payments; the research nature of the first half cannot be used to cover the solicitation conduct in the second half.
Yinfa [2026] No. 42 imposes restrictions on internet companies providing online business premises, commercial displays, marketing promotion, and paid traffic diversion, and requires strengthening relevant advertising supervision. Where domestic agents channel clients to overseas products through official accounts, community groups, QR codes, or direct messages, the fact that the final step occurs overseas does not by itself mean there is no mainland risk. Where participants know or should know that the platform is unlawfully serving the mainland, liability for assisting may also arise.
Where the same brand operates both fiat currency payment and overseas stablecoin business, the promotional page must correspond to the services that are genuinely approved to be provided to that customer. For example, if an advertisement displays ordinary cross-border collection services, and sales staff subsequently direct mainland customers to stablecoin exchange through a "faster solution," the assessment must still be based on the complete sales pathway. Changing the contracting entity between teams or moving referrals into private chats will not automatically change the service recipients and the actual business.
General research, risk education, and commercial promotion must be distinguished based on the facts. It cannot be promised that all industry exchanges are prohibited, nor can it be promised that merely not distributing account-opening links will necessarily be lawful. Before publishing content or holding events, complete course materials, lecture scripts, registration conditions, sponsorship arrangements, and post-event contact plans should be retained, and a review should be conducted as to whether they contain inducements to product transactions. For mainland customer acquisition demands that cannot be explained, the promotion pathway should be stopped first, rather than continuing conversion by deleting words, changing groups, or hiding the brand.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
If the service in substance completes unauthorized RMB-to-foreign-currency exchange for clients, the stablecoin is merely an intermediary medium, and the arrangement may still constitute illegal foreign-exchange trading and, in serious cases, a criminal offense. The facts that the two ends are collected and paid by different entities, that funds do not directly cross the border, or that only a technology fee is charged do not necessarily change the substance of the business; the risks relating to virtual assets and payment settlement must also be separately reviewed.
This model typically involves the client paying RMB in mainland China, a designated overseas payee receiving foreign currency, and the operator using stablecoins to replenish positions at both ends. From the client's perspective, what is purchased remains a cross-currency, cross-border funds delivery service. The fact that no single sum is directly remitted between accounts does not prove that no currency exchange occurred; the quotation, orders, RMB transaction records, on-chain addresses and foreign-currency payments need to be examined together.
In a typical case published by the Supreme People's Procuratorate and the State Administration of Foreign Exchange in 2023, Zhao and others operated currency exchange by collecting dirhams overseas, paying RMB domestically, and using Tether to circulate funds. The official case expressly states that using virtual currency as a medium to achieve conversion between domestic and foreign currencies falls within the scope of illegal foreign exchange trading. This is the judicial conclusion in a specific case and does not mean that any holding of tokens or ordinary token transfers automatically constitutes this offence.
The Foreign Exchange Administration Regulations require that current-account foreign exchange receipts and payments have a genuine and lawful underlying transaction and that foreign exchange be purchased and paid through qualified institutions in accordance with the rules. Suppose the client genuinely has import payment obligations, but the platform collects RMB and has an overseas affiliate pay US dollars on its behalf; a genuine order does not confer foreign exchange operating qualifications on the platform. Splitting entities, splitting orders, or renaming the spread as a service fee are not paths to lawfulness.
First confirm whether the client needs to resolve trade payment, investment, or personal funds transfer, and then refer the matter to a bank or institution with the corresponding qualifications to assess it according to the genuine purpose. The platform should reject arrangements premised on concealing the payer, falsifying the purpose, or borrowing accounts. Where transactions have already occurred, complete order, communication, funds and wallet records should be preserved, existing funds reconciled, and dedicated legal advice obtained promptly; transactions must not continue to be added or records deleted in order to balance the books.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Genuine trade does not mean that a stablecoin settlement pathway is automatically lawful. Where corporate receipts and payments involve mainland China, virtual currency, payment and foreign exchange restrictions must still be observed; in offshore markets that permit the relevant business, customer, exchange, custody and fiat payment qualifications must each be verified separately. Orders and invoices evidence the transaction background but cannot substitute for service provider market access.
First verify the buyer and seller, the goods or services, the amount and the payment obligation, and then verify the payment instrument and the service pathway. The first item answers "why the payment is made"; the second answers "who pays lawfully, and by what means." If a platform has only a trade contract but cannot clearly explain who owns the wallet receiving the tokens, who bears exchange losses, and who pays the seller, then even if the order is genuine, the issues concerning customer assets and licensing remain unresolved.
Yinfa [2026] No. 42 restricts the relevant virtual currency business and supporting settlement, while Articles 12 to 14 of the Regulations on the Administration of Foreign Exchange separately set out the genuine and lawful basis for current account transactions and the requirements for purchasing and paying foreign exchange. Suppose a mainland exporter has the buyer deliver stablecoins to an offshore channel, and then an unrelated domestic individual transfers RMB to the exporter. This not only requires an explanation of the source of the payment for goods, but may also involve prohibited services and illegal foreign exchange. An invoice cannot be treated as a document that eliminates all risks.
For buyers and sellers genuinely operating outside the mainland, it should first be confirmed that the applicable law permits the instrument and that the service provider holds the required qualifications. For example, the EU's MiCA distinguishes crypto-asset services from related payment services, and obtaining a crypto licence does not automatically permit handling all fiat currency steps. The contract should also specify whether the seller accepts stablecoins or fiat currency, whether on-chain confirmation equals completion of payment, who handles de-pegging or freezing, and in what currency and amount refunds are to be made.
Before launch, a hypothetical order may be selected to simulate how contractual obligations, on-chain transfers, exchange receipts and fiat currency credits correspond one to one, and then to test scenarios of underpayment, refunds and address errors. Such an exercise is an implementation recommendation, not proof of regulatory approval. If the finance team can provide only an on-chain hash but cannot prove the attribution of the funds and the commercial reason, tax, bank review and dispute resolution will all lack evidence, and the gaps should be filled first rather than launching with unresolved issues.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Wages governed by the labor laws of mainland China must be paid in legal tender and cannot be replaced with USDT. An employee's consent to receive crypto, a contract denominated in US dollars, or payment by an offshore entity does not automatically extinguish the wage obligation. Where an offshore entity directly employs personnel, it must first ascertain the employment relationship and the applicable law; a consultancy agreement or a "bonus" label cannot be treated as a solution.
The Interim Provisions on Wage Payment apply to employees who have formed an employment relationship with an employer within the territory, and Article 5 requires wages to be paid in the lawful currency. Where an overseas company directly hires a person working in the mainland, issues of the employer's capacity to employ, the employment relationship and the applicable law also arise, and no conclusion can be drawn merely from the statement that "the person is in the mainland" or "the contract is overseas." It should be ascertained who recruits, manages, assesses and pays the person, and whether a mainland-affiliated employer exists.
Yinfa [2026] No. 42 clarifies that virtual currencies such as Tether do not have a legal status equivalent to that of the lawful currency. Assuming a contract provides for a monthly wage in RMB and the company instead transfers an equivalent amount of USDT, the employee may still assert that wages were not paid in accordance with the law; an on-chain record of receipt does not of itself prove that the wage obligation has been performed. A signed declaration consenting to receive payment in crypto assets likewise cannot serve as a reliable basis for the company to be relieved of its mandatory wage obligations.
A fixed salary cannot be renamed a project bonus and then continue to be paid in crypto assets; genuinely independent contracting, overseas employment or other remuneration must be reassessed according to the specific relationship and the applicable rules, and mainland employment conclusions cannot simply be carried over, nor can stablecoin payment therefore be found to be feasible. Regardless of what the remuneration is called, the recipient's tax status, the nature of the income and the filing obligations must be confirmed. The form of payment is not inherently a tax-exemption condition.
It is advisable to compile the employment contract, payroll schedules, amounts payable, withholding records, the type and quantity of crypto assets and the actual transfer times, and have employment and tax professionals verify the unperformed obligations and how to address them. Employees should not be required to sell the crypto assets themselves first, or to sign a waiver of claims, in place of rectification. Going forward, a lawful wage payment channel should be established, wage statements should be provided on schedule, and how overseas funds may be used for remuneration in compliance should be explained separately.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
A group's business structure can be assessed, but "mainland fiat currency payment + offshore crypto payment" is not an inherently compliant combination. Each entity must separately satisfy market-access and regulatory requirements, and mainland accounts, teams and client resources must not be used for prohibited virtual currency businesses; where offshore token issuance controlled by a domestic entity is involved, the 2026 rules also impose specific restrictions.
Group isolation should be reflected in a genuine division of contracting, decision-making, funds and service recipients, not merely an organizational chart. Assume that a mainland payment institution provides ordinary collection services for merchants, and an overseas subsidiary provides stablecoin services permitted locally. If mainland sales directly channel merchants into overseas products and domestic accounts redeem RMB for them, the arrangement must still be reviewed as a whole. An affiliate relationship between licensed entities cannot convert prohibited activities into lawful business.
The Regulations on the Supervision and Administration of Non-bank Payment Institutions require operation within the business types and operating regions stated in the license, prohibit renting, lending or disguised transfer of licenses, and impose restrictions on outsourcing of core business and merchant management. The 2026 virtual currency notice separately prohibits financial institutions, including non-bank payment institutions, from providing related account opening, transfer and clearing and settlement services. Therefore, mainland fiat currency business cannot become a RMB on-ramp and off-ramp tool for overseas crypto business.
The group's plan to connect to existing stablecoin payments and its own issuance of stablecoins are different projects. The 2026 notice provides that, without the consent of the relevant authorities in accordance with laws and regulations, domestic entities and the overseas entities they control may not issue virtual currencies overseas; RMB-pegged stablecoins are also subject to special restrictions. The room to assess general overseas services cannot be expanded into permission to issue coins through an overseas subsidiary. Investment, control structures and other approval obligations should also be separately verified before implementation.
It is recommended to separately list customer contracts, bank accounts, wallet controllers, brand pages, customer acquisition sources, employee permissions and related-party transactions. Sharing back-office, customer service or risk management systems is not merely a matter of signing an outsourcing agreement; it is also necessary to examine whether the mainland team actually undertakes restricted business and whether cross-border data transfer is involved. Banks and regulators need enforceable boundaries and evidence, not a statement that "the two entities are each responsible." Business that does not meet access requirements should be excluded rather than packaged.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Possibly. Neither overseas incorporation nor the failure to remit income back to mainland China can, on its own, exclude PRC tax obligations. The corporate tax residency status, the domestic establishment or source of income, and the tax status of shareholders and employees as individuals should be assessed separately; receiving payment in stablecoins is likewise not automatically tax-exempt. Tax treatment and whether the business may be lawfully carried on are two independent questions.
Articles 2 and 3 of the Enterprise Income Tax Law include within the scope of resident enterprises those enterprises established under foreign laws whose place of effective management is within China, and prescribe the corresponding tax obligations on domestic and foreign-source income. The Implementing Regulations refer to place of effective management as substantive, comprehensive management and control over operations, personnel, books and records, and property. Accordingly, arrangements in which key approvals are completed by a mainland team over the long term and in which books, records and funds are all controlled from the mainland must be assessed on the facts; producing a foreign registration certificate alone is not sufficient.
Where a foreign enterprise establishes an establishment or place of business in China or derives China-source income, non-resident enterprise taxation may also arise. Whether a permanent establishment exists within the meaning of a tax treaty, and how profits are attributed, must be determined in light of the applicable treaty and the working facts. Suppose an offshore company has a mainland team that signs contracts externally on its behalf over the long term; the mere fact that the contracting payer is offshore does not exclude a tax nexus. Conversely, the presence of one remote employee does not warrant a direct assertion that a permanent establishment exists.
The Individual Income Tax Law determines resident individuals by rules including domicile and length of residence; in principle, the domestic and foreign-source income of a resident individual enters the corresponding tax regime, while specific incentives, tax treaties and foreign tax credits must still be separately verified. A company earning service fees, distributing dividends to shareholders and paying salaries to employees are distinct tax events and cannot be assessed uniformly on the basis that "the money stays in the company" or "it has not been converted into RMB." Nor should Chinese nationality be equated directly with a conclusion of tax residency for any given year.
Client contracts, fee rules, transaction times, currency types and amounts, wallet ownership, exchange records and foreign tax payment certificates should be retained, and only then should the nature of the income, the recognition point and an appropriate valuation method be determined. This question does not provide a uniform valuation rule applicable to all token income. If the business touches upon mainland prohibitions, filing and paying tax will not render it lawful; the business boundaries must be addressed at the same time, rather than treating tax payment as proof of compliance.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
A license exemption is not necessarily available. The fact that an upstream entity is authorized to exchange or make payments only means that the upstream entity may carry out the corresponding work within the scope of its license; if you yourself accept client mandates, control assets, or undertake exchange and settlement, you must still analyze your own market access. Technology outsourcing, client referrals, regulated agency, and independent service providers are different roles and cannot be mixed together under a single cooperation contract.
The starting point for the assessment is the client contract and actual operations. Suppose a merchant contracts directly with a licensed institution, delivers assets to it, and that institution confirms the exchange rate and receipt of funds, while the company only provides order software. This is clearly different from the company quoting prices itself, collecting stablecoins, and then finding an upstream party to pay out fiat currency. In the latter arrangement, the upstream party may merely be your supplier; the client's claims against you do not disappear simply because a licensed party stands behind you.
Taking the UK payment regime as an example, the exclusion for technical services is subject to specific conditions, and payment initiation and account information services are not automatically excluded merely because no funds are held. Accordingly, where a company receives client instructions, determines the execution of payments, or arranges specific services, it must examine its actual activities rather than merely checking whether funds pass through its own bank account. This example illustrates only the method of assessment; the UK exclusion rules cannot be applied directly to other jurisdictions or to all crypto asset services.
UK FCA guidance makes clear that an agent of a payment institution must be registered by the principal institution and may provide only the payment services of the principal institution; it may not hold itself out as independently providing services in its own capacity. The EU's MiCA, in turn, requires entities providing crypto asset services to meet the corresponding admission requirements, and the related payment services carry separate qualification requirements. Therefore, "the upstream party holds a licence + we are partners" is not a licence-free formula that can be used across jurisdictions.
It is advisable to assign a responsible party, one by one, across the seven stages of account opening, client due diligence, quotation, collection and payment, refunds, complaints, and data retention, and to specify who has the final decision-making authority. Then check whether the product pages, customer service scripts, API permissions, and client statements are consistent. If the contract says the upstream party is responsible for payment, but the platform first promises receipt of funds and the upstream party has the right to reject orders at any time, there is a responsibility gap that should be closed before launch, rather than leaving clients to pursue the upstream party after the fact.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
A white label is not a license that can be shared. Whether you need your own license depends on whom customers contract with, who provides the regulated services, and whether the relevant jurisdiction permits the corresponding agency or distribution arrangements. Your own brand may appear on the interface, but customers must not be led to believe that the brand owner holds the partner's license or is conducting business for which it has not in fact obtained permission.
A white-label arrangement may be merely rebranded software, or it may include accounts, exchange, custody of funds and payment capabilities. In an assessment, it is not enough to look only at the supplier's demonstration page; the brand owner, the counterparty to the service contract, and the person controlling the bank or wallet account should each be confirmed separately. A scenario where the page uses your brand but the customer contract is signed by an upstream licensed institution and funds are paid directly to the upstream institution is a different structure from one where the customer contracts only with you and the upstream institution bears no obligations to customers at all.
The actual service provider, its regulated status and the complaints channel should be clearly displayed before account opening, confirmation of a quote and payment. If the main page claims "we provide licensed accounts" while deep in the agreement it states "we only provide software", this can easily cause confusion about roles. The EU's MiCA prohibits entities without the relevant qualifications from using names or advertising that could easily lead people to mistake them for crypto-asset service providers; this also shows that brand presentation cannot be designed independently of the legal role.
Under FCA guidance, payment institution agents must meet registration requirements, and the principal institution must also effectively supervise them and bear corresponding responsibility for the agent's conduct. This cannot be established merely by writing "agent" into a contract between the parties, nor can payment agency be automatically extended to all crypto-asset activities. If the white-label provider separately controls customer stablecoins, arranges exchange or provides its own balance services, it is necessary to examine further whether that part exceeds the scope of lawful cooperation.
What is most easily overlooked in white-label products is who handles customers after service suspension. It is advisable to agree on termination notice, transactions in progress, return of funds, complaint handling, export of customer data and the necessary account reopening procedures. Customer assets cannot be transferred away by the platform at will simply because the supplier changes, nor can data necessarily be transferred across institutions merely because the contract says "transferable". Conducting a service-suspension drill before launch is more likely to reveal gaps in responsibility than merely comparing interface prices.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Merely providing contact information and participating in transaction arrangements may lead to different regulatory outcomes; the license exemption cannot be determined based on the commission model alone. Even without handling funds, promoting crypto products in a specific region may trigger marketing or solicitation rules. First clarify how far the introduction goes, what products are introduced, and to whom, then verify the requirements of the jurisdiction and the client market.
An ordinary introduction usually involves passing prospective client information to a service provider, which then decides on its own whether to onboard, contract and execute transactions. If the introducer goes on to recommend specific currencies, negotiate exchange rates, receive payment instructions, collect client assets or promise that funds will arrive, the role cannot be assessed merely as that of handing over a business card. Commission based on registrations, trading volume or revenue share may be a risk indicator, but no single billing method can by itself determine whether a licence is required.
Suppose an offshore institution is licensed locally to exchange stablecoins, while a domestic channel advertises to mainland merchants that they can “exchange directly into RMB.” An upstream licence cannot resolve the mainland risks of the channel itself. The 2026 notice expressly addresses liability for related marketing and traffic referral and for assisting the provision of services to the mainland unlawfully. A channel cannot automatically exclude its participation in client acquisition merely by sending account-opening links in private chats and having clients submit applications themselves.
The UK FCA has made clear that financial promotions of relevant crypto assets directed at UK consumers must comply with local rules regardless of whether the promoter is located overseas. Websites, social media and app content may all be subject to scrutiny; merely introducing products operated by others does not mean the content is unrestricted. This example concerns relevant crypto asset promotions in the UK. It does not mean the same rule applies to all business-to-business introductions; rather, it is a reminder to check business licences and marketing licences separately.
It is advisable to agree on the promotional materials that may be used, prohibitions on making promises, the method of passing on leads, personal information handling and the referral of complaints, and to make clear that channels may not collect funds on their behalf, sign service agreements on their behalf or modify quotations without authorization. Service providers should retain mechanisms for spot checks and for terminating non-compliant channels, and introducers should also keep approved materials and versions. If the business in practice requires channels to handle transactions in depth, the question of agency or of holding a licence in their own right should be reassessed, rather than merely changing the title of the contract.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
You cannot directly borrow a bank's license to operate your own crypto payment business. Bank account opening, fiat currency transfer, or settlement services cover only the parts the bank actually undertakes and is authorized to conduct; your exchange, custody, and payment commitments still require separate assessment. Locally permitted bank agency or outsourcing arrangements must also have genuine authorization, defined scope, and a clear allocation of responsibilities.
"Bank cooperation" may mean nothing more than a corporate operating account; it may also mean custody of client funds, payment accounts, agency collection and payment, or other products. Suppose the stablecoin is controlled and exchanged by the platform, and the bank pays out US dollars only on the platform's instructions; in that case the bank participates in fiat currency transfers, but that does not mean the bank becomes the operator of the stablecoin exchange, nor does it automatically guarantee all of the platform's obligations to its clients. Each segment of the actual service should be set out in writing, to avoid substituting a bank logo for legal analysis.
Taking the United Kingdom as an example, the FCA's PERG guidance distinguishes between payment institution agents and payment agents of credit institutions such as banks, and the latter are treated differently for agent registration under the payment services regulations. However, this specific regime still presupposes a genuine agency status; it does not mean that any bank client can independently carry on business in its capacity as a bank. Whether crypto asset services are separately regulated, and whether the place where the agent is located recognizes the arrangement, must also be checked further; this cannot be inferred directly from fiat currency agency.
The cooperation agreement should specify when funds are handed over to the bank, to whom the bank owes the payment obligation, how notice is given when an instruction is refused or delayed, and how the platform refunds clients. If the bank provides only an account to the platform, while the client contract is signed by the platform, clients may need to assert their rights against the platform first. The platform's commitments to the outside world must not exceed the services the bank has agreed to in writing; otherwise the upstream party may be entitled to refuse payment while the downstream obligation has already fallen due, and the funding gap will still fall on the platform.
Yin Fa [2026] No. 42 prohibits financial institutions from providing account, transfer and clearing and settlement services related to virtual currency business. Therefore, the bank cooperation model used in overseas markets cannot be applied directly in the mainland, nor can ordinary trade accounts be used to handle coin-related settlements. In practice, confirmation should be obtained from the bank as to the real business, client types and account use; however, a bank's willingness to provide services cannot replace an independent legal assessment of market access.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
First choose a bank that clearly understands and accepts the actual business, then compare fees, currencies and account-opening speed. An operating-expense account, an account that collects platform service fees, and an account that handles funds collected and paid on behalf of customers must not be conflated. Whether an account is usable should be determined jointly by the actual purpose, the scope of customers, the safeguarding of funds and the bank's written conditions.
Before opening an account, you should at least explain the company's incorporation and licensing, which customers it serves, what role stablecoins play in the process, and where fiat currency comes from and to whom it is paid. Describe the company's own funds separately from customer-related funds, and list the expected currencies, transaction volumes and main payment countries. A bank's acceptance of ordinary software companies does not mean it is willing to take on equivalent transactions for payment platforms or crypto businesses.
The 2023 HKMA circular requires banks to adopt a risk-based approach and encourages them to support the reasonable account-opening needs of licensed virtual asset service providers regulated by the Hong Kong Securities and Futures Commission; this is not a guarantee of account opening for any company, nor an approval of all transaction channels. You must still explain product and customer risks to the specific bank, and cannot substitute regulatory encouragement or peers' successful account opening for your own due diligence.
Assume the bank allows the company to collect service fees paid by overseas institutions, but does not allow it to collect large amounts of funds from unidentified merchants. Even if this account has already been opened, it is not suitable for directly launching merchant collection. It is advisable to submit the payer, account name, ultimate beneficial owner, refund path and intermediary institutions to the bank one by one for confirmation, and to verify whether third-party payments are accepted, whether the required clearing networks are supported, and whether further manual review may occur after funds arrive.
As a commercial due diligence recommendation, you should also compare transaction inquiries, returned remittances, reconciliation files, emergency contacts, return of funds after account closure and available backup arrangements. If customer funds need to be safeguarded, you should ascertain whether the bank provides the corresponding accounts and confirmation documents, rather than merely saying that 'funds are very safe in the bank'. Backup accounts must also disclose the same genuine business, and must not be used to continue operations under a concealed purpose after the main account is restricted.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
A license does not mean a bank is obliged to open an account. The bank must also independently understand the actual business, the customers, the source of funds, and whether it can itself manage the relevant risks. However, a refusal does not necessarily mean the business is unlawful; a distinction should be drawn between insufficient materials, a product mismatch, and the bank's own risk decision, before deciding whether to provide supplementary explanations, apply for review, or seek a suitable counterparty.
A licence demonstrates that a specific entity is permitted to carry out specific activities, whereas a bank must assess entering into a specific account relationship with that company. The UK FCA's guidance on risk management states that banks need to assess risk on a customer-by-customer basis and cannot simply treat an entire industry as unacceptable; at the same time, relationships whose risks cannot be effectively managed should not be established or maintained. It follows that independent bank review and the avoidance of indiscriminate exclusion can coexist.
Suppose the licence materials describe corporate remittance, the account opening form states software subscription revenue, yet the fund flow diagram shows the platform exchanging stablecoins on behalf of merchants; the bank then cannot determine what account is actually being requested. In other cases, the entity holds a licence, but the scope of permission, target countries or customer industries do not match the intended use in the application. Contracts, websites, financial forecasts and application forms should be checked for consistency, rather than repeatedly deleting words such as "crypto" to reduce visibility.
You may ask the bank to clarify whether materials are still missing, whether there is a suitable product or industry team, and whether there is an internal review channel. A bank may not be able to disclose all of its risk judgments or review details, and an applicant cannot infer specific problems from a single reference to "compliance reasons". HKMA circulars encourage banks to improve account opening processes for specialised industries and fair access to basic services; enterprises may raise specific process questions on that basis, but the circulars cannot be interpreted as mandating approval of account opening.
Useful supplements include the industry and country distribution of customers, samples of source-of-funds verification, on-chain risk handling procedures, segregation of customer funds, and escalation mechanisms for unusual transactions. If the bank expressly does not support this type of account, continuing to repackage the same application may not be effective, and an institution that accepts the genuine model should be sought. Where trading has already begun, it is also necessary to assess whether customer obligations can be performed while the account is unavailable, and reliance on employees' or shareholders' personal accounts for temporary receipt of funds is not permissible.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
First distinguish whether the funds received are the company's own payment for goods or service fees, or funds received, held temporarily and transferred on behalf of clients. The latter cannot be used directly as a settlement account merely because an ordinary corporate account can receive deposits; it is necessary to verify business qualifications, bank restrictions on account use and applicable client-fund protection requirements. Segregating accounts does not by itself mean that legal bankruptcy remoteness has been achieved.
Suppose a platform collects payments on behalf of one hundred merchants, deducts fees and then pays out. The amounts owed to merchants generally cannot all be classified as freely usable operating revenue merely because they first entered the platform's account. The ownership of funds and payment obligations should be determined under the contracts and applicable law. By contrast, software service fees already earned and collected by the company may constitute its own funds, but the bank should still know the true business source, and this distinction cannot be used to conceal collection and payment on behalf of others.
The current FCA guidance in the United Kingdom requires payment and e-money institutions within scope to safeguard relevant client funds, which may be achieved through statutory segregation or qualifying insurance, guarantees and similar arrangements, together with record-keeping and reconciliation requirements. It therefore cannot be said broadly that the whole world must use the same type of trust account, nor can opening another ordinary account be regarded as completing safeguarding. The institution holding the funds, account confirmation and the legal effects in insolvency should all be verified under the applicable regime.
China's Regulations on the Supervision and Administration of Non-bank Payment Institutions require reserve funds to be deposited in accordance with the rules and prohibit misappropriation, occupation, borrowing or use as security; a 2026 notice further restricts supporting settlement involving virtual currencies. Reserve fund arrangements under a mainland payment licence are not a lawful channel for receiving and paying RMB for stablecoin business. Naming an account a "client segregated account" cannot alter the prohibitive boundary.
It is advisable to reconcile client ledgers, bank balances and funds in transit daily or at the applicable statutory frequency, and to record separately earned fees, refunds, security deposits and amounts pending settlement. Then test the following assumption: if the bank freezes the platform's own funds, can client funds be clearly identified and returned in accordance with law? If this can only be explained by the platform's internal Excel, without account and contractual safeguards, the risk remains. Before launch, withdrawal authority, bank set-off clauses and mechanisms to cover funding shortfalls should all be reviewed together.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Working with qualified institutions can be evaluated, but virtual accounts or virtual IBANs are not a uniform legal product. Some are merely collection identification numbers under a master account, while other arrangements may substantively constitute a client payment account. The account's location, the account-opening entity, rights to balances and payment liability must be clearly defined, and not all virtual numbers should be marketed as the client's own bank account.
A typical virtual IBAN can allocate incoming payments from different sources to the same master account, making it easier to identify orders and customers. Suppose a customer receives a dedicated number, but the account name of the bank master account is the platform; the customer may only have a corresponding claim to the balance against the platform or the payment institution, rather than directly becoming a bank depositor. It is necessary to review the account-opening contract, the funds ledger and the provider's responsibilities; characterization cannot be based solely on the number format or on the ability to receive payments.
In their official 2026 report, the French ACPR and Tracfin stated that some virtual IBAN arrangements correspond to payment accounts separate from the master account; for virtual IBANs bearing the French country code, the report proposes that they be analyzed as payment accounts held in France. This is the specific position of the French authorities on the relevant arrangements and cannot be generalized to the rules of all countries, yet it is sufficient to serve as a reminder: a cross-border number does not inherently exempt one from local account regulation.
If a product only performs order reconciliation, the legal issues may differ from a situation where customers can retain balances over the long term, pay any third party at will, and transfer funds to other users. It should be confirmed who provides the payment service, who carries out customer identification, who controls withdrawals, and which regime applies to the protection of customer funds. The functions of an ordinary fiat currency account cannot automatically be extended to stablecoin exchange permissions, and bank deposit protection and the protection of funds at payment institutions must not be conflated.
It is advisable to use hypothetical transactions to verify whether the payee name entered by the payer, the country displayed and the actual destination of the funds are consistent, and to test duplicate payments, unknown incoming payments, and credits and refunds after a customer closes an account. Contracts and web pages should explain the actual service provider and the flow of funds; where automatic cross-border transfers are involved, particular attention should be paid to whether customers or payers are misled into believing that the funds remain local. Necessary data must be traceable to the actual payer and the ultimate beneficiary.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Selecting a channel requires examining four matters at the same time: who actually provides the service, whether the qualifications cover the entire funds path, how customer assets are safeguarded, and who bears responsibility when errors occur or the service is discontinued. Low fees, examples of successful settlement and screenshots of licences are all insufficient to prove that a channel can be used lawfully over the long term. Channel due diligence must be connected to your customer-facing contracts, rather than reviewing only the supplier itself.
Behind a single channel brand there may be an exchange company, a custodian, a payment institution and several banks. The counterparty should be required to identify, for each step, the contracting entity, the entity actually performing the obligations and the person controlling the assets, and to explain whether subcontractors are used. If the contract is signed by Company A, stablecoins are transferred to Wallet B, and fiat currency is paid by an unrelated Company C, the relationships among the three, their legal basis and their respective responsibilities should be verified, rather than merely checking the licence displayed by Company A.
The EU MiCA regime distinguishes between crypto-asset service authorisation and the qualifications required for related payment services; holding a crypto-asset licence does not mean that all fiat currency payments can be completed unconditionally. UK payment agents must likewise act within the corresponding agency relationship and scope. Actual due diligence should therefore check official registers, licence restrictions and the uses accepted by banks, and in particular verify who is authorised to accept customer assets, effect exchanges, hold assets in custody and make payments, rather than merely asking whether a licence exists.
It is advisable to review at least the service contract, the fund-flow chart, the fund-protection statement and the exception-handling procedures. The contract should specify when quotations take effect, fee deductions, completion of payment, the currency of refunds, reserves or security deposits, and dispute resolution; the fund-protection statement should explain whether customer assets are segregated from the channel operator's own operating property and who has withdrawal rights. These are due-diligence recommendations; the specific statutory obligations remain governed by the applicable market, and safety cannot be presumed merely because the counterparty describes an account as a "segregated account".
One may assume that stablecoins are frozen by the issuer, that a bank returns a remittance, or that the channel loses its authorisation, and should then ask, item by item, how orders that have not yet been exchanged, orders already exchanged and orders for which payment has already been sent would each be handled. The EU MiCA regime emphasises, in relation to outsourcing, that a licensed service provider cannot thereby transfer its own responsibility; even if that rule does not apply directly to you, you should check whether the upstream disclaimers are unbalanced against the commitments you have made to your customers. Any replacement channel must complete legality and data review in advance; customer funds must not be taken over through unfamiliar accounts on an ad hoc basis.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Sharing is technically possible, but it may not be permissible under law and contract. A bank's support for a given currency does not mean it accepts payers, merchants and purposes from all countries; a payment or crypto licence may likewise not cover newly added markets. A more prudent approach is to reuse the technical layer while separately confirming market access and channel authorisation by customer region, transaction purpose and fund flow path.
The fact that a channel can send US dollars does not mean it may solicit clients in any region or accept US dollar payments from all industries. Suppose the original channel only served corporate trade payments in one region, and the product adds personal wallet withdrawals in another country; although the currency has not changed, the clients, product and risk have. The local service rules and bank conditions need to be re-verified, rather than merely testing whether the API can submit an order.
Taking the EU as an example, providing crypto-asset services across member states under MiCA is subject to a clear notification mechanism, and the official Q&A of the Central Bank of Ireland requires submission of information such as the intended host member states, the types of services and the start date. This does not equate to a global operating licence, nor does it replace the qualifications required for fiat payment. For payment collection and disbursement markets outside the EU, local rules still need to be verified; EU market-access conclusions cannot be applied directly merely because funds pass through a European account.
It is recommended that each row correspond to "client location + client type + product + payment/collection currency + final destination of funds", with the contracting entity, licensing basis, bank/channel permission, safeguarding of funds and refund method filled in separately. A technical back office showing that a country is supported only indicates that routing may be possible; it does not prove that the combination has been approved for launch. Bank contracts should also verify the actual end clients, not merely the place of incorporation of the company that directly opens the account.
If all markets rely on the same bank or exchanger, suspension of an account may affect multiple product lines at the same time. A single technical monitoring and reconciliation framework may be shared, but the ownership and safeguarding of client funds in different markets should be identified, and all balances should not be commingled. Adding a backup is not a way to circumvent the restrictions of the original channel; rather, the same review must be completed for another lawful route. Before switching, client notification, transfer of information, in-flight orders and duplicate payments must also be addressed.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
There is no globally applicable "list of serviceable industries." One should simultaneously verify whether the merchant's actual business and place of sale are lawful, the scope of the payment institution's license, and the onboarding policies of banks and payment channels. Ordinary e-commerce merchants may also sell restricted goods; high-risk industries cannot be onboarded merely on the basis of a single overseas business license.
Names such as software, e-commerce and consulting can help locate customers, but they cannot complete a compliance assessment. A software seller may sell ordinary office tools, or may in fact provide investment trading or gambling services; a cross-border trader may deal in entirely different goods, destinations and counterparties. Institutions should understand the specific sales content, customer base, performance methods and refund mechanisms before deciding whether they have the capacity to identify the risks.
In its customer due diligence guidance, AUSTRAC of Australia emphasizes that verification is not merely collecting identity documents; it also requires understanding the customer and the business relationship and continuously updating information. What is cited here is an explanation of Australian regulatory requirements; other markets need to check their locally applicable rules, and this guidance cannot be treated directly as global law.
Assume an offshore online gambling merchant holds a licence in its place of incorporation and wishes to accept UK customers through a stablecoin collection service. The UK Gambling Commission makes clear that providing remote gambling services to consumers in Great Britain requires its licence, even if the operator is established offshore. This example shows that payment teams cannot look only at where a merchant is incorporated, but must also look at whom it provides services to; nor can they ignore the underlying industry restrictions simply because the payment currency changes.
A bank or settlement partner may refuse a lawful industry based on its own risk appetite, which is not the same thing as a legal prohibition. Conversely, a channel being willing to take on business is not proof that the operation is lawful. The true industry, customer base and transaction path should be explained to the counterparty, and written approval should be tied to the specific contracting entity and product, rather than relying on a salesperson saying orally that "we have handled similar customers".
In practice, three lists can be established: permitted, enhanced review and refused, but the reasons for classification should be specific. An industry requiring additional materials, transaction limits or manual review does not mean it must be permanently excluded; where the purpose of funds cannot be explained, performance cannot be verified, or disclosure of the true business is refused, those gaps should be addressed first.
Before the client acquisition team introduces a new industry, it is recommended that the business, compliance, risk management and channel heads jointly confirm whether to onboard it, and record the required capabilities and limitations. After launch, observe deviations against the expected average transaction value, customer source regions and refund rate. The above classification and approval are management methods that may be adopted; they are not a standard format uniformly prescribed by any jurisdiction. The key point is that the institution can explain why it accepts the merchant and how it will handle anomalies when they arise.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Yes. A company name, certificate of incorporation and wallet address answer only part of the question; they cannot prove what the merchant actually sells or the commercial rationale for each payment received. Goods, customers, performance and fund flows should be understood on a risk-based basis, with ongoing monitoring for anomalies; this does not amount to a full audit of every merchant transaction by transaction.
A business license can prove that an entity exists, but "who this company is" and "why it received this payment" are two separate questions. For merchant crypto asset collection, it should at a minimum be possible to understand the merchant's main business, the recipients of its payments, and the purpose of settlement. Otherwise, proceeds from ordinary sales, payments collected on behalf of others, and funds generated through fictitious orders will appear in the system as the same on-chain transfer.
AUSTRAC's customer due diligence guidance makes clear that due diligence should understand customer risk and the purpose of the business relationship, and should be updated when circumstances change. FATF's virtual asset risk indicators also list amounts lacking a reasonable business explanation, frequency, and abnormal customer behavior as factors of concern. FATF documents are international references for risk identification; specific obligations and reporting procedures still depend on local law.
For ordinary physical-goods e-commerce, websites, product categories, price ranges, logistics, and after-sales samples can be checked; for subscription software, subscription terms, user sources, and service delivery records are more suitable. For professional services, service contracts and milestone deliverables can be reviewed. There is no need to request exactly the same large package of documents from every type of merchant, but it should be possible to match revenue sources, collection scale, and operating capacity.
Assume a company declares that it sells low-priced software, then consecutively receives multiple payments far above its ordinary per-order price and requests settlement to an unrelated third party. The reasonable action is not merely to check whether an address has been flagged red by a risk tool, but to inquire about the transaction content, the payment relationship, and the reason for third-party collection, and then decide whether to continue processing based on the responses and evidence. This scenario is hypothetical and does not mean that a high amount is itself unlawful.
A transaction hash can help locate asset transfers, but it cannot independently prove that goods have been delivered, that the buyer agreed to pay, or that the merchant holds the necessary qualifications. Conversely, a formally complete invoice cannot automatically rule out problems. A more reliable approach is to cross-check on-chain records against orders, contracts, user behavior, and settlement accounts, and to retain records of how inconsistencies were handled.
It is advisable to establish a basic transaction profile at onboarding and to use newly added high-risk regions, changes in business type, concentrated complaints, or sudden changes in collection patterns as signals for review. Upon identifying anomalies, supplementary due diligence, restrictions on new transactions, or escalation for approval may be adopted in accordance with applicable law and contract; whether to report, freeze, or notify the customer must be determined separately, and all anomalies must not be treated uniformly as crimes, nor should the sales team be allowed to release them on its own.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Deposits and withdrawals for exchanges and wallets generally connect fiat currency accounts with crypto asset trading or balances; they are not simply another way of collecting payment for ordinary goods sales. The exchange, transfer, custody and end-user relationships must be re-identified, and recognition of the true purpose must be obtained from banks, acquirers or local payment channels.
An e-commerce payment generally corresponds to a single product or service; a deposit to an exchange may merely place funds into a tradable balance, with the coin purchase occurring afterward; a withdrawal from a wallet may involve selling crypto assets and paying funds to a bank account. Even if the interface has only one "pay" button, these arrangements differ in transaction object, delivery outcome and refund logic. They should be identified step by step along the flow of funds and assets, and an ordinary e-commerce acquiring contract cannot simply be applied.
For example, the Monetary Authority of Singapore (MAS) expressly brings certain facilitation of token transfer and exchange activities within the regulation of payment services, even where the service provider does not hold funds or tokens. Therefore, if a platform receives exchange instructions, arranges transactions or determines the flow of funds, it cannot conclude that it is merely providing technology solely because its partner exchange holds a licence. This is a specific example of Singapore's rules and does not mean that every country adopts the same definitions.
For card deposits, Visa's public rules separately impose coding and page information requirements for non-sovereign-currency transactions, indicating that coin purchases cannot simply be disguised as ordinary retail transactions. The specific codes, acceptable customers and onboarding conditions should be confirmed by the acquirer on a product-by-product basis; card scheme rules, financial licences and bank contracts are constraints at different levels.
Assume a platform receives a consolidated settlement payment from an exchange, but the exchange actually has a large number of individual users behind it. The platform should first clarify whether it is handling the exchange's own funds or collecting and paying on behalf of its users; who reviews end users, who retains payer information, and whether information can be obtained when an investigation or refund request arises. It cannot be asserted arbitrarily that all models must re-identify every user, nor can it be assumed that corporate customers inherently shield underlying risks.
In particular, a distinction must be drawn between deposits by the customer personally, payments made by third parties on the customer's behalf, and centralized corporate payments. The three may require different supporting materials and rejection conditions. Mixing them within the same account and the same business description is neither conducive to due diligence nor easy to explain when a bank raises questions.
Deposits not credited, failed coin purchases, failed on-chain transmissions, refunds and account closures should each be run through, to confirm who owes what to the user at each step. It is advisable first to obtain written confirmation from counterparties on the scope of business and markets, and then to verify reconciliation fields and authority to handle exceptions. Successful technical integration only proves that the interface is usable; it does not prove that qualifications, customer relationships or risk allocation have been resolved.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Stablecoins may shorten the time for cross-border value transfer and processing by intermediary institutions, but on-chain transaction fees alone cannot be used to determine whether they are cheaper. Enterprises should compare the full-process costs for the same amount, same currency and same receipt outcome, and should also factor in the bid-ask spread on buying and selling coins, local disbursement, liquidity and the handling of failed transactions.
Does the client need "stablecoins received in a wallet" or "usable local currency received in the supplier's bank account"? The former can end once the on-chain transfer is complete, while the latter still has to go through selling the coins and the bank or local payment network. Comparing the on-chain stablecoin transfer time with the full settlement time of a traditional bank involves inconsistent starting and ending points, and it is easy to reach misleading promotional conclusions.
Research by the Bank for International Settlements on stablecoin cross-border payments notes that on-ramp and off-ramp arrangements are an important part of the overall process. A 2026 small-value remittance field test by the Bank of Italy likewise found that costs and speeds vary widely, mainly due to on-ramp and off-ramp arrangements and local payment infrastructure. That study covered specific corridors and transaction sizes and cannot be directly extrapolated to quotes for large corporate settlements.
The first category is explicit fees, including transfer, network and local payout fees; the second is implicit spreads, including fiat currency exchange, coin sales and foreign exchange conversion; the third is the cost of tied-up funds, including pre-funding, margin deposits and weekend reserves; and the fourth is operational risk cost, including reconciliation, manual review, refunds, failed retries and handling of asset anomalies. Not every item will actually arise, but each should be confirmed during assessment rather than assumed to be zero-cost.
Assume that both the payer and the payee of Enterprise A are willing to hold the same stablecoin, while Enterprise B must have its overseas employees receive funds in local bank accounts. A may save one coin sale and one payout, while B still depends on local bank business hours and processing arrangements. Even if the on-chain transfer fees are the same for both, the final cost and available time cannot be regarded as the same. This example illustrates structural differences; it is not a promise that stablecoins will necessarily save money.
For high-frequency corporate payments, attention should also be paid to whether a single failed transaction drags down an entire batch of settlements, and how much funds the channel requires to be pre-deposited. Average speed may look good, but if funds cannot be paid out when funds are tight, the product promise may still not be fulfilled.
It is advisable to select specific corridors in which operations have been approved, record the full-process settlement time and net amount received on weekdays, weekends and at different amounts, and compare them with banks or other payment solutions on the same basis. Externally, present "on-chain confirmation," "conversion completed" and "available in bank" separately, and explain exceptional circumstances. Before stable data is available, it is not appropriate to promise global instant arrival, a fixed savings percentage or the complete absence of intermediary costs.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Payment licensing, labor remuneration rules, tax and data responsibilities must each be addressed separately. Overseas employees and independent contractors cannot be lumped into a single category, and the parties' agreement to receive payment in crypto does not by itself satisfy local wage-payment requirements. The platform should also make clear whether it merely executes payments or also assumes employment, payroll calculation or tax filing services.
The legal basis differs between an enterprise paying wages to employees and settling contractual fees with independent service providers. The determination should not rest solely on whether the contract describes the person as a "consultant" or whether the payment reference states "service fee"; rather, the work arrangement and the applicable local classification criteria should be verified. A payment platform generally need not make all employment determinations on behalf of its customers, but it should at least require customers to state the nature of the payment, so as to avoid designing a payroll product as a bulk transfer tool without payee classification.
The platform's own business should also be broken down: does it merely execute payments on instruction, or does it calculate wages, withhold taxes, hold balances in custody, or even contract as an employer of record? The latter arrangements may change the scope of liability. Deliverables should be set out in quotations and contracts, and a single label of "global payroll" must not cover matters for which no one is in fact responsible.
Taking Singapore as an example, the Ministry of Manpower imposes requirements on the manner and timing of wage payment and on wage records, and its guidance on payment of wages in kind emphasizes that legal currency should be used. Accordingly, it should not be asserted, merely because an employee clicks to consent, that stablecoins can directly replace statutory wage payments. Different categories of employees, components of remuneration and arrangements still require specific review.
Where an employer lawfully pays wages into an employee's bank account and the employee subsequently purchases stablecoins on their own, that is a different process from the employer sending tokens directly to a wallet and asserting that wages have been settled. For independent contractors, local contract, payment and tax rules should be examined separately; the conclusions reached for employee wages cannot be mechanically applied to all service fees.
HMRC guidance in the United Kingdom on tokens provided by third parties as employment income indicates that this method may still give rise to income tax and National Insurance obligations and involves employer PAYE processing. This example shows that changing the asset in which remuneration is delivered does not remove that remuneration from the tax system, and the specific tax liability cannot be determined solely by reference to the token symbol.
Product design should include fields for fiat denomination, valuation point, allocation of taxes and fees, transaction charges and proof of receipt. If a net amount received is agreed, it should also be clear who makes up any shortfall after exchange-rate fluctuations or deductions; if the commitment is merely to execute customer instructions, the product should not be marketed as having resolved all local employment and tax compliance matters.
It is advisable first to select the confirmed places of employment and places of receipt, verify the methods of receipt and the service permissions of the payment platform, and then configure contracts, payslips or invoices, necessary tax information and procedures for exceptional supplementary payments. Where personnel information is shared, the purposes and scope of data access by each party should also be limited. Initial testing should verify when the payee can actually use the funds, rather than merely confirming that the wallet address received tokens.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
A license may still be required. A technical fee, subscription fee or exchange spread is merely a pricing method and cannot change the service actually provided. The assessment should focus on whether the platform exchanges, transfers, custodies or initiates payments on behalf of customers, and on how the applicable jurisdiction defines these activities, rather than treating "not earning a spread" as a condition for exemption from licensing.
Business review first looks at what service the customer is purchasing, what commitments the platform makes, and who executes key instructions. A company may charge monthly fees and still be continuously operating a payment service on behalf of customers; a company may charge per transaction and may genuinely be providing only software. The fee model can be part of the facts, but it cannot independently answer the market-access question. A contract may be written as "technical services," yet if it in substance promises to convert the customer's stablecoins and pay them into a designated account, the corresponding business still needs to be reviewed.
The UK FCA's PERG payment regulatory guidance explains that software or technical services that merely support payments may fall within a specific exclusion, but payment initiation services do not fall within that technical-services exclusion. In other words, under the UK framework, not holding funds and not providing regulated payment services are not the same proposition.
In Singapore, MAS's explanation of the scope of payment services likewise covers certain token-transfer and exchange-facilitation activities that do not involve holding funds or tokens. These rules do not mean that all interfaces require a license; rather, they remind teams to break down the order, authorization and execution process for analysis, and then determine whether a specific definition or exclusion is engaged.
Assume A provides order-management software to merchants; the merchants themselves contract with payment institutions, confirm conversions and make payments, and A only transmits business data. B also charges a monthly software fee, but B accepts payment requests, arranges conversions, selects the payout institution and is responsible for funds arriving. The two price lists can be completely identical, yet the legal relationships are different. B cannot directly rely on the pure-software conclusion applicable to A, and A should also confirm that its actual functions have not crossed the established boundaries.
It is also necessary to check who charges whom, whether fees are deducted directly from customer assets, and whether fees are tied to quotations. Renaming an exchange spread as an interface fee, if the fund handling and customer commitments have not changed, generally does not resolve the original problem and may instead create an inconsistency between the accounts and the substance of the business.
It is advisable to map each fee to a clearly defined service and list, item by item, the provider, customer authorization, delivery standards and failure handling. Then check whether the system logs are consistent with the contract: who receives instructions, who can modify the payee, and who has authority to deduct fees and issue refunds. If the genuine intention is to operate only a technical business, the permissions, contracts and customer experience should be genuinely adjusted, rather than merely changing the name on the invoice; the specific structure must still be verified against the target market.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Purchasing crypto assets by card requires simultaneously satisfying the target market's crypto business access requirements, acquirer approval, card network rules and risk management requirements. A successful charge does not mean the business is authorized; ordinary e-commerce acquiring agreements also cannot automatically be used for crypto purchases. Before onboarding, the nature of the transaction, delivery address, dispute handling and allocation of liability should be clearly stated.
If a platform quotes prices to users and sells crypto assets in its own name, its eligibility to provide trading services must be reviewed; if users purchase crypto assets directly from an independent third party, the platform must also review whether it is receiving orders, arranging transactions or promoting regulated services. Taking Article 3 of the EU's MiCA as an example, exchanging own funds and executing orders on behalf of clients are distinct service items, and not all of them can be placed within "acquiring technology."
Visa's public rules contain dedicated coding arrangements for transactions involving the purchase of non-sovereign currencies and require the payment page to disclose relevant information. These are card network rules, not a government license. Actual onboarding should also require the acquirer to confirm the applicable transaction type, customer region, processing path and whether it accepts such business. Purchasing crypto assets must not be packaged as software, membership or other goods in order to obtain a channel that would otherwise not apply.
The payment page should enable users to understand the currency they are purchasing, the total cost, the delivery destination and refund restrictions. The above information is not only used to reduce misunderstandings, but also affects whether it can later be explained what the user actually agreed to. Transaction coding and page disclosures should be tested together to avoid a situation where the front end displays a crypto asset purchase while the back end reports it as an ordinary good.
Assume that after a user pays by card, the platform immediately sends the assets to a wallet that the platform cannot recall. If card fraud or another dispute subsequently occurs, on-chain delivery cannot automatically prevent the bank card dispute process. The Visa Merchant Dispute Guide distinguishes fraud, processing errors and consumer disputes, and identity verification is not a guarantee that covers all disputes.
Therefore, risk management checks and failure handling should be specified before delivery is permitted. For example, where payment is authorized but the exchange fails, the asset transfer fails or the user submits an order repeatedly, it is necessary to design who reverses the charge, who bears the price difference and how duplicate refunds are avoided. Assets must not be held indefinitely for the purpose of preventing chargebacks, nor should users be promised that no refund is possible under any circumstances.
The legal column confirms the service entity and market permissions; the channel column retains the acquirer approval, transaction codes and rule versions; the operations column verifies reconciliation, refunds, fraud review and customer service evidence. Only when all three columns are completed is there a basis to assess launch. There is no uniform answer on security deposits, settlement cycles and fees; these should be calculated based on the actual contract, with particular confirmation of disputes that may still arise after termination of cooperation and arrangements for retention of funds.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
It may lose the value corresponding to the crypto assets already delivered, and may also bear dispute-handling fees, occupied security deposits and additional operational costs. Who ultimately bears the loss depends on the reason for the chargeback, the card network rules and the contract. On-chain irreversibility, passing 3DS or including a statement that no refunds will be made does not mean that card funds can never be clawed back.
A user's denial of having made the payment, duplicate charges, incorrect amounts, failure to deliver as agreed, and a promise to refund that was not honored are distinct issues. Visa's merchant dispute guide classifies disputes into multiple categories and requires evidence to be submitted according to the specific reason and applicable handling rules. Upon receiving a chargeback notice, the first step should be to confirm the reason, the transaction status and the response deadline, rather than issuing a uniform reply that "the assets are already on-chain, so the chargeback is not accepted."
Visa's explanation of 3-D Secure indicates that fraud-related dispute protection depends on conditions such as how the transaction was processed and the required authentication data. Successful authentication does not mean that the goods or assets have been correctly delivered, nor does it automatically cover other disputes such as duplicate charges or incorrect amounts. Whether the specific protection applies should be determined by the acquirer based on the transaction records and the applicable rules.
Assume a coin purchase transaction completed identity verification, but the platform charged the user twice due to an error in its retry logic. Even if both charges have authentication records, the duplicate charge cannot be denied solely on the basis that "3DS was passed." Conversely, where the assets were indeed delivered to the address confirmed by the user, the wallet address, on-chain transaction records and order information can serve as useful evidence, but their probative value still depends on the type of dispute.
Projects should calculate the losses that cannot be recovered after asset delivery, as well as contractual processing fees, rolling reserves, delayed settlement and labor costs. If an upstream party first deducts the amount from the platform's settlement funds, the platform may need to top up cash first, even if it can later seek recovery from the merchant or the user. The existence of a right of recovery and the actual recovery of funds are two different matters.
Who ultimately bears the loss must be checked layer by layer along the contracts: who the merchant is, who signed the acquiring agreement, whether the platform has undertaken to backstop losses, in what circumstances deposits may be deducted, and what surviving obligations remain after the contract is terminated. This article does not provide a uniform reserve ratio or chargeback deadline, because these vary with transaction type, region, rules and contracts.
It is advisable to link order confirmations, authentication results, charge and clearing records, the address confirmed by the user, asset delivery and refund status to the same transaction number, and to retain necessary materials in accordance with data protection requirements. After receiving a dispute, first rule out duplicate compensation caused by an already-issued refund, and then submit materials according to the reason. Risk management should also fix the root causes, such as duplicate requests, easily misidentified billing descriptors or customer service delays, and should not rely solely on case-by-case appeals.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Value transfer may occur primarily on-chain, but complete cross-border collection and payment need not take place entirely on-chain. Wherever the payee requires bank fiat currency, customer identification, tax documentation or dispute resolution, off-chain steps remain. The licensing and liability attaching to the provision of services on behalf of clients do not disappear merely because the transfer does not pass through a bank.
When the parties agree to and lawfully use stablecoin settlement, on-chain delivery may form part of performance; however, whether a contractual debt has been discharged still depends on the applicable law and the agreement, and a general conclusion cannot be drawn from a single transaction hash alone. If the contract requires the payee's bank account to receive a specified fiat currency, sending stablecoins to an intermediary institution is merely one step in the overall process.
Research by the BIS Committee on Payments and Market Infrastructures (CPMI) on stablecoin cross-border payments incorporates on- and off-ramp arrangements into its overall analysis. For payment products, this means that on-chain speed and the speed at which funds ultimately become available should be stated separately; round-the-clock on-chain operation cannot replace the processing capacity of the stablecoin seller, banks and local payment channels.
Article 82 of the EU's MiCA sets out requirements such as client agreements for crypto-asset transfer services on behalf of clients. ESMA's public Q&A further clarifies that activities meeting the definition of a transfer service, even if embedded in other crypto-asset services, should be analyzed against the corresponding authorization requirements. Therefore, "we only transfer coins, not fiat currency" cannot automatically exclude regulation.
A distinction should be drawn between an enterprise paying its own debts with assets it controls and a platform accepting instructions from others to transfer assets on their behalf. This is not to say that the former is risk-free in all jurisdictions, but that the roles of the parties differ, and the same set of licensing conclusions cannot be applied interchangeably merely because an on-chain address appears in both cases.
Suppose a procurement contract is denominated in US dollars and the supplier agrees to receive a certain stablecoin. The parties must still specify the conversion time point, the network used, how shortfalls or mistaken transfers are handled, and whether a top-up is required if the asset depegs. If all of these are left blank, disputes after receipt will merely shift from the banking stage to the contract level; they will not disappear.
Tax records cannot be omitted either. The Singapore IRAS guidance on enterprises accepting or using digital tokens for payment requires treatment under the applicable income tax rules and generally requires transactions to be recorded at their Singapore dollar value. This is merely a jurisdictional example of tax treatment; it does not mean that any token payment is licensed for business, nor that every country adopts the same valuation method.
It is advisable to link client authorization, payee information, invoices, on-chain records, conversion and fiat disbursement evidence into a complete chain of evidence. Products that only provide on-chain delivery should clearly define their endpoint and limitations; products that promise fiat currency arrival should implement local disbursement and contingency plans for failures. Do not, in pursuit of a "fully on-chain" concept, exclude from the product the evidence, refunds or customer service responsibilities that clients actually need.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Multi-currency support may be explored, but it should be reviewed item by item according to "currency and issuer—service function—customer type—target market." Names such as USDT and USDC cannot substitute for legal classification; permission to hold, permission to transfer, and permission to sell to retail customers are also not the same question. Technical integration should follow confirmation of the applicable rules and settlement capabilities.
Displaying balances in a wallet, receiving incoming transfers, safekeeping, permitting purchases, automatic conversion and settlement to merchants involve different activities. Platforms should first clearly state, for each stablecoin, the extent to which it is supported, and then verify local rules. In particular, the fact that an asset can be transferred on a blockchain must not be taken to mean that it can be sold to all customers in all countries, or that it can always be redeemed for fiat currency.
The Hong Kong Government's official response concerning the Stablecoins Ordinance states that the provision of specified stablecoins involves permitted providers and restrictions on customer categories, and that the conditions for offering to retail customers differ from those for offering to professional investors. Accordingly, both the provider's eligibility and the stablecoin to be offered must be verified, rather than merely checking whether the platform itself holds a particular financial licence. The specific issuance and licensing status should be checked against the HKMA register.
Article 48 of the EU's MiCA sets requirements for the public offering and admission to trading of e-money tokens. It should also be noted that ESMA's supervisory opinion published on 8 October 2026 requires competent authorities to push CASPs to cease providing services to EU clients involving stablecoins that do not meet MiCA requirements, including custody and transfer; existing holdings may exit only under strict, time-limited and supervised arrangements. The opinion requires that remaining legacy exposures identified by competent authorities be remediated as soon as possible and no later than three months after publication of the opinion; this is not a uniform grace period for new business. Therefore, the 2025 statement that "mere custody and transfer may still be possible" can no longer be relied upon as a basis for continuing operations. This is a current supervisory opinion and should not be mischaracterised as a newly amended statutory provision.
Suppose a merchant requires final receipt in fiat currency, while the payer wishes to use stablecoins on two different networks. Even if the interface prices are all close to one US dollar, the platform still needs to confirm whether what is received is the issuer's native token or a cross-chain wrapped asset, whether the conversion counterparty will accept it, and how funds are returned if settlement fails. The technical team should not whitelist tokens based solely on ticker symbols; at a minimum, the network and contract identifiers should be confirmed.
Issuer terms, redemption eligibility, freeze arrangements, market liquidity and channel support may also differ. The platform need not assume all issuer risks on the customer's behalf, but it should state whether what it undertakes is to receive the coin, to convert it, or to settle a fixed amount, and should design notification and exit procedures for suspending receipt or delisting.
It is recommended that the first batch include only assets whose legal classification and complete settlement path can be explained, and that the approver, source and review date be retained. Adding a new network, a change of issuer, an adjustment of regulatory restrictions or an upstream cessation of conversion should all trigger a re-review. The external token list should preferably also display applicable regions and functional restrictions, so that users do not discover only after completing a transfer that they can only hold the asset and cannot sell or withdraw it.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
A service that genuinely provides only wallet software, with users independently controlling their assets, may not constitute a custodial or money transmission business in certain jurisdictions. However, "self-hosted" is not a general exemption: recovery permissions, signing on behalf of users, exchange and transfer-on-behalf-of-customer functions all require separate assessment. The actual allocation of control should be mapped out first, before discussing licensing.
When reviewing a wallet, the most valuable materials are usually not the marketing pages but the permission descriptions: who generates the keys, who stores the shards, who can recover the account, who can change the signing rules, and whether users can transfer assets out on their own after the platform ceases operations. MPC, multisignature and smart contract wallets are all technical arrangements, and whether they constitute custody cannot be determined by name alone. In particular, administrative permissions outside day-to-day processes should be examined to avoid a situation where the front end displays "user signature" while the back end can in fact still move assets unilaterally.
The 2019 guidance of the US Financial Crimes Enforcement Network (FinCEN) distinguishes between the actual control models of wallet services, and also distinguishes between developing software and using software to operate money transmission. Its multisignature analysis permits, under specific facts, services that merely provide additional verification and do not accept and transmit value to be treated differently from custodial wallets. This is a determination under the US federal anti-money laundering framework and does not mean that licensing questions in US states or other countries have already been answered.
In the EU, Article 3 of MiCA separately lists services such as custody, exchange, reception and transmission of orders, and transfer of assets on behalf of clients. Therefore, even if a design does not constitute custody, it cannot skip the other service categories. The assessment should proceed by identifying functions item by item, rather than first obtaining a "non-custodial" product label and then excluding all regulation on that basis.
Assume Company A sells offline signing software, users independently generate and store keys, and the company cannot recover, sign on behalf of, or arrange transactions for users; Company B likewise markets itself as self-custodial, but can recover account permissions and, after user authorization, automatically select exchange paths and complete payments. This is not a direct licensing conclusion about the two companies, but an explanation that Company B needs to submit more facts about control and transaction services and cannot simply copy Company A's analysis.
Recovery functions in particular need to be examined separately: helping a user recover access to a login interface is not the same thing as reconstructing permissions capable of disposing of assets. The technical team should be asked to demonstrate the permission boundaries through actual testing, and the test results should be aligned one by one with the contracts, help center and customer service statements.
It is advisable to prepare a review record organized by "current version—target countries—customer-facing," clearly identifying which functions only provide information and which involve asset control or transaction execution. When automatic transfers, third-party deposits and withdrawals, session keys or yield functions are added, the review should be conducted anew rather than relying on the original software conclusion. Security audits can verify code risks but cannot replace business characterization; legal review also cannot replace key security testing.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Possibly. Swap and cross-chain functions are not automatically exempt as inherent ancillary features of self-custodial wallets; it depends on whether the platform quotes prices, accepts orders, selects routes, arranges execution, or transfers assets on behalf of customers. The fact that users retain their private keys establishes only part of the control facts; the names of third-party protocols, smart contracts and interfaces cannot substitute for a business analysis.
A wallet may only display links to third-party tools, or it may automatically compare quotes, receive users' trading intentions, transmit orders to counterparties, or even execute trades with its own funds. The interface may look similar, but to whom the customer purchases what service may be entirely different. Article 3 of the EU's MiCA lists exchange, order execution, reception and transmission of orders, and transfer on behalf of clients as separate service categories; it is not enough to merely verify whether private keys are held.
Cross-chain may include locking assets on the original chain, acquiring assets on another chain, and using liquidity providers for exchange. During review, it should be confirmed whether the platform can select the bridge or route, set the receiving address, control contract upgrades, and decide how assets are returned after a failure. Automatic code execution does not mean there is no operator involvement, nor does it prove that the wallet operator is necessarily subject to regulation; its actual role must still be examined.
The payment regulatory scope of Singapore's MAS expressly includes certain transmission and exchange-facilitation activities that do not hold funds or tokens. In the EU, ESMA Q&A also states that a transfer service meeting the definition will not avoid authorization requirements merely because it is embedded in other business. Therefore, "no custody" or "cross-chain is merely a back-end step" is not sufficient to end the analysis directly.
Assume Wallet A has users actively leave the application, independently choose and contract with a third party; Wallet B provides a final quote on its own exchange page, deducts fees, and promises arrival, and even if it calls an external protocol at the underlying level, B's service still needs to be re-analyzed. A is not necessarily exempt from regulation, and B does not necessarily fall within a particular license merely because it charges fees; this comparison shows that the user relationship, instructions, and commitments are more important than disclaimers on the page.
If the product retains a "best quote" or automatic routing function, it should also explain the scope of comparison, the source of fees, and failure handling. It cannot be assumed that the recommended route is the risk level the user wants, nor can the risks of bridge attacks, expanded slippage, or lack of support on the target chain all be hidden in technical terms.
It is recommended to first map out the entities and asset paths for each route, identify licenses, customer authorization, and fault liability, and then decide whether to integrate. Testing should include timeouts, partial completion, duplicate requests, and refunds, not just successful exchanges. Re-review should also be conducted when adding new protocols or changing default routes, to avoid the initial pure-display model becoming a wallet that substantively provides complete trading services through continuous iteration.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
The parties are generally each responsible for the services they actually provide. The fact that a deposit and withdrawal institution holds a license does not automatically bring the wallet company within the scope of that license; nor should the wallet assume all of its partner's responsibilities as its own. The key is to distinguish independent referrals, agency cooperation and outsourcing of the wallet's own services, and to ensure that the contract, the interface and the flow of funds are consistent.
The fact that a user submits identity information within a wallet does not necessarily mean the wallet is a deposit and withdrawal service provider. It is necessary to examine who accepts the user, provides exchange quotes, signs contracts, collects payment and promises delivery. If these are all carried out by a third party in its own name, the wallet may primarily provide an entry point; if the wallet itself sells a complete service to the user and then delegates the operations to a third party, that is closer to outsourcing of its own business. As for the agency model, it is separately necessary to check whether local law permits it and what registration is required.
The UK FCA's payment guidance indicates that payment institutions providing services through agents are subject to corresponding registration and supervision arrangements, and that e-money distributors are also distinct from payment agents. Article 73 of the EU's MiCA, in turn, provides that a crypto-asset service provider outsourcing operational functions does not thereby exempt itself from its own obligations. The two point to boundaries of responsibility under different regimes, and "third-party licensing" cannot be uniformly understood to mean that any white-label arrangement or referral is lawful.
A scenario in which the user directly accepts the terms of a deposit and withdrawal institution and the wallet merely displays a clearly identified entry point is factually different from one in which the wallet promises the user a fixed exchange rate and fixed arrival, and handles the entire balance itself. The latter model cannot suddenly claim in a dispute that it is merely an advertising platform, and the former should likewise not imply in its marketing that the wallet is a regulated funds provider.
It is not enough to keep a screenshot of a license. It is advisable to verify the contracting entity, scope of services and status in the official register, and to require the counterparty to confirm in writing the countries accepted, customer types, currencies and networks. As for outsourcing layers, it should also be asked clearly whether actual custody, exchange and disbursement are further delegated to other institutions, and what information the wallet can obtain if funds are frozen or the counterparty becomes unreachable.
Who collects customer data, why it is shared, and who responds to inquiries should be arranged separately. Do not hide the authorization and the service provider merely to save the user one click; nor should a broad consent box be used to treat all future uses by the counterparty as already authorized. Specific data rules need to be reviewed according to the user and the place of processing.
It is advisable to set out in the cooperation table who takes the lead, who provides evidence and who explains to the user in respect of account-opening refusal, failure to purchase coins after deduction, refunds, fraud, complaints, investigations and service suspension respectively. Termination of the cooperation should also be rehearsed: whether customers can contact the service provider directly, how records are exported, and how balances are handled. Good integration is not only about successfully converting a user, but also about being able to explain the subsequent path clearly when the product ceases cooperation.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
A U-card is generally not a standalone statutory license, but rather a product combination that connects crypto assets with bank card spending. A project must separately address card issuance and payment accounts, asset custody and exchange, card network access, and market access for customer acquisition. Finding a card issuance interface or a card BIN provider only demonstrates that some technical or partnership capabilities have been integrated.
What the market calls a U card may involve the user first selling stablecoins, with fiat currency entering a prepaid account before being spent; it may also be that conversion is triggered only at the time of spending; and some products use assets as collateral to provide credit. The asset ownership, payment obligations and risks of these three models are not the same. Before review, it should be confirmed whether the user holds stablecoins, a claim against the payment institution for the balance, or a credit line, and they must not all be uniformly referred to as an "on-chain bank card."
The UK FCA classifies the issuance of payment instruments and the execution of card payments as payment services, and has separate rules for the issuance of electronic money. This UK example shows that the card manufacturer, the technical processor and the institution authorized to provide financial services are not the same role. Whether the service is provided specifically by a bank, an electronic money institution or another eligible institution must be determined according to the local product structure.
On the crypto asset side, it is necessary to verify who safekeeps, who converts, and who transfers on behalf of clients. The EU MiCA classifies these as different service categories, so the financial qualification of the card issuer cannot substitute for review of the crypto side, nor can it be assumed that possessing a crypto services qualification allows one to provide bank card accounts on one's own. Qualification for cooperation with card organizations is a separate layer of arrangement.
Assume the user first transfers in stablecoins, and the project immediately converts them into fiat currency and forms a spendable balance. At this point, it should be possible to answer who holds the assets before and after conversion, to whom the user may request return, and whether merchant refunds come back as fiat currency or as repurchased coins. If coins are sold only at the time of spending, it is also necessary to explain the handling of locked quotes, insufficient balance, conversion failure and revocation of authorization.
There may be multiple contracts among the project party, the card issuing institution, the processor, and the custody and conversion institutions. The brand owner should at least obtain confirmation of the scope of services related to its own role, arrangements for fund handling and user exit. It cannot, merely on the basis of an upstream promise that cards "can be issued," assure users of account security, withdrawal at any time, or usability in any country.
It is recommended to first lock in one customer type, limited customer acquisition regions and a clear balance model, form four comparison tables covering entity, license, assets and contracts, and then proceed with technical integration testing. Functions involving credit or returns should be subject to a separate review project. The cost model should also include card processing, foreign exchange, asset conversion, refunds and service-discontinuation migration, rather than calculating only the production cost of each card.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
As a general rule, one cannot directly promise that customers worldwide may apply. The fact that a card can be used in multiple locations is distinct from the project being permitted to open accounts for, provide wallets to, or offer exchange services to local residents. The customer acquisition regions, card issuance qualifications, coverage of crypto features, and scope of use should each be determined separately, and the registration process should correspond strictly to the promotional statements.
A user using an existing card while traveling and a platform actively promoting account opening to residents of a travel destination are different legal facts. Coverage of a consumption network addresses the issue of transaction acceptance; customer eligibility also involves card-issuing product conditions, account services and access to crypto business. Even if merchants in a certain region can accept the card, it cannot be inferred on that basis that all residents of that region can apply.
The customer regions permitted by the card issuer, the markets permitted by the exchange institution and the functions the wallet can provide may not fully overlap. The fact that a fiat currency account can be opened in a certain place does not mean that all stablecoins can be purchased there; the fact that a wallet can be used in a certain place does not necessarily mean that the corresponding bank card can be applied for. The intersection should be taken based on the complete product, or regional versions should be clearly separated, to avoid users being told only after topping up that they cannot open a card or withdraw funds.
The UK FCA's guidance on payments and electronic money indicates that operating relevant services in the UK requires the corresponding qualifications or the application of an exemption; the EU's MiCA sets separate boundaries for third-country institutions providing services to EU customers. A license from a certain overseas place cannot automatically cover these markets merely by its name; local rules and the actual cooperation arrangements should be checked one by one.
Article 61 of MiCA sets out specific arrangements for third-country services wholly initiated by customers on their own initiative, but at the same time makes clear that when an institution actively solicits EU customers, it cannot recharacterize the service as customer-initiated through contracts or disclaimers. If a U-card project bundles crypto services, the marketing methods should also be included in the review, rather than merely adding a line in the terms stating "users apply voluntarily".
Assuming a project allows residents of a certain country to apply and allows them to travel to multiple countries for consumption, the website may truthfully distinguish these two scopes; if the advertisement instead states that "residents worldwide may open accounts", while the regions where applicants are actually rejected keep changing, this will create risks of misleading and customer disputes. This comparison does not mean that a customer can obtain eligibility by providing an overseas address; the facts of actual eligibility should still be verified.
It is recommended that, for each new market, written confirmation from the card-issuing and crypto partners be obtained first, and then local access, marketing, customer terms and identity verification configurations be completed. For existing customers changing their place of residence or partners narrowing their scope, review, notification and exit plans should also be pre-established. Regional restrictions should not be written only at the end of lengthy terms; users should be able to see them before applying.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
The fact that a project issues cards or holds a license overseas does not justify directly promoting U cards that include functions such as buying and exchanging coins to residents of mainland China. Crypto services, customer acquisition and fund arrangements should be reviewed under the currently applicable mainland rules; the ordinary use of an overseas bank card and the operation of crypto services directed at entities in mainland China must be assessed separately.
"U card" is not a unified product name under mainland law. If a product requires users to deposit stablecoins and then convert them into fiat currency for spending, the analysis cannot stop at which overseas bank issues the card; it must also examine who provides users with deposit, conversion, asset custody and settlement. The fact that a service is lawful overseas does not mean it may be offered to mainland entities, nor does it mean a mainland team may promote it on that basis.
The notice issued on February 6, 2026 as Yin Fa [2026] No. 42 expressly repeals Yin Fa [2021] No. 237 at the same time. The new notice continues to prohibit relevant virtual currency business within the mainland and makes clear that overseas entities and individuals may not, in any form, unlawfully provide virtual currency-related services to mainland entities. For U card schemes involving relevant activities, the new notice should be applied in light of the actual service content; an admission conclusion cannot be reached solely on the basis of an overseas company or an overseas card number.
The new notice also addresses internet commercial display, marketing and promotion, paid traffic diversion, and liability for continuing to assist where one knows or should know that an overseas entity is unlawfully providing relevant services within the mainland. Accordingly, short-video promotion, community distribution, referral commissions and mainland customer service assisting with account opening should all be brought within review, rather than merely checking where the website server is located.
Suppose a client who meets the conditions of an overseas product and has long lived overseas uses an existing bank card while traveling. That is a different scenario from a project specifically promoting to mainland residents that "topping up USDT enables card spending." The latter involves active customer acquisition and a complete crypto service, and the former common cross-border card spending scenario cannot be used as a lawful basis for it.
Likewise, merely discussing the application for or use of an overseas fiat currency bank card cannot, without analysis, be equated with operating a crypto business. Actual residence, service recipients, transaction paths and marketing content need to be verified; nationality, an overseas mobile number or a single mailing address cannot alone determine the entire conclusion. This article also does not on that basis conclude that all mainland residents' use of overseas cards is unlawful.
It is advisable first to organize the product functions, mainland-affiliated personnel and all customer acquisition channels, and to identify whether there are restricted services and fund arrangements directed at mainland entities. Before permission is confirmed, advertisements should not be placed or agents recruited first in reliance on regional disclaimers in the terms as a remedy. For projects that genuinely serve only compliant overseas markets, customer conditions, registration review, counterparty approval and promotion channels should be consistent with one another; where traffic that does not meet the conditions is identified, there should be refusal and review mechanisms, rather than guiding customers to package their information.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Possibly, but the license required is not necessarily the same as that of the card issuer. Merely handling branding or introducing customers differs in legal role from providing payment services as an agent, controlling balances oneself, or promising that redemption will be credited. A partner's license does not automatically authorize the brand owner; the conditions applicable to agency, distribution and promotion in the target market should also be reviewed.
When assessing this, one can work backwards from the user experience: who opens the user's account, who displays the available balance, who decides to freeze or close the account, who sets the exchange quote, and whom the user believes should repay the money if a problem arises. If the brand actually controls these key steps, merely stating at the end of a contract that "we do not issue cards" is usually insufficient to explain the full service. Conversely, a genuine introduction that involves only clear disclosure should not automatically be treated as a card issuer.
The UK FCA's guidance on payment services and e-money distinguishes payment agents from e-money distributors: providing payment services through an agent involves a registration arrangement, a distributor cannot provide payment services on that basis, and e-money issuance itself cannot be carried out by an agent or distributor in place of the issuing institution. This is a specific classification under the UK regime, and "agent" should not be used as a universal label implying no market access requirements anywhere in the world.
Therefore, after signing a channel cooperation agreement with an upstream party, it is also necessary to confirm whether the agreed role exists in the relevant jurisdiction, what it can do, whether registration is required, and whether the counterparty has completed the corresponding formalities. Calling a role an agent in a commercial contract does not mean regulatory registration has been completed; and receiving only referral commissions does not necessarily exclude regulatory issues relating to the actual functions performed.
Assume Brand A merely introduces a card to eligible customers, the customers contract directly with the card issuer and the crypto institution, and Brand A does not handle balances; Brand B, by contrast, accepts top-ups, displays its own account balances, and undertakes to convert stablecoins for spending. Even if both cards bear the brand name, the business that Brand B needs to analyze is clearly greater, and Brand A's introduction model cannot simply be applied to it.
Customer acquisition itself must also be lawful. For EU promotions bundled with crypto services, Article 61 of MiCA makes clear that active solicitation cannot be turned into fully unsolicited customer action by means of a disclaimer. In other markets, including mainland China, local restrictions should be checked separately, and an overseas agent status cannot replace local marketing review.
It is advisable for the contract to specify clearly who holds the customer relationship, who safekeeps funds and records, who handles complaints, and who will notify customers, refund or migrate balances after the cooperation ends. Customers should know the actual financial service provider before opening an account, rather than seeing the upstream name for the first time only after problems arise with their funds. Internally, the marketing team should also be restricted from making unverified promises on its own, such as principal protection, global availability, or unconditional instant withdrawal.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Balance yield cannot be treated as an ordinary ancillary feature of a payment account. First, it is necessary to check whether there is a direct prohibition, and then to determine whether a lending, investment or other financial product is formed. For example, the EU MiCA imposes explicit restrictions on interest on relevant stablecoins; a customer's voluntary participation or renaming interest as a reward does not necessarily resolve the issue.
Articles 40 and 50 of the EU MiCA respectively impose restrictions on interest for asset-referenced tokens and e-money tokens, covering issuers and service providers offering crypto-asset services related thereto, and bring certain remuneration or benefits related to holding periods into the analysis. Accordingly, designs such as "awarding points based on the number of days a balance is held" and "third-party funding of payouts" cannot be deemed to avoid the restrictions merely by changing the name or the paying entity.
This does not mean that all rewards worldwide are prohibited by the same rule; rather, the jurisdiction, asset type and method of calculating benefits must first be confirmed. The structures of consumption cashback, one-off promotional rewards and ongoing holding yield may differ, but it is also not possible to promise, without review, that a particular rebranding scheme will necessarily be compliant.
If the yield comes from lending, funds, staking or other investments, users no longer face only payment execution risk. It is necessary to confirm whether the assets are transferred, whether users become creditors, who manages the investment, how long exit takes, and whether the relevant product can be sold to the target customers. Article 2 of the EU MiCA sets out scope exclusions for financial instruments and the like, which also shows that a product leaving MiCA does not mean it leaves other financial regulation.
The investor alert issued by the staff of the U.S. SEC specifically explains that crypto-asset interest-bearing accounts differ from bank deposits, and that investment and lending activities may bring risks such as liquidity and institutional failure. That alert is not a new legal rule, but it is suitable for reminding product teams: investment risk must not be packaged as being as safe and available at any time as a payment balance.
Assume that a U-card account by default uses idle stablecoins for an investment that cannot be redeemed immediately, and the user needs to spend the next day. If the project advances funds from its own capital, it bears liquidity pressure; if it directly refuses payment, the original promise of spending at any time may fail; if it uses other customers' funds to fill the gap, more serious problems are introduced. This scenario shows that, for a yield feature, a funds and liability analysis must be done first, and historical returns must not be the only thing looked at.
Having users actively opt in, separating investments from payment balances, and clearly disclosing risks are designs worth assessing, but they do not automatically eliminate interest prohibitions, issuance and sales requirements, or investment management requirements. Before launch, product characterization, licensing, customer suitability, asset protection and redemption plans should be independently formed, and exit capability under extreme market conditions should be verified. Where compliance has not yet been confirmed, ordinary payment functions should be retained, and yield should not be made an essential promise for customer acquisition.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
It may, but a distinction should be drawn between protecting ordinary commercial privacy and obstructing lawful verification. Reducing the public display of amounts or transaction relationships is not inherently unlawful; however, if a product prevents regulated institutions from identifying customers, understanding the source of funds, or fulfilling necessary record-keeping obligations, it will affect market access and bank cooperation, and some markets impose explicit restrictions.
A company may wish to keep supplier lists, order amounts or wallet associations from public view, and this is a legitimate commercial need. Product review should specify which information is not visible to the public, which information remains held by customers or appropriate institutions, and whether it can be verified upon a lawful request. Privacy protection need not be equivalent to complete anonymity; likewise, a claim of being "traceable" cannot replace the information actually available and the lawful access mechanisms.
Article 76 of the EU's MiCA sets conditions for trading platforms admitting assets with built-in anonymity features, concerning whether holders and transaction histories can be identified. This provision targets the trading platform scenarios it specifies and cannot be directly expanded into a prohibition on all self-hosted wallets, all encrypted communications or all privacy technologies.
The FATF virtual asset risk indicators list anonymity-enhancing technologies, mixing services and the like as risk factors. A risk factor means that analysis in light of the business and transactions is required; it does not mean that "the presence of a privacy feature proves a crime." Whether something is specifically permitted, what verification must be adopted and whether reporting is required should each be referred back to the applicable local regime, rather than looking only at the label of a particular on-chain analytics company.
Suppose Product A merely does not show the purpose of corporate payments to the public, but service institutions can still lawfully obtain information on customers, orders and sources of funds; Product B, by contrast, promises that institutions can never know who the customer is and cannot explain the fund path. The impact of the two on bank due diligence is clearly different. Product A is not necessarily accepted by banks either, but it can demonstrate an auditable business arrangement; Product B must first confront the problem that it may itself be unable to perform its obligations.
When seeking banks or channels, it is advisable to provide design explanations that can be verified, including data retention, customer identification, anomaly investigation and access approval. Do not merely present a technical paper or the phrase "zero-knowledge compliance"; demonstrate what actual personnel can obtain when compliance requires it, how quickly they can obtain it, and who approves it.
Compliance access should likewise have permission boundaries; the need to investigate does not justify opening all customer transaction information to all partners. Purposes, scope and security measures should be controlled in accordance with applicable data protection rules, and three scenarios should be tested: normal services, suspicious transactions and lawful investigations. In publicity, neither promise absolute anonymity or untraceability, nor claim identity-identification or asset-freezing capabilities that do not actually exist.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
This must be assessed based on the actual business, rather than automatically requiring or exempting a license simply because the product is called an AI agent. Generating payment recommendations, initiating payments, transferring tokens on behalf of clients and safekeeping funds are distinct roles; even without holding funds, the product may involve regulated services such as payment initiation. The scope of authorization, error handling and human intervention should also be clearly designed.
The first type of product only consolidates bills and recommends payments, with the user separately entering a bank or payment institution to operate independently; the second type accepts user requests and initiates payments through an interface; the third type manages balances or keys and automatically completes exchanges and payments. The three cannot share a single conclusion of a "purely technical assistant." Whether a license is required should also be analyzed in light of the operator, the location of customers, and the manner in which the service is provided.
The UK FCA's payment regulatory guidance makes clear that payment initiation services do not fall within the general exclusion for technical services; its consumer guidance also emphasizes that the relevant services require the user's explicit consent. Therefore, the fact that "the money always stays in the bank" or that "the bank ultimately executes the payment" cannot be treated as a sufficient reason for an AI application to be outside payment regulation. On the other hand, where the AI merely generates recommendations without actually providing the relevant services, it also cannot be presumed to require a license merely because a model is used.
The FCA's current AI guidance emphasizes the use of the existing financial regulatory framework rather than establishing a separate set of dedicated AI rules. Accordingly, this article does not assume the existence of a general "AI payment license." If the AI further exchanges or transfers crypto assets on the customer's behalf, this must also be assessed according to the corresponding service; the EU MiCA classification of transfers on behalf of clients is one example.
Assume a user requests monthly procurement of office supplies not exceeding an agreed amount, and the AI selects a more expensive product because the merchant's page was misleading, or makes a duplicate payment due to a timeout and retry. It is necessary to distinguish the user's original authorization, the model's selection, the platform's failure of risk management, and payment execution errors, and it cannot simply be written into the terms that "all AI decisions are borne by the user." Specific refunds and compensation are still determined under applicable law and contract.
The product should convert the payee, amount, time, frequency, and purchasable scope into machine-verifiable limits, and require reconfirmation when limits are exceeded. Web pages, emails, and order content that the model can read should not have the authority to expand payment permissions on their own. After authorization is withdrawn, it must also be verified that subsequent tasks have actually stopped, rather than merely deleting a single instruction from the chat interface.
It is recommended to retain the necessary versions of user authorization, order elements, model outputs, rule validations, payment requests, and final results, and to control the scope of retention in accordance with data protection requirements. Establish duplicate-charge protection, limits on retries after failure, emergency stop, and a human complaint channel. The FCA's latest guidance on AI practices emphasizes governance, monitoring, and effective human oversight; these management approaches cannot replace payment licensing, but they can help projects avoid a state in which "payments can be made automatically but no one can explain or stop them."
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
The most basic work is not collecting an identity card, but knowing who the customer is, why the transaction occurred, and continuously identifying and handling anomalies. The specific obligations are determined by the law applicable to the place of operation and the business; customer due diligence, identification of beneficial owners, transaction monitoring, recordkeeping and reporting, and personnel governance generally need to form an operational system.
The FATF Recommendations provide international standards, but each jurisdiction must implement them through local regimes; the Recommendations cannot be treated directly as a single list of statutory obligations common to all platforms. For example, the UK FCA applies anti-money laundering registration supervision to money changers and custodial wallet service providers operating in the UK and falling within the relevant scope; registration is not a full financial business license, still less a security endorsement. Where the same company also engages in fiat payment, the payment business rules must be examined separately.
One should first identify the customer, the persons operating on the customer's behalf, and the beneficial owners behind the enterprise, and then understand the product's use, expected amounts, payees and source of funds. Further verification should be conducted when risk is triggered or local rules require it; the same set of materials should not be mechanically requested for every transaction. On-chain address analysis can provide only part of the evidence and needs to be corroborated against bank credits, orders and customer explanations; the requirement to accompany transfers with transfer information where legally applicable also cannot be replaced by a transaction hash.
A distinction should also be drawn among three categories of subjects: customer accounts, counterparties and cooperating service providers. A customer passing due diligence does not mean that each of its payees or upstream parties has been understood; cooperating with another platform does not mean that the other party's conclusions can be directly adopted. In practice, the purpose of verification, acceptable information and review timing can be recorded separately for different subjects, and transaction monitoring can then be linked to these records. In this way, when an alert arises, the handling personnel can know whether what is missing is identity, authorization or a commercial explanation, without having to ask the entire set of questions again.
Assume a trading company that has completed real-name verification normally pays a fixed supplier monthly, and suddenly requests that a large amount of stablecoins be transferred in a dispersed manner to unfamiliar personal wallets. Genuine identity documents cannot explain such a change. The commercial background, payee relationships and authorization of the new transactions may first be checked, and then the matter escalated in accordance with internal procedures; whether to suspend, whether to report, and how much can be explained to the customer should be determined by applicable law and the specific risk, and an anomaly cannot simply be equated with a crime.
The UK FCA's application guidance examines risk assessment, how policies are translated into day-to-day operations, and arrangements for responsible persons and outsourcing. A more useful approach for startup teams is to designate, for each type of alert, the handler, escalation conditions and evidence requirements, retain the reasons for judgments, and keep records, submit necessary reports and conduct training in accordance with local rules. Before launch, test with real business patterns: whether transactions can be blocked when materials are missing, who can decide in emergencies, and who takes over after a tool failure. A small headcount may justify narrowing the product scope, but reducing costs by leaving alerts unhandled is not advisable.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Serving only enterprises does not mean low risk, nor does it automatically lower anti-money laundering requirements. Clear business and payment materials facilitate review, but multi-tiered equity structures, agency transactions, shell companies and complex supply chains may increase difficulty. Effective corporate due diligence requires connecting the legal entity, the actual control relationships and the genuine purpose of the transaction.
The fact that a company exists does not mean that its account is used by authorized persons, nor does it mean that the equity materials have revealed the ultimate beneficial owners. Taking Canada's FINTRAC rules as an example, beneficial ownership should in principle be traced through to natural persons, with an understanding of ownership, control and organizational structure; one cannot stop after finding an offshore holding company. Proportional thresholds, the treatment of trusts and exceptions differ across countries, so it is inadvisable to copy one set of forms directly to all clients.
For trading companies, contracts, invoices and logistics can help explain transactions; for software companies, subscription revenue, customer distribution and service delivery records may be more relevant. Review materials should match the business rather than requiring all enterprises to provide the same kind of proof. In particular, it is necessary to distinguish whether the client is paying its own bills or collecting and transferring funds on behalf of others; the latter may change the client's risk and the platform's assessment of its business qualifications.
Entity mismatches are especially likely with group clients: the contracting party is a subsidiary, the payment comes from the parent company, yet the invoice is issued by another affiliate. The existence of relationships among the three does not automatically mean the transaction is not genuine, but the respective roles and authority should be explainable. Clients can be asked to provide intra-group settlement arrangements, and actual orders can be checked on a sample basis, to avoid recording all affiliated companies under the same client. If the client's business shifts to receiving and making payments on behalf of external enterprises, the original risk assessment should also be reviewed promptly.
Assume Company A has verifiable single-layer equity, fixed purchasers and continuous orders; Company B has just been established, its shareholders span multiple layers of entities, and immediately after account opening it requests to make payments on behalf of unrelated third parties. Both are corporate clients and their transaction volumes are similar, but Company B clearly has more control relationships and sources of funds to explain. Even if Company A is rated lower risk, it cannot be permanently exempt from review: after changes in beneficial owners, industry or payees, it should be reassessed.
Canada's ongoing monitoring guidance requires regulated entities to pay attention to whether transactions are consistent with what is known about the client, which provides a clear example for corporate client management. In practice, an equity chart, a list of authorized persons and an expected transaction profile can be established, recording which materials come from official registries and which are merely the client's own statements; when contradictions arise, it should be clear who will verify them. Familiarity with an industry can reduce ineffective inquiries, but familiarity with the client's responsible person cannot replace necessary verification.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Platforms subject to anti-money laundering regulation generally cannot treat anonymous accounts for unidentifiable customers as a standard service. Privacy protection, simplified due diligence and exemption from a particular reporting requirement are not the same thing. Whether verification may be simplified under specific conditions should be determined under local rules, rather than by a platform setting its own "no-real-name allowance".
Merely publishing software is a different activity from exchanging, safekeeping or executing transfers on behalf of customers. Taking the United Kingdom's current anti-money laundering regulation as an example, crypto exchange and custodial wallet businesses that fall within scope are required to register and comply with the relevant requirements; describing oneself as decentralized and charging only technology fees cannot replace an analysis of actual functions. Genuine technology products that do not touch customer business should likewise not be subjected to financial institution rules without first verifying the regulatory boundary.
The EU Regulation on Information accompanying transfers of funds and certain crypto-assets still imposes information requirements on transfers between service providers subject to it and self-hosted addresses. Verification of control over an address above a specified amount is an additional requirement and cannot be read backwards to mean that smaller amounts require no identification of the persons involved in the transaction at all. Rules vary across jurisdictions regarding occasional transactions, ongoing business relationships and suspicious circumstances, and marketing statements that "no information whatsoever is required below a certain amount" particularly require verification.
Assume a product allows users to display an alias to merchants, while necessary identity information is accessible only to authorized compliance personnel. This differs from a platform that does not collect required information at all and cannot respond to lawful investigations. Exposure can be reduced through field minimization, tiered permissions and encrypted storage, without publishing identity documents or residential addresses on-chain; whether third-party verification results may be relied upon depends separately on local rules and the ability to retrieve the information.
Account-opening disclosures should explain what is collected, why it is collected, when additional documents may be required and how long information is retained. For customers who cannot satisfy necessary verification, processes for not establishing a relationship, restricting functions or exiting in accordance with law should be designed in advance, rather than promising unlimited anonymity first and then imposing additional requirements at the time of withdrawal. If a business model only works when customers can never be identified at all, the model should be reassessed first, rather than packaging identity requirements as optional.
Products should also avoid using transaction splitting to maintain an appearance of low thresholds. For the same customer, the same purpose or interrelated activities, which should be assessed together must be configured according to the applicable regime, rather than letting customers choose for themselves whether to be identified. Privacy disclosures can clearly distinguish the three purposes of platform collection, provision to partners and reporting in accordance with law, so that users know information will not be disclosed arbitrarily and that using an alias does not exempt them from necessary verification. Such a commitment is more accurate than a blanket claim of complete anonymity.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Accepting only wallets controlled by the client can reduce some of the risk of account misuse and payment by unidentified third parties, but it cannot prove that the funds in the wallet are lawful. Control of the address, legal ownership of the assets, source of funds and purpose of the transaction are four distinct issues that must be assessed in light of the client's background and the circumstances of the transaction.
A signature challenge or a small-value verification transaction can help determine whether a person can operate an address, but it cannot on its own prove who ultimately owns the assets, still less explain the prior source of funds. A corporate wallet may also be controlled by employees, trustees or multiple persons jointly. Wallet whitelisting therefore needs to be combined with corporate authorization, personnel changes and the purpose of the transaction; it cannot be that once a verification is completed, the wallet is cleared forever.
The EU Transfer of Funds Regulation requires regulated service providers, for relevant transfers to self-hosted addresses exceeding EUR 1,000, to assess whether the address is owned or controlled by the corresponding customer; the EBA guidelines list signature, verification transaction and other optional methods. This is an EU-specific rule, not a globally uniform requirement. Addresses of multisignature, smart contract wallets or custodial platforms may not be verifiable by the same method, and appropriate alternatives and manual review should be available, rather than inducing customers to hand over private keys or seed phrases.
Assume a customer has previously paid only from a verified wallet, and one day that wallet receives a large amount of assets inconsistent with its business, followed by an immediate request to exchange and remit them. The wallet's own rules are still satisfied, but the transaction background has changed. The platform should assess the matter in light of the fund path, the customer's explanation and the order materials; on-chain risk labels may serve as leads, but the customer should not be characterized as unlawful without verification.
Risk analysis should also take into account that a customer may receive unsolicited small-value transfers. A remote association involving only a very small amount should not be indiscriminately equated with directly receiving clearly high-risk funds. As an internal assessment method, the platform may record the association path, the proportion of the amount, the timing and whether the customer can explain it, and where necessary check the source of the label with the tool provider. The platform should not assure customers that all coins are absolutely clean, nor should it treat an automated label lacking context as the sole reason for permanently refusing service.
First decide whether to accept withdrawals from exchanges, payments by group companies and operations by authorized employees, and then list the acceptable evidence for each scenario. Otherwise, a normal customer withdrawing funds from an exchange custodial account may be wrongly rejected because no “personal dedicated on-chain address” can be seen. Sources that cannot be explained should be handled under the risk process with a record retained; for assets received in error, a return path should also be designed within the lawful scope, and they must not be automatically sent back to a suspicious source address without assessment.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
A third party can provide verification capabilities, but the platform still needs someone responsible for managing outsourcing, understanding the results and making compliance decisions. Whether a dedicated position is mandatory, and whether the position can be combined with other roles or outsourced, must be assessed under the local licensing regime and the scale of the business. Purchasing a system cannot replace the responsible person's authority, judgment and ongoing oversight.
Document verification addresses questions of document and identity matching, while on-chain tools flag address associations and risk indicators. Neither necessarily knows the client's contracts, counterparties, and reasonable commercial rationale, nor can either explain conflicting evidence on the platform's behalf. False positives, insufficient data coverage, and delayed updates to address labeling should all have manual handling pathways; a single score cannot simply determine all freezes or reports.
The UK FCA's guidance on crypto business applications requires explaining how third-party tools are used in operational processes, as well as outsourcing and money laundering reporting officer arrangements. This specific example shows that regulators focus on who can turn results into action, not on the number of vendors. Contracts should specify data sources, service quality, incident notification, access to materials, audit, and exit arrangements; which roles must remain local or be assumed by the company itself must be verified against local requirements.
Vendor replacement is also a real cost: if investigation records, evidence attachments, and rule settings cannot be exported, the platform may lose the ability to explain historical decisions after the contract ends. During selection, require a demonstration of the export and reconstruction process using a set of anonymized test data, and verify access permissions, retention arrangements, and fees. For major failures, do not merely agree on compensation amounts; also agree on notification recipients, recovery assistance, and methods for retrieving materials, so that business teams do not discover at service shutdown that they only have a sales contact.
Assume an on-chain service provider flags a payment as high-risk, sales considers the client important, but the technical department has already automatically released the funds. If no one has the authority to suspend and organize a review, buying the tool still provides no effective control. A reasonable arrangement could be: operations collects materials, compliance forms recommendations, authorized personnel make the decision and record the reasons; where a statutory report must be submitted, the responsible person and confidentiality scope are determined separately under law.
Initially, external professionals can supplement experience, but internally it must be clear who supervises their work, who handles urgent matters, and how continuity is maintained after departure or service shutdown. The budget should include, in addition to service fees, investigation time, training, rule tuning, and independent checks. Transactions already approved and rejected can be periodically sampled to test whether anomalies were missed or over-blocking occurred. As the business expands, processing capacity should be increased accordingly, rather than letting alerts queue for long periods.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Anti-money laundering requirements add necessary steps, but they need not require every customer to repeatedly submit the same materials. The key to improving the experience is to align information collection with actual risk, product features and legal requirements. Steps that may lawfully be simplified can be simplified; when anomalies arise, enhanced review that is warranted must not be converted into a step that can be bypassed by paying a fee.
Common friction in corporate account opening stems from unclear requirements: customers are first put through review, and only when the first payment arrives are they asked for control relationships or industry materials that could have been foreseen earlier. Requirements, purposes and acceptable alternative evidence can be explained in advance by customer type, repeated fields can be pre-filled, and checks can be made as to whether different teams within the same group are making duplicate requests. Reducing duplication does not equal cancelling statutory obligations, nor does it mean that old materials remain valid indefinitely.
Material prompts should preferably explain acceptable combinations of documents, rather than listing only a single document name. For example, where a newly established enterprise has no long operating history, which other evidence can be provided to help explain its business requires compliance personnel to determine in accordance with the rules; front-line staff must not make their own promises of alternatives in order to improve pass rates. For valid materials already provided, the system can prompt their reuse; for information that has expired or conflicts with a new transaction, the purpose of the supplement should be explained, so that customers do not misunderstand necessary updates as arbitrary obstruction.
Canada's FINTRAC ongoing monitoring guidance requires monitoring to be arranged according to customer risk, and attention to whether transactions are consistent with known background. A similar operational approach can help in product design: customers with clear business and consistent information go through a smoother process; customers with complex structures, changed payment patterns or specific alerts enter supplementary review. Which circumstances permit simplified due diligence in accordance with law must still be based on local rules, and cannot be decided solely by a customer's fee tier.
Assume a platform provides collection and large-value batch payments for exporters. After necessary verification, features that have been approved and whose risk is controllable are opened first, and batch payment is opened only once the payees and authorization materials required for it are complete; this is usually more explicable than promising full availability first and then temporarily holding up funds. This is a product design suggestion and does not constitute a general exemption permitting transactions before verification required by law is completed.
Observable metrics include the number of supplementary document requests, repeated questions, manual waiting time, the proportion of false positives and unhandled alerts, and a review of whether customers truly understand the restrictions. When providing progress explanations for delays, suspicious reports or investigation information that is confidential under law should not be disclosed. If credible evidence can never be obtained for a certain type of business, it is better to narrow the scope of support than to keep adding questionnaires; a smooth process is built on clear access boundaries.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
It may still be possible, but three situations must be distinguished: what is prohibited by law, what is subject to enhanced regulatory requirements, and what banks are simply unwilling to take on. Enhanced review can manage some high-risk elements, but it cannot make prohibited transactions lawful; obtaining a license also does not guarantee that a bank account can be opened. The first step should be to confirm whether the actual customer market can be accepted by the regulatory regime and by counterparties.
The FATF increased monitoring list, the call for action list, national sanctions lists, and banks' internal country ratings differ in nature and consequences. In its June 2026 increased monitoring statement, the FATF made clear that inclusion on that list does not by itself require enhanced due diligence across the board or the severing of an entire category of customers. This does not prevent a jurisdiction from imposing stricter requirements under local law, nor does it preclude a bank from declining business based on its own capabilities. Lists and sanctions measures change, so today's lists should not be written into long-term product rules.
The application materials should describe the customers' actual place of business, the source and destination of funds, the industry, the beneficiaries and the expected transactions. It is not acceptable to state only the company's place of incorporation in order to obscure its main markets. The UK FCA's requirement that applicants describe their target customers and risk management is a specific regulatory example. A bank may additionally require evidence that transactions are explainable, that evidence can be obtained, and that restricted payments can be identified; this is a bank cooperation assessment and does not mean the regulator has issued an additional “proof of legality”.
Account-opening inquiries must also be specific to the use case. A bank's statement that it accepts customers from a certain country may cover only specific industries, currencies, counterparties or amount arrangements, and does not mean it accepts all crypto-related funds from that country. Representative sample fund flows may be submitted, with a request to confirm which elements are supported and which are not. If the bank's preliminary response, the formal contract and the actual system permissions are inconsistent, this should be clarified before onboarding; the fact that a customer has already deposited funds must not be used to force the counterparty to accept risks that were not previously disclosed.
Assume a certain region is rated high risk by a bank. A food importer with verifiable orders applying to make a payment, and a prohibited transaction involving a sanctioned entity, cannot be handled solely with the same enhanced due diligence form. The former may be accepted after further investigation, or may still fall outside the bank's policy; the latter, if it falls within applicable prohibitions, should be stopped in accordance with law or assessed for a licence, rather than substituting more information for legal authorisation.
The main markets and transaction structures can be anonymised and summarised, then checked against acceptable boundaries with local lawyers and candidate banks before a formal application is made. For business that is permitted, the cost of manual investigation, backup channels and the ability to exit customers should be calculated. Any counterparty's preliminary indication of interest should not be described as a guarantee of account opening; if the core customer base is excluded by all available channels, the business plan needs to be adjusted rather than dealt with after the licence is obtained.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Attention is required, but it cannot be said that all offshore companies are directly subject to the same set of U.S. sanctions. A separate analysis should be made of U.S. persons or U.S. transaction connections, the impact of specific sanctions on non-U.S. persons, and the contractual policies of banks and stablecoin issuers. At the same time, the law of the place of business should also be checked, so as to avoid treating compliance as established merely because U.S. lists have been screened.
OFAC guidance for the virtual currency industry explains that digital assets do not alter applicable sanctions obligations. U.S. citizens, permanent residents, persons located in the United States, and entities established in the United States generally must comply with the relevant requirements; where a non-U.S. company involves U.S. persons, processing by U.S. banks, or other U.S. jurisdictional connections, a case-specific assessment is also required. The sanctions applicability of a payment cannot be fully answered on the basis of the currency name or the company's place of incorporation alone.
Certain sanctions authorizations may impose measures on specific conduct by non-U.S. persons, but the applicable conditions vary by sanctions program, and it cannot be said that all dealings with a sanctioned person automatically trigger the same consequences. On the other hand, foreign banks or stablecoin issuers may adopt policies in contracts that are stricter than the company's own legal obligations. The fact that something is not directly prohibited by law does not mean that the channel will necessarily process it, nor that the issuer cannot freeze assets under applicable rules.
Assume a foreign payment company promises to settle U.S. dollars to merchants, and the transaction must pass through a U.S. correspondent bank. Even if neither the customer nor the platform is in the United States, it is still necessary to examine whether the bank's processing is prohibited, whether a license exists, and whether the platform would cause the relevant U.S. persons to violate the law. Switching to on-chain payment does not automatically solve the problem: the stablecoin issuer, service providers, and the actual payee may still create other applicable connections.
Screening needs to focus on the identity of the subject, the relevant ownership and control relationships, and the applicable program, not merely on whether an address appears on a list. For teams with a Chinese background, it should also be assessed whether countermeasure, blocking, and similar rules in China and other places of operation create conflicts, and all extraterritorial restrictions should not be directly implemented without analysis. When a hit occurs, evidence should be retained and referred to personnel with capabilities in the relevant jurisdictions for determination; it is inadvisable to attempt to clear the payment by changing addresses, splitting transactions, or concealing payment information.
The trigger points for sanctions screening should also not be limited to account opening only. During the payment period, the subject lists, ownership, and scope of services may change, and the platform may incorporate key changes into re-review and retain the screening time and the version of the list used. For same-name hits, reliable identity information is needed to distinguish them; for related entities that are not directly hit on a list, it should also be verified whether the relevant regime contains ownership or control rules. Both internal automatic clearance and automatic blocking should leave a path for explaining and correcting errors.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Potentially yes. Where an overseas service provider receives identity documents, remotely accesses a customer database, or a bank obtains payer contact details, all of this should be included in the data-flow analysis. Corporate customer data may also contain personal information of natural persons; a customer's click-to-consent does not by itself complete all cross-border transfer compliance, and the use of encrypted storage does not by itself turn the data into anonymized data.
Do not look only at where the servers are located. Registration pages, identity verification SDKs, customer service backends, cloud backups and remote access by overseas teams may all form cross-border processing chains. You should record the data source location, recipients, access locations, purposes and retention periods, and distinguish between situations where the platform determines the purpose and situations of entrusted processing; the same vendor may also assume different roles for different purposes.
The 2024 regulations of the Cyberspace Administration of China and the accompanying press conference adjusted the applicable conditions for assessments, standard contracts and certification. For example, where necessary for concluding or performing a contract to which an individual is a party, cross-border payment information may qualify for a specific mechanism exemption, but not all corporate account-opening materials can be fitted into that exception. Whether sensitive personal information or important data is involved, and whether the entity is a critical information infrastructure operator, will affect the analysis; exemption from a particular mechanism does not mean exemption from other obligations such as necessity, notification and security protection.
Assume the platform serves an overseas trading company, and the uploaded documents include a director's passport, a mainland finance employee's mobile number and account information. The fact that the contractual client is a legal person does not mean the entire package of materials is outside the scope of personal information rules; nor does the fact that the documents have been desensitized mean they are completely anonymous. Under Articles 4 and 73 of the Personal Information Protection Law, de-identified data that can be used, with additional information, to re-identify an individual may still constitute personal information.
In practice, unnecessary fields requested by banks or vendors can first be deleted, and then the purposes of use, sub-entrustment, access permissions, incident notification, deletion and return should be agreed. Information that anti-money laundering requirements require to be retained may conflict with a client's deletion request; the lawful retention scope should be determined rather than promising deletion of everything at any time. If other markets are involved, local privacy and international transfer requirements should be verified separately; data compliance also cannot provide legitimacy for crypto payment business that may not be carried out in the first place.
When selecting an identity service provider, you can also ask whether it will use customer identity documents for independent model training, product improvement or other commercial purposes, as these uses may not fall within the original entrusted verification scope. Writing the contract as processing solely for the platform while allowing the vendor to retain and reuse data on its own will cause the arrangement to be inconsistent with the facts. The actual uses should be assessed by privacy professionals; fields that need not be transmitted should not be transmitted; secondary uses that cannot be shown to be necessary should not be enabled by default; and configurations and vendor responses should be retained.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Possibly, but the platform should first verify whether it qualifies as a local reporting crypto-asset service provider and identify the specific reporting period. The Crypto-Asset Reporting Framework (CARF) is an international framework that must be implemented through local rules; information collection, reporting to the domestic tax authority, and exchange between tax authorities are distinct steps, and it cannot be said that global platforms all report uniformly on the same day.
UK HMRC guidance brings certain operators that transact for customers or provide a means of transacting within the scope of reporting crypto asset service providers, and the specific UK nexus and asset classes must still be assessed. A platform's self-description as a payment instrument or technical interface, or its lack of an exchange licence, is not sufficient to exclude tax reporting obligations; conversely, pure software cannot be swept in merely because it involves a wallet. Each item should be checked against actual functions, transaction methods and local definitions.
As of 29 October 2026, the UK rules require relevant data collection from 1 January 2026, and the first report covering 2026 must be submitted to HMRC by 31 May 2027. New Zealand's official guidance sets the first reporting period as 1 April 2026 to 31 March 2027, with the first reporting deadline on 30 June 2027. These two examples show that even where CARF is adopted, business systems cannot be configured with a single globally uniform reporting cycle. Exchange arrangements between tax authorities must also be verified separately.
Assume the platform has collected a customer's passport and registered address, but has no tax residence, tax identification number or appropriate self-certification. Completion of identity due diligence does not equal satisfaction of tax reporting. Corporate customers may also require identification of relevant controlling persons under local rules. The reasonableness of information and changes to it should be checked, and nationality, mobile phone country codes or company registration place must not be treated directly as the entirety of tax residence.
Whether information is exchanged with a particular region depends on the implementing rules, effective exchange relationships, customer identity and the scope of reporting. It cannot be broadly claimed that all on-chain transactions will be automatically transmitted to mainland China in real time, nor can it be guaranteed that they will not become known. Platforms should explain the statutory purpose of reporting and retain correction and objection-handling mechanisms. The reporting obligation and whether a customer actually owes tax are two separate matters, and a platform's submission of data does not itself replace the customer's tax analysis.
Finance, compliance and engineering teams should reconcile the same sample set of transactions, covering executions, cancellations, refunds, internal transfers and cross-wallet transfers. How items are specifically classified should follow local reporting specifications, but the system must first be able to retain original records and the correction chain, avoiding treating every wallet movement as a new customer transaction or deleting cancelled transactions entirely. Reconciling reporting results with financial accounts and customer details makes it easier to identify problems than hastily extracting data from the chain at the reporting deadline.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Liability may still arise. Third-party custody resolves the question of who actually holds the assets; whether the platform bears obligations such as settlement, selection and supervision of counterparties depends on the applicable law and the contract. A bank's or custodian's brand is not proof of the platform's exemption from liability, and deposit insurance cannot be directly equated with the safety of all client balances on the platform.
A client opening an account in its own name and contracting directly with a bank is a different arrangement from a platform pooling client funds in its own name and then recording them internally. Under a custody agreement, the platform may be the only contracting party, and the merchant may not be able to demand payment directly from the custodian. The contractual relationship, account name, beneficial ownership and operational authority should be examined together, rather than judging solely on the basis of a screenshot showing that "funds are at a certain bank".
It is also possible to require the counterparty to explain its subcontracting or re-custody chain. The fact that the platform contracts with one institution does not mean the assets always remain in accounts directly controlled by that institution; the counterparty may use other banks or custodians. It should be understood who in the chain maintains client details, who can suspend withdrawals, and how notification is made when an event occurs at different levels. A transparent hierarchy chart helps identify concentration risk, but it does not replace legal review of the validity of contracts at each level and the attribution of assets.
Article 73 of the EU's MiCA expressly provides that a crypto-asset service provider subject to it that outsources operational functions does not change its own obligations to clients and needs to retain supervisory capacity. This is an express rule in a specific jurisdiction; other regions must check their own requirements. Civil compensation also requires assessment of undertakings, fault, loss and causation: a counterparty's breach of contract does not necessarily mean the platform bears all losses, nor does it mean the platform can refuse responsibility across the board.
Assume the bank where client funds are deposited has not failed, but the platform's internal records are missing and the funds have been misappropriated, so clients cannot withdraw. The US FDIC explains that its insurance covers deposit risk at insured banks and does not cover crypto assets or the failure of non-bank platforms themselves. Even where insurable deposits are involved, specific conditions such as account and beneficiary records must be verified; bank participation in insurance must not be described as a comprehensive guarantee by the platform.
Before signing, the custodian's qualifications, account purpose, reconciliation capability, whether set-off or lien arrangements exist, and who can obtain client details and issue return instructions after the platform ceases operations should be verified. The platform should maintain independent records sufficient to prove each client's rights and test the operational path for changing institutions. Marketing may explain what protections have been adopted, but it should not promise that "third-party custody means zero risk", nor should it push all recovery work back onto clients.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Not necessarily, but the platform cannot rely solely on a one-line disclaimer citing "market risk" or "issuer freeze." First determine whether the merchant was entitled to receive a fixed amount of fiat currency, a specified quantity of stablecoins, or the actual proceeds after conversion; then examine when risk transferred, the reason for the freeze, and whether the platform performed its duties. Different commitments may correspond to entirely different approaches to allocating losses.
If the merchant contract provides for USD 10,000 to be credited, and the platform's use of stablecoins is merely an internal settlement mechanism, then de-pegging is primarily a question of the platform's cost of performance; the obligation cannot, without basis, be converted into delivery of a depreciated token. If the merchant elects to receive a specified quantity of a particular stablecoin, and the risk allocation is effective, the analysis of price fluctuation may differ. Ultimately, the governing law, mandatory rules and the complete terms must still be reviewed; this comparison should not be understood as meaning that compensation will necessarily be awarded or necessarily denied in any particular jurisdiction.
A freeze may arise from an order of a competent authority, restrictions imposed by the issuer under its terms, or a platform operational error or screening error. Circle's current terms for non-EEA holders list address restrictions and freeze scenarios, which shows that technical ability to transfer does not mean the assets are available at all times; however, the issuer's contract cannot directly determine liability between the platform and the merchant. Lawful injunctions, commercial refusals and the platform's own errors should each be documented and analysed separately.
Assume the payer has paid stablecoins and the price falls before conversion. Platform A has locked in the fiat amount to be credited to the merchant; Platform B has expressly undertaken to convert at the price at which a sale can then be executed. Although both receive the same asset, their performance objectives are not the same. Even if B does not guarantee the price, it should still be examined whether it executed promptly and followed the agreed route; if losses were increased by delay without reasonable grounds, the entire difference cannot be explained by market fluctuation alone.
It is possible to specify the quotation validity period, the price-lock point, the completion marker for settlement, the handling of exceptional events and the customer's options, and to align these item by item with upstream redemption and freeze terms. Where a jurisdiction such as English law is adopted, the effectiveness of exclusions must still take into account applicable reasonableness or other mandatory rules. Internally, the firm should also assess coin concentration, settlement timing gaps and its own liquidity, and must not misappropriate other customers' protected funds in order to maintain commitments.
The pricing team should also distinguish price risk from liquidity risk. An asset's market price may be close to par yet it may temporarily be impossible to redeem or transfer, which may likewise prevent the platform from settling on time; conversely, if the asset can be sold promptly but at a price differential, it is necessary to determine who bears the difference. Different contingency plans can be tested on this basis, including suspending new quotations, shortening the validity period or allowing customers to choose among legally available settlement options. Any plan should be specified in advance, and the risk allocation should not be unilaterally rewritten after a loss has occurred.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Suspension is not automatic. Whether an upstream service suspension affects the obligation to settle with customers depends on the legal basis for suspension, contractual commitments and actual impediments. A legal prohibition on payment is a different issue from an operational failure or insufficient liquidity of the channel; an upstream exemption clause does not automatically become an exemption clause of the platform vis-à-vis downstream parties.
If an applicable freezing order or sanctions prohibition applies, it should be handled according to its object, scope and conditions, and performance must not be used to circumvent the restrictions. If it is merely an internal bank review, a system outage at a counterparty, or insufficient funds on a platform, it is still necessary to determine whether other lawful means of performance exist and whether the customer contract permits an extension. An upstream email citing "compliance reasons" alone is insufficient to confirm that the law already prohibits all relevant payments.
In RTI v MUR Shipping, the UK Supreme Court emphasized analyzing obstacles to performance under the contract and considered that a relevant reasonable-efforts clause does not automatically require acceptance of a mode of performance not agreed in the contract. That case is not a crypto payment dispute, nor is it a globally uniform standard, but it points to an important method: the payment currency, alternative performance, notice and reasonable efforts should be agreed in advance. Any third-party failure cannot be directly labeled force majeure, nor, conversely, can it be concluded that every alternative channel must be adopted.
Assume an upstream party restricts only one group of transactions pending review, yet the platform stops all settlements for all merchants. It should be examined whether the restricted transactions can be lawfully distinguished from other funds, whether the scope of the suspension is necessary, and whether customer assets are commingled. If the platform has promised all merchants a fixed settlement date, the upstream party's inability to perform may still leave the platform exposed to its own breach-of-contract risk; recovery against the upstream party and liability to customers should be pursued separately.
First secure the evidence, verify the affected amounts and customers, and then determine whether to suspend new orders, switch to permitted channels, or negotiate an extension under the contract. Alternative handling must not circumvent legal prohibitions, nor should customer funds be moved to fill a corporate shortfall. Explain to customers the confirmed status and the schedule for the next update, without disclosing information required by law to be kept confidential; where the recovery time cannot be determined, the uncertainty should be made clear rather than repeatedly promising that funds will "arrive soon."
Backup channels also need to be verified in advance. If only one backup institution has been engaged but customer, currency or limit configurations have not been completed, it may not be able to take over when an incident occurs. Within the scope of lawful business, small-scale switchover drills can be conducted, recording the ability to receive funds, reconcile accounts and process refunds, and making clear who may activate emergency arrangements. If an alternative channel changes the delivery currency, the receiving entity or customer fees, the contract and customer authorization should be re-examined, rather than treating so-called business continuity as a reason for unlimited changes to transaction terms.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
The assessment should turn on who controls the assets, who issued the transfer instruction, and why the loss occurred. Platform security defects, unauthorized operations, customer entry of an incorrect address, and blockchain failures should not be conflated. The difficulty of reversing on-chain transactions affects recovery methods, but does not automatically eliminate any contractual or statutory liability the platform may bear.
It should be verified who holds the private keys or signing shares, who can change the receiving address, and who has recovery and administrator permissions. Although a product describes itself as self-custodial, if the platform can still replace addresses through its backend or participate in required signatures, its liability analysis cannot rely on the name alone. Conversely, where the customer independently controls the wallet and initiates transfers themselves, the platform cannot be presumed to have custody of the assets merely because the platform interface was used.
Multi-signature and sharding technologies also cannot be assessed for their level of protection based on marketing language alone. It is necessary to examine whether multiple signatories are in fact controlled by the same administrator, whether approval devices are independent, and whether the permissions of departed personnel can be revoked. The distinction between transaction signing and contract authorization should also be identified: a user may not have directly transferred assets out, yet may have authorized a contract that can subsequently access the assets. Explaining these permissions to the business and to customers in plain language is of more practical significance than merely writing "industry-leading security technology is adopted" in a contract.
Article 75 of the EU's MiCA, for custodial service providers subject to it, provides for liability for the loss of client assets or means of access caused by attributable events, and sets out that article's specific value cap and non-attributable circumstances. This is not a rule that "all wallet thefts are fully compensated," nor can it be directly applied to other countries or to all payment disputes. Whether an event is attributable requires investigation of permissions, operations, security controls and the cause of the incident.
Suppose a customer confirmed the correct address, but the platform interface replaced it with another address before broadcasting; this is different from the customer themselves pasting a wrong address and confirming it through a valid confirmation. Interface displays, network selection, address book changes and approval logs should also be examined; liability cannot be determined solely on the basis of on-chain transfer records. If the platform had promised specific verification or manual review but failed to perform it, the fact that the error was initiated by the customer does not automatically exclude the platform's liability.
Original logs, authorization records, device and service provider notifications should be retained, affected pathways should be suspended in accordance with lawful authority, and it should be verified whether any other customers are affected. The conditions for notifying receiving platforms, issuers, law enforcement and regulators may be assessed, but it cannot be guaranteed that they will be able to freeze or return the assets. Disclose known facts and unknown causes externally, and avoid requiring customers to acknowledge before an investigation that they "bear all losses themselves"; subsequent remediation and compensation negotiations should be based on ascertained facts.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Liability is possible, but "having processed payments for a merchant suspected of fraud" does not automatically constitute joint criminal liability. Administrative, civil and criminal liability each have their own conditions, and the company's conduct, knowledge, risk-management measures and the relationship to the harm should be assessed separately. Continuing to assist with collecting or transferring funds after a clear risk has emerged will significantly increase the legal risk that must be explained.
Taking the rules of mainland China as an example, the 2025 Opinions of the Supreme People's Court, the Supreme People's Procuratorate and the Ministry of Public Security require a comprehensive determination of knowledge, the act of assistance and serious circumstances in the crime of assisting information network criminal activities, taking into account the manner and number of instances of assistance, whether regulatory supervision was evaded, the profits obtained and the actor's experience, among other factors. Whether the conduct constitutes an accomplice to fraud, money laundering or another crime also requires satisfaction of the respective elements. No conclusion can be drawn on the basis of a single sum of funds involved in fraud, nor can "we do not know the specific victim" be treated as a self-evident ground for exemption from liability.
Even if the evidence is insufficient to establish a crime, a company may still be subject to regulatory action for failing to perform applicable anti-money-laundering, merchant management or customer protection obligations; whether it bears civil liability to victims depends separately on the governing law and causation. Whether the business itself is lawful must also be determined first. The restrictions in the 2026 mainland China notice on virtual currency risks do not disappear merely because the platform has conducted real-name verification or a merchant has submitted a business licence. Offshore establishment and licensing also cannot directly answer the legal character of conduct connected to mainland China.
Suppose a merchant occasionally has delivery disputes; the platform may first verify the order and refund. If multiple unrelated payers provide consistent evidence of fraud and the merchant then asks to transfer the balance immediately to an unfamiliar address, the nature of the risk has changed. The investigation should be escalated promptly and measures with a proper basis should be taken, rather than continuing to process transactions because the fee rate is higher. Conversely, a single unsupported complaint from a competitor should not automatically lead to the permanent confiscation of a merchant's funds.
At onboarding, understand the actual goods, delivery methods, refund rules and payment-collection relationships; during operations, place complaints, chargebacks, abnormal transfers and customer information on the same timeline. When the conditions for reporting or assisting an investigation are met, handle the matter in accordance with law and limit the scope of those with knowledge. After identifying suspicious points, do not destroy chat records, do not retroactively fabricate old review materials and do not privately instruct merchants to circumvent restrictions; whether to suspend, terminate or return funds should be checked concurrently with qualified personnel.
Merchant review should also guard against "shell switching of business". A merchant initially operates ordinary goods, but after onboarding provides its payment link for use on another website, while the entity information seen by the platform may remain unchanged throughout. As a routine monitoring recommendation, spot-check whether the merchant name in payment pages, order descriptions and customer complaints is consistent, and require customers to explain material business changes. Where inconsistencies arise, first preserve the facts and verify them; sales staff should not privately alter the industry classification to maintain the channel's approval rate.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Where required by applicable law, by a valid authority request or under valid contractual authorization, transactions may or must be restricted, but "risk" cannot be treated as a reason to arbitrarily withhold funds. Suspending a particular payment, restricting account functions, terminating services and ultimately disposing of the balance are distinct decisions, each of which should have its own basis, scope and review mechanism.
For law-enforcement freezes, verify the authority's powers, the target and the scope; for sanctions restrictions, verify the applicable regime; for internal platform risk review, state the provisions relied on, the facts and the extent of necessity. Do not describe internal review as a government freeze, and do not take possession of all customer assets on the ground of an ordinary commercial dispute. Whether investigation fees may be charged, arrears offset or security deposits retained must rest on a separate lawful basis and cannot be derived without limit from general risk-control clauses.
Current guidance from the UK NCA explains that procedures such as DAML provide a specific criminal-law defence arrangement, not blanket approval of or an endorsement of the legality of the proposed activity. This suggests that platforms should analyse reporting, suspension of transactions and disposal of assets separately. Whether there is a waiting period, a permission and a prohibition on disclosure differs across jurisdictions, and a single global template under which assets automatically vest in the platform after a certain number of days of freezing cannot be applied universally.
Assume a customer cannot provide the information required for continued service, and the platform terminates the relationship under valid rules. Termination does not mean the balance becomes platform revenue; it is still necessary to verify whether any statutory restrictions exist, who is entitled to receive the funds and what is a safe method of return. Where a suspicious source is involved, returning the funds directly by the original route is not necessarily lawful either; where there is no basis for continuing restrictions, indefinite delay merely because of customer complaints or refusal to accept new terms is inappropriate.
A restriction decision log may be established, recording the facts, scope, approver, review events and conditions for lifting. Without breaching confidentiality requirements, explain to the customer the service status, the supplementary materials that may be provided and the channels for appeal. Apply a consistent process to the same facts and review new evidence promptly. Where standard-form contracts from jurisdictions such as the UK are used, the validity of unilateral restriction and exemption clauses should also be reviewed; it cannot be assumed that every restriction is reasonable merely because the user has ticked a box.
At the system level, "prohibition on new deposits", "prohibition on withdrawals", "suspension of specified transactions only" and "account termination" can be designed as distinct states, so that a single operation does not expand its impact. Each state should specify who may change it, which queries are permitted and how to exit it, and the displayed balance should be distinguished from the actually available amount. If the front end still shows funds as withdrawable at any time while the back end has imposed a long-term restriction, this readily gives rise to new disputes. Synchronising customer notification with actual functionality also helps prevent the mistaken receipt of further funds that could not in any event be processed.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
There is risk, but not all customers will automatically become ordinary creditors. The outcome depends on the local insolvency law, the nature of the customer's rights, and whether fund segregation is genuinely established and consistently implemented. Opening a separate wallet, naming an account "customer segregated account," or stating in the terms that "funds do not belong to the company" cannot by itself prove that bankruptcy remoteness is effective.
If the arrangement is that the platform owes the client a sum of money, the client's claim may be a creditor's right; if the platform holds specific assets in custody for the client and local law recognizes their separate ownership, the handling path may differ. The contract, account and on-chain addresses, internal records and actual use of funds must be mutually consistent. Even if the books show a balance, it is still necessary to verify whether there are sufficient, identifiable corresponding assets that have not been improperly pledged.
For an omnibus account or omnibus wallet model, it should also be verified whether the platform can reconstruct each client's entitlements at any point in time. A sufficient aggregate balance does not mean that entitlements among clients are accurately attributed; where there are pending credits, pending refunds or unsettled fees, discrepancies may be concealed. In practice, client records, on-chain records and bank records can be independently reconciled, with the reasons for discrepancies and the persons handling them recorded. Whether reconciliation is performed by finance or outsourced does not change the operational need for the platform to know whether its records of client entitlements are reliable.
The UK FCA requires applicable payment and e-money institutions to safeguard relevant client funds, and under the rules this may be achieved through segregation or insurance, guarantees and similar methods; this regime should not be directly applied to all crypto assets. Article 75 of the EU's MiCA, by contrast, imposes legal and operational segregation requirements on client crypto assets in respect of applicable custody services. Both regimes must be considered in light of the specific entity and asset type, and it cannot be inferred merely from the word "licensed" that all balances receive the same protection.
Assume the platform places client coins in a dedicated omnibus wallet but lends part of them to an affiliate, while the back office still shows the full balance. Separating the address from the platform's own wallet does not resolve the problems of asset shortfall and client entitlement records. Even if a protective arrangement exists in law, return may be delayed due to reconciliation, disputes or insolvency proceedings; the FCA's user-facing guidance also cautions that safeguarding is not equivalent to deposit protection or a guarantee of immediate full return.
It should be verified whether client assets may be subject to set-off, liens or security in favor of banks, custodians or lenders, and lawyers in the relevant jurisdictions should assess their effectiveness. Prepare client balance, account, authority and contact information that receivers can use, and regularly verify that the books match the assets. Where a shortfall is identified, it must not be concealed through deposits from new clients; it is necessary to escalate promptly, stop expanding the risk, and assess top-up and disposal arrangements in accordance with law.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Liability may be limited in part to the extent permitted by applicable law, but there is no assurance that a clause stating that "all risks are borne by the customer" will be valid. The service obligations must first be clearly defined before discussing which losses may be excluded, how the liability cap is calculated, and which liabilities must be retained. The fact that corporate clients have room to negotiate does not mean that mandatory law and the review of standard-form clauses are inapplicable.
Merely undertaking to transmit orders and undertaking to complete settlement of a fixed amount impose different obligations. If the homepage advertises instant receipt, customer service promises principal protection, yet the contract states that the platform bears no payment liability whatsoever, this will increase interpretive disputes. Limiting liability is not a matter of using contract wording to alter the actual business, and still less may licenses, customer asset protection or security controls that should be in place be turned into matters that users voluntarily waive.
For example, the UK government's guidance on standard-form contracts for businesses states that exemptions for certain losses caused by negligence must satisfy a reasonableness requirement, and courts will consider bargaining power, whether there was actual negotiation and the information available at the time of contracting. Other jurisdictions have different mandatory rules on intentional acts, gross negligence and consumer rights. Therefore, it cannot be directly advertised that "B2B contracts may exclude liability at will," nor is it appropriate to state broadly that the same invalidity rules apply to all gross negligence clauses worldwide.
Assume that the platform charges only a small fee per transaction but controls a very large amount of customer principal, and then sets the cap on all liability at the amount of that fee. A low fee does not automatically prove that the cap is valid; it is still necessary to examine who controls the risk, whether customers have a genuine choice, whether the clause is clear, and whether the specific law permits it. The obligation to return customer principal, compensable losses and the exclusion of indirect losses should also be analyzed separately and cannot be merged into a single "total compensation amount."
Liability can be broken down into scenarios such as unauthorized transactions, security incidents, delayed settlement, incorrect information provided by customers and third-party interruptions, with clear notification, investigation, cooperation and loss-mitigation procedures. For negotiable risks, reasonable caps, exceptions and arrangements matching insurance coverage may be considered; liabilities that cannot be excluded should be expressly retained. Finally, check whether upstream contracts can support downstream commitments, so as to avoid bearing all risks toward customers while having almost no right of recourse against counterparties.
The manner in which the clauses are presented should also be provable. It is advisable to retain the specific version accepted by the customer, the location of notices of important limitations and records of negotiated amendments, so that in the future it is not possible to produce only a webpage that has already been superseded. For existing customers, it should not be assumed that updating the website completes all contract changes; notification, consent and effectiveness arrangements should be checked in accordance with the contract and the governing law. Such evidence does not guarantee that the clauses are valid, but it can help distinguish the two questions of what the parties actually agreed and whether a given provision can ultimately be enforced.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Recourse may be assessed, but whether funds can actually be recovered depends on evidence of liability, enforceable assets and available procedures. Locating an on-chain address, sending a lawyer's letter or obtaining a favorable judgment does not mean the money will automatically come back. Records should be preserved as early as possible, further losses should be stopped, and recovery from the upstream party should be handled separately from obligations owed to customers.
The contracting party, the website brand, the actual receiving account and the person controlling the wallet may not be the same entity. Registration materials, account-opening notices, payment instructions, statements, transaction hashes and debt confirmations should be organized to establish a timeline for each payment. On-chain records can prove the movement of assets, but the correspondence between addresses and legal entities, and whether a payment was a deposit, an exchange payment or an entrusted settlement payment, often still require other evidence.
Evidence should not be limited to a few messages selected because they are favorable to one's own side. Complete conversations, original attachments and the corresponding transaction records are more conducive to explaining the timing of quotations, authorization, performance and breach, and also help lawyers identify defenses the other party may raise. For on-chain analysis reports, a distinction should be drawn between transfer facts that are clearly visible and inferences about address attribution, and the basis for the inferences should be retained. Speculation must not be written as established fact in order to strengthen a claim, otherwise it may undermine the credibility of litigation or give rise to other disputes.
Where there is an arbitration clause, the validity of the clause, the seat of arbitration and the location of the property should be examined; the New York Convention provides a framework for the recognition and enforcement of foreign awards, but procedural issues and grounds for refusing enforcement still exist. For litigation routes, court jurisdiction and cross-border enforcement need to be analyzed. The procedural rules of England and Wales permit applications for interim relief such as freezing orders, but evidentiary and procedural conditions must be met, and a cross-undertaking in damages may be involved. The availability of such tools does not justify promising that a freeze will definitely be obtained or that recovery will definitely be achieved.
Assume that the upstream party refuses to settle and further demands an additional "deposit" before releasing funds. The contract and the basis for the restriction should be verified first, rather than continuing to pay solely on the basis of chat promises. If there are indications of fraud, criminal reporting or reporting to the relevant authorities may be assessed, but reporting does not replace the exercise of civil rights, nor does it guarantee that law enforcement will recover the full amount of a commercial debt. Where a lawful freeze is involved, a distinction should also be drawn between lifting the restriction and seeking to hold the upstream party liable.
First protect unaffected client funds and original evidence, then verify limitation periods, the urgency of preservation measures and asset leads, and subsequently choose appropriate routes such as negotiation, litigation, arbitration or filing a claim in bankruptcy. In external communications, avoid accusing specific individuals without verification, and do not purchase services that claim to be able to hack wallets or guarantee recovery of coins. The cost budget should include investigation, translation, local counsel and enforcement work, and milestones should be set for adjusting strategy in light of new evidence.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
An offshore company generally has a separate legal personality, but that does not provide a comprehensive shield for an individual's own unlawful acts or guarantee obligations. Whether founders, directors and de facto managers are liable depends separately on their conduct, their duties of office, the applicable law and their personal undertakings. An ordinary commercial loss does not mean that shareholders must repay the company's debts from all of their personal assets.
Shareholder capital contributions, directors' performance of duties, employee execution and personal guarantees are distinct sources of liability. A person who holds few shares but actually makes decisions, or who serves only as a nominee director, cannot have risk assessed on the basis of title alone. Taking official UK guidance as an example, directors are generally not personally liable for company debts, but specific circumstances such as wrongful trading may give rise to liability; guarantees given personally must also be performed separately. The conditions and scope of remedies in other places of incorporation must be verified separately.
The UK Insolvency Service reminds that, upon entering relevant financial distress, directors should have regard to creditors' interests, protect assets and seek professional advice. This reminder cannot be simplified into "a loss means you cannot trade", nor should unfounded assurances continue to be given to clients when performance is clearly impossible. Whether trading, financing or returning a particular sum of money may continue should be judged on the basis of local rules and real-time financial circumstances, and related-party payments in particular should be recorded transparently.
Assume A operates under proper governance and the business fails, without providing a personal guarantee or misappropriating funds; B instructs finance to transfer client balances into a private account and conceals the facts in application materials. The two cannot be found to bear the same liability merely because both used an offshore company. If a founder has separately signed a personal guarantee with a bank, even if the business failure involves no illegality, that founder may still bear payment liability under that independent undertaking.
The 2026 mainland notice on virtual currency risks involves arrangements for the legal liability of relevant entities and individuals, but it cannot be presumed that all offshore operations are unlawful merely on the basis of Chinese nationality. The place of conduct, the recipients of services, the fund paths and the nature of participation must be examined. In practice, it is advisable to ensure separation of company and personal accounts, a basis for key decisions, and clear duties and authority; having others act as nominees or switching to another offshore company cannot reliably eliminate liability for conduct that has already occurred.
Board records should also reflect genuine judgment, rather than consents signed after the event. Material risk warnings, available options, dissenting views and the basis for measures taken may be retained, so that managers know that what they approved was not abstract business growth but specific funding and client risks. Where they lack the capacity to understand technical or financial matters, they should obtain appropriate explanations before deciding. External adviser opinions can assist, but should not be used as a tool to transfer all management duties to advisers.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
It is possible to assess obtaining qualification or changing the business model, but a "retroactive application" is not automatic ratification and does not guarantee approval. First, it is necessary to confirm whether a licensing obligation actually exists and which businesses are affected, and then concurrently address historical risks, funds held for existing customers, and the future operating path. Submitting an application must not be treated as permission to continue unlicensed operations.
Establish when the service was launched, which countries it serves, where clients and funds are located, and what the platform specifically controlled, then assess this against the rules in force at the time and the rules currently in force. Some technical services may fall outside the scope of regulation, while certain exchange, custody or payment activities may long ago have required a licence. The UK FCA makes clear that businesses falling within the scope of its anti-money laundering registration must complete registration before commencing business; this is a different status from 'the application has already been submitted'. It cannot be presumed that all business is unlawful merely because the platform has no licence, nor can the issue be excluded on the basis of a self-description as a technology company.
It may be necessary to stop accepting new clients, suspend the addition of restricted functions, and arrange migration to a lawful service provider or an orderly exit, but the legal basis and contractual requirements should be confirmed at each step. Client assets, outstanding orders, reports and records must not disappear because the site is shut down; changing the brand or the contracting entity does not automatically sever the original liabilities. Where lawfully frozen or suspicious funds are involved, it is equally impermissible to refund them directly without assessment on exit.
During the suspension, the business team should be given clear instructions: which orders may still be lawfully completed, which must not continue to be accepted, who is to answer client enquiries, and what review is required for refunds or migration. Without written boundaries, sales may interpret a stop on new orders as merely ceasing marketing, while the system continues to accept automated deposits. Website entry points, interface permissions and partner routing can be tested item by item to confirm that the remediation plan has been implemented at the operational level; retaining the necessary enquiry and data access functions also assists existing clients in pursuing remedies later.
Assume that an EU undertaking once operated under the former local regime but never completed the MiCA transition. In its official 2026 announcement, the French AMF stated that the transitional arrangements under the former local regime applied until 1 July 2026 and ended with effect from 2 July. This example shows that what was permissible historically is not necessarily permissible now, and the specific transitional conditions and existing licences of the relevant country should be checked; undertakings that do not meet the transitional conditions certainly cannot rely on another party's grace period.
The future workstream should identify the business activities that may be applied for, together with gaps in personnel, capital and systems; the historical workstream should verify transactions, client losses, necessary reporting and the manner of communication with regulators. Whether and how to make voluntary disclosure should be handled under local rules and with professional advice, without concealment or the creation of documents after the event. Where business prohibited in mainland China is involved, under the 2026 risk notice there is no general route by which the original model can be legitimised by applying for an ordinary crypto payment licence; cessation or substantive restructuring should be considered rather than seeking a nominal wrapper.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
The key is not to assemble the company's documents in order, but to demonstrate that revenue derives from a sustainable lawful business, that client assets are genuinely segregated, that key partnerships can continue, and that the transaction structure complies with regulatory requirements. Financing and M&A may change control, capital or contractual relationships, and these should be identified before signing and closing arrangements, rather than completing formalities after the investment funds arrive.
Revenue sources, contracting entities, licensing bases and actual fund flows can be listed by product and country, and whether the descriptions in regulatory applications remain accurate can be checked. The fact that investors can see operating revenue does not mean that such revenue comes from business covered by a licence. A distinction should also be drawn between customer principal, amounts payable to merchants, platform fees and own assets; customer balances cannot be treated as free cash or distributable profits merely because they have passed through a company account.
The UK FCA requires prior notification and approval for certain acquisitions or increases of holdings, and crypto businesses registered with it are also subject to corresponding control review arrangements. Financing at the group level, voting rights, joint control or contractual rights may need to be analysed together; it is not sufficient to look only at whether the shareholder register of the licensed company has changed. Thresholds and procedures differ in other jurisdictions. Transaction documents may make the necessary approvals conditions to closing and avoid transferring control in advance through governance arrangements before approval.
Assume that the investor wishes to move the business to a new group entity after financing, but the bank and upstream agreements permit use only by the original company, and a change of control also triggers notice or termination provisions. Even if the transaction itself is lawful, business continuity may still be affected. It should first be ascertained who must consent and which products and markets the consent covers, and only then should the migration be arranged; the licensed subsidiary, bank accounts and technical systems must not be treated as a package of assets that can be transferred at will.
In addition to equity and intellectual property, document packages can be established for customer fund reconciliation, historical complaints, anti-money laundering issues, tax reporting, data and key outsourcing. A distinction should be drawn between issues that must be resolved before closing, matters that can be completed after closing and risks that are unacceptable; for each item, the responsible person, evidence and conditions should be stated. Disclosing customer information to investors also requires controlling the necessary scope and access permissions; complete identity documents and transaction databases should not be uploaded indiscriminately for due diligence.
A remediation list should preferably distinguish between missing facts and actual violations. The inability to find a contract does not mean that the contract does not exist; however, signing a new contract cannot eliminate problems in the earlier period. Regarding historical gaps, the current evidence, the supplementary investigation process and the remaining uncertainty should be truthfully explained, and records should not be backdated or recreated in order to satisfy investor questionnaires. Transaction terms may provide for disclosure, warranties or indemnities, but such commercial allocation does not automatically change the rights that regulators or customers have against the company.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
It is not necessarily necessary to reapply for an entirely new licence, but each expansion should involve checking whether the licence, market access, asset classification and scope of cooperation have changed. A new country, new function and new currency are three different types of change: some require notification, some require an extension of authorisation or a separate licence, and some cannot be launched in the target market under the original plan at all.
MiCA permits qualifying service providers to provide services across Member States, but Article 65 sets out specific notification arrangements; this does not confer automatic global operating rights. Entering non-EU jurisdictions requires separate review of local market-access, marketing and client-protection rules; even without an office, solicitation and actual services directed at local clients may be relevant. Geographic settings at product launch should align with legal determinations and the scope acceptable to banks.
Article 59 of MiCA makes clear that a licence should specify the authorised services, and adding services requires an application to extend authorisation. For example, adding custody to exchange services should not be treated merely as an app version update. Credit payments, yield on balances or products with securities characteristics may also engage rules beyond the original crypto-asset services regime. Whether a partner undertakes the activity, with whom clients contract, and whether the platform still makes performance commitments all require fresh analysis.
Suppose a platform previously supported an issuer's native stablecoin on one chain and later plans to support a bridged version on another chain. Similar names do not mean the redemption entity, custody, smart contracts and freeze mechanisms are the same. A new token does not necessarily require a new licence, but legal classification, issuance and circulation conditions, service-provider support and technical risks should be verified; the fact that both tokens trade close to one dollar does not mean their risks are equivalent.
For each material change, prepare a one-page note: what changed, which entity and market are affected, what regulatory action is required, and who has confirmed it. Then update client contracts, risk disclosures, monitoring rules, safeguarding of funds and exit plans accordingly. Legal advice should correspond to the final version rather than an early product sketch; if key features change again during development, they should be re-verified rather than relying on old advice to endorse a new business.
After launch, also verify that actual traffic matches the approved scope. For example, if the plan is to open only to specific markets but customer service accepts clients from other regions, or a partner automatically routes to an institution that has not been assessed, the paper scope will diverge from reality. Product, compliance and operations teams can jointly review the countries, assets and paths of the first orders and establish fallback arrangements for deviations. The post-launch review here is a risk-management recommendation; it does not mean that trading may begin where approval is required and the licence later supplemented through retrospective spot checks.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
It is possible to first conduct a comparison of business feasibility and regulatory pathways without immediately choosing a country or purchasing a license. An effective preliminary analysis should explain which functions can be performed, by whom, which customers are served, what conditions are relied upon, and the differences in liability between obtaining a license oneself and a cooperation model. Final establishment still needs to be verified by professionals in the relevant jurisdictions, rather than being replaced by a country ranking.
What the lawyer needs is not merely the statement "do stablecoin payments," but rather where the payer and the merchant are located, what is collected and what is paid, who controls the wallet, whether balances are retained, whether fixed settlement is promised, and how fees are charged. You can first use a typical order to map out the flows of funds, instructions and contracts, and then list functions that may be added in the future. Without these facts, even a low-threshold licence may be unrelated to the actual business.
If the team does not yet have a complete plan, it can first provide fixed conditions and adjustable conditions. For example, whether the target customers must be retained, whether the team can deploy local personnel, whether customer balances must be held, and whether it is willing to have customers contract directly with counterparties. Setting out these commercial constraints in writing helps rule out plans that are compliant on their face but cannot be operated. Assumptions made in consultations should be confirmed by the team, and if they change later, the assessment should be updated accordingly, rather than treating the views expressed at the initial meeting as long-term general conclusions.
Obtaining a licence oneself may require ongoing investment in personnel, systems, capital and reporting; cooperating with a licensed institution requires confirming who provides services to customers, who controls assets and who is responsible for handling exceptions. The EU MiCA provisions on outsourcing responsibility show that cooperation cannot automatically transfer one's own obligations away; the UK FCA requires business plans to take account of target customers and governance arrangements, which also shows that regulatory assessment does not look only at the place of registration. Budgets should include banking and operational conditions, not merely a comparison of application fees.
Assume Team A only wants to provide order tools to a small number of familiar overseas merchants, while Team B wants to custody assets itself, lock in exchange rates and guarantee fiat settlement. Even if both use the same stablecoin, Team A can prioritise verifying the compliant division of technical responsibilities, whereas Team B needs to focus on assessing licensing, customer funds and liquidity responsibilities. Both models should be judged on the facts, and "not handling funds" or "serving businesses only" must not be treated as automatic exemptions.
Where mainland China customers, operations or fund flows are involved, the restrictions such as the 2026 virtual currency risk notice should be checked first, and it must not be assumed that an overseas company can resolve the matter. The preliminary deliverable can be a conditional roadmap: the functions for the first phase, the customers that cannot be taken on, the cooperation required and the matters to be verified, and then an indication of what changes in facts would trigger a reassessment. If there is no reliable basis for fees, timelines and bank acceptance, they should be marked as to be confirmed, and market experience should not be packaged as a regulatory guarantee.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Some models may be permissible, but advance funding or credit payment should be assessed separately against payment, credit extension and lending rules; the existing crypto licence cannot be assumed to cover them automatically. Short-term settlement timing gaps and revolving credit lines may be different in nature; own funds are not automatically exempt either. The funds used for advance funding, credit risk and customer asset protection must each be addressed separately.
A platform paying merchants in advance settlement funds it has not yet received, customers obtaining a buy-now-pay-later credit limit, and a platform purchasing merchants' receivables may correspond to different legal structures. The borrower or financing counterparty, recourse rights, maturity dates, fees, guarantees and actual fund flows should be verified. A product named "fast settlement" does not mean there is no financing, nor can it be concluded that credit regulation does not apply merely because no interest is charged.
The UK FCA Handbook makes clear that certain incidental credit permitted under the payment regulations does not exempt a firm from other credit business permissions that would otherwise apply. Irish payment regulations likewise impose conditions on corresponding incidental credit, including transaction purpose, source of funds and capital, and do not exclude consumer credit rules. These are examples from specific jurisdictions and do not mean all crypto asset service providers can copy them; stablecoin lending or consumer credit limits must still be analyzed separately according to the nature of the assets and customers.
Assume a platform pays a merchant one day early for confirmed orders and recovers the funds after upstream settlement; another product allows a merchant to use a credit limit over the long term, borrow and repay at will, and charges financing fees. Both address working capital turnover, but continuous credit extension, purpose controls and default risk differ materially, and the same payment services agreement cannot cover both. Even where the former is very short-term, it should be confirmed who bears the loss from upstream non-payment, chargebacks or order disputes.
The relevant Irish rules expressly restrict the use of funds received or held for payment transactions to provide incidental credit. For other jurisdictions as well, asset segregation and purpose restrictions must be verified; funds awaiting settlement for Merchant A must not be used to advance funds to Merchant B. In practice, own liquidity, credit-limit concentration and stress scenarios should be measured separately, and overdue, dispute and recourse processes should be agreed; where a licensed financing partner undertakes the business, it must also be clear whether the platform provides guarantees, repurchases or bears first loss, rather than looking only at who transfers the funds.
Stress testing should not test only customers' normal repayment. It can also simulate consecutive upstream delays, multiple merchants refunding at the same time, depreciation of guaranteed assets and financing partners tightening credit limits, to observe whether the company can still complete settlement for unrelated customers. Credit-limit approval should match risk tolerance, and it should be clearly stated whether ceasing new financing affects existing payment obligations. If a product depends on continuously absorbing new customer funds to repay old debts, it should be reassessed immediately rather than masking structural funding problems by raising fees.
This content is for general information only and does not constitute legal advice. Please consult a qualified lawyer about specific matters.
Tell us about the business model, target markets and current issue. We will help identify the practical next step.