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

March 18, 2016

New Payment Systems Bill: E-Payments and Beyond

Bangkok Post, Corporate Counsellor Column

In recent months, there has been excitement about the prospect of new electronic payment services in Thailand. News reports have described a system that will enable instantaneous funds transfer using only ID cards.

From a public policy standpoint, it is challenging to move small payments to the electronic space. When that is accomplished, however, it can result in substantial benefits. For example, reducing the usage of cash can reduce the yield of robberies on the street and ultimately reduce the occurrence of robberies.

Bringing micropayments into the electronic realm is exciting, but it is only part of what could be made possible under the new payment systems bill approved in principle by the cabinet and based on a version proposed by the Finance Ministry.

Electronic payment services in Thailand are currently regulated under the Royal Decree on Electronic Payment Systems issued under the Electronic Transactions Act, as well as under a notification of the Finance Ministry issued under Section 5 of Revolutionary Council Decree No. 58. A considerable body of regulatory notifications exists under each.

Taken together, they set out the regulatory regime and the different categories of electronic payment businesses, which require notification, registration, or licensing.

The new bill is expected to replace the older rules and consolidate the regulatory regime under a single act. It would discern between electronic payment systems and electronic payment services. The finance minister would set the major objectives and the Bank of Thailand would be responsible for the details and mechanics.

The central bank would have the authority to establish and operate payment systems that are systemically important, and to issue regulations.

A key feature in the new act is clarity with respect to finality of payment. In a transfer of funds among two parties, finality is the point at which the transferring party has irrevocably lost access to the funds, and the receiving party has irrevocably gained access to the funds.

If a court can issue an order that has the effect of reversing, changing, stopping, or revoking a funds transfer, this means that payment is not actually final. Where a bank has received funds and made use of them, but is then ordered by a court to reverse the transaction, this can create significant problems, and thus presents systemic risk.

As an example, some jurisdictions feature a “zero-hour rule.” The Bank for International Settlements describes this as “a provision in the insolvency law … whereby the transactions conducted by an insolvent institution after midnight on the date the institution is declared insolvent are automatically ineffective by operation of law.”

If an institution had received funds and made use of them, and the transaction was then rendered invalid under the foregoing, this could—if the invalidated transaction was large enough—threaten the solvency of the receiving financial institution. This is among the reasons that several financial institutions place holds on funds received. Unfortunately, holds run contrary to the instantaneous transfers that people expect these days.

In a 2008 review of Thailand’s Bahtnet system, the International Monetary Fund noted that Thai law does not feature a zero-hour rule, but it recognized the possibility that a court could issue an order with similar retrospective effect.

The Bank of Thailand sought an opinion from the Council of State, which took the position that court-ordered receivership shall be effective from the time the order is read.

The new payment systems bill would provide that transfer, settlement, or clearing through an electronic payment system that was successful and effective by the rules of the system cannot be revoked or reversed, suspended, or stopped, even if ordered by a court, and even in the context of receivership or rehabilitation.

Though it will be necessary to review the full text of the law as enacted, the concept is present. Properly crafted, it can serve to eliminate systemic risk that would otherwise exist due to lack of finality of payment.

The new act would also address criminal penalties and administrative sanctions more clearly than the old regime, with a stronger regulatory framework benefiting everyone.

Finally, the new law would address transitional matters. Importantly, those who are already registered or licensed under the old regime would be deemed registered or licensed under the new one.

The bill has been referred to the Council of State and for review by the Justice Ministry and the Office of the Judiciary. We look forward to the further development of the law relating to electronic payments, in a manner that promotes the growth of electronic payments in Thailand.

RELATED INSIGHTS​ 

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,
August 4, 2026
Thailand’s Personal Data Protection Act B.E. 2562 (2019) (PDPA) could soon see some important changes, as a draft bill to amend the PDPA has been introduced in the House of Representatives. The draft amendment is currently in the public consultation phase, with comments accepted from July 16 to August 15, 2026. If enacted in its current form, the amendment would make three key changes: expanding the government exemption to cover anticorruption operations, introducing a statutory definition of “government agency,” and restructuring the lawful bases for personal data processing to align with international standards. Background The PDPA has encountered several enforcement challenges since its implementation, including three core problems identified by the bill’s sponsors: (1) the current exemptions for government agencies do not cover anticorruption and misconduct-prevention operations; (2) the PDPA lacks a clear statutory definition of “government agency,” causing legal uncertainty as to which entities are covered; and (3) the existing framework for lawful bases of data processing does not align with international standards—particularly the multiple-lawful-bases system in the EU’s General Data Protection Regulation (GDPR)—making compliance inflexible for both government and private sector entities. Expanded Government Exemption The current PDPA exempts government agencies performing duties related to national security (including fiscal security), public safety, anti-money laundering, forensic science, and cybersecurity. The proposed amendment adds “prevention and suppression of corruption and misconduct” to this list of exempted functions. This would allow anticorruption bodies—most notably the National Anti-Corruption Commission (NACC), which is identified as a directly affected party—to collect, use, and disclose personal data without being subject to PDPA requirements when carrying out their duties. New Statutory Definition of “Government Agency” Notably, while the current PDPA use the term “government agency” in several provisions, the term is not comprehensively defined, creating potential uncertainty as to its scope. The draft bill therefore
August 3, 2026
On July 23, 2026, the Bank of Thailand (BOT) released for public comment its draft Notification on Digital Channel Security, which would significantly expand the scope and stringency of Thailand’s existing mobile banking security framework. If finalized in its current form, the draft notification would extend mandatory security requirements to credit card providers and credit providers, cover internet banking in addition to mobile applications, phase out SMS one-time passwords (OTPs) for transaction authentication, and introduce biometric verification requirements for high-value transactions. The public comment period is open through August 24, 2026. Background The BOT’s existing Mobile Banking Security Notification, issued in 2024, sets minimum security standards for financial institutions, specialized financial institutions (SFIs), and e-money providers, significantly reducing “money-draining app” fraud. However, fraudsters have since shifted to nonbank providers and internet banking channels, prompting the BOT to propose broader security requirements. Expanded Scope of Regulated Entities and Channels The existing Mobile Banking Security Notification covers only financial institutions, SFIs, and e-money providers offering mobile banking services. The draft expands coverage in two key areas: entities and channels. On the entity side, it adds credit card providers and credit providers that offer fund transfers to third parties at other financial service providers or that provide cash withdrawal services to individual retail customers. On the channel side, it broadens coverage to include internet banking in addition to mobile banking. Strengthened Customer Authentication The draft introduces enhanced authentication requirements in three areas: Service enrollment and device changes. Providers must implement rigorous identity verification, notify customers of enrollment results through out-of-band communication channels, and adopt risk-mitigation measures such as cooling-off periods and temporary transaction limits. Transaction-level authentication. Providers must use two-factor authentication for fund transfers, cardless ATM withdrawals, and transaction limit increases. Secure authentication factors. Key requirements include the following: “What-you-know” factors must