Language:
PRODUCTS▾
Home Core Serverless EditionHealthcare Why It’s DifferentExecution RightsGlobal Requirements CDS — Constitutional Screening STFL — Sovereign Transaction Finance Layer Verify Security All Gates
SECTORS▾
All SectorsHealthcareDefenceAviationHeavy IndustryFinancial MarketsAsset Management & Securities FinancingPharma & Clinical TrialsLogisticsSport & MotorsportMusic & Digital MarketsEnergy & ESGPublic SectorSociety & AdministrationAI · Data · Cyber · TelecomReal Estate & TransactionsAgriFood & Food Safety
MORE▾
ASSURANCE
Authority Surface Execution RightsOverride Accountability Capabilities Authoritative Sources Evidence Evidence Registry Fortress Baseline Adversarial Verification Machine Law Evolution
SOLUTIONS
Institutions Regulators Governments Investors · PE Jurisdictions Due Diligence
RESOURCES
Facts Press Newsroom FAQ Machine Law Gate SDK Public Documentation The Sound of Machine Law
COMMERCIAL
Pricing
Quantum Security 🔍 Search Request Access →
gateFATF — Global AML Standard-Setting Gate
// 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 → access@immoquick.eu
GATE CATALOG · REGULATORY DETERMINATION DOMAIN

gateFATF

gateFATF determines encoded FATF-related risk-framework, jurisdiction and countermeasure conditions used as determination inputs. The gate contributes a bound regulatory determination state; it creates neither regulatory authority nor Execution Permission.

DOMAIN_DETERMINATION_ONLY = true · EXECUTION_AUTHORITY = false · EXECUTION_PERMISSION = false
Explore Gate Catalog →Execution Rights →
gateFATF regulatory determination domain
AUTHORITY BOUNDARY

FATF STATE IS NOT NATIONAL AUTHORITY.

CAN

  • deterministically evaluate encoded regulatory conditions
  • bind determinations to source, scope, time and input state
  • surface missing, expired or conflicting regulatory dependencies
  • produce attributable evidence for the concrete determination

CANNOT

  • replace a regulator, supervisor, court or competent institution
  • create legal or regulatory authority through score, consensus, AI or administration
  • turn a gate PASS into an Execution Right on its own
  • mint an ExecutionCapabilityToken on its own
REGULATORY STATE

Regulatory determination is evidence. Not regulatory authority.

SOURCE

Authoritative source

The relevant rule must originate outside the system from a legitimate normative or institutional source.

SCOPE

Defined matter

The determination is limited to the encoded subject, entity, transaction or operation under review.

TIME

Point-in-time state

Effective dates, transition periods, expiry and version state remain explicit.

INPUT

Canonical input

A reproducible determination requires a defined canonical input state.

DEPENDENCY

Dependencies

Missing or contradictory dependencies remain visible rather than being converted into invented permission.

EVIDENCE

Bound evidence

The resulting state can be bound to source, input, scope and time for later verification.

RELATED DETERMINATION DOMAINS

Regulatory domains compose. They do not confer authority on one another.

gateAMLgateAMLARegulationgateLegalConflict

Only scope-relevant determinations become dependencies in Execution Rights resolution. The links shown are not a universally mandatory sequence.

EXECUTION RIGHTS

Five dimensions. Regulatory state can inform them; no gate replaces them.

AAUTHORITY
RRULE
JJURISDICTION
TTIME
DDEPENDENCY
ALL FIVE REQUIRED DIMENSIONS VALID → VALID EXECUTION RIGHT · ANY REQUIRED DIMENSION ABSENT → NO VALID EXECUTION RIGHT → NO CAPABILITY → NO EXECUTION
INVARIANT

A regulatory PASS is a determination. Never a permission by itself.

AUTHORITY → DETERMINATION → EXECUTION RIGHTS → CAPABILITY OR NONE → EXECUTION OR NONE → EVIDENCE

Request Access →