On this page
The essentials
- Get the memo from the actual recipient’s deposit details.
- Network success does not guarantee credit without a required memo.
- A second transfer cannot edit the first transfer’s comment.
Address and memo have different jobs
The address determines where an on-chain transfer goes. A memo, tag or comment may help the receiving service identify which customer should be credited. A correct address therefore does not guarantee correct service-level credit. The GRAM coin can reach an address successfully without appearing in the intended account.
The recipient defines the memo requirement for the particular route. It is not automatically required because the network is TON, nor is it mandatory for every transfer. One service may use a shared address with comments; another may use a different accounting design.
Where the correct value comes from
Open the intended asset’s deposit page in your own receiving account and select TON. If an obligatory memo appears beside the address, copy it exactly. Preserve leading zeros, letters and capitalization where present; do not substitute your name or an order number without explicit instructions.
Do not use a memo from an article example, someone else’s screenshot or another user’s history. It may identify a different account. When receiving details through messages, verify them using a familiar channel, especially after an unexpected address or memo change.
When it can be empty
If the current deposit details do not require a memo, do not add a random comment “for safety.” Receiving into an ordinary personal self-custodial address usually does not need a service-account identifier. Transfers to a service or payments for a particular order need their own check.
For example, Walt’s current help says its deposits do not require a memo. That does not imply every custodial provider works without comments. Similarly, a previous transfer to a personal address without a memo says nothing about the next exchange deposit.
Example: a shared address
Imagine a service giving Oleg address A and memo 004217 in a hypothetical example. Marina receives the same address A but memo 006830. The blockchain routes both transfers to A; the different comments help the service allocate them. These illustrate the principle and are not real payment details.
If Oleg sends 4217 instead of 004217, he cannot assume the two values are equivalent. If he omits the comment, an explorer’s successful status does not solve identification. Compare both fields before sending; after a mistake, contact the receiving service.
If the wallet has no memo field
Do not send a memo-required transfer through a form that cannot include one. Check advanced options and the wallet’s official instructions first. A field may be called Comment, Message or Tag, but confirm its purpose rather than relying only on similar wording.
Do not append the memo to the address field or send it separately in Telegram expecting automatic matching. Payments with special details need a supported sending method. If none is available, ask the recipient for an alternative before moving funds.
If it has already been sent
Use an explorer to check the actual destination, amount and comment included in the operation. Save its hash and time, then contact the receiving service’s official support. Explain that the required memo is missing or incorrect and supply transfer details without secrets.
Do not try to repair the previous operation by making another transfer with the correct comment: that creates a new operation rather than editing the first. The service may request proof of sending and apply its own return or credit process. Availability, timing and cost are not guaranteed.
Check comments after autofill
A payment link or QR code can populate several fields at once. Check the address, amount, asset and comment after opening it; convenient autofill does not authenticate the recipient. If the preview truncates a value, find the full details before signing. Do not add spaces or explanations to an identifier requiring an exact match. Multiple orders with the same recipient may use separate payment details, so do not automatically reuse the previous comment without checking.
A comment is not a place for secrets
An ordinary blockchain-transfer comment can be public. Do not include recovery phrases, passwords, identity documents or detailed personal circumstances. Even when the interface resembles a private chat, operation details may be readable in an explorer.
Before confirmation, check the complete set: asset, TON, address, required memo, amount and costs. Stop if anything differs from the recipient’s instructions. A successful previous payment does not remove this brief check: another asset, new address or updated service design may change the requirements.
