System positioning and regulatory adaptation
eDon™ It is a transaction monitoring (Transaction Monitoring) platform for financial institutions and licensed entities.，The core goal is to make "risk identification - investigation and evidence collection - regulatory submission - review and optimization" auditable、Quantifiable、Sustainable iterative process system。
Applicable institutions include：Hong Kong MSO、Virtual asset service provider、payment institution、Cross-border settlement platform、OTC and high-risk merchant acquiring entities。The system can be used with account opening KYC、List screening、customer ratings、Case management linkage，Form an end-to-end AML/CFT control chain。
If you plan payment and digital asset business at the same time，Can be combined Payment Gateway (PSP) Compliance、Hong Kong VASP License and VASP/FinTech Compliance Serve，Achieve parallel advancement of system and license compliance。
Alarm、case、Disposal records and STR materials can directly map regulatory inquiry standards，Reduce temporary supplementary materials。
Pass customer tiering thresholds、Scenario-based rules and historical feedback training，Gradually reduce the proportion of invalid alarms。
Rule version、manual review、Traces are left throughout the entire chain of approval flow and conclusion evidence，Support internal and external audits。
Smoothly expands from MSO scenario to VASP、PSP or multi-jurisdictional business model。
Core functional architecture
eDon TM recommends using “Data layer - detection layer - investigation layer - governance layer"Four-tier architecture：
1) data layer：Access transaction flow、Customer portrait、Equipment and IP、Counterparty information、List screening results。
2) detection layer：Rule engine (threshold/frequency/pattern) + scoring model (behavior deviation/relationship network/timing anomaly)。
3) investigation layer：Case assignment、Graded disposal、Certificate supplement list、Management review、Suspicious transaction reporting materials。
4) Governance：Rule versioning、Hit rate and false alarm rate monitoring、Parameter tuning、Model validation and annual lookback。
In terms of customer risk pre-positioning，Suggestions and financial risk assessment system and Hong Kong Xintong AML/CRM Compliance System Linkage，Ensure that high-risk customers enter a stricter monitoring track。
Support split transactions、short time high frequency、Closed loop reflow、Unusual geographic migration、Typical risk scenarios such as sudden surges at night。
By customer type、Trading products、Dynamically set monitoring thresholds by region and historical behavior，rather than one size fits all。
T+0/T+1 case time limit and upgrade path can be set，Ensure priority handling of high-risk events。
Output alarms by day/week/month、case、Disposal efficiency、Residual risk and regulatory reporting status。
Implementation process and delivery standards
Sort out the business model、Licensing requirements、Historical alarms and regulatory concerns，Define monitoring boundaries。
Complete field dictionary、Data quality check、Unification of customer and transaction primary keys。
Deploy basic rules and high-risk scenario rules in batches，Set initial thresholds and tiering strategies。
Run 4-8 week parallel period，hit rate、False alarm rate、Calibrate for risk of false negatives。
Establish investigation SOP、Approval and submission template，Form a reusable evidence chain。
Optimize rules by quarter，Complete model retrospective verification and audit data archiving on an annual basis。
If the organization is involved in business development in the United States or other regions，Can be referenced 2026The US MSB license just applied for，Experience sharing and US MSB license regulatory practices，Turn transaction monitoring strategies into multi-jurisdiction compatible templates。
Cost and Budget Reference
The service fees are subject to applicable jurisdiction、Business scope、Main structure、Data complexity and delivery schedule assessment；Involving government fees，The latest fees announced by the corresponding regulatory agency shall prevail.。
hint：When an organization introduces eDon TM，It is recommended to synchronize and improve Customized compliance documents and data governance mechanisms，To avoid the audit gap of "the system is online but the system is not closed loop"。
Rules and Case Closed Loop of Transaction Monitoring System
Transaction monitoring should be driven by risk assessment，Override rules、threshold、scene、manual judgment、Reporting and continuous optimization。Simply setting an amount threshold cannot replace risk-based monitoring.。
- by customer、product、nation、channel、frequency、Speed and correlation design risk scenarios。
- Record rule version、threshold basis、Model testing、False alarm rate and reasons for manual adjustments。
- Create alarm classification、investigation、Supplementary information、upgrade、Reporting and closing case process。
- Regularly backtest with known risks and historical cases，And have the effect reviewed by independent personnel。
Official verification：FATF recommendations。Specific obligations must be combined with the subject、business、Customer location and latest regulatory confirmation。
FAQ：5 issues that companies are most concerned about
cannot。Systems are used to amplify team capabilities and standardize processes，critical judgment、Upgrade decision-making and regulatory communication still need to be led by the compliance officer。
Check the data first、Customer stratification and rules，Then use the survey results to backtest and adjust parameters.，and simultaneously assess the risk of omissions。The extent and time of improvement must be verified with actual data，No guarantee of significant improvement in one to two quarters。 SeeSFC AML risks、Due Diligence and Continuous Monitoring Guidelines。
Look at rule interpretability、Alarm handling evidence chain、Model backtest verification、Management oversight records，And whether the system is consistent with the system。
The basis for processing should be checked、Required fields、Permissions、log、Storage and cross-border transfer；Implementing purpose limitations when GDPR applies、Minimization and safety requirements。Monitoring needs cannot automatically authorize unlimited collection or reuse。 SeeEU GDPR Official Regulations。
Cross-border、cash、Factors such as complex third-party funding and larger scale can affect risks，However, the deployment method must be combined with the overall assessment。Projects should select controls based on actual risks and requirements，One system cannot be used as a unified mandatory product。 SeeSFC AML risks、Due Diligence and Continuous Monitoring Guidelines。
KYC provides customer background and expected activity，Continuously monitor to determine whether actual transactions are consistent with this information。Should be able to communicate transactions with customers、Beneficial owner and review information link，rather than just looking at the amount。 SeeSFC AML risks、Due Diligence and Continuous Monitoring Guidelines。
It is recommended to check the customer identification、Amount、Currency、time、channel、counterparty、Status and Fund Flow Roles；Missing or different calibers will affect the effect of the rules。Fields and update frequency must be confirmed during interface acceptance。 SeeHong Kong Customs and Excise Department MSO Anti-Money Laundering Policy and System Procedure Guidelines。
Various transaction statuses and their risk implications should be clarified，区分重复传输与真实重复交易，并保留原始记录。避免把全部事件当作成功结算或把失败记录完全排除。
金额比较须明确汇率来源、换算时间和舍入方式，保留原币种及原金额。不能因换算或时区不同把相关交易错误拆开。
建立基于客户背景、业务目的及预期活动的合理比较，并考虑金额、frequency、counterparty、地区及组合变化。异常是调查线索，不自动等于违法。 SeeSFC AML risks、Due Diligence and Continuous Monitoring Guidelines。
no。内部阈值用于发现需调查的情形，可疑报告须按适用法律及事实判断；Structured or unusual transactions below the threshold may also require escalation。 SeeSFC AML risks、Due Diligence and Continuous Monitoring Guidelines。
Check the time window with authorized test samples、customer association、Currency、Counterparties and accumulation logic，and test for boundary values and missing data。Testing must not generate real transactions or mis-issue statutory reports。 SeeHong Kong Customs and Excise Department MSO Anti-Money Laundering Policy and System Procedure Guidelines。
To explain why a transaction triggered or did not trigger at that time，and who approved the changes。Should be able to correlate the effective time、Test and Survey Results，Avoid using new rules to explain past processing without explanation。 SeeSFC AML risks、Due Diligence and Continuous Monitoring Guidelines。
Recommendations based on risk classification、Assign responsibilities and escalate arrangements，Monitor overdue dates and resource bottlenecks，and document significant limitations。Uninvestigated alarms cannot be closed in batches just to reduce the quantity。 SeeSFC AML risks、Due Diligence and Continuous Monitoring Guidelines。
For example, "customers have always cooperated", "the system often reports false alarms" or business department requirements，is not enough to explain the specific facts。Close due investigation information、Conclusion and appropriate review，Unsolved doubts should be upgraded。 SeeSFC AML risks、Due Diligence and Continuous Monitoring Guidelines。
Subject to organizational authority、Contract and Applicable Legal Design，First distinguish and screen suspected hits、Real Sanctions and Other Anomalies。The basis for restriction or freezing is different in different situations.，Cannot be uniformly and automatically processed。 SeeSFC AML risks、Due Diligence and Continuous Monitoring Guidelines。
Don’t just look at the false alarm rate。Can be combined with identified events、risk sample、Untriggered transaction spot checks and data integrity testing，Explain coverage restrictions；After parameter adjustment, it should be verified that important risk patterns are not missed.。 SeeSFC AML risks、Due Diligence and Continuous Monitoring Guidelines。
The customer-payer or payee relationship should be understood、Reasonable purposes and sources of funds，Handle unexplained third-party transactions in conjunction with applicable policies。The system must provide the ability to record relationships and evidence。 SeeHong Kong Customs and Excise Department MSO Anti-Money Laundering Policy and System Procedure Guidelines。
应按机构所受法律及记录种类设置保存、访问和删除规则，并考虑诉讼或调查保留。适用GDPR时也须避免超过必要期限，不能全行业使用同一时长。 SeeEU GDPR Official Regulations。
应以约定业务场景、数据和验收标准测试导入、rule、Alarm、investigation、权限及导出，明确不支持或待改事项。产品名称或预设模板不能代替实际验收。
