An allowlist is a transfer rule enforced at the token level: addresses on the list may hold or receive the token, addresses off it cannot, and a transfer that violates the rule reverts on-chain. Regulated issuers use allowlists to keep tokenized assets inside their eligibility perimeter.
The important property is where the rule lives: not in each venue's terms of service but in the token contract itself, checked on every transfer by anyone. A tokenized stock that says U.S. persons may not hold can actually enforce it at the protocol layer.
In tokenized assets, an allowlist is the compliance pattern where holding and transferring are limited to pre-approved addresses: eligibility is verified before the fact rather than policed after it. The standard model is the transfer-hook or rule extension that checks the counterparty addresses against the approved set, reverting anything outside it.
It is the strictest of the three common compliance shapes. A freeze authority acts reactively, stopping specific addresses when flagged. A blocklist denies known-bad counterparties. An allowlist permits only known-good ones, shifting the default from open to closed. The trade is operational: every new holder must be onboarded to the set before their first transfer, which suits programs under real securities obligations more than open retail circulation.
What it means practically for a buyer: a wallet that has not been through the program's eligibility process cannot receive the token, so purchasing flows ask the eligibility questions first. For issuers it is the design that most directly satisfies transfer restrictions, at the cost of the most ceremony. U.CASH checkout surfaces the eligibility confirmation where a token carries these rules.
A tokenized security restricts transfers to addresses its program has verified. A buyer confirms eligibility at checkout, receives to their approved wallet, and every onward transfer checks counterparty membership in the rule set at the chain level.
Tokenized assets on U.CASH carry their issuers' on-chain transfer gates, and checkouts surface the live gate status beside your receiving address so a blocked transfer never costs gas.
Merchants holding rule-bound assets should expect onboarding ceremony per program and keep such holdings compartmentalized from operational floats. The checkout flow carries the eligibility steps so the ceremony happens at purchase rather than at first attempted transfer. One planning note: because eligibility attaches to addresses, a business moving holdings between its own wallets should onboard each destination to the program before initiating, which turns an internal transfer into a checklist item rather than a surprise revert. The programs make onboarding straightforward; they simply insist that it happen in order.
Every term behind the rails, the assets, and the settlement.