Tokenize an Asset

Map a real-world asset to the right SDP token model, authorities, and implementation flow.

Use this page when you want to issue a stablecoin, tokenized security, loyalty token, or any other asset through Solana Developer Platform. It walks you from business decision to the first API call.

Choose a token model

Pick the Tokenization Template that matches your asset's compliance and operational requirements:

Asset modelTemplateTypical controls
Fiat-backed stablecoinstablecoinMint authority, freeze authority, pausable, permanent delegate
Tokenized security or RWAtokenized-securityAllowlist required, freeze authority, pausable, permanent delegate
Loyalty, rewards, or utility tokencustomManually selected extensions
Non-standard assetcustomManually selected extensions

Custody wallets hold your token's authorities by default, so SDP can execute deploy, mint, and compliance actions without external signing.

Implementation sequence

Each step links to its own guide with UI and API instructions:

  1. Set Up Your Organization & Projects
  2. Set Up Wallets
  3. Manage API Keys
  4. Create a Token
  5. Deploy a Token
  6. Mint and Burn
  7. Basic payment — transfer tokens between wallets
  8. Allowlists — Token Access Control, required for tokenized-security
  9. Manage Token Settings — freeze, pause, seize for compliance workflows

Core API endpoints

MethodEndpointPurpose
GET/v1/issuance/templatesList available token templates
POST/v1/issuance/tokensCreate a token definition
POST/v1/issuance/tokens/{tokenId}/deployDeploy to Solana
POST/v1/issuance/tokens/{tokenId}/mintMint new supply
POST/v1/issuance/tokens/{tokenId}/burnReduce supply
POST/v1/issuance/tokens/{tokenId}/allowlistAdd a Token Access Control entry
POST/v1/issuance/tokens/{tokenId}/freezeFreeze an account
POST/v1/issuance/tokens/{tokenId}/pausePause all transfers
POST/v1/payments/transfersTransfer tokens

See the full schema in the Issuance API reference and Payments API reference.

Operational constraints

  • A token must be created before deployment, and deployed before minting or transfer.
  • If the token is paused, minting and transfer operations are unavailable until it is unpaused.
  • Freeze and unfreeze flows accept a holder wallet address; SDP derives the associated token account automatically.
  • SDP operations require the relevant authority on a custody wallet. If an authority has been rotated outside SDP, rotate it back to a controlled wallet before deploying, minting, or running compliance actions.

For AI agents

If you are driving SDP through an agent workflow, start from Documentation for AI. That page links the machine-readable SDP discovery files and keeps AI-facing guidance grounded in the supported public API surface.

Is this page helpful?