# View restriction

Source: https://docs.settlemint.com/docs/console/participants/held-positions
Read the open positions a wallet restriction lists, see which ones DALP holds, and release one held position with a second person while the restriction stays.

When a [wallet restriction](https://docs.settlemint.com/docs/console/participants/restrict-a-wallet) is active, **Restriction details** lists all open positions for that wallet valued in your organisation's base currency. DALP holds every XvP settlement, trading venue escrow lock, and bank rail cash-out in which the restricted wallet delivers a covered token until the restriction is lifted or a second approver releases that position.

Holds are enforced across DALP API requests and background workers rather than inside settlement contracts ([Settlements outside DALP](#settlements-outside-dalp)).

## Before you start [#before-you-start]

- **Active wallet restriction.** The wallet must show a "Restricted: " badge on the user's **Wallets** tab ([Restrict a wallet](https://docs.settlemint.com/docs/console/participants/restrict-a-wallet)).
- **Roles to view vs request release.** Owners, Platform administrators, and Compliance managers can read open positions (opening the user's **Wallets** tab also requires System manager, Identity manager, or Verification issuer). Only a Compliance manager can request a release, and a different user (another Compliance manager by default, or the role configured on the **Restrictions** row in [Approvals](https://docs.settlemint.com/docs/console/organisation-settings/general#approvals)) must approve it.
- **No wallet verification.** Release requests and approvals send no on-chain transaction and require no PIN.

## Steps [#steps]

### Review the open positions [#review-the-open-positions]

1. Open **Organisation participants** → **Users**, open the user, and select **Wallets** (or **More** → **Wallets**).
2. Open the restricted wallet's row menu (`...`) and select **View restriction** to open the read-only **Restriction details** sheet (bookmarkable by URL).
3. Inspect **Open positions** (held positions appear first, showing kind, asset, amount, base-currency value, "Held" or "Listed", and release state, or "No open positions" if none exist). A position with an approved release reads "Listed" because DALP no longer holds it.

Positions recompute live on every read with no historical snapshot stored, so export or record the list and timestamp if reporting to an authority. Unpriced assets show no valuation, and unreachable sources show "Some positions could not be read" naming omitted kinds.

### Review the release history [#review-the-release-history]

Under **Release history**, the sheet lists every release requested on the restriction, newest first, with the position kind, asset, release state, requester and timestamp, approver and timestamp, and reason or authorisation reference. Releases remain listed after their positions settle, cancel, or withdraw and leave **Open positions**, preserving the full regulatory record. A restriction with none shows "No releases requested".

## Request the release of a held position [#request-the-release-of-a-held-position]

A release lifts DALP's hold on one position while keeping the wallet restriction active (for example, under a regulatory licence for one settlement). A venue lock release frees all fills for that order, while an XvP release frees all legs of one delivered token in that settlement (delivering two tokens creates two separate positions).

1. On **Restriction details**, select **Request release** on a held position row (Compliance manager only).
2. Review the wallet, asset, amount, valuation, and counterparty, enter a **Reference** or reason (1 to 500 characters, such as a licence number), and submit.
3. Have a second authorised approver open [Actions](https://docs.settlemint.com/docs/console/essentials/actions) (or follow **Open in Actions**) and approve or reject the request. You cannot approve your own request.

While pending, the row shows "Waiting for approval" and disables **Request release**. Once approved, DALP lifts the hold immediately: participants can execute the XvP settlement, parked venue fills re-enter the settlement queue automatically, and held bank rail cash-outs instruct the bank on the next pass. Releasing lifts DALP's hold without unfreezing unlocked wallet balances.

After approval, the row reads "Listed" and its release line shows both the requester and approver with their timestamps. The restriction retains every release (requester, approver, both timestamps, and reference) in **Release history** even after the position settles, and the audit trail records each request.

| Release state | Meaning |
| --- | --- |
| `pending` | Waiting for a second approver in **Actions** (lapses after 7 days unless changed in **Approvals**). |
| `approved` | Hold lifted while the restriction remains active. |
| `rejected` | Rejected by the checker. Position stays held, and you may submit a new request. |
| `withdrawn` | Cancelled because the requester left the organisation. Position stays held. |
| `expired` | Timed out before a decision. Position stays held, and you may submit a new request. |
| `failed` | Approval could not be recorded on the restriction. Position stays held, and you may retry. |

Only one active release per position is allowed at a time. The **Restrictions** row in [Approvals](https://docs.settlemint.com/docs/console/organisation-settings/general#approvals) is always required ("Always required"). See [Maker-checker](https://docs.settlemint.com/docs/concepts/custody-and-signing/maker-checker#releasing-a-position-a-wallet-restriction-holds).

## Open positions and holds [#open-positions-and-holds]

DALP tracks five open position kinds on the restriction's network, including positions opened after restriction. A position is held when the wallet delivers a covered token and no release is approved for it. Under scope `all`, every token is covered (including previously escrowed units), while under scope `tokens` ([Send a restrict request](https://docs.settlemint.com/docs/console/participants/restricted-wallet-api#send-a-restrict-request)), only listed tokens are covered. XvP settlements where the wallet only receives are omitted.

| Position | API kind | Held when | Blocked while held |
| --- | --- | --- | --- |
| Token delivered by the wallet in an open XvP settlement | `xvp-delivery` | Delivered token is covered | Execute, approve, and secret reveal |
| Units locked in a trading venue escrow for an order | `venue-escrow-lock` | Locked token is covered | Settling fills where the wallet delivers |
| Bank rail cash-out initiated by the wallet | `cash-out` | Token is covered and bank has not been instructed to pay | Instructing the bank to pay |
| Unfinalised token sale contributions (net of refunds) | `sale-contribution` | Never (listed for reporting until the sale is finalised) | Nothing |
| Unclaimed dividend, interest, or yield payout | `unclaimed-payout` | Never (listed for reporting) | Nothing: DALP still sends the claim (see [Payouts into the wallet](#payouts-into-the-wallet)) |

Cash-outs already instructed to the bank are listed rather than held to avoid unfunded bank payments. Valuations use current portfolio prices (`priced`, `no-price`, or `amount-unavailable`). A fixed-yield payout shows the yield the wallet can claim now (the same amount **Collect all** offers). Fixed-yield payouts with nothing claimable are omitted, and ones whose amount DALP cannot read appear as `amount-unavailable`.

### What DALP refuses [#what-dalp-refuses]

- **XvP settlements:** Refuses execute, approve, and secret reveal by any party (including counterparties) across all routes, returning `409` `DALP-211172` (`XVP_POSITION_HELD_BY_RESTRICTION`) on v2 and transaction-preparation routes (or `422` `DALP-12324` on v1). Checks run again right before submission and across every organisation whose system created the settlement.
- **Trading venue fills:** Parks fills where the restricted wallet delivers (`wallet-restriction`) without blocking other fills in the batch, and automatically re-queues parked fills once the hold ends.
- **Bank rail cash-outs:** Keeps tokens locked without instructing the bank, opens an operations case, re-checks every five minutes, and returns tokens to the holder if the payout deadline passes before the hold ends.

### What stays allowed [#what-stays-allowed]

Subject to on-chain token freezes, operations returning units to the wallet remain allowed: cancelling or revoking XvP settlements, post-expiry withdrawals, venue order refunds and bust reversals, cash-out unlocks/refunds, and incoming dividend, interest, or sale refund payouts.

### Payouts into the wallet [#payouts-into-the-wallet]

DALP adds no extra hold to payouts into a restricted wallet and submits dividend, interest, or fixed-yield claims as usual. Because a restriction freezes the wallet on every covered token, on-chain dividend, interest, and fixed-yield features reject claims from a frozen holder with `HolderFrozen` until the restriction is lifted, recording nothing. Payouts on tokens outside scope `tokens` claim normally.

Interest and fixed yield continue accruing on the frozen balance, so the holder can claim all accrued periods once the restriction lifts. Dividends remain claimable only until their claim deadline, after which the issuer can reclaim unclaimed amounts. A dividend whose deadline passes while the wallet is frozen can be lost unless the issuer extends the deadline.

## What a hold does not stop [#what-a-hold-does-not-stop]

### Settlements outside DALP [#settlements-outside-dalp]

Because DALP enforces position holds in its API and background workers rather than inside settlement contracts, direct on-chain calls to an XvP settlement, venue escrow, or bank rail escrow can bypass the hold. Rely on on-chain token freezes to block token movement directly.

### A restriction created while a transaction is in flight [#a-restriction-created-while-a-transaction-is-in-flight]

DALP evaluates holds immediately before submitting transactions. A restriction created after submission and before block inclusion does not stop that in-flight transaction. Refresh **Restriction details** after restricting to confirm remaining open positions.

## You should see [#you-should-see]

- **View restriction** lists open positions with every covered outgoing settlement, venue lock, and cash-out marked "Held".
- After submitting a release, the row displays "Waiting for approval" with the requester and an **Open in Actions** link.
- After approval, the row reads "Listed" with the requester, approver, and both timestamps, and held operations can proceed.
- After the released settlement executes, **Release history** still lists the release.

## Troubleshooting [#troubleshooting]

**Execute settlement returns 409 with DALP-211172**

A delivering wallet in the settlement is restricted (`data.restrictionId` and `data.positionId` identify the hold).
Lift the restriction, or have a Compliance manager request a position release and a second approver approve it in
**Actions**, then retry. Cancelling and post-expiry withdrawals stay open.

**Release request returns 409 with DALP-211173**

The position is not held by an active restriction (it was lifted, closed, or is listed-only). Refresh the restriction
and request release only on rows marked "Held".

**Release request returns 409 with DALP-211174**

A pending or approved release already exists (`data.approvalId`). Decide the open request in **Actions** first, and
submit a new request only if it is rejected, withdrawn, expired, or failed.

**A position kind is missing from the list**

DALP could not reach that data source during the read (`positionsUnavailable` lists omitted kinds). Retry shortly.
Restrictions without a linked participant always omit `cash-out`.

## Frequently asked questions [#frequently-asked-questions]

### What happens to held positions when the restriction is lifted?

Once a restriction closes as lifted, DALP releases all open position holds automatically regardless of individual release states. On systems with the wallet restriction module, holds remain active while **Wallet restriction module** reads "Lift pending" until the lift confirms and closes ([Lift a restriction](https://docs.settlemint.com/docs/console/participants/restrict-a-wallet#lift-a-restriction)).

## API routes [#api-routes]

Authenticate with an [API key](https://docs.settlemint.com/docs/api-reference/guides/authentication-api-keys) (using `X-Chain-Id` for non-default networks). See the [Platform API reference](https://docs.settlemint.com/docs/api-reference/v2) for full read schemas.

### Read the positions [#read-the-positions]

Owners, Platform administrators, and Compliance managers receive `positions` and `positionsUnavailable` on `GET /api/v2/restrictions/{restrictionId}` (other callers receive `positions: null` on restrict/lift responses):

```bash
curl "https://your-instance.example.com/api/v2/restrictions/0198f1a2-3c4d-7e8f-9a0b-1c2d3e4f5a6b" \
  -H "X-Api-Key: sm_dalp_..."
```

CLI equivalent: `dalp get restrictions <restrictionId>`. See [Send a restrict request](https://docs.settlemint.com/docs/console/participants/restricted-wallet-api#send-a-restrict-request) and [List and read restrictions](https://docs.settlemint.com/docs/console/participants/restricted-wallet-api#list-and-read-restrictions).

### Send a release request [#send-a-release-request]

A Compliance manager submits `positionId` and `reference` (1 to 500 characters, optional `Idempotency-Key`):

```bash
curl -X POST "https://your-instance.example.com/api/v2/restrictions/0198f1a2-3c4d-7e8f-9a0b-1c2d3e4f5a6b/position-releases" \
  -H "X-Api-Key: sm_dalp_..." \
  -H "Content-Type: application/json" \
  -d '{
    "positionId": "xvp:0x9fe46736679d2d9a65f0992f2272de9f3c7fa6e0:0x71c7656ec7ab88b098defb751b7401b5f6d8976f",
    "reference": "OFSI licence INT/2026/123"
  }'
```

DALP opens a `restriction-position-release` checker approval and returns `200` with the restriction, recording the entry under `releases`:

```json
{
  "id": "xvp:0x9fe46736679d2d9a65f0992f2272de9f3c7fa6e0:0x71c7656ec7ab88b098defb751b7401b5f6d8976f",
  "kind": "xvp-delivery",
  "held": true,
  "releases": [
    {
      "approvalId": "0198f702-1a2b-7c3d-8e4f-5a6b7c8d9e0f",
      "state": "pending",
      "reference": "OFSI licence INT/2026/123",
      "requestedBy": "user_5d2e9a",
      "requestedAt": "2026-10-25T14:10:00.000Z",
      "approvedBy": null,
      "approvedAt": null
    }
  ]
}
```

A second user decides the approval with `POST /api/v2/checker-approvals/{approvalId}/decision` (`{"decision": "approve"}` or `{"decision": "reject"}`). Once approved, `state` becomes `approved` (ending the hold while `held` stays `true`). Note: the release route is HTTP-only and not in the CLI, SDK, or generated OpenAPI reference.

### Errors [#errors]

| Status | Error | Cause | Resolution |
| --- | --- | --- | --- |
| `403` | [DALP-9485](https://docs.settlemint.com/docs/api-reference/errors) | Caller lacks Compliance manager on the system. | Grant Compliance manager on the system and retry. |
| `404` | [DALP-17457](https://docs.settlemint.com/docs/api-reference/errors) | Restriction not found, or caller cannot view restrictions and lacks Custodian on it. | Verify the ID or ask an Owner or Compliance manager. |
| `409` | [DALP-211172](https://docs.settlemint.com/docs/api-reference/errors) | XvP execute, approve, or secret reveal blocked by a held delivering leg. | Lift the restriction or approve a position release, then retry. |
| `409` | [DALP-211173](https://docs.settlemint.com/docs/api-reference/errors) | Target position is not held by an active restriction. | Read the restriction again and target only `held: true` rows. |
| `409` | [DALP-211174](https://docs.settlemint.com/docs/api-reference/errors) | Position already has a `pending` or `approved` release (`data.approvalId`). | Decide the existing approval in **Actions** first. |