# Structured products Source: https://docs.settlemint.com/docs/executive-overview/use-cases/structured-products Map principal-protected notes, autocallable notes, and asset-backed tokens to DALP instrument templates, EVM token controls, and the external payoff or reserve processes that remain outside DALP. Structured product teams use DALP when a programme needs a governed EVM token record for an instrument whose economics depend on terms outside the token itself. The structured template family covers Principal-Protected Note, Autocallable Note, and Asset-Backed Token patterns. DALP can model the issued token, attach required token features, enforce holder and transfer controls, and expose event and holder records. The institution still owns the payoff formula, underlying exposure, reserve or collateral evidence, cash settlement, accounting, investor notices, and legal approvals. The routing decision is whether the product should start from a DALP structured template, a fixed-income template, or the Configurable Asset starter. The page is not a pricing model, term-sheet generator, regulatory opinion, or reserve-attestation process. ## Business challenge [#business-challenge] Structured products combine token-lifecycle control with product economics that usually live in term sheets, calculation-agent processes, reference-asset data, and reserve or collateral workflows. A platform team needs one place to operate the token lifecycle without pretending that the token contract proves the entire product. DALP gives the programme a reusable issuance and servicing layer: * instrument templates for structured product starting points; * metadata fields for maturity, reference terms, collateral context, and product identifiers; * token features for maturity, redemption, fees, historical balances, or other configured behaviour where selected; * compliance modules for holder eligibility and transfer checks; * indexed token, holder, transaction, and event records for integration and reconciliation. The surrounding institution must still approve and operate the commercial terms. For an autocallable note, the observation logic and payoff determination belong to the product and calculation-agent process. For a principal-protected note, principal protection depends on the approved terms and funding arrangement. For an asset-backed token, DALP can record collateral-related controls and token actions, but the reserve, warehouse, trustee, custodian, or other external evidence source must prove the underlying backing. ## How DALP fits structured products [#how-dalp-fits-structured-products] DALP records and enforces the configured EVM lifecycle. The DALP token lifecycle layer does not replace the product term sheet, calculation agent, pricing source, market venue, cash rail, collateral agent, custody provider, legal register, or accounting ledger. ## Template routing [#template-routing] The structured family is useful when the product's economics do not fit a plain bond, equity, fund, deposit, stablecoin, or real-asset pattern. | Template | Selection condition | DALP handles | External owner | | ------------------------ | ------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------- | | Principal-Protected Note | The instrument needs a note-like token with maturity context and approved principal-protection terms. | Asset setup, holder controls, lifecycle actions, maturity or redemption features where configured, and event records. | Principal-protection economics, funding arrangement, payoff calculation, cash settlement, investor disclosures, and accounting. | | Autocallable Note | The instrument depends on observation dates, call conditions, or reference-asset performance outside the token workflow. | Token configuration, eligibility checks, lifecycle records, servicing actions, and integration evidence. | Observation logic, reference data, calculation-agent decisions, cash movement, notices, and dispute handling. | | Asset-Backed Token | The token represents an asset-backed programme where backing evidence must be reconciled outside the token contract. | Token issuance, transfer controls, collateral-related configuration where selected, holder and event history, and API records. | Asset pool eligibility, reserve or warehouse evidence, custodian or trustee process, valuation, insurance, and reporting. | If the product is simply debt with maturity and coupon-style servicing, start with [Corporate bonds](/docs/executive-overview/use-cases/corporate-bonds). If the product needs a blank or organisation-specific model, start with [Instrument templates](/docs/user-guides/asset-creation/instrument-templates) and duplicate the closest library template or create a template from scratch. ## Operating model [#operating-model] A structured product programme usually needs these decisions before launch. | Decision | DALP answer | External answer | | --------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | | Which token pattern should be issued? | Select a structured instrument template or a configurable template, then define the asset identity, metadata, required features, and compliance controls. | Approve the legal instrument, offering terms, payoff method, calculation role, and investor disclosures. | | Who may hold or transfer the token? | Configure roles, identity claims, compliance modules, and transfer controls before issuance and transfer. | Decide eligibility rules, jurisdictional restrictions, suitability checks, exception handling, and investor communication. | | How are payoff or reserve facts proven? | Use metadata, token actions, events, holder views, API reads, reports, and integration records as DALP evidence. | Operate the pricing source, observation process, reserve attestation, collateral inventory, custody records, and accounting evidence. | | How does settlement complete? | Execute token transfers, burns, mints, redemptions, or settlement workflows when the configured EVM rules allow them. | Operate fiat payments, bank-core posting, market venue activity, cash reconciliation, and final client statements. | ## Controls to confirm before implementation [#controls-to-confirm-before-implementation] * Confirm that the target network and token lifecycle are EVM-based. DALP is EVM-only. * Decide whether the product should use a structured template, a fixed-income template, or the Configurable Asset starter. * Define which metadata fields the Asset Designer must collect, which fields must be immutable, and which fields can follow the supported metadata update flow. * Select compliance modules and identity claims before relying on secondary transfers. * Assign an external owner for calculation-agent decisions, reserve evidence, custody, payment rails, accounting, and investor notices. * Connect external systems to DALP token, holder, transaction, event, webhook, and reporting records for reconciliation. ## Related pages [#related-pages] * [Use cases](/docs/executive-overview/use-cases) compares the full template taxonomy. * [Instrument templates](/docs/user-guides/asset-creation/instrument-templates) explains how templates define asset class, required features, and metadata fields. * [Tokenization modeling](/docs/architecture/concepts/tokenization-modeling) explains the split between asset class, token type, token features, and metadata. * [Compliance overview](/docs/architecture/security/identity-compliance) explains holder eligibility and transfer checks. * [Operational integration patterns](/docs/developer-guides/api-integration/operational-integration-patterns) explains how external systems consume DALP records.