Is a TON transaction hash enough to prove a USD₮ payment?

No. The completed transaction must also match the allowlisted official USD₮ Jetton master, exact recipient, base-unit amount and any required invoice reference.

Can a screenshot prove that a TON/USD₮ invoice was paid?

No. Screenshots can be edited, can show a pending operation and do not independently authenticate the asset, recipient, amount or final transaction state.

Does Exact Receipt hold the payment or wallet keys?

No. Invoice funds go directly to the registered recipient address. Exact Receipt is watch-only and does not request seed phrases or private keys.

What payment rail does Exact Receipt automatically match today?

The production Telegram service automatically matches official USD₮ transfers on TON. Telegram wallet connections use TON Connect; eligible Exact Receipt digital services are sold for Telegram Stars.

How to verify a USD₮ payment on TON

Do not mark an invoice paid from a screenshot or transaction hash alone. Verify one completed transfer against the official USD₮ Jetton master, the exact recipient, the exact base-unit amount and the invoice reference.

Check one TON transaction · 250 Stars Use the five-check method

One public TON transaction and a concise receipt within one working day. Terms are shown before Telegram opens checkout.

What exactly must match?

All five conditions belong to the same payment intent. One failure keeps the invoice open or sends it to review.

Is it the official USD₮ Jetton?
Authenticate the token by its allowlisted Jetton master, not by the name, ticker or image. Anyone can deploy a look-alike token.
EQCxE6…2Id_sDs
Did the correct recipient receive it?
Resolve and verify the recipient’s Jetton wallet against the expected owner address. A transfer to a similar-looking or unrelated address does not count.
Exact address
Does the base-unit amount match?
Compare the integer amount using the token’s decimals. Do not rely on rounded explorer display text.
No tolerance
Does the invoice reference match?
When a request requires a reference, match the expected query or payload. A correct transfer without the required reference can remain ambiguous.
Replay-safe
Is the transfer completed?
Pending submission, a wallet success screen or an isolated message is not final evidence. Record the receipt only after the required completed chain event is observed.
Completed

Questions that prevent false receipts

Open each answer while inspecting a real public transaction. Never paste wallet secrets into an explorer, form or support chat.

Is a transaction hash enough?

No. A hash only locates public data. You still need to authenticate the asset and match recipient, amount, reference and completed state to the original request.

Can I trust the symbol “USD₮” in an explorer?

No. Names, symbols and images are metadata. Verify the Jetton master against an issuer or maintained allowlist, then derive or confirm the recipient Jetton wallet.

Why compare the amount in base units?

Interfaces may round decimal values. Matching the integer amount and declared decimals prevents an underpayment from looking equal after formatting.

Does a wallet “sent” screen prove receipt?

No. It proves only what that interface chose to display. The chain evidence must show the expected completed transfer, and the same event must not already belong to another invoice.

Does Exact Receipt hold funds?

No. The payer approves the transfer in their own TON Connect wallet and funds go directly to the registered recipient address. Exact Receipt holds no merchant invoice funds and requests no seed phrase or private key.

A manual review that fails closed

Write the expected values down before opening the transaction. Then compare public evidence field by field.

ExpectedInspectReject when

NetworkTON mainnet transactionWrong network or testnet

AssetAllowlisted USD₮ Jetton masterTicker-only or different master

RecipientDerived Jetton wallet and ownerOwner or wallet differs

AmountInteger base units and decimalsAny shortfall or rounding ambiguity

ReferenceRequired query or payloadMissing, changed or already consumed

StateCompleted transfer evidencePending, failed, bounced or incomplete

Manual checks are useful. Repeated checks should be consistent.

Exact Receipt fixes the expected fields before payment, watches the registered address and keeps open, pending and confirmed states separate. Ambiguous evidence does not silently become a receipt.

Watch-only
No wallet keys
Invoice funds held: 0

Buy transaction check · 250 Stars Start free monitoring trial

Primary technical sources

These references describe the issuer address and TON Jetton mechanics. Exact Receipt is independent and is not affiliated with or endorsed by the named projects.

TetherSupported protocols and official TON USD₮ address TON DocsJetton payment processing and wallet verification TEP-74Fungible token transfer and notification standard Exact ReceiptPublic verification model and limits

What exactly must match?

Is it the official USD₮ Jetton?

Did the correct recipient receive it?

Does the base-unit amount match?

Does the invoice reference match?

Is the transfer completed?

Questions that prevent false receipts

A manual review that fails closed

Manual checks are useful. Repeated checks should be consistent.

Primary technical sources