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 model | Template | Typical controls |
|---|---|---|
| Fiat-backed stablecoin | stablecoin | Mint authority, freeze authority, pausable, permanent delegate |
| Tokenized security or RWA | tokenized-security | Allowlist required, freeze authority, pausable, permanent delegate |
| Loyalty, rewards, or utility token | custom | Manually selected extensions |
| Non-standard asset | custom | Manually 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:
- Set Up Your Organization & Projects
- Set Up Wallets
- Manage API Keys
- Create a Token
- Deploy a Token
- Mint and Burn
- Basic payment — transfer tokens between wallets
- Allowlists — Token Access Control, required for
tokenized-security - Manage Token Settings — freeze, pause, seize for compliance workflows
Core API endpoints
| Method | Endpoint | Purpose |
|---|---|---|
GET | /v1/issuance/templates | List available token templates |
POST | /v1/issuance/tokens | Create a token definition |
POST | /v1/issuance/tokens/{tokenId}/deploy | Deploy to Solana |
POST | /v1/issuance/tokens/{tokenId}/mint | Mint new supply |
POST | /v1/issuance/tokens/{tokenId}/burn | Reduce supply |
POST | /v1/issuance/tokens/{tokenId}/allowlist | Add a Token Access Control entry |
POST | /v1/issuance/tokens/{tokenId}/freeze | Freeze an account |
POST | /v1/issuance/tokens/{tokenId}/pause | Pause all transfers |
POST | /v1/payments/transfers | Transfer 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.