When a wallet restriction 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).
Steps
Review the open positions
- Open Organisation participants → Users, open the user, and select Wallets (or More → Wallets).
- Open the restricted wallet's row menu (
...) and select View restriction to open the read-only Restriction details sheet (bookmarkable by URL). - 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
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
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).
- On Restriction details, select Request release on a held position row (Compliance manager only).
- Review the wallet, asset, amount, valuation, and counterparty, enter a Reference or reason (1 to 500 characters, such as a licence number), and submit.
- Have a second authorised approver open 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.
Only one active release per position is allowed at a time. The Restrictions row in Approvals is always required (“Always required”). See Maker-checker.
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), only listed tokens are covered. XvP settlements where the wallet only receives are omitted.
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
- XvP settlements: Refuses execute, approve, and secret reveal by any party (including counterparties) across all routes, returning
409DALP-211172(XVP_) on v2 and transaction-preparation routes (orPOSITION_ HELD_ BY_ RESTRICTION 422DALP-12324on 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
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
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
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
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.
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
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).
API routes
Authenticate with an API key (using X-Chain-Id for non-default networks). See the Platform API reference for full read schemas.
Read the positions
Owners, Platform administrators, and Compliance managers receive positions and positionsUnavailable on GET /api/ (other callers receive positions: null on restrict/lift responses):
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 <restriction. See Send a restrict request and List and read restrictions.
Send a release request
A Compliance manager submits positionId and reference (1 to 500 characters, optional Idempotency-Key):
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- checker approval and returns 200 with the restriction, recording the entry under releases:
{
"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/ ({"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.