Stablecoins are crypto assets designed to seek a stable reference value, commonly one unit of a currency such as the U.S. dollar. “Designed to” matters: a peg is a mechanism and objective, not a guarantee that every stablecoin will always trade exactly at its reference value.
How stablecoins differ
USDT, USDC and RLUSD are examples of issuer-backed stablecoins. They have their own issuers, terms, reserve disclosures, redemption arrangements, supported networks and legal or geographic limitations. A token symbol alone does not tell you all of those details.
Issuer-backed stablecoins
Typically seek to support a reference value through issuer-managed assets and redemption processes.
Crypto-backed stablecoins
May use crypto collateral and automated rules, creating different market and liquidation risks.
Algorithmic designs
May use incentives or algorithms rather than direct reserve backing, with distinct failure risks.
A stablecoin has more than one risk layer
The asset’s market price is only one consideration. Users should understand the issuer and reserve model, legal terms, redemption access, blockchain network, smart-contract controls, custody arrangement and the risk of sending the wrong token or chain.
- Read the issuer’s current official documentation and reserve information.
- Confirm the exact token contract and supported network before sending or receiving.
- Do not assume a token called “USDC” or “USDT” is the official asset without checking its contract or provider.
- Stablecoins can face depegging, issuer, liquidity, operational and policy risks.
Network selection is critical
The same stablecoin name may appear on more than one network. A receiving service may support only some networks. Before a transfer, confirm the asset, network, address format, fee requirements and any memo or tag instruction. Test transfers can reduce the cost of an avoidable mistake.
- An Ethereum-style address can appear on several compatible networks, which does not mean every destination supports every network.
- A transaction can be final even when the sender chose an unsupported deposit network.
- Keep enough native network asset for transaction fees where applicable.
Why CryptoRetail uses stablecoin references in the API
CryptoRetail’s developer API is priced in small stablecoin-denominated payments on supported networks. This does not mean CryptoRetail endorses a token or makes a claim about its safety; it simply provides a common unit for a micropayment amount.
Developer API documentation
Read the x402 API and MCP server documentation.
Crypto glossary
Clarify custody, keys, tokens and network fees.
Wallet safety guide
Review safe transaction basics.
A practical next step
Use the crypto glossary to clarify wallet and network terms, then read the mobile wallet safety guide before making a first transfer.