This page lists every token operation that refuses differently in DALP 3.2 (mints, burns, transfers, yield claims, fees, and prices). For platform-level refusals (list queries, audit trail, maker-checker, templates, documents, external tokens, compliance roles, and wallet factors), see New platform refusals in 3.2. For schema and SDK changes, see Upgrade an integration to 3.2.
New refusals on existing operations
These operations keep their 3.1 request and response shapes but reject requests 3.1 accepted or return new error codes. Generated clients do not flag them at compile time.
Gas refusals
What changed. Token writes refused because the paying account lacks gas now return 400 TRANSACTION_ (DALP-14062, data., non-retryable), with data.transactionId when recorded. This covers direct token and token-feature writes, token role changes, synchronous token creates and price updates, and coordinated corporate-action preview, confirm, abort, and leg release steps.
When a self-paying smart wallet lacks gas, DALP returns 422 TRANSACTION_ (DALP-14034) with smartWalletAddress and shortfallWei in data.
Who is affected. Clients performing token writes, role updates, price updates, or coordinated corporate actions.
How to detect it. Writes return 400 with data. or 422 with DALP-14034.
What to do. Fund the paying account before retrying. Do not auto-retry DALP-14062. If a retry returns TRANSACTION_ (DALP-14066), inspect the original transaction and resend under a new Idempotency-Key. See Error handling.
Bundler wallet without a fee quote
What changed. POST /api/ now sizes funding from the network's live fee quote. If no fresh fee quote exists or the funding request cannot be recorded, it returns 503 (DALP-12250, retryable) instead of 200 with funding: "unknown".
Who is affected. Clients creating or repairing a bundler wallet and treating funding: "unknown" as success.
How to detect it. The call returns 503 instead of 200.
What to do. Retry after a short delay. The operation reuses the existing bundler wallet.
Mint and burn during a corporate action
What changed. Mints and burns on an asset are refused with 409 CORPORATE_ (DALP-12067) while a corporate action run is in flight on that asset, from start until completion or abort. data.corporateActionId identifies the active run.
Who is affected. Every client that mints or burns, even when another operator started the corporate action.
How to detect it. Mint or burn calls return 409 CORPORATE_.
What to do. Wait for the run in data.corporateActionId to complete, or abort it, then resend the mint or burn. See Corporate actions.
Burns and forced transfers on a frozen address
What changed. Assets on the DALP 3.2 token contract now refuse burns from a fully frozen address with DALP-1076 (“Sender address frozen”) and forced transfers into one with DALP-1074 (“Recipient address frozen”). Multi-holder requests fail as a whole if any named address is frozen. Partial balance freezes do not block either operation.
Template-issued assets move to the 3.2 token contract when the organisation runs System updates. Assets from the seven original factories keep 3.1 behaviour, though the API still blocks maturity redemptions from a frozen holder on every asset.
Who is affected. Clients calling POST /api/ or POST /api/ on potentially frozen addresses.
How to detect it. Because the API does not pre-check address freezes on these routes, async writes return 202 Accepted and end FAILED with contractError.id DALP-1076 or DALP-1074. Calls with Prefer: wait return 422 CONTRACT_ERROR with that data.id.
What to do. Check data. via GET /api/ first. Lift the freeze with PUT /api/ (freeze: false), or forced-transfer from the frozen sender to an eligible wallet and burn there.
Burns that name a restricted wallet
What changed. DALP 3.2 introduces wallet restrictions. Operations targeting restricted wallets behave by operation type:
Who is affected. Clients that burn, force-transfer, force-convert, confirm corporate actions, or settle fund redemptions in any organisation using wallet restrictions or sharing a system with the wallet restriction module.
How to detect it. Burn responses (200 or 202) include skipped, or return 409 TOKEN_ (DALP-9590). Buyback, partial redemption, reverse split, capital decrease, and forced conversion calls return the same 409 DALP-9590 when refused. Corporate action holders carry skipReason ("restricted" or "frozen") or cashOwed.
What to do. Read skipped on every burn response and book only settled pairs. Update strict decoders to accept optional skipped, restrictedSenders, cashOwed, skipReason values restricted and frozen, and entries or DALP-9590 refusals (for burns, forced conversions, and corporate-action confirms) without restrictionId (omitted for other organisations' restrictions, module-only restrictions, or callers lacking owner, admin, complianceManager, or custodian access).
When a forced conversion returns DALP-9590, send it again after the holder's restriction is lifted while the trigger is active and the conversion window stays open.
To burn restricted holders in place during reverse splits, capital decreases, or rights closes, execute from a smart wallet with both custodian and supplyManagement. Raise at most one follow-up per run (a second returns 409 CORPORATE_, DALP-12069). After a restriction lift or unfreeze, run a follow-up for any skip, skip, or unpaid cashOwed entry. See Restricted holders.
The wallet restriction module
What changed. DALP 3.2 adds the system-wide wallet-restriction compliance module type, which blocks transfers from restricted wallets across every token in the system and blocks ordinary burns on 3.2 token contracts. Forced transfers and forced burns still bypass compliance modules.
The platform installs it automatically on new systems and during System updates on existing systems (loading all active restricted wallets). Until installed, transfers and burns keep 3.1 behaviour.
Who is affected. Clients creating wallet restrictions, transferring or burning from restricted wallets, decoding ComplianceTypeId, or installing compliance modules by type.
How to detect it. Installs return 409 with data., module reads include wallet-restriction, and transfers fail with DALP-1076 or DALP-1120.
What to do. Accept wallet-restriction in decoders and exclude it from install and token-create requests. Treat DALP-1120 (COMPLIANCE_) as a module block. Do not rely on GET /api/ alone because non-compliance callers get an empty list and direct module restrictions have no DALP restriction record. In an emergency, a Compliance manager can disable the module via POST /api/ (preserves wallets) or remove it via DELETE /api/ (drops wallets until the next System update). See Global controls.
Settlements a restricted wallet delivers in
What changed. An active wallet restriction holds open positions where the restricted wallet delivers a covered token until the restriction is lifted or a position release is approved.
Who is affected. Clients executing, approving, or revealing XvP settlements (directly or via transaction preparations) and workflows tracking venue fills or cash-outs.
How to detect it. XvP and transaction-preparation calls return 409 DALP-211172 (v1 returns 422 DALP-12324), and venue fills remain parked with reason wallet-restriction.
What to do. Do not retry unchanged. Lift the restriction, or have a Compliance manager request a position release approved by a second user, then retry. Cancelling and post-expiry withdrawal remain allowed, and parked venue fills or held cash-outs resume automatically once released.
Maturity redemptions by a frozen holder
What changed. POST /api/ now refuses redemptions for a fully frozen signing holder before queueing, returning 422 CONTRACT_ERROR with DALP-1076 (“Sender address frozen”) on every token contract. Partial balance freezes do not block redeeming unfrozen units (3.2 contracts protect frozen units, while 3.1 contracts still draw them down).
Who is affected. Clients redeeming matured units on behalf of holders.
How to detect it. Redemptions return 422 CONTRACT_ERROR (DALP-1076) instead of 202 or 200. Validation runs in order: walletVerification, pause state, address freeze, then maturity, so a frozen holder gets DALP-1076 even before maturity.
Because the pre-check reads indexed state, a redemption sent before a freeze is indexed reaches the chain:
- On 3.2 token contracts, the chain reverts it: queued calls end
FAILEDwithcontractError.idDALP-1076, whilePrefer: waitor holder-signed calls return409MATURITY_(REDEMPTION_ UNAVAILABLE DALP-12373). - On 3.1 token contracts, redemptions that reach the chain still burn frozen units and pay out.
What to do. Handle DALP-1076 and check data. on GET /api/ before redeeming. After lifting the freeze with PUT /api/, wait until isFrozen reads false before retrying.
Mints and transfers refused before they are queued
What changed. POST /api/, POST /api/, and POST /api/ (mint and transfer) now refuse five invalid writes before queueing. All five are non-retryable and checked after walletVerification on writes. Preflights need no walletVerification and return data. when passing:
Checks read indexed chain state: unindexed freezes or mints still revert on chain (FAILED with the same contractError.id), and recently lifted freezes, new registrations, or raised caps can be refused until indexed. Assets using Booked movements, Canton instruments, burns, and forced transfers skip these pre-checks.
Who is affected. Clients that mint or transfer, or wait for FAILED transactions to detect these conditions.
How to detect it. Writes return 422 CONTRACT_ERROR or 409 TOKEN_ immediately without queueing.
What to do. Handle all five codes on the write response while retaining contractError.id handling on FAILED transactions. Use POST /api/ before prompting for a PIN. Unfreeze via PUT /api/ (or lift a wallet restriction if it returns 409 TOKEN_), register unregistered recipients, or reduce the mint amount to fit data.args.cap or data.headroom.
Amounts in transfers, forced transfers and burns
What changed. Every transfers[].amount in POST /api/ and POST /api/, every amounts entry in POST /api/, and matching preflights actions now require a positive integer of base units up to 2^256 - 1. Zero, negative numbers, decimals, exponent notation, and larger values return 400 REQUEST_INVALID naming the field (for example, transfers.0.amount). Mints continue to refuse zero with 400 TOKEN_ (DALP-9484).
Who is affected. Clients sending zero, fractional, or scientific-notation amounts to transfers, forced transfers, or burns.
How to detect it. Requests return 400 REQUEST_INVALID with the amount field in data.errors.
What to do. Omit zero-amount entries and format every amount as a positive integer string in plain digits.
Yield claims on a frozen address
What changed. Interest claims and fixed-yield coupon claims now refuse a fully frozen holder address with DALP-9295 (matching dividend claims). Lost-wallet recovery claims are refused while either the lost wallet or replacement wallet is fully frozen. Interest and coupons continue accruing while frozen and pay out after unfreezing. Partial freezes do not block claims.
Who is affected. Clients calling POST /api/, POST /api/, or their recovered-wallet-claims routes.
How to detect it. Queued claims end FAILED with contractError.id DALP-9295, or return 422 CONTRACT_ERROR (DALP-9295) with Prefer: wait.
What to do. Check data. via GET /api/ first and claim after lifting the freeze.
Fee recipient changes
What changed. On the DALP 3.2 management fee feature (activated by System updates), PATCH /api/ pays accrued fees to the old recipient before switching recipients. The update fails without changing the recipient if the asset is halted (DALP-1109), the old recipient is frozen (DALP-1074), or the old recipient fails compliance (DALP-1110).
Who is affected. Clients updating a management fee recipient.
How to detect it. Async requests return 202 Accepted and end FAILED with DALP-1109, DALP-1074, or DALP-1110 (or 422 CONTRACT_ERROR with Prefer: wait). Successful changes record a fee payout to the old recipient.
What to do. Resume the asset or unfreeze and re-verify the old recipient before switching recipients, and reconcile the automatic payout.
Pause and resume codes
What changed. On the DALP 3.2 token contract, halting an already halted asset reverts with DALP-1109 and resuming an active asset reverts with DALP-9059 (the reverse of older contracts). PATCH /api/ also pre-checks indexed state and refuses redundant requests with DALP-9488. Contract codes surface when chain state leads the index, either in contractError.id or 422 CONTRACT_ERROR with Prefer: wait.
Who is affected. Clients branching on DALP-1109 or DALP-9059 after a halt or resume.
How to detect it. A redundant halt returns DALP-1109 instead of DALP-9059, and a redundant resume returns the reverse.
What to do. Treat DALP-9488, DALP-1109, and DALP-9059 uniformly as “the asset is already in the requested pause state”.
Prices with too many decimals
What changed. Token price updates, price-feed submissions, and initial prices on token creation now refuse values with more decimal places than the feed stores, returning 400 FEED_ (DALP-12245, non-retryable). 3.1 truncated extra digits toward zero.
Who is affected. Clients sending unrounded price strings.
How to detect it. Price writes return 400 FEED_ naming the price and feed decimals.
What to do. Round or format prices to the feed's configured decimals before submitting.