Working notes from the team building the FIN-TECHAI risk layer — crypto AML compliance and wallet screening, transaction monitoring and false positives, the Travel Rule and MiCA, stablecoin payment routing, and on-chain credit. Written for the people who have to integrate this, not for a brochure.
What a crypto AML compliance programme actually needs now that regulators inspect whether controls function rather than whether they are documented: pre-execution wallet screening, transaction monitoring built on on-chain typologies, continuous re-screening, and an evidence layer you can hand to an examiner.
Where the screening call belongs in a payment flow, what a useful response contains, latency budgets, and whether to fail open or fail closed.
Originator and beneficiary data, thresholds that differ by jurisdiction, unhosted wallet verification, and why the sunrise problem is still unsolved.
A score is a signal about an address, not a verdict about a person. The inputs behind it, why hop distance dominates, and how to read the confidence band.
Measure precision per rule, tune on hop distance and attribution confidence rather than raising thresholds, and suppress patterns instead of addresses.
Why a counterparty clean on Ethereum can be funded entirely through TRC-20 flows, and what Tron ingestion needed that EVM tracing did not.
A raised figure cannot be shown honestly before the sale contract is live, so we do not show one — plus a due-diligence checklist you can apply to anyone.
How PayRoute picks a corridor, why settlement finality matters more than first confirmation, and what happens when the cheapest route is not the safest one.
The signing threshold, who holds keys, the three classes of transaction, and why a timelock only counts as a control if someone is watching.
Building a repayment signal from on-chain history when there is no off-chain file to pull — and why behaviour under stress beats any balance snapshot.