You are using an outdated browser and your browsing experience will not be optimal. Please update to the latest version of Microsoft Edge, Google Chrome or Mozilla Firefox. Install Microsoft Edge

August 31, 2020

Bank of Thailand Revamps Know-Your-Customer Procedures for E-Money Service Operators

Informed Counsel

A recent notification from the Bank of Thailand (BOT) has introduced new know-your-customer (KYC) guidelines for e-money businesses, updating the country’s regulatory regime to accommodate the greater variety of e-money services that have come into the market. The new regulations better differentiate between the types of risk relating to each product, and are expected to help e-money service providers overcome difficulties in identifying their customers.

Notification Sor Nor Chor 1/2563 Re: Know Your Customer Regulations for Activating the Use of e-Money Services was issued by the BOT on March 13, 2020, supplementing the KYC requirements for e-money services stipulated under the Anti-Money Laundering Act B.E. 2542 (1999) (AMLA). The notification came into force on May 6, 2020.

Identification and Verification               

The KYC procedures that e-money service operators must adopt are a two-stage process—first identifying, and then verifying, customers. In doing so, they must ensure that the information received is actually the customer’s information, and that the information is correct, true, and up to date.                

The notification sets out specific KYC requirements for different product offerings so that e-money service providers will be able to adapt their procedures to suit the level of risk for each product. For non-transferable payments for products or services in Thailand, e-money services must follow the customer identification and verification procedural requirements in the AMLA. For transferable payments for products or services (whether in Thailand or not), e-money services must conduct additional face-to-face or non-face-to-face verification of customers. 

For face-to-face verification, e-money services must confirm that the information and evidence received for verification is correct, true, up to date, and from a reliable source (e.g., the National Credit Bureau). Service operators must also prove that the information provided by the customer is the customer’s own information and proof of identity. If a smart ID card is provided as evidence, the card must be validated with a smart card reader and verified through a government electronic inspection system (e.g., National Digital ID).

When face-to-face verification is not possible, or not a preferred option, in addition to confirming and verifying the information received, operators must obtain a photograph of the customer and record it using advanced technology that adheres to accepted standards, in order to verify the customer’s identity by comparing the individual’s face with the biometric information embedded in the smart ID card. E-money payment or transfer services that have implemented measures to minimize risks in line with the AMLA’s criteria for low-risk services (such as regulated e-payment services) may confirm the information and evidence used for verification themselves, similar to the requirements for face-to-face confirmation.   

For corporate customers, the procedures must enable the identification and verification of the corporate entity’s authorized person, in addition to the KYC procedures set out by the AMLA (meaning that corporate customers must provide the company name, objectives, address, phone number, etc.). This can be any procedure that meets the standards set out in the BOT’s notification—for example, an e-money service may designate an employee to be in charge of a corporate customer and validate that the information received is correct, true, and up to date. Evidence is also required to prove that the person using the e-money service for the first time is authorized to do so by the corporate entity.    

As part of their internal risk-management procedures, e-money services must implement other KYC procedures for corporate customers when there are temporary technical difficulties that could prevent compliance with any of the above verification requirements.   

The BOT notification also allows e-money service operators to verify customers using the national digital ID system, either alone or in conjunction with the procedures outlined above.    

When a customer of one e-money service intends to activate or use another type of e-money service with the same provider, operators that have already implemented the KYC requirements in the regulations for activating or changing of the type of e-money service, and have kept the customer’s information correct and up to date, should follow authentication procedures that are secure and able to prove the customer’s genuine identity and correlation with the risk level of the relevant product or service. For example, an operator could use a biometric comparison technology to verify customers. 

Other Requirements

Other requirements under the BOT notification include implementing policies, risk management measures, and internal controls to ensure that risk management systems for KYC procedures are appropriate, concise, and aligned with the relevant product and activation channels. In addition, a secured storage system for customer information must be maintained.

E-money service providers that want to implement any other KYC process will need to obtain approval from the BOT and, if necessary, test any new technology in the BOT’s regulatory sandbox.

Compliance Steps and Exemption Requests

E-money services should be in compliance with the BOT’s KYC notification by November 2, 2020. In advance of that compliance, by July 5, 2020, existing services need to have submitted a clear operating plan to the BOT showing how they would bring their operations into compliance with the regulations. Service providers are also required to notify the BOT immediately upon achieving full compliance with the regulations.   

E-money services that are unable to comply with the regulations may submit an exemption request (in writing or electronically) to the BOT, detailing the reasons for not being able to comply with the regulations. Upon receipt, the BOT will consider whether to approve the exemption.
 

RELATED INSIGHTS​ 

August 11, 2026
On July 27, 2026, the State Bank of Vietnam (SBV) released a draft decree proposing amendments to Decree No. 52/2024/ND-CP dated May 15, 2024, on non-cash payments (Decree 52). The draft decree would amend 17 of Decree 52’s 38 articles, with several key changes directly affecting providers of intermediary payment service (IPS). The key proposed changes affecting IPS providers are outlined below. Streamlining IPS Licensing Procedures A central objective of the draft decree is to simplify regulatory procedures for IPS providers. Notably, it would significantly reduce IPS licensing documentation requirements by removing the need to submit enterprise registration certificates, investment registration certificates, and documents evidencing the qualifications of the legal representative and general director. Instead, the SBV would retrieve this information directly from national business registration and other specialized databases, requesting additional documents only where the relevant information cannot be verified electronically or is incomplete. The draft decree also removes the current limit of two rounds for dossier supplementation and shortens processing timelines for several IPS licensing procedures such as issuance, amendment, and reissuance of IPS licenses. The processing time for new IPS license applications would be thereby reduced from 90 to 60 working days. In addition, several continuing IPS business conditions would be removed. For example, IPS providers would no longer be required to maintain certain representations relating to corporate restructuring or the legality of contributed capital. Likewise, the IPS project plan (đề án) would become a one-time application document rather than an ongoing licensing condition. If retained in the final decree, this change could provide IPS providers with significantly greater flexibility to implement post-licensing technology upgrades, system integrations, and corporate restructuring transactions without needing to revisit the originally approved project plan. The draft decree also removes the requirement for the SBV to consult the Ministry of Public
August 10, 2026
Thailand has finalized its social media KYC (“know your customer”) rules under Notification of the Electronic Transactions Commission on Measures to Prevent Technological Crimes for Social Media Service Providers (No. 2), which was published in the Government Gazette on May 5, 2026, and will take effect on November 1, 2026. While an early draft of the notification proposed requiring social media platforms to arrange identification of every user account, the final notification is significantly more targeted, focusing on paid online advertising and advertiser identity verification. Though the regulatory initiative primarily aims to combat online fraud and technology-related crimes, it also has important consequences for intellectual property enforcement, because the verified platform records that will be generated under the new requirements can help IP rights holders to identify anonymous online infringers. Key Regulatory Mandates The notification requires social media service providers to verify the identity of advertisers before their paid advertisements are published and disseminated in Thailand through social media, regardless of whether the advertising fees come from the advertisers or third parties. Verification of an advertiser is valid for one year, after which verification would have to be performed again before the platform could publish additional paid advertisements from the advertiser. Permitted verification methods are specified under the notification. A platform may verify an advertiser by checking identity evidence and confirming the connection between the advertiser and that identity evidence, with the notification giving facial comparison against certain government-issued identity documents as an example. Alternatively, platforms may verify advertisers through a digital identity verification and authentication system with an identity-proofing assurance level not lower than the level prescribed by Thailand’s Electronic Transactions Commission. The notification further requires platforms to retain only the advertiser’s information necessary to identify the advertiser, beginning from the start of the advertising activity and for
August 10, 2026
On July 31, 2026, Thailand’s Big Data Institute (BDI) launched a public consultation on the principles of a proposed new data-sharing law, with comments accepted until August 31, 2026. If enacted, the law would establish Thailand’s first comprehensive framework for government and private-sector data sharing, creating a systematic, secure, and transparent regime to support analytics, policymaking, research, and innovation. Central Data-Sharing Platform The draft law establishes a central system for data sharing, managed by the BDI. Government agencies would be required to connect to the BDI’s Data Integration and Intelligence Platform (also referred to as D2), in accordance with the BDI’s rules and procedures. Five Dimensions of Data Sharing The draft law covers five key types of data sharing between government (G), businesses (B), and consumers (C): G2B: Private organizations may request government data specifically for research and development purposes. The BDI will assess the applicant’s data governance, security, and privacy capabilities whether such measures meet prescribed standards before forwarding the request to the relevant government agency within 90 days. Any dispute may be escalated to a newly established Data-Sharing Promotion Committee for final determination. G2G: Government agencies may request data from other agencies through the central system. The data-holding agency must respond within 90 days, taking legality, necessity, proportionality, public interest, and personal data protection into account. Disputes may be referred to the Data-Sharing Promotion Committee for adjudication. B2G: In emergency situations involving public safety, economic security, or disaster response, the Minister of Digital Economy and Society may require private entities to provide data through the central data-sharing system. Government agencies must specify the data requested, demonstrate its necessity and expected benefits, and request only data reasonably available to the data holder. Requests for personal data must be limited to the minimum amount necessary. B2C: Royal decrees may
August 10, 2026
Thailand’s Office of the Personal Data Protection Committee (PDPC) recently released draft guidance on records of processing activities (ROPA) for personal data controllers and processors under the Personal Data Protection Act B.E. 2562 (2019) (PDPA). The draft guidance, which was presented to the public on July 7, 2026, addresses both controller records of collection, use, and disclosure of personal data and processor records of processing activities carried out on behalf of controllers. If implemented, the guidance will significantly expand organizational expectations for ROPA preparation, maintenance, and use across all sectors. Key Takeaways The draft guidance contains several important implications for organizations subject to the PDPA: ROPA reframed as a core accountability tool. The guidance elevates ROPA from an administrative record to a central accountability mechanism, connecting controller duties with recordkeeping obligations. ROPA as a source for privacy notices and governance documents. ROPA should serve as the primary source for privacy notices and align with consent management, retention schedules, DPIAs, incident response plans, and vendor contracts. Expanded scope across all activities. ROPA must cover all processing activities across the organization—including security, finance, HR, and external contractors—with correct controller or processor classification for each. Ongoing maintenance and auditability. ROPA must be updated for any change to systems, purposes, or processors, reviewed at least annually, and maintained with version control and a designated owner. Enhanced vendor, processor, and cross-border transfer requirements. Organizations must document all processors, external recipients, and cross-border transfers, specifying purposes, access scope, and destination countries. Linkage with risk assessment, DPIAs, and LIAs. ROPA should assign risk levels to each activity and identify when data protection impact assessments (DPIAs) or legitimate interests assessments (LIAs) are required, functioning as a risk-management tool. ROPA and data breach readiness. Incomplete ROPA can delay breach response and notification. Organizations should map data flows, vendors,