Skip to main content
After sending, look up the final result and details. The SDK exposes two lookup functions.

By body hash

Use the Base64 hash of the signed message body payload.

By reference

Use the reference returned by createTonPayTransfer.

Return shape

Use status to drive UI state and use reference, bodyBase64Hash, and txHash for reconciliation.

Response fields

string
required
Human-readable amount with decimals.
string
required
Amount in base units; nano for TON and jetton base units.
string
required
Sender wallet address.
string
required
Recipient wallet address.
string
required
Asset address. “TON” for coin or jetton master address.
string
required
Possible values:
  • pending – the transfer is created and awaits confirmation on the blockchain.
  • success – the transfer is completed successfully; the trace completes without errors.
  • error – the transfer fails; the trace completes with an error.
string
required
Tracking reference returned at creation time.
string
required
Base64 hash of the signed message body content (payload). Used for lookups.
string
required
Transaction hash assigned by the network.
string
required
Trace identifier for explorer.
string
Optional note shown to the payer while signing. Public on-chain; avoid confidential data and keep under 120 characters to reduce gas.
string
Optional note shown to the payee after receipt. Public on-chain; avoid confidential data and keep under 120 characters to reduce gas.