Language:
PRODUCTS
SECTORS
MORE
Quantum Security 🔍 Search Request Access →
gatePCMLTFA — Canada FINTRAC AML and Reporting Gate
// The problem

A reporting threshold that exists only in someone's head becomes a problem at the next audit.

The PCMLTFA requires ten documented compliance building blocks. gatePCMLTFA checks all ten as pure boolean computation, with no external API dependency, which guarantees determinism and the lowest latency of any gate in this group.

LCTR at 10,000 CAD as its own transaction-bound cluster
The Large Cash Transaction Reporting duty at 10,000 CAD is handled separately from the general compliance-programme check, because it is triggered transaction-specifically, not held permanently.
// Architecture

5 clusters, checked sequentially.

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

CLUSTER 1
FINTRAC Registration & Programme
Checks FINTRAC registration (§5), documented compliance programme (§6), and a designated compliance officer.
fintrac_registered · compliance_program · officer_designated
CLUSTER 2
Client Identification & UBO
Checks completed client identification (§7) and identified beneficial owner (§9).
client_id_complete · ubo_identified
CLUSTER 3
STR & Risk Assessment
Checks STR filing where required (§7.1) and a current risk assessment (§9.1).
str_filed_if_required · risk_assessment_current
CLUSTER 4
Retention & Third-Party Determination
Checks 5-year record retention (§12) and third-party determination (§73).
retention_5y · third_party_determined
CLUSTER 5
LCTR at 10,000 CAD
Checks LCTR filing for cash transactions of 10,000 CAD or more (§14).
lctr_filed_if_applicable
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 C1C2C3C4C5 Verdict Latency
Full FINTRAC compliancePASSPASSPASSPASSPASSPCMLTFA_SEALED317ms
Full non-compliance, 6 criticalFAILFAILFAILnot evaluatednot evaluatedBLOCK_PCMLTFA_NONCOMPLIANT588ms
MSB partial, 3 warningsPASSWARNWARNPASSnot applicableWARN_PCMLTFA_PARTIAL490ms
Casino, LCTR 25,000 CAD not filedPASSPASSPASSPASSFAILBLOCK_PCMLTFA_S14_NO_LCTR495ms
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 gatePCMLTFAReceipt entity with a 10-year retention period.
// Clarification

What gatePCMLTFA is not.

  • Not automatic recognition by FINTRAC. The gate delivers a cryptographic proof, not regulatory filing confirmation.
  • Not an independent filing system. The gate seals the pre-check, it does not itself file an STR or LCTR with FINTRAC.

For Canadian financial institutions that want to make FINTRAC compliance provable.

GATE CATALOG · REGULATORY DETERMINATION DOMAIN

gatePCMLTFA

gatePCMLTFA determines encoded Indian AML, customer, reporting and transaction conditions for a defined matter. 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
gatePCMLTFA regulatory determination domain
AUTHORITY BOUNDARY

PCMLTFA STATE IS NOT ENFORCEMENT 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.

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 →