Language:
PRODUCTS
MORE
Quantum Security 🔍 Search Request Access →
gateFATF — Global AML Standard-Setting Gate
// IMMO.QUICK · GATEFATF · 40 RECOMMENDATIONS · CDD · WIRE TRANSFER RULE

The global floor, beneath every national law.

gateFATF forensically seals that a cross-border transaction passes four clusters, due diligence, PEP screening, wire-transfer data, and high-risk jurisdiction review, as the global baseline beneath every national AML law such as the GwG or the BSA. Support for globally active institutions, never a replacement for national regulatory recognition.

In one sentence: gateFATF checks every cross-border transaction against the global FATF minimum standard, regardless of which national law additionally applies.
✓ RELEVANT IF...
  • You process cross-border payments or customer relationships
  • You need to check transactions involving a FATF high-risk jurisdiction
✕ NOT RELEVANT IF...
  • You expect the FATF itself to recognise the result as national approval
  • No cross-border transaction or customer relationship is involved
// The problem

National AML laws build on a global foundation that is often overlooked.

The forty FATF recommendations are not law in the formal sense, but they are the template for the GwG, the BSA, and virtually every national anti-money-laundering law worldwide. gateFATF checks directly against this global standard, even where national implementation leaves gaps.

High-risk jurisdiction list as the fourth cluster
The FATF grey and black lists change several times a year. The gate checks every transaction against the currently valid list, not against an outdated internal copy.
// Architecture

4 clusters, checked sequentially.

Every cluster is dispositive (material_block_mode: true), a hit blocks bindingly, not merely for documentation.

CLUSTER 1
Customer Due Diligence (CDD)
Checks customer and beneficial-owner identification and verification under Recommendation 10.
customer_identified · ubo_verified
CLUSTER 2
PEP Screening
Checks screening against politically exposed persons under Recommendation 12, including enhanced due diligence on a hit.
pep_screening_completed · enhanced_dd_applied
CLUSTER 3
Wire Transfer Data
Checks complete originator and beneficiary information for cross-border wire transfers under Recommendation 16.
originator_data_complete · beneficiary_data_complete
CLUSTER 4
High-Risk Jurisdiction Review
Checks origin and destination jurisdictions against the current FATF grey and black lists and requires enhanced measures on a hit.
jurisdiction_risk_list_checked · enhanced_measures_applied
No case, no doubt
Every cluster returns its own sealed result. A single hit in an active cluster is enough to block the overall action.
// Test results

Two tested scenarios.

All values on this page are fictional test data and serve only to illustrate the gate logic.

Scenario C1C2C3C4 Verdict Latency
Wire transfer DE→SG, complete originator data, no high-risk jurisdiction, no PEP hitPASSPASSPASSPASSFATF_SEALED372ms
Wire transfer to a FATF grey-list jurisdiction without enhanced measuresPASSPASSPASSFAILBLOCK_FT4_HIGHRISK_JURISDICTION_NO_EDD355ms
Cryptographic chain continuation
Every test produces a deterministic receipt_id, an input_snapshot_hash, an HMAC-SHA256 signature, and a merkle_link to the previous receipt. Persistence occurs in the gateFATFReceipt entity with a 10-year retention period.
// Clarification

What gateFATF is not.

  • Not automatic recognition by the FATF itself, it is a standard-setter, not an enforcement authority. The gate delivers a cryptographic proof, not approval.
  • Not a replacement for national AML laws such as the GwG or the BSA. The gate adds the global baseline on top of them.

For globally active institutions that want to make the FATF baseline standard provable.

Request Access →