Fraud Prevention
Pre-execution participant verification, transaction governance and movement compliance — coordinated.
For institutions where fraud prevention requires coordinated state across identity, payments and digital asset movement.
Fraud lives in the seams between systems.
Fraud prevention is largely reactive. Identity is verified once at onboarding, payments are screened in their own system, digital asset movement runs through a separate stack, and fraud signals from each layer arrive at different speeds with different formats. The fraud team’s job is to stitch them together, after the event.
Three structural problems compound. Disconnected signals — identity, payments and movement compliance run as separate systems with their own state. Latency between signals — by the time the fraud team has correlated the data, the transaction has already executed. Sophisticated fraud exploits the gaps — the seams between the systems are where fraud lives.
Institutions running cross-asset, cross-jurisdiction operations feel this most acutely. The fraud surface is the entire transaction lifecycle, not any one stage. Reactive fraud prevention is a structural cost of fragmented infrastructure, not a tooling problem.
Three layers, one coordinated fraud signal.
Verified counterparty context
Every transaction starts with a current, network-coordinated participant verification — not a stale onboarding check. Compliance state is live, not historic.
Pre-execution payment screening
Sanctions, AML and fraud rules applied at the moment of payment intent, not after submission. The transaction either satisfies controls or it does not begin.
Movement compliance signals
Counterparty discovery, sanctions screening and policy state attached to digital asset transfers in real time. Movement is governed by the same compliance posture as fiat flows.
Coordinated fraud signal
Identity, payment and movement signals coordinate as a single fraud-evaluation state. The decision is made before the transaction executes, with all three layers in agreement — or it does not execute.
Three layers active. One coordinated state.
01 — Identity Trust
BlockID
Verify the participant.
02 — Payment Control
BlockPay
Govern the transaction.
03 — Digital Asset Transfer Compliance
BlockTravel
Enable compliant movement.
04 — Settlement Certainty
BlockSettle
Settle with confidence.
Fraud Prevention activates three of the four layers of the Block Infrastructure architecture. Identity verification, payment governance and movement compliance evaluate the same transaction simultaneously, sharing state in real time. The fraud signal is the coordinated state of the architecture, not a post-hoc reconciliation between separate systems.
Inherited from BlockID, BlockPay and BlockTravel.
- FCA
- MiCA
- FATF
- PSD2
- GDPR
- MAS
- ISO 20022
- IVMS 101
- OpenAPI 3.0
- OAuth2
- TLS
Fraud Prevention inherits the regulatory and technical standards of BlockID, BlockPay and BlockTravel. ISO 20022 carries fiat payment messaging; IVMS 101 carries digital asset transfer messaging. PSD2 governs payment-services obligations in EU and UK jurisdictions. The use case is bounded by the strictest of any framework that applies to any leg.
Three products. One coordinated signal.
Catch fraud before the transaction executes.
Design partners running cross-asset, cross-jurisdiction operations get early access to the coordinated Fraud Prevention capability, a direct line to the build team, and influence over how identity, payment and movement signals coordinate. We ask for genuine integration intent, a structured feedback loop with named fraud, compliance and technical counterparts, and a mutual non-disclosure agreement.