> ## Documentation Index
> Fetch the complete documentation index at: https://docs.digitalasset.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Force Transfer

> Enable registrars to take back holdings of an instrument, for example to comply with a court order.

Court orders and regulatory requirements can require an issuer to take back assets from a holder, even when the holder does not cooperate.

The **DA Registry** lets registrars enable **force transfer** for a new instrument. For an instrument with force transfer enabled, the registrar can force transfer holdings from any holder to itself, without the holder's approval. Every force transfer is recorded on the ledger and appears in the holder's transaction history.

> [!NOTE]
>
> The registrar enables or disables force transfer when creating an instrument, and cannot change this later. Force transfer is disabled for all instruments created before this feature was available.

## For Registrars

As a Registrar, you are legally and operationally responsible for the lifecycle of the assets you manage. This feature provides the essential control mechanism required to maintain compliance and resolve disputes ensuring you have ultimate authority over your asset registry.

To create an instrument with force transfer enabled and perform force transfers, see the [Force Transfer guide](https://docs.digitalasset.com/registry/guides/force-transfer.md).

## For Holders and Wallets

While this feature allows assets to be moved without your direct consent, it is strictly governed by the Registrar. It exists to ensure the overall integrity and regulatory compliance of the asset. If your assets are subject to a forced transfer, it will be recorded immutably on the ledger, and you should contact your Asset Issuer or Registrar for details regarding the force transfer action.

To detect force transfer on holdings and show force transfers in the transaction history, wallets can follow the [Force Transfer guide](https://docs.digitalasset.com/registry/guides/force-transfer.md#for-wallets).

## For Trading Venues

Due to Canton's topology-aware package selection (TAPS), trading venues need to check which instruments have force transfer enabled. If any participant involved in a settlement (instrument admins, traders, the venue itself, or any other informee) has only vetted Registry App version `0.14` or earlier, a settlement of an instrument with force transfer enabled is not possible, neither in V1 nor in V2. TAPS selects a single Registry App version for the whole settlement transaction, and versions before `0.15` cannot represent holdings and instrument configurations with force transfer enabled.

The [recommended approach for trading venues](https://docs.digitalasset.com/registry/apis/token-standard/cross-version-compatibility.md#recommended-approach-for-trading-venues) describes which checks to make before orchestrating a settlement. To check whether an instrument has force transfer enabled, see the [Force Transfer guide](https://docs.digitalasset.com/registry/guides/force-transfer.md#for-trading-venues).