BOT 4/2568 Is Live. Is Your Mobile Banking App Ready?
Notification 4/2568 sets minimum Mobile Banking security standards for every financial institution under the Financial Institutions Businesses Act: one user account on one device, face comparison on high-value transfers, no links in SMS or email, and controls on the app, the device, and the data. We break down each control and show you how to prove it holds before your next BOT examination.
What is BOT Notification 4/2568?
The Bank of Thailand issued Notification 4/2568 under sections 39 and 41 of the Financial Institutions Businesses Act. It targets unauthorized payment fraud, where a criminal installs malware, takes control of a user's device or app, and transfers money without consent. It replaced the 2019 Guiding Principles for Mobile Banking Security (ว. 1922/2562).
Reference: BOT Notification No. 4/2568, clause 5.3
Who Falls Under BOT 4/2568?
4/2568 applies to every financial institution under the Financial Institutions Businesses Act (clause 4) that offers Mobile Banking to individual users. Specialized financial institutions and e-money licensees fall under other BOT rules.
Financial institutions and specialized financial institutions run the yearly penetration test under สกช. 5/2566, and e-money operators run a yearly pentest and VA under สนช. 1/2564 ข้อ 5.1.6, covered in our BOT penetration testing guide.
What 4/2568 and 18/2568 Require, Clause by Clause
Financial institution duties under 4/2568 and e-money operator duties under 18/2568 sit in separate tables. Each row names its clause, links to the page of the BOT PDF that holds it, and states what our testing proves.
Financial institution duties under 4/2568, by clause
| Clause | What the rule says | What Reconix testing proves | Source |
|---|---|---|---|
| 4/2568 ข้อ 5.3.1(1) | Binding rule You must not attach links of any kind to SMS or email, including URL text that cannot be clicked, images showing a URL, clickable images, and QR codes (Q&A 2). On social media, you must not attach links that ask for identity verification or personal data. You may attach a link on any of the three channels when the user requests it, one request at a time, and you must remind the user that it was sent only because they asked (Q&A 3). If mobile app; financial institutions under the Financial Institutions Businesses Act, not specialized financial institutions | No Reconix assessment covers this duty. | BOT Notification 4/2568 on Security of Mobile Financial and Payment Services for Financial Institutions, p. 4 (opens in a new tab) |
| 4/2568 ข้อ 5.3.1(2) | Binding rule You must have a process to monitor and respond in time to fake apps or apps impersonating yours in official app stores, such as Google Play Store and Apple App Store, and a process to respond to fake apps outside those stores. BOT's Q&A says the process must at least name an owner, set the response and takedown steps, and set a deadline for each step (Q&A 4), and counts Huawei AppGallery and Samsung Galaxy Store as official stores (Q&A 5). If mobile app; financial institutions under the Financial Institutions Businesses Act, not specialized financial institutions | No Reconix assessment covers this duty. Group service from BAYCOMS (opens in a new tab) and ECOP (opens in a new tab): digital risk protection | BOT Notification 4/2568 on Security of Mobile Financial and Payment Services for Financial Institutions, p. 4 (opens in a new tab) |
| 4/2568 ข้อ 5.3.1(3) | Binding rule You must limit each user to one user account per Mobile Banking service at your institution, used on one mobile device only. If you run more than one Mobile Banking app, the limit applies to each app (Q&A 6). If mobile app; financial institutions under the Financial Institutions Businesses Act, not specialized financial institutions | A MASTG-based test tries to enroll a second device and a second user account for the same user, and shows whether your backend refuses both. You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding | BOT Notification 4/2568 on Security of Mobile Financial and Payment Services for Financial Institutions, p. 4 (opens in a new tab) |
| 4/2568 ข้อ 5.3.1(4) | Binding rule You must add an identity check by face comparison with presentation attack detection, such as liveness detection, at least for a single transfer of 50,000 baht or more, each time transfers total another 200,000 baht in one day, and any raise of the daily transfer limit to 50,000 baht or more. You may waive the check for users who cannot use face comparison, such as visually impaired users, provided you have compensating risk-reduction measures. You may also waive it for low-risk transactions, such as transfers between the user's own accounts and automatic recurring transfers verified the first time. BOT's Q&A applies the check to every transfer type, including interbank, overseas, and PromptPay Thai QR transfers (Q&A 7). If mobile app; financial institutions under the Financial Institutions Businesses Act, not specialized financial institutions | Testing runs transfers at each threshold and a daily limit raise, then tries to skip or replay the face comparison step against your server, and shows whether the check holds server side. You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding | BOT Notification 4/2568 on Security of Mobile Financial and Payment Services for Financial Institutions, p. 4 (opens in a new tab) |
| 4/2568 ข้อ 5.3.1(5) | Binding rule You must set a maximum daily limit for withdrawals or transfers that fits the risk level of each user group. For example, cap users under 15 at no more than 50,000 baht a day. You may use an industry standard to set risk levels or group caps. When a user asks to be exempt from their group's cap, you must have a clear and strict process to consider it. BOT's Q&A lists identity proof, the reason, the criteria, and a clear risk notice for such an exemption (Q&A 9). If mobile app; financial institutions under the Financial Institutions Businesses Act, not specialized financial institutions | Testing sends transactions past your daily cap straight to the API, and shows whether your server enforces the cap when the app is bypassed. You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding | BOT Notification 4/2568 on Security of Mobile Financial and Payment Services for Financial Institutions, p. 5 (opens in a new tab) |
| 4/2568 ข้อ 5.3.2(1.1) | Binding rule You must avoid storing sensitive data, such as authentication or personal data, on the mobile device. If you must store it, you must protect it strictly, at least by encrypting it with a secure method that meets international standards and destroying it at the end of use. If mobile app; financial institutions under the Financial Institutions Businesses Act, not specialized financial institutions | A local storage review of the installed app shows which sensitive data it keeps on the device, whether that data is encrypted, and whether it is destroyed at the end of use. You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding | BOT Notification 4/2568 on Security of Mobile Financial and Payment Services for Financial Institutions, p. 5 (opens in a new tab) |
| 4/2568 ข้อ 5.3.2(1.2) | Binding rule Your app must show users' sensitive information only as far as needed and securely, and at least must mask passwords and blur the screen when the app is minimized (application blurring). If mobile app; financial institutions under the Financial Institutions Businesses Act, not specialized financial institutions | Testing checks password masking and the app-switcher snapshot, and shows whether sensitive data stays hidden while your app sits in the background. You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding | BOT Notification 4/2568 on Security of Mobile Financial and Payment Services for Financial Institutions, p. 5 (opens in a new tab) |
| 4/2568 ข้อ 5.3.2(1.3) | Binding rule You must use a secure protocol and authenticate with certificate pinning or an equivalent method, and you must also encrypt sensitive data at the application layer in transit, to prevent man-in-the-middle attacks. If mobile app; financial institutions under the Financial Institutions Businesses Act, not specialized financial institutions | Man-in-the-middle testing with a certificate pinning bypass attempt shows whether an attacker on the network can read or change your app's traffic, and whether sensitive data is also encrypted at the application layer. You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding | BOT Notification 4/2568 on Security of Mobile Financial and Payment Services for Financial Institutions, p. 5 (opens in a new tab) |
| 4/2568 ข้อ 5.3.2(2.1) | Binding rule Your app must request access to device resources and services (application permission) only as needed, and you must review those permissions on every significant change to the app. If mobile app; financial institutions under the Financial Institutions Businesses Act, not specialized financial institutions | A manifest and runtime permission review shows which permissions your app requests beyond what its functions need. You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding | BOT Notification 4/2568 on Security of Mobile Financial and Payment Services for Financial Institutions, p. 6 (opens in a new tab) |
| 4/2568 ข้อ 5.3.2(2.2) | Binding rule You must not serve old versions of your app that may have vulnerabilities and could open the way to unauthorized transactions. If mobile app; financial institutions under the Financial Institutions Businesses Act, not specialized financial institutions | Testing runs an older build of your app against the current backend, and shows whether your server refuses to serve it. You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding | BOT Notification 4/2568 on Security of Mobile Financial and Payment Services for Financial Institutions, p. 6 (opens in a new tab) |
| 4/2568 ข้อ 5.3.2(2.3) | Binding rule You must check your app for modification every time a user opens it (anti-tampering), and must not let users run a modified app. If mobile app; financial institutions under the Financial Institutions Businesses Act, not specialized financial institutions | A repackaging test launches a modified build of your app, and shows whether anti-tampering detects it at launch and blocks use. You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding | BOT Notification 4/2568 on Security of Mobile Financial and Payment Services for Financial Institutions, p. 6 (opens in a new tab) |
| 4/2568 ข้อ 5.3.2(2.4) | Binding rule You must manage sessions securely to prevent unauthorized access by session hijacking. If mobile app; financial institutions under the Financial Institutions Businesses Act, not specialized financial institutions | Session testing replays and reuses tokens and checks their expiry, and shows whether an attacker could hijack a user's session. You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding | BOT Notification 4/2568 on Security of Mobile Financial and Payment Services for Financial Institutions, p. 6 (opens in a new tab) |
| 4/2568 ข้อ 5.3.2(2.5) | Binding rule You must keep your app's source code from being easy to read, for example with source code obfuscation. If mobile app; financial institutions under the Financial Institutions Businesses Act, not specialized financial institutions | Decompiling your app shows how easily an attacker can read its code and whether obfuscation slows reverse engineering. You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding | BOT Notification 4/2568 on Security of Mobile Financial and Payment Services for Financial Institutions, p. 6 (opens in a new tab) |
| 4/2568 ข้อ 5.3.2(3.1) | Binding rule Your app must not run on a mobile device detected as rooted or jailbroken. If mobile app; financial institutions under the Financial Institutions Businesses Act, not specialized financial institutions | Root and hooking detection testing runs your app on a rooted or jailbroken device and tries to bypass the check, and shows whether your app refuses to run. You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding | BOT Notification 4/2568 on Security of Mobile Financial and Payment Services for Financial Institutions, p. 6 (opens in a new tab) |
| 4/2568 ข้อ 5.3.2(3.2) | Binding rule Your app must not run while another app with risky behavior runs on the device, such as an app requesting accessibility services without need, a remote control app, or an app that covers or steals what is shown on screen. If mobile app; financial institutions under the Financial Institutions Businesses Act, not specialized financial institutions | Testing runs your app alongside an accessibility service, a remote control app, and a screen overlay, and shows whether your app stops working while they run. You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding | BOT Notification 4/2568 on Security of Mobile Financial and Payment Services for Financial Institutions, p. 6 (opens in a new tab) |
| 4/2568 ข้อ 5.3.2(3.3) | Binding rule You must avoid serving your app on devices running an operating system that a recognized security body, such as TB-CERT, flags as at risk of cyber attack or unauthorized transactions. If you still serve those devices, you must add risk controls, warn the user of the risk, and limit that user group to transfers of no more than 5,000 baht a day. This clause takes effect 60 days from the day after Royal Gazette publication; the rest of 4/2568 takes effect after 30 days (ข้อ 7). If mobile app; financial institutions under the Financial Institutions Businesses Act, not specialized financial institutions | Testing runs your app on an operating system flagged as risky, and shows whether it warns the user and whether your server holds those users to 5,000 baht of transfers a day. You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding | BOT Notification 4/2568 on Security of Mobile Financial and Payment Services for Financial Institutions, p. 7 (opens in a new tab) |
| 4/2568 ข้อ 5.3.2 closing paragraph | Binding rule You must keep monitoring and improving the security of your service against new cyber threats and fraud, in line with international standards. When a new vulnerability is found, you must act quickly to put protection in place and close it within a suitable timeframe or within the period BOT sets. If mobile app; financial institutions under the Financial Institutions Businesses Act, not specialized financial institutions | One retest of every Critical and High finding, after your team fixes them, shows which fixes closed their vulnerabilities. Closing new vulnerabilities in time stays your duty. You receive: Report updated after the retest, recording which Critical and High fixes held and the residual risk that remains | BOT Notification 4/2568 on Security of Mobile Financial and Payment Services for Financial Institutions, p. 7 (opens in a new tab) |
4/2568 ข้อ 5.3.1(1)
Binding rule- What the rule says
- You must not attach links of any kind to SMS or email, including URL text that cannot be clicked, images showing a URL, clickable images, and QR codes (Q&A 2). On social media, you must not attach links that ask for identity verification or personal data. You may attach a link on any of the three channels when the user requests it, one request at a time, and you must remind the user that it was sent only because they asked (Q&A 3).
- If mobile app; financial institutions under the Financial Institutions Businesses Act, not specialized financial institutions
- What Reconix testing proves
No Reconix assessment covers this duty.
4/2568 ข้อ 5.3.1(2)
Binding rule- What the rule says
- You must have a process to monitor and respond in time to fake apps or apps impersonating yours in official app stores, such as Google Play Store and Apple App Store, and a process to respond to fake apps outside those stores. BOT's Q&A says the process must at least name an owner, set the response and takedown steps, and set a deadline for each step (Q&A 4), and counts Huawei AppGallery and Samsung Galaxy Store as official stores (Q&A 5).
- If mobile app; financial institutions under the Financial Institutions Businesses Act, not specialized financial institutions
- What Reconix testing proves
No Reconix assessment covers this duty.
Group service from BAYCOMS (opens in a new tab) and ECOP (opens in a new tab): digital risk protection
4/2568 ข้อ 5.3.1(3)
Binding rule- What the rule says
- You must limit each user to one user account per Mobile Banking service at your institution, used on one mobile device only. If you run more than one Mobile Banking app, the limit applies to each app (Q&A 6).
- If mobile app; financial institutions under the Financial Institutions Businesses Act, not specialized financial institutions
- What Reconix testing proves
A MASTG-based test tries to enroll a second device and a second user account for the same user, and shows whether your backend refuses both.
You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding
4/2568 ข้อ 5.3.1(4)
Binding rule- What the rule says
- You must add an identity check by face comparison with presentation attack detection, such as liveness detection, at least for a single transfer of 50,000 baht or more, each time transfers total another 200,000 baht in one day, and any raise of the daily transfer limit to 50,000 baht or more. You may waive the check for users who cannot use face comparison, such as visually impaired users, provided you have compensating risk-reduction measures. You may also waive it for low-risk transactions, such as transfers between the user's own accounts and automatic recurring transfers verified the first time. BOT's Q&A applies the check to every transfer type, including interbank, overseas, and PromptPay Thai QR transfers (Q&A 7).
- If mobile app; financial institutions under the Financial Institutions Businesses Act, not specialized financial institutions
- What Reconix testing proves
Testing runs transfers at each threshold and a daily limit raise, then tries to skip or replay the face comparison step against your server, and shows whether the check holds server side.
You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding
4/2568 ข้อ 5.3.1(5)
Binding rule- What the rule says
- You must set a maximum daily limit for withdrawals or transfers that fits the risk level of each user group. For example, cap users under 15 at no more than 50,000 baht a day. You may use an industry standard to set risk levels or group caps. When a user asks to be exempt from their group's cap, you must have a clear and strict process to consider it. BOT's Q&A lists identity proof, the reason, the criteria, and a clear risk notice for such an exemption (Q&A 9).
- If mobile app; financial institutions under the Financial Institutions Businesses Act, not specialized financial institutions
- What Reconix testing proves
Testing sends transactions past your daily cap straight to the API, and shows whether your server enforces the cap when the app is bypassed.
You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding
4/2568 ข้อ 5.3.2(1.1)
Binding rule- What the rule says
- You must avoid storing sensitive data, such as authentication or personal data, on the mobile device. If you must store it, you must protect it strictly, at least by encrypting it with a secure method that meets international standards and destroying it at the end of use.
- If mobile app; financial institutions under the Financial Institutions Businesses Act, not specialized financial institutions
- What Reconix testing proves
A local storage review of the installed app shows which sensitive data it keeps on the device, whether that data is encrypted, and whether it is destroyed at the end of use.
You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding
4/2568 ข้อ 5.3.2(1.2)
Binding rule- What the rule says
- Your app must show users' sensitive information only as far as needed and securely, and at least must mask passwords and blur the screen when the app is minimized (application blurring).
- If mobile app; financial institutions under the Financial Institutions Businesses Act, not specialized financial institutions
- What Reconix testing proves
Testing checks password masking and the app-switcher snapshot, and shows whether sensitive data stays hidden while your app sits in the background.
You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding
4/2568 ข้อ 5.3.2(1.3)
Binding rule- What the rule says
- You must use a secure protocol and authenticate with certificate pinning or an equivalent method, and you must also encrypt sensitive data at the application layer in transit, to prevent man-in-the-middle attacks.
- If mobile app; financial institutions under the Financial Institutions Businesses Act, not specialized financial institutions
- What Reconix testing proves
Man-in-the-middle testing with a certificate pinning bypass attempt shows whether an attacker on the network can read or change your app's traffic, and whether sensitive data is also encrypted at the application layer.
You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding
4/2568 ข้อ 5.3.2(2.1)
Binding rule- What the rule says
- Your app must request access to device resources and services (application permission) only as needed, and you must review those permissions on every significant change to the app.
- If mobile app; financial institutions under the Financial Institutions Businesses Act, not specialized financial institutions
- What Reconix testing proves
A manifest and runtime permission review shows which permissions your app requests beyond what its functions need.
You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding
4/2568 ข้อ 5.3.2(2.2)
Binding rule- What the rule says
- You must not serve old versions of your app that may have vulnerabilities and could open the way to unauthorized transactions.
- If mobile app; financial institutions under the Financial Institutions Businesses Act, not specialized financial institutions
- What Reconix testing proves
Testing runs an older build of your app against the current backend, and shows whether your server refuses to serve it.
You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding
4/2568 ข้อ 5.3.2(2.3)
Binding rule- What the rule says
- You must check your app for modification every time a user opens it (anti-tampering), and must not let users run a modified app.
- If mobile app; financial institutions under the Financial Institutions Businesses Act, not specialized financial institutions
- What Reconix testing proves
A repackaging test launches a modified build of your app, and shows whether anti-tampering detects it at launch and blocks use.
You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding
4/2568 ข้อ 5.3.2(2.4)
Binding rule- What the rule says
- You must manage sessions securely to prevent unauthorized access by session hijacking.
- If mobile app; financial institutions under the Financial Institutions Businesses Act, not specialized financial institutions
- What Reconix testing proves
Session testing replays and reuses tokens and checks their expiry, and shows whether an attacker could hijack a user's session.
You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding
4/2568 ข้อ 5.3.2(2.5)
Binding rule- What the rule says
- You must keep your app's source code from being easy to read, for example with source code obfuscation.
- If mobile app; financial institutions under the Financial Institutions Businesses Act, not specialized financial institutions
- What Reconix testing proves
Decompiling your app shows how easily an attacker can read its code and whether obfuscation slows reverse engineering.
You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding
4/2568 ข้อ 5.3.2(3.1)
Binding rule- What the rule says
- Your app must not run on a mobile device detected as rooted or jailbroken.
- If mobile app; financial institutions under the Financial Institutions Businesses Act, not specialized financial institutions
- What Reconix testing proves
Root and hooking detection testing runs your app on a rooted or jailbroken device and tries to bypass the check, and shows whether your app refuses to run.
You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding
4/2568 ข้อ 5.3.2(3.2)
Binding rule- What the rule says
- Your app must not run while another app with risky behavior runs on the device, such as an app requesting accessibility services without need, a remote control app, or an app that covers or steals what is shown on screen.
- If mobile app; financial institutions under the Financial Institutions Businesses Act, not specialized financial institutions
- What Reconix testing proves
Testing runs your app alongside an accessibility service, a remote control app, and a screen overlay, and shows whether your app stops working while they run.
You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding
4/2568 ข้อ 5.3.2(3.3)
Binding rule- What the rule says
- You must avoid serving your app on devices running an operating system that a recognized security body, such as TB-CERT, flags as at risk of cyber attack or unauthorized transactions. If you still serve those devices, you must add risk controls, warn the user of the risk, and limit that user group to transfers of no more than 5,000 baht a day. This clause takes effect 60 days from the day after Royal Gazette publication; the rest of 4/2568 takes effect after 30 days (ข้อ 7).
- If mobile app; financial institutions under the Financial Institutions Businesses Act, not specialized financial institutions
- What Reconix testing proves
Testing runs your app on an operating system flagged as risky, and shows whether it warns the user and whether your server holds those users to 5,000 baht of transfers a day.
You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding
4/2568 ข้อ 5.3.2 closing paragraph
Binding rule- What the rule says
- You must keep monitoring and improving the security of your service against new cyber threats and fraud, in line with international standards. When a new vulnerability is found, you must act quickly to put protection in place and close it within a suitable timeframe or within the period BOT sets.
- If mobile app; financial institutions under the Financial Institutions Businesses Act, not specialized financial institutions
- What Reconix testing proves
One retest of every Critical and High finding, after your team fixes them, shows which fixes closed their vulnerabilities. Closing new vulnerabilities in time stays your duty.
You receive: Report updated after the retest, recording which Critical and High fixes held and the residual risk that remains
E-money operator duties under 18/2568, by clause
| Clause | What the rule says | What Reconix testing proves | Source |
|---|---|---|---|
| 18/2568 ข้อ 5.2.1(1) | Binding rule You must not attach links of any kind to SMS or email, including URL text that cannot be clicked, images showing a URL, clickable images, and QR codes (Q&A 2). On social media, you must not attach links that ask for identity verification or personal data. You may attach a link on any of the three channels when the user requests it, one request at a time, and you must remind the user that it was sent only because they asked (Q&A 3). If e-money licensee with an app that transfers to accounts at other providers | No Reconix assessment covers this duty. | BOT Notification 18/2568 on Security of Mobile Financial and Payment Services for E-Money Operators Providing e-Money Mobile Applications, p. 4 (opens in a new tab) |
| 18/2568 ข้อ 5.2.1(2) | Binding rule You must have a process to monitor and respond in time to fake apps or apps impersonating yours in official app stores, such as Google Play Store and Apple App Store, and a process to respond to fake apps outside those stores. BOT's Q&A says the process must at least name an owner, set the response and takedown steps, and set a deadline for each step (Q&A 4), and counts Huawei AppGallery and Samsung Galaxy Store as official stores (Q&A 5). If e-money licensee with an app that transfers to accounts at other providers | No Reconix assessment covers this duty. Group service from BAYCOMS (opens in a new tab) and ECOP (opens in a new tab): digital risk protection | BOT Notification 18/2568 on Security of Mobile Financial and Payment Services for E-Money Operators Providing e-Money Mobile Applications, p. 5 (opens in a new tab) |
| 18/2568 ข้อ 5.2.1(3) | Binding rule You must limit each user to using each of your e-Money Mobile Application apps on one mobile device only, so others cannot use e-money accounts as mule accounts. BOT's Q&A reads this as one device at any one time: a device change needs a new identity check and revokes the old device, and if you allow more than one user account, every account is limited to one device at a time (Q&A 6). This clause takes effect 90 days from the day after Royal Gazette publication; the rest of 18/2568 takes effect after 30 days (ข้อ 7). If e-money licensee with an app that transfers to accounts at other providers | A MASTG-based test logs in from a second device while the first is still active, and shows whether your backend refuses it or revokes the old device. You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding | BOT Notification 18/2568 on Security of Mobile Financial and Payment Services for E-Money Operators Providing e-Money Mobile Applications, p. 5 (opens in a new tab) |
| 18/2568 ข้อ 5.2.1(4) | Binding rule You must add an identity check by face comparison with presentation attack detection, such as liveness detection, at least for a single transfer of 50,000 baht or more, each time transfers total another 200,000 baht in one day, and any raise of the daily transfer limit to 50,000 baht or more. You may waive the check for users who cannot use face comparison, such as visually impaired users, provided you have compensating risk-reduction measures. You may also waive it for low-risk transactions, such as transfers between the user's own accounts and automatic recurring transfers verified the first time. BOT's Q&A applies the check to every transfer type, including transfers between e-money accounts with you (close loop), to accounts at other providers, overseas, and by PromptPay Thai QR (Q&A 7), and to foreign users as well (Q&A 9). If e-money licensee with an app that transfers to accounts at other providers | Testing runs transfers at each threshold and a daily limit raise, then tries to skip or replay the face comparison step against your server, and shows whether the check holds server side. You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding | BOT Notification 18/2568 on Security of Mobile Financial and Payment Services for E-Money Operators Providing e-Money Mobile Applications, p. 5 (opens in a new tab) |
| 18/2568 ข้อ 5.2.1(5) | Binding rule You must set a maximum daily limit for transfers that fits the risk level of each user group. For example, cap users under 15 at no more than 50,000 baht a day. You may use an industry standard to set risk levels or group caps. When a user asks to be exempt from their group's cap, you must have a clear and strict process to consider it. BOT's Q&A lists identity proof, the reason, the criteria, and a clear risk notice for such an exemption (Q&A 10). If e-money licensee with an app that transfers to accounts at other providers | Testing sends transactions past your daily cap straight to the API, and shows whether your server enforces the cap when the app is bypassed. You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding | BOT Notification 18/2568 on Security of Mobile Financial and Payment Services for E-Money Operators Providing e-Money Mobile Applications, p. 6 (opens in a new tab) |
| 18/2568 ข้อ 5.2.2(1.1) | Binding rule You must avoid storing sensitive data, such as authentication or personal data, on the mobile device. If you must store it, you must protect it strictly, at least by encrypting it with a secure method that meets international standards and destroying it at the end of use. If e-money licensee with an app that transfers to accounts at other providers | A local storage review of the installed app shows which sensitive data it keeps on the device, whether that data is encrypted, and whether it is destroyed at the end of use. You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding | BOT Notification 18/2568 on Security of Mobile Financial and Payment Services for E-Money Operators Providing e-Money Mobile Applications, p. 6 (opens in a new tab) |
| 18/2568 ข้อ 5.2.2(1.2) | Binding rule Your app must show users' sensitive information only as far as needed and securely, and at least must mask passwords and blur the screen when the app is minimized (application blurring). If e-money licensee with an app that transfers to accounts at other providers | Testing checks password masking and the app-switcher snapshot, and shows whether sensitive data stays hidden while your app sits in the background. You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding | BOT Notification 18/2568 on Security of Mobile Financial and Payment Services for E-Money Operators Providing e-Money Mobile Applications, p. 7 (opens in a new tab) |
| 18/2568 ข้อ 5.2.2(1.3) | Binding rule You must use a secure protocol and authenticate with certificate pinning or an equivalent method, and you must also encrypt sensitive data at the application layer in transit, to prevent man-in-the-middle attacks. If e-money licensee with an app that transfers to accounts at other providers | Man-in-the-middle testing with a certificate pinning bypass attempt shows whether an attacker on the network can read or change your app's traffic, and whether sensitive data is also encrypted at the application layer. You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding | BOT Notification 18/2568 on Security of Mobile Financial and Payment Services for E-Money Operators Providing e-Money Mobile Applications, p. 7 (opens in a new tab) |
| 18/2568 ข้อ 5.2.2(2.1) | Binding rule Your app must request access to device resources and services (application permission) only as needed, and you must review those permissions on every significant change to the app. If e-money licensee with an app that transfers to accounts at other providers | A manifest and runtime permission review shows which permissions your app requests beyond what its functions need. You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding | BOT Notification 18/2568 on Security of Mobile Financial and Payment Services for E-Money Operators Providing e-Money Mobile Applications, p. 7 (opens in a new tab) |
| 18/2568 ข้อ 5.2.2(2.2) | Binding rule You must not serve old versions of your app that may have vulnerabilities and could open the way to unauthorized transactions. If e-money licensee with an app that transfers to accounts at other providers | Testing runs an older build of your app against the current backend, and shows whether your server refuses to serve it. You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding | BOT Notification 18/2568 on Security of Mobile Financial and Payment Services for E-Money Operators Providing e-Money Mobile Applications, p. 7 (opens in a new tab) |
| 18/2568 ข้อ 5.2.2(2.3) | Binding rule You must check your app for modification every time a user opens it (anti-tampering), and must not let users run a modified app. This clause takes effect 90 days from the day after Royal Gazette publication; the rest of 18/2568 takes effect after 30 days (ข้อ 7). If e-money licensee with an app that transfers to accounts at other providers | A repackaging test launches a modified build of your app, and shows whether anti-tampering detects it at launch and blocks use. You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding | BOT Notification 18/2568 on Security of Mobile Financial and Payment Services for E-Money Operators Providing e-Money Mobile Applications, p. 7 (opens in a new tab) |
| 18/2568 ข้อ 5.2.2(2.4) | Binding rule You must manage sessions securely to prevent unauthorized access by session hijacking. If e-money licensee with an app that transfers to accounts at other providers | Session testing replays and reuses tokens and checks their expiry, and shows whether an attacker could hijack a user's session. You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding | BOT Notification 18/2568 on Security of Mobile Financial and Payment Services for E-Money Operators Providing e-Money Mobile Applications, p. 7 (opens in a new tab) |
| 18/2568 ข้อ 5.2.2(2.5) | Binding rule You must keep your app's source code from being easy to read, for example with source code obfuscation. If e-money licensee with an app that transfers to accounts at other providers | Decompiling your app shows how easily an attacker can read its code and whether obfuscation slows reverse engineering. You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding | BOT Notification 18/2568 on Security of Mobile Financial and Payment Services for E-Money Operators Providing e-Money Mobile Applications, p. 7 (opens in a new tab) |
| 18/2568 ข้อ 5.2.2(3.1) | Binding rule Your app must not run on a mobile device detected as rooted or jailbroken. If e-money licensee with an app that transfers to accounts at other providers | Root and hooking detection testing runs your app on a rooted or jailbroken device and tries to bypass the check, and shows whether your app refuses to run. You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding | BOT Notification 18/2568 on Security of Mobile Financial and Payment Services for E-Money Operators Providing e-Money Mobile Applications, p. 8 (opens in a new tab) |
| 18/2568 ข้อ 5.2.2(3.2) | Binding rule Your app must not run while another app with risky behavior runs on the device, such as an app requesting accessibility services without need, a remote control app, or an app that covers or steals what is shown on screen. This clause takes effect 90 days from the day after Royal Gazette publication; the rest of 18/2568 takes effect after 30 days (ข้อ 7). If e-money licensee with an app that transfers to accounts at other providers | Testing runs your app alongside an accessibility service, a remote control app, and a screen overlay, and shows whether your app stops working while they run. You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding | BOT Notification 18/2568 on Security of Mobile Financial and Payment Services for E-Money Operators Providing e-Money Mobile Applications, p. 8 (opens in a new tab) |
| 18/2568 ข้อ 5.2.2(3.3) | Binding rule You must avoid serving your app on devices running an operating system that a recognized security body, such as TB-CERT, flags as at risk of cyber attack or unauthorized transactions. If you still serve those devices, you must add risk controls, for example allowing transfers only to the user's own accounts, a daily transfer cap that fits the user group's risk, or added face comparison when the user makes a financial transaction, and you must warn the user of the risk. BOT's Q&A says you should avoid such devices and may consult BOT before serving them (Q&A 11). This clause takes effect 90 days from the day after Royal Gazette publication; the rest of 18/2568 takes effect after 30 days (ข้อ 7). If e-money licensee with an app that transfers to accounts at other providers | Testing runs your app on an operating system flagged as risky, and shows whether it warns the user and which added risk control your server applies. You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding | BOT Notification 18/2568 on Security of Mobile Financial and Payment Services for E-Money Operators Providing e-Money Mobile Applications, p. 8 (opens in a new tab) |
| 18/2568 ข้อ 5.2.2 closing paragraph | Binding rule You must keep monitoring and improving the security of your service against new cyber threats and fraud, in line with international standards. When a new vulnerability is found, you must act quickly to put protection in place and close it within a suitable timeframe or within the period BOT sets. If e-money licensee with an app that transfers to accounts at other providers | One retest of every Critical and High finding, after your team fixes them, shows which fixes closed their vulnerabilities. Closing new vulnerabilities in time stays your duty. You receive: Report updated after the retest, recording which Critical and High fixes held and the residual risk that remains | BOT Notification 18/2568 on Security of Mobile Financial and Payment Services for E-Money Operators Providing e-Money Mobile Applications, p. 8 (opens in a new tab) |
18/2568 ข้อ 5.2.1(1)
Binding rule- What the rule says
- You must not attach links of any kind to SMS or email, including URL text that cannot be clicked, images showing a URL, clickable images, and QR codes (Q&A 2). On social media, you must not attach links that ask for identity verification or personal data. You may attach a link on any of the three channels when the user requests it, one request at a time, and you must remind the user that it was sent only because they asked (Q&A 3).
- If e-money licensee with an app that transfers to accounts at other providers
- What Reconix testing proves
No Reconix assessment covers this duty.
18/2568 ข้อ 5.2.1(2)
Binding rule- What the rule says
- You must have a process to monitor and respond in time to fake apps or apps impersonating yours in official app stores, such as Google Play Store and Apple App Store, and a process to respond to fake apps outside those stores. BOT's Q&A says the process must at least name an owner, set the response and takedown steps, and set a deadline for each step (Q&A 4), and counts Huawei AppGallery and Samsung Galaxy Store as official stores (Q&A 5).
- If e-money licensee with an app that transfers to accounts at other providers
- What Reconix testing proves
No Reconix assessment covers this duty.
Group service from BAYCOMS (opens in a new tab) and ECOP (opens in a new tab): digital risk protection
18/2568 ข้อ 5.2.1(3)
Binding rule- What the rule says
- You must limit each user to using each of your e-Money Mobile Application apps on one mobile device only, so others cannot use e-money accounts as mule accounts. BOT's Q&A reads this as one device at any one time: a device change needs a new identity check and revokes the old device, and if you allow more than one user account, every account is limited to one device at a time (Q&A 6). This clause takes effect 90 days from the day after Royal Gazette publication; the rest of 18/2568 takes effect after 30 days (ข้อ 7).
- If e-money licensee with an app that transfers to accounts at other providers
- What Reconix testing proves
A MASTG-based test logs in from a second device while the first is still active, and shows whether your backend refuses it or revokes the old device.
You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding
18/2568 ข้อ 5.2.1(4)
Binding rule- What the rule says
- You must add an identity check by face comparison with presentation attack detection, such as liveness detection, at least for a single transfer of 50,000 baht or more, each time transfers total another 200,000 baht in one day, and any raise of the daily transfer limit to 50,000 baht or more. You may waive the check for users who cannot use face comparison, such as visually impaired users, provided you have compensating risk-reduction measures. You may also waive it for low-risk transactions, such as transfers between the user's own accounts and automatic recurring transfers verified the first time. BOT's Q&A applies the check to every transfer type, including transfers between e-money accounts with you (close loop), to accounts at other providers, overseas, and by PromptPay Thai QR (Q&A 7), and to foreign users as well (Q&A 9).
- If e-money licensee with an app that transfers to accounts at other providers
- What Reconix testing proves
Testing runs transfers at each threshold and a daily limit raise, then tries to skip or replay the face comparison step against your server, and shows whether the check holds server side.
You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding
18/2568 ข้อ 5.2.1(5)
Binding rule- What the rule says
- You must set a maximum daily limit for transfers that fits the risk level of each user group. For example, cap users under 15 at no more than 50,000 baht a day. You may use an industry standard to set risk levels or group caps. When a user asks to be exempt from their group's cap, you must have a clear and strict process to consider it. BOT's Q&A lists identity proof, the reason, the criteria, and a clear risk notice for such an exemption (Q&A 10).
- If e-money licensee with an app that transfers to accounts at other providers
- What Reconix testing proves
Testing sends transactions past your daily cap straight to the API, and shows whether your server enforces the cap when the app is bypassed.
You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding
18/2568 ข้อ 5.2.2(1.1)
Binding rule- What the rule says
- You must avoid storing sensitive data, such as authentication or personal data, on the mobile device. If you must store it, you must protect it strictly, at least by encrypting it with a secure method that meets international standards and destroying it at the end of use.
- If e-money licensee with an app that transfers to accounts at other providers
- What Reconix testing proves
A local storage review of the installed app shows which sensitive data it keeps on the device, whether that data is encrypted, and whether it is destroyed at the end of use.
You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding
18/2568 ข้อ 5.2.2(1.2)
Binding rule- What the rule says
- Your app must show users' sensitive information only as far as needed and securely, and at least must mask passwords and blur the screen when the app is minimized (application blurring).
- If e-money licensee with an app that transfers to accounts at other providers
- What Reconix testing proves
Testing checks password masking and the app-switcher snapshot, and shows whether sensitive data stays hidden while your app sits in the background.
You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding
18/2568 ข้อ 5.2.2(1.3)
Binding rule- What the rule says
- You must use a secure protocol and authenticate with certificate pinning or an equivalent method, and you must also encrypt sensitive data at the application layer in transit, to prevent man-in-the-middle attacks.
- If e-money licensee with an app that transfers to accounts at other providers
- What Reconix testing proves
Man-in-the-middle testing with a certificate pinning bypass attempt shows whether an attacker on the network can read or change your app's traffic, and whether sensitive data is also encrypted at the application layer.
You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding
18/2568 ข้อ 5.2.2(2.1)
Binding rule- What the rule says
- Your app must request access to device resources and services (application permission) only as needed, and you must review those permissions on every significant change to the app.
- If e-money licensee with an app that transfers to accounts at other providers
- What Reconix testing proves
A manifest and runtime permission review shows which permissions your app requests beyond what its functions need.
You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding
18/2568 ข้อ 5.2.2(2.2)
Binding rule- What the rule says
- You must not serve old versions of your app that may have vulnerabilities and could open the way to unauthorized transactions.
- If e-money licensee with an app that transfers to accounts at other providers
- What Reconix testing proves
Testing runs an older build of your app against the current backend, and shows whether your server refuses to serve it.
You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding
18/2568 ข้อ 5.2.2(2.3)
Binding rule- What the rule says
- You must check your app for modification every time a user opens it (anti-tampering), and must not let users run a modified app. This clause takes effect 90 days from the day after Royal Gazette publication; the rest of 18/2568 takes effect after 30 days (ข้อ 7).
- If e-money licensee with an app that transfers to accounts at other providers
- What Reconix testing proves
A repackaging test launches a modified build of your app, and shows whether anti-tampering detects it at launch and blocks use.
You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding
18/2568 ข้อ 5.2.2(2.4)
Binding rule- What the rule says
- You must manage sessions securely to prevent unauthorized access by session hijacking.
- If e-money licensee with an app that transfers to accounts at other providers
- What Reconix testing proves
Session testing replays and reuses tokens and checks their expiry, and shows whether an attacker could hijack a user's session.
You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding
18/2568 ข้อ 5.2.2(2.5)
Binding rule- What the rule says
- You must keep your app's source code from being easy to read, for example with source code obfuscation.
- If e-money licensee with an app that transfers to accounts at other providers
- What Reconix testing proves
Decompiling your app shows how easily an attacker can read its code and whether obfuscation slows reverse engineering.
You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding
18/2568 ข้อ 5.2.2(3.1)
Binding rule- What the rule says
- Your app must not run on a mobile device detected as rooted or jailbroken.
- If e-money licensee with an app that transfers to accounts at other providers
- What Reconix testing proves
Root and hooking detection testing runs your app on a rooted or jailbroken device and tries to bypass the check, and shows whether your app refuses to run.
You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding
18/2568 ข้อ 5.2.2(3.2)
Binding rule- What the rule says
- Your app must not run while another app with risky behavior runs on the device, such as an app requesting accessibility services without need, a remote control app, or an app that covers or steals what is shown on screen. This clause takes effect 90 days from the day after Royal Gazette publication; the rest of 18/2568 takes effect after 30 days (ข้อ 7).
- If e-money licensee with an app that transfers to accounts at other providers
- What Reconix testing proves
Testing runs your app alongside an accessibility service, a remote control app, and a screen overlay, and shows whether your app stops working while they run.
You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding
18/2568 ข้อ 5.2.2(3.3)
Binding rule- What the rule says
- You must avoid serving your app on devices running an operating system that a recognized security body, such as TB-CERT, flags as at risk of cyber attack or unauthorized transactions. If you still serve those devices, you must add risk controls, for example allowing transfers only to the user's own accounts, a daily transfer cap that fits the user group's risk, or added face comparison when the user makes a financial transaction, and you must warn the user of the risk. BOT's Q&A says you should avoid such devices and may consult BOT before serving them (Q&A 11). This clause takes effect 90 days from the day after Royal Gazette publication; the rest of 18/2568 takes effect after 30 days (ข้อ 7).
- If e-money licensee with an app that transfers to accounts at other providers
- What Reconix testing proves
Testing runs your app on an operating system flagged as risky, and shows whether it warns the user and which added risk control your server applies.
You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding
18/2568 ข้อ 5.2.2 closing paragraph
Binding rule- What the rule says
- You must keep monitoring and improving the security of your service against new cyber threats and fraud, in line with international standards. When a new vulnerability is found, you must act quickly to put protection in place and close it within a suitable timeframe or within the period BOT sets.
- If e-money licensee with an app that transfers to accounts at other providers
- What Reconix testing proves
One retest of every Critical and High finding, after your team fixes them, shows which fixes closed their vulnerabilities. Closing new vulnerabilities in time stays your duty.
You receive: Report updated after the retest, recording which Critical and High fixes held and the residual risk that remains
What We Test in Your Mobile App
4/2568 sets controls and contains no testing clause. We verify each control with a test based on the OWASP MASTG, a Reconix method mapped clause by clause to the notification.
Duties That Continue After Launch
These four duties create work after go-live, and each one needs evidence when BOT asks.
Close New Vulnerabilities in Time
When a new vulnerability is found, you must put protection in place and close it within a suitable time, or by the deadline BOT sets (4/2568 clause 5.3.2 and 18/2568 clause 5.2.2, closing paragraphs).
Waivers Are Case by Case
An institution that cannot meet a control must apply to BOT with its reasons and a plan to comply. BOT decides within 30 business days of a complete request and may add conditions (clause 5.4).
App-in-App Counts
The controls apply whether users reach Mobile Banking through the institution's own app or through another provider's app (Q&A item 1).
Risky Operating Systems
Under 4/2568, if you still serve operating systems flagged as risky, you must warn those users and cap their transfers at ฿5,000 a day (clause 5.3.2(3.3)).
Related BOT Rules
4/2568 sets controls. The yearly penetration test and the e-money app rules sit in other BOT notifications.
BOT Notification 5/2566: IT Risk Supervision
Requires a penetration test by independent internal or external experts of Internet-facing systems at least once a year and on significant change (attachment 2, clause 6.7). BOT's Q&A names Mobile Banking as one of those systems (item 3). A security test is also due before go-live (attachment 2, clause 7.2). Covers financial institutions and specialized financial institutions.
BOT Notification 18/2568: e-Money Mobile Apps
E-money operator duties under 18/2568 have their own clause table on this page.Financial Institution Business Act B.E. 2551 (2008)
BOT issued 4/2568 under sections 39 and 41 of this Act, and the notification applies to every financial institution under it (clauses 2 and 4).
How a Reconix Mobile Test Runs Under 4/2568 and 18/2568
4/2568 (clause 5.3.2, closing paragraph) and 18/2568 (clause 5.2.2, closing paragraph) require you to close new vulnerabilities in a suitable time or by BOT's deadline. Reconix adds the rest: a test mapped to each control, run to the OWASP MASTG, a report with CVSS 4.0 severity and a PoC for every finding, and one retest of every Critical and High finding.
BOT 4/2568 Readiness Checklist
Use this checklist to gauge where your organization stands against each control in Notification 4/2568, plus the yearly penetration test under 5/2566.
Official References
Consult the original regulatory documents for full requirements.
Related Security Services
Complement your BOT compliance with these specialized security assessments.
Frequently Asked Questions
Everything you need to know about BOT Notification 4/2568 and mobile banking security compliance.
Close Your BOT 4/2568 Compliance Gaps
Get an assessment mapped to each control in Notification 4/2568, with a proof of concept for every finding and one retest of every Critical and High finding.
Reconix is the proof-first offensive security specialist for digital businesses in Thailand where a breach ends the business.