Notifications - Tron Mainnet: contractAddress Returning a Symbol

On Tron Mainnet, notifications related to two fungible tokens (TRC-20) return the attribute contractAddress containing the token symbol (USDT_TRON or INRT_TRON) instead of the actual contract address.

This behaviour applies only two legacy tokens supported by Tatum and is expected.

Example notification:

{
  "currency": "TRON",
  "chain": "tron-mainnet",
  "amount": "0.006043",
  "address": "TS4kth6SCbZGPgwPktnaeJGRtsiqWnuxrf",
  "counterAddress": "TMszoJ2M2iUFnsmUAZM2GCAqG8MMSxAPko",
  "subscriptionType": "INCOMING_FUNGIBLE_TX",
  "blockNumber": 62139354,
  "txId": "6933f55def9223e51df7b0b3c4a4c5f73dda5c070a724a7797b0f5b03bf93ea4",
  "contractAddress": "USDT_TRON" // Returns symbol rather than "TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t"
}

Expected Behaviour (Legacy Tokens)

For the tokens listed below, Tatum notifications currently return the symbol in the contractAddress field instead of the blockchain token address.

ChainSymbol (currency)ContractAddressDigits
TRONINRT_TRONTX66VmiV1txm45vVLvcHYEqPXXLoREyAXm2
TRONUSDT_TRONTR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t6

📘

Note

These tokens only exist in Mainnet.


Workaround

This behaviour can be bypassed by using Notification Templates, which allow you to define a custom webhook payload.
When creating a template, you can select which fields are included in the notification, ensuring that the actual contract address is returned instead of the symbol.

For details, see: Create Notification Template