About Address Registry Screening

Address Registry Screening (ARS) checks a transaction’s source or destination against Fireblocks’ shared registry of verified addresses, so you can, for example, reject transactions with unverified counterparties or block restricted jurisdictions. It is free and runs first, before AML/KYT. It is not a risk screening and does not decide whether the Travel Rule applies: a not found result means only that the address is not a registered Fireblocks counterparty. ARS needs Address Registry, which every workspace is opted in to by default. If your workspace has opted out, activation fails. See About Address Registry.

What you can do through the API

Step	Task	Console	API
1	Create a counterparty group	Yes	`POST /counterparty_groups`
1	List counterparty groups	Yes	`GET /counterparty_groups`
1	Get a counterparty group	Yes	`GET /counterparty_groups/{groupId}`
1	Update a counterparty group	Yes	`PATCH /counterparty_groups/{groupId}`
1	Delete a counterparty group	Yes	`DELETE /counterparty_groups/{groupId}`
2	Build the Trigger (Screening Policy) and Outcome (Post-Screening Policy)	Yes	No
2	Configure timeout behavior	Yes	No
3	Activate ARS	Yes	`POST /screening/ars/config/activate`
3	Deactivate ARS	Yes	`POST /screening/ars/config/deactivate`

Step 1: Create counterparty groups

A counterparty group is a named set of jurisdictions; jurisdiction is the only grouping attribute today. Your Outcome rules reference these groups. Create, update, and delete require the Admin or Non-Signing Admin role. Create and update accept an optional Idempotency-Key header, valid for 24 hours; delete does not.

Field	Type	Description
`groupId`	string (UUID)	Returned by Fireblocks.
`name`	string	Required. Display name.
`description`	string	Optional.
`jurisdictionCodes`	string[]	Required. ISO 3166-1 alpha-2 codes, for example `["US", "SG"]`.
`isActive`	boolean	Whether the group is active.
`createdAt`, `updatedAt`	string (ISO 8601)	Returned by Fireblocks.

const { data: group } = await fireblocks.compliance.createCounterpartyGroup({
  createCounterpartyGroupRequest: {
    name: "APAC Financial Partners",
    jurisdictionCodes: ["SG", "HK"],
  },
});
console.log(group.groupId);

Step 2: Build the policy in the Console

Under Policies > Compliance, add Trigger rules for which transactions ARS checks, set the timeout behavior (accept or reject if the check does not return in time), and add Outcome rules:

Condition	Action
Counterparty is in a group	Accept or Reject
Counterparty found, but in no group	Your catch-all default rule
Counterparty not found in the registry	Accept or Reject

See About Address Registry Screening on the Help Center.

Step 3: Activate ARS

Activate or deactivate with the endpoints above. Both return the current configuration:

{ "active": true, "lastUpdate": "2026-01-29T12:00:00.000Z" }

Once active, ARS applies to every transaction that matches your Trigger. Deactivating stops the check until you activate it again.

Limitations

GET /screening/transaction/{txId} does not include ARS results. A rejection shows as REJECTED_AML_SCREENING, the same value as other checks; see Transaction states.
Not supported on European or Swiss-hosted workspaces, or on Developer Sandbox workspaces. Lookups from these workspaces return not_found, so your “not found” rule applies.
The registry resolves addresses within the Fireblocks network only.

On the Help Center

To build the ARS policy or manage counterparty groups in the Console, see About Address Registry Screening.

Get Started

Transactions

API Co-Signers

Webhooks

Workspace & Security

Identity & Compliance

Manage Wallets

Smart Contracts & Tokenization

Treasury & Trading

Gas Management

Payments

Embedded Wallets

Offchain Signing

Direct Custody Wallets

Integrations

Assets & NFTs

Canton

Key Link

What you can do through the API

Step 1: Create counterparty groups

Step 2: Build the policy in the Console

Step 3: Activate ARS

Limitations

On the Help Center

​What you can do through the API

​Step 1: Create counterparty groups

​Step 2: Build the policy in the Console

​Step 3: Activate ARS

​Limitations

​On the Help Center

What you can do through the API

Step 1: Create counterparty groups

Step 2: Build the policy in the Console

Step 3: Activate ARS

Limitations

On the Help Center