Skip to main content
Fireblocks Flow includes compliance checks that your app can run on their own, with or without a payment. They are separate from the screening that every Flow payment includes by default: a flow never runs these checks for you, and your app decides when to trigger them.

​
Checks

  • Wallet ownership verification. The user signs a message that proves they control the wallet.
  • Spam token filtering. Known spam tokens are removed when you show a wallet’s balances.
  • Name matching. The depositor’s identity is checked against a name you expect, for payments where you already know who should be paying.

​
Using them with a payment

Flow payments does not run these checks, but your app can run them before or alongside a payment:
  • Verify ownership when the payer connects a wallet, before your app attaches that wallet as the payment source.
  • Show the payer’s balances with spam tokens filtered out, and let them choose the token to pay with from that list.
A check your app runs does not change the flow. If a check fails, your app decides what happens next, for example not attaching the wallet as the payment source.

Screening

The risk screening included in every Flow payment.

Address screening

How Dynamic screens addresses across products.
Last modified on October 27, 2026