2 Token Force Transfer

2.1 Registrar provides details on Investors

The Registrar is able to provide the PartyID of Investor1 to the Issuer.

Actor

Utility Module

Registar

REGISTRY

Select HOLDINGS on the left navigation.

../../_images/request_force_transfer_1.png

2.2 Issuer initiates force transfer

The Issuer can initiate a force transfer from Investor1 to the Issuer

Actor

Utility Module

Issuer

REGISTRY

Select FORCE TRANSFER on the left navigation.

../../_images/request_force_transfer_2.png

Click REQUEST FORCE TRANSFER:

  • Requestor Rationale: Mandatory text field describing rationale for Force Transfer

  • Registrar: Registrar’s Party ID

  • Instrument: Name of Instrument to be transferred

  • Amount: Quantity of Tokens to be transferred

  • Reference: <anything or empty>

  • Sender: Investor from whom the token will be transferred

  • Receiver: Issuer receiving the token from the Sender

../../_images/request_force_transfer_3.png

Click REQUEST. The transfer is pending decision from the Registrar.

2.3 Registar reviews the request

Actor

Utility Module

Registrar

REGISTRY

Select FORCE TRANSFER on the left navigation.

The Registrar reviews the Force Transfer request and either Accept or Reject the Force Transfer request from the Issuer.

../../_images/request_force_transfer_4.png

The Registrar is required to document the rationale of their acceptance.

../../_images/request_force_transfer_5.png

If accepted, the Registrar has to then Execute the Force Transfer.

../../_images/request_force_transfer_6.png

After choosing Execute the instrument is transfered to the Issuer from Investor1 without requiring the approval of Investor1.

../../_images/request_force_transfer_7.png

The Registrar and the Issuer are now able to confirm in the Holdings view that BOND is now owned by the Issuer.

../../_images/request_force_transfer_8.png

Congratulations! The force transfer is complete.