Execute a Transfer

Overview

A transfer runs through evaluation, restriction review, the consent chain, approvals, execution, registry verification, and settlement. The steps below expand Execute Transfer Intent into the full lifecycle.

Prerequisites

• API key with positions:read, intent:read, intent:write, registry:read scopes
• Position(s) eligible for transfer
• Understanding of Transferability and Rights Engine

Step 1: Evaluate transfer feasibility

Call the Rights Engine or feasibility endpoint with the position entity_id and proposed transfer parameters. Receive a feasibility result: allowed, restricted (with consent requirements), or blocked. Understand which parties must consent and any other conditions.

Step 2: Review restrictions

Examine the restriction details: consent-required parties (GP, LPAC, etc.), lock-up periods, right of first refusal, transfer windows. Determine the consent workflow and sequencing. Some restrictions may be waivable; check documentation for override paths.

Step 3: Initiate consent chain

Create the transfer intent and initiate the consent workflow. The system notifies consent parties; they approve or reject via the API or dashboard. Track consent status per party. Partial consent may be sufficient depending on the position's terms.

Transfer Intent Created
│
├─→ GP Consent Request ──→ Approved ✓
│
├─→ LPAC Review ──→ Approved ✓
│
├─→ ROFR Holder ──→ Waived ✓
│
└─→ All consents obtained
     │
     ▼
Transfer Executes → Registry Updated

Step 4: Monitor consent approvals

Poll consent status or subscribe to webhooks (transfer.consent_updated). Wait for all required approvals. Handle rejections by cancelling the intent or revising terms. Timeouts and escalation paths depend on your configuration.

Step 5: Execute transfer

Once consent is complete, the transfer executes (automatically or via explicit API call, depending on configuration). The registry updates ownership. You receive a completion event and updated position records for buyer and seller.

Step 6: Verify registry update

Query the registry to confirm the new ownership structure. The seller's position may be closed or reduced; the buyer has a new or updated position. Validate entity_id, status, and economic terms. Use this for reconciliation and downstream systems.

Settlement

Settlement (cash movement, document execution) may be handled by DMTR, a partner, or your own process. Integrate with custody and settlement systems as needed. DMTR provides registry and workflow state; financial settlement is typically a separate integration.