Smart Contract Addresses

A 64-character hexadecimal representation of the address, used for low-level operations or technical scenarios requiring strict data formatting. Learn more about TON addressesExample:

0:906697a57af1cdb1bc39214b7049ae02b3c92a5b0c342ac61e0eb8bd9304b5f1

Features:

The prefix 0: indicates the network (0 for the mainnet).
Commonly used in smart contracts and API integrations.

This address is intended for standard TON transfers. If the transaction cannot be accepted (e.g., the wallet is not activated), the funds will be returned to the sender. Learn more about TON addressesExample:

EQCQZpelevHNsbw5IUtwSa4Cs8kqWww0KsYeDri9kwS18eCz

Features:

Typically used in user interfaces (wallets, applications).
Suitable for most transfer scenarios.

This address is used for transfers that must be completed without returning the funds. It is commonly applied in special cases, such as smart contracts, where refunds are not possible or desired. Learn more about TON addressesExample:

UQCQZpelevHNsbw5IUtwSa4Cs8kqWww0KsYeDri9kwS18b12

Features:

Used for deposits where it is critical that the transaction is completed without a refund.
It is recommended to avoid using this format for regular transfers.

Technical Guides

REST API

Technical Guides

REST API

Documentation Index