When a compliance module refuses a transfer, mint, or burn, the transaction reverts before balances change. This reference maps refusal errors and reason codes to their owning module and explains how to diagnose unexpected refusals. For each module's parameters and behaviour, see Compliance modules.
When a module refuses
Detailed module errors identify the refusing rule directly, while generic transfer or mint rejections require simulation to isolate the blocker.
Second-generation (V2) modules fail with DALP-1120, carrying the module instance address, module type, machine-readable reason code, and message. First-generation (V1) modules fail with DALP-1009, carrying plain text only. The contract error reference documents both error envelopes.
A plain transfer or mint can also fail before module details surface: DALP-1096 for a transfer and DALP-1110 for a mint. A recipient missing from the asset's identity registry is refused before queueing with identity-not-registered. Any other generic refusal omits the reason code, so run Transfer pre-check to inspect the exact blocker.
Two modules emit dedicated error codes instead of generic compliance reason codes:
Most V2 reason codes map to one module, while the count modules share theirs:
Four modules share one reason code when the receiver has no registered identity:
Capital raise limit also fails closed on missing or invalid pricing, with one code per cause (a missing price feed returns the price resolver's own error without a reason code):
Token supply limit stays on plain-text V1 errors with no reason code. Time lock can also emit two internal bookkeeping codes that represent platform faults to escalate rather than party refusals:
A refusal reflects live rules and on-chain state, not a transient fault, so retrying unchanged fails again. Update the underlying condition first: adjust a list entry, re-issue an expired claim, wait for a window rollover, edit a limit, or adjust the amount. A burn restores capacity only on modules that credit burns (capital raise limit never does).
Before retrying, open the token's Transfer pre-check tab (visible to asset freeze holders, System managers, Identity managers, Verification issuers, and Compliance managers). Enter the Sender, Recipient, and Amount, then select Run check to simulate the transfer and see blockers grouped by who can resolve them.
Troubleshooting
A module you expect is not offered
The Console filters the catalogue to modules compatible with the surface's module-set generation and hides modules already enabled there. A second-generation module does not appear on a first-generation policy template, and a module the token already carries is not offered twice.
A configured field cannot be changed
Some fields lock once the module is enabled: the issuance volume limit's period length and window mode, the time lock's hold period, the transfer approval mode, and every parameter of the capital raise limit. The Console marks the locked field. To use a different value, remove the module and install a new instance. The new instance starts with no memory of what the old one had tracked.
Adding the capital raise limit, or creating an asset with it, fails
The module converts mint amounts to fiat through the price resolver add-on. While the system lacks that add-on,
creating an asset with the rule, adding it to a token, and adding it as a global control are all refused with
compliance.. Install the add-on first, then try again. A request that names its own price
resolver and price topic for the rule keeps them and is not refused.
A refusal names a rule no token-level module explains
Check the rows marked “Global” in the Rules table of the token's Compliance tab. Global controls apply to the token automatically, refuse operations the same way its own rules do, and show “Set in Compliance › Global controls” in the Setting column. Change them in global controls, not from the token.
A country sits on both the allow list and the block list
No holder in that country can satisfy both rules, so an ordinary transfer or mint to that receiver fails when both rules apply. If every allowed country is also blocked, no country passes. Check for overlap between the country allow list and the country block list before deploying both on the same token.