Quick Answer: On 12 November 2026, Thailand's Securities and Exchange Commission opened a public consultation on draft requirements for stablecoin transactions conducted through digital-asset business operators. The draft would restrict transfers between an operator account and external accounts or wallets to those verified as belonging to the same customer, alongside other controls on liquidity providers and off-platform trades. It is a proposal, with comments due 26 November, not a rule already in force. Its scope is transactions through regulated operators, so claims about a blanket ban on all self-custody transfers would overstate the announcement.
What did the Thai SEC publish?
The SEC's 12 November notice describes a draft notification governing stablecoin transactions through digital-asset business operators. The regulator says its aims include preventing money laundering, cybercrime and circumvention of international-money-transfer rules, while improving its ability to supervise operators. The consultation follows principles published and discussed earlier in 2026. The November text is a more detailed proposal after those discussions, not evidence that operators were newly ordered to change their systems on publication day.
Readers should retain three distinctions. First, the proposed obligations concern businesses in the defined operator category; they do not make every blockchain transfer a regulated-operator transfer. Second, a stablecoin deposit or withdrawal involving an operator has a different compliance workflow from a direct payment between two self-custody wallets. Third, a consultation can change before final adoption. A headline in the past tense such as “Thailand bans stablecoin transfers” compresses these distinctions into an inaccurate claim.
The notice gives a public-hearing end date of 26 November 2026 and links to the consultation paper. That date is a deadline for comments, not an effective date for the proposed rules. Any article published before a final notification should keep verbs such as “proposes” and “would require.” If a final rule appears later, the article needs a dated update rather than a silent conversion of draft terms into current law.
How would the same-customer wallet rule work?
The proposal says that a stablecoin transfer into a customer's account with a digital-asset operator, or out from that account, would need to involve an originating or destination account or wallet verified as belonging to the same customer. Transfers involving another person's account or wallet would be prohibited within that defined operator flow. This is more specific than a generic requirement to know a wallet address. The operator would need a way to establish ownership or control and link that evidence to the customer whose account is involved.
In practice, verification can be difficult. A named bank account provides an owner field; a self-custody wallet address does not. Signing a message can show control of a private key but may not prove the legal identity of the controller. A custodial wallet can be assigned to an omnibus structure where the visible on-chain address does not map one-to-one to a customer. An operator implementing the draft would need policies for these cases, and the consultation should be read for any exemptions or accepted evidence standards. The press notice alone does not settle every edge case.
The SEC also references Travel Rule requirements, customer profiling, screening and blockchain analytics to identify high-risk wallets. These are related but separate checks. A wallet can be controlled by the same customer and still be associated with suspicious flows. Conversely, a clean transaction history does not prove wallet ownership. Treating one check as a substitute for the other would leave gaps in the stated policy aim.
Why are market makers and liquidity providers included?
Stablecoin markets depend on entities that quote and move inventory. A strict transfer rule can affect how market makers rebalance between venues, settle customer trades or source liquidity. The Thai SEC's notice refers to revised supervision of market makers, liquidity providers and source exchanges. It also states a proposed restriction on the use of liquidity providers for stablecoin/Thai-baht pairs. Those details matter because liquidity can migrate from transparent on-platform order books to bilateral channels if compliance design ignores the trading workflow.
The regulatory question is not simply whether a market maker is permitted. It is how the operator identifies the counterparty, verifies the source of stablecoins, monitors transactions and prevents an opaque external venue from becoming a route around domestic controls. A registered Thai operator may use an overseas source exchange under the draft only if that source meets the proposed oversight and monitoring requirements. The SEC specifically mentions competent regulatory supervision of source exchanges and ongoing screening comparable to that applied to liquidity providers.
There is a trade-off. Tighter controls can reduce channels for fraud and illicit transfers, but they can also add friction to legitimate liquidity management. Wider spreads or slower settlement are possible if fewer counterparties qualify. The proposal does not quantify such effects. Any claim that it will make stablecoins safer or more expensive in a specific amount would need data after implementation.
What would change for off-platform transactions?
The draft also addresses transactions conducted by digital-asset brokers and dealers outside an exchange order book. The SEC notice proposes a minimum off-platform transaction value of 3 million baht, public disclosure of trading prices for price verification, and a restriction on brokers matching customers with each other off-platform. It says a broker may arrange for a customer order to be matched on a digital-asset exchange in Thailand or overseas under the stated framework.
Those provisions address transparency and routing, not only wallet identity. An off-platform quote can be difficult for a customer or supervisor to compare with an exchange price. Public price disclosure may make it easier to check execution quality, though it does not by itself reveal spread, fees, market depth or whether the customer received the best available execution. A material transaction should still be evaluated against the total delivered amount and the settlement risk of the counterparties.
For a broker, the operational questions include which prices must be published, when they must be updated, how order records are retained and whether a transaction meets the minimum. For a customer, the key questions include who is the contracting counterparty, where the stablecoins are held before settlement and what happens if the transfer is delayed or rejected. The announcement supplies a proposed framework, not the implementation details of every operator.
Does the draft apply to all stablecoins and all users?
The notice addresses stablecoin transactions through digital-asset business operators. It does not mean every token that tracks a currency has identical legal status, issuer risk or network behavior. It does not establish that a stablecoin payment made entirely outside an operator is approved or prohibited under every other Thai law. Cross-border payments can be subject to other rules, and the draft's purpose explicitly includes preventing circumvention of those rules. Readers should avoid extrapolating from one announcement to a universal statement about self-custody or international remittances.
Location and service model matter. A global exchange, a Thai-licensed broker, a wallet software provider and a payment merchant may occupy different legal roles. Phemex readers should not assume a product's availability or regulatory permissions in Thailand from this consultation alone. Users need to check the service's current terms and local rules. This is especially important before moving funds in anticipation of a rule that has not yet been finalized.
What should stakeholders watch next?
The first milestone is the 26 November comment deadline. After that, the SEC may revise and publish a final notification with an effective date and transition provisions. Operators should compare final language with the November draft rather than relying on a news summary. Users should watch for provider notices explaining verification methods, supported transfer routes and treatment of existing addresses. Payment businesses should assess whether their use case involves a regulated operator, a third-party beneficiary or a cross-border transfer subject to other requirements.
The most consequential practical question is how customer control of a wallet will be demonstrated without blocking ordinary custody arrangements. The next is whether liquidity-provider and broker controls preserve executable markets while meeting the SEC's traceability objective. Both require specific implementation evidence. Until the final text exists, the article's conclusion is limited: Thailand has proposed a tighter operator-mediated stablecoin regime and invited feedback, but it has not announced a blanket ban on every stablecoin transfer.
FAQ
Are transfers to a family member's wallet already illegal under this announcement?
The announcement is a draft consultation. It proposes restrictions for transfers through a regulated operator involving a wallet that does not belong to the operator's customer. It does not establish the status of every direct wallet-to-wallet transfer.
Is the 26 November date when the rule starts?
No. It is the consultation deadline given in the SEC notice. A final rule and effective date would require a later regulatory step.
Why would operators need blockchain analytics if wallets are verified?
Ownership verification and transaction-risk screening answer different questions. A wallet controlled by a customer can still have links to high-risk activity.
