Transaction monitoring software for the UAE, ADGM and DIFC

SonarPulse TMX is real-time transaction monitoring software for banks, payment providers and other firms in the UAE, ADGM and the DIFC. It screens every transaction as it happens on an ISO 20022-aligned schema, runs fraud, AML and sanctions rules in one engine, finds smurfing, layering and round-trip patterns across counterparties, explains every alert and generates goAML filings to the UAE FIU under four-eyes control. TMX runs on-premises inside your payment perimeter.

What the UAE asks of your monitoring and reporting

• STRs without delay, through goAML. Federal Decree by Law No. (10) of 2025, Article 18, requires a report to the UAE FIU without delay and directly; DIFC and ADGM firms file under the same law. DFSA Rule AML 13.3.1 also puts the MLRO’s inquiry under a without-delay duty and asks for the DFSA to be notified immediately after filing; FSRA Rule AML 14.3.1 does the same for the investigation in ADGM. STR deadlines compared.
• Suspension and freezing. Under Article (51) of Cabinet Resolution No. (134) of 2025, the FIU may suspend a suspected transaction without prior notice for up to ten working days, and freeze suspected funds for thirty days. Resolution 134/2025.
• Wire transfers. Originating institutions verify originator information on international wire transfers at or above AED 3,500 (Article 28); smaller transfers must still carry the data.
• The travel rule for virtual assets. ADGM’s rulebook now has its own section 10.3 for virtual asset and fiat-referenced token transfers, including transfers to or from unhosted wallets. The ADGM travel rule.
• Tipping off. Article 29 of Decree-Law 10/2025 punishes disclosing information about suspicious transactions under review with imprisonment and a fine of at least AED 50,000, or either.

How TMX monitors transactions

• Real-time ingestion. Transaction screening on an ISO 20022-aligned payment schema with country and currency validation.
• Fraud, AML and sanctions in one engine. Unified FRAML rule sets rather than three systems reconciled after the fact.
• Graph typologies. Smurfing, layering and round-trip patterns resolved across counterparties at depth.
• Behavioural signals. Velocity, geography and device history scored against a rolling baseline per subject.
• Machine-learning anomaly detection. Isolation-forest anomaly scoring under champion/challenger model governance with version tracking.
• Explainable decisions. A per-alert narrative rationale behind every APPROVE, FLAG or DENY, with the input vector retained.
• Travel rule screening. Originator and beneficiary screening with subject resolution (FATF Recommendation 16).
• goAML filing. goAML and FinCEN SAR generation under four-eyes control, over a tamper-evident SHA-256 hash-chain audit log.

Questions about transaction monitoring in the UAE

Can TMX file STRs to the UAE FIU through goAML?

Yes. TMX generates goAML filings under four-eyes control, and every step is written to a tamper-evident hash-chain audit log.

Does transaction data leave our premises?

No. TMX runs on-premises inside your payment perimeter. TMX Connect, on-premises middleware, feeds it from core banking and payment systems.

Is there a fixed number of days for filing an STR in the UAE?

No. Federal law says without delay and directly. The DFSA and FSRA rules add process: the MLRO’s inquiry and determination are themselves under a without-delay duty.

Further reading

• AML/CFT screening software for the UAE, ADGM and DIFC
• KYC, onboarding and identity verification software for the UAE, ADGM and DIFC
• STR deadlines across the six
• ADGM: virtual asset and fiat-referenced token transfers now have their own travel rule
• UAE: who can penalise a reporting entity, and for what