Coinvay’s TON integration verifies the native coin on the TON blockchain. Its current interface may label that option Gram, while the underlying network and API asset are TON. That display choice is not evidence that Toncoin has officially been renamed or that a separate Gram token is supported.
Explain the actual asset before payment
State that the customer must send the native TON coin on the TON mainnet route shown in checkout. Do not describe the option as every token in a TON wallet. Jettons, including stablecoins issued on TON, are separate token contracts and are outside this native-payment adapter.
For a community membership, the merchant can share an invoice link and let a buyer select the TON route. The buyer should verify the receiving address and exact native quantity, rather than searching a token list for any asset with a matching marketing name.
Respect TON-specific address behavior
TON addresses can have raw and user-friendly representations. Friendly formats carry additional information, including bounce-related and testnet flags. These formats should be handled by compatible wallet software rather than manually edited by a payer.
A merchant should test receipt at the intended wallet and preserve the address displayed by checkout. If a sending service requires extra instructions, confirm that its behavior is compatible with the payment request before using it. Do not add an arbitrary memo and assume the gateway uses it to reconcile the invoice.
Use recipient-side evidence when troubleshooting
TON’s message-based transaction flow can produce different sender-side and recipient-side transaction references. Coinvay’s manual verification expects the recipient-side transaction hash shown for the receiving account, not an unrelated hash copied from another stage of the transfer.
The verifier checks finalized evidence and the expected native amount. It does not automatically convert the receipt, enable jetton support or promise that a failed or bounced attempt is a completed payment. Staff should inspect the actual receiving transaction when an invoice remains pending.
Practical checklist
- Identify the network as TON and the asset as its native coin.
- Keep address flags intact when copying payment instructions.
- Use the recipient transaction reference for manual verification.
Common questions
Does Coinvay’s Gram label mean a different coin can pay?+
No. In the current implementation the label maps to the native TON asset. A separate token with a similar name is not interchangeable with that route.
Can USDT on TON pay this checkout?+
Not under the native TON quote. USDT jettons require their own supported token-verification flow. Use a configured USDT network elsewhere in checkout if the customer prefers USDT.
Sources and further reading
Primary references and Coinvay product documentation. Check the linked pages for current details.
AI-assisted drafting, published by Coinvay. Examples are illustrative. Read our editorial approach.