Once a compliance policy is in place, most transactions pass through screening without you having to do anything. This article covers the states a transaction can be in after screening, how to read its screening result, and the actions you can take on a single transaction.
For the automatic actions your policy applies (Accept, Reject, Alert, Freeze, and so on), see Building a Compliance Policy. This article covers what happens next.
Transaction states
| State | What it means | What you can do |
| Screening | The transaction is still being evaluated. | Wait, or rescreen it if it is taking longer than expected. |
| Accepted | Your policy accepted the transaction, with or without an alert. An outgoing transaction continues to Policies approval and signing. An incoming transaction's funds are available in your wallet. | |
| Frozen | A policy outcome held the funds of an incoming transaction, or you froze them manually through the API. The rest of the wallet keeps working. | |
| Rejected | A policy outcome blocked an outgoing transaction. No funds moved. | Bypass it if you determine the block was a false positive. |
These states appear in the Console's Transaction History. The API uses different values for the same states. See Transaction Screening Operations on the Developer Portal.
Why does a transaction stay in Screening
A transaction can remain in Screening for reasons unrelated to the screening result, most often due to network confirmation delays between Fireblocks and your provider. In most cases, this resolves on its own within a short time and does not indicate a problem with the transaction or your policy. A transaction waits in Screening until the provider answers or the timeout elapses; then the Outcome rules decide. You cannot rescreen a transaction while it is in Screening.
Transactions with several destinations: when an outgoing transaction has several destinations, Fireblocks screens each destination and applies the most restrictive result to the whole transaction: a freeze takes precedence, then reject, then alert, then accept. Travel Rule with Notabene and Bring Your Own Screening gives one decision per transaction. Incoming AML/KYT screening supports a single destination; transfers with more than one are bypassed.
Read the screening result
In the Console, open the transaction in Transaction History. The Transaction Details panel shows the screening outcome and the result returned by your provider.
You can also read the full result through the API. See Transaction Screening Operations on the Developer Portal for the endpoint and fields.
Act on a transaction
By default:
| Operation | What it does | Who can do it | Available via |
| Bypass | Creates a new transaction that skips Screening; the original stays rejected. Outgoing transactions only, after Screening rejected or failed them. Not available when the workspace setting Admins can initiate transactions that bypass policy rules is off. | Owner, Admin. Console and API. | Console, API |
| Rescreen | Screens an incoming transaction again after Screening rejected or failed it; the transaction returns to Screening. Not available for frozen transactions. | All | Console, API |
| Freeze | Releases frozen incoming funds and records the result as bypassed (manual). The checks that were skipped because of the freeze do not run. Funds frozen through the API are unfrozen the same way, in the Console or through the API | Admin, Non-Signing Admin | API |
| Unfreeze | Releases frozen funds once you have reviewed the case. | Owner, Admin, Non-Signing Admin | Console, API |
You can also do all four through the API. See Transaction Screening Operations on the Developer Portal for endpoint details.
These permissions are workspace-level defaults, not fixed rules. If Bypass or Unfreeze is turned off for your workspace, that operation requires a Fireblocks Support ticket instead.
Limitations
Some assets cannot be frozen, e.g. Canton.
FAQ
The questions below are the ones readers ask most often.
If I bypass a rejected transaction, does that change my policy?
No. Bypassing affects that one transaction only. Your policy and how future transactions are screened stay the same.
Can I bypass a rejected incoming transaction?
No. Bypass applies to outgoing transactions. When your policy rejects an incoming transaction, the funds are already in your wallet, so Fireblocks freezes them instead. Review the case and unfreeze the funds if appropriate.