Skip to main content

Sending Transactions via Transatron for Custody Services

Prerequisites​

  1. Register using TransatronBot and get your RPC URL and API Key. Don't forget to top-up your account.
  2. Use the Transatron node for all TRON operations, not just /broadcasttransaction.
  3. Secure your keys. Never expose them in client-side code or logs.

Recommendations for Custody Solutions​

Custody solutions typically manage two transaction types relative to the Hot Wallet: Deposits (incoming) and Withdrawals (outgoing).

For custodial flows, all transactions are usually sent from the server using the ADMIN API key, which ensures fees are covered by the internal company account.

Deposit Transactions​

Options include:

  1. Consolidation transactions
    Merchant wallet → Hot Wallet, sent via Transatron.
  2. Approve / TransferFrom schema
    • approve is normally sent from the Merchant address.
    • transferFrom is issued on behalf of the Hot Wallet → follow the Withdrawal options below.
      Both operations can be covered by Transatron.

Withdrawal Transactions​

Options include:

  1. Standard withdrawals
    Send transactions via Transatron.
  2. Delayed transactions
    Extend the transaction expiration parameter. Transatron collects these into a buffer and broadcasts them in batches, further reducing fees.
warning

Always monitor your internal company balance. If the balance reaches 0, transactions are bypassed to TRON directly and will burn TRX for fees.

Flow: Sending Transactions​

  1. Create the transaction.
  2. Estimate resources by calling /triggersmartcontract.
  3. Sign and broadcast the transaction via /broadcasttransaction.
  4. Receive the user transaction hash and monitor it as usual.

Flow: Sending Delayed Transactions​

info

Requires the Hot Wallet to be registered on Transatron before sending delayed transactions.

  1. Create the transaction.

  2. Estimate resources with /triggersmartcontract.

  3. Extend the expiration time, then sign.

  4. Broadcast via /broadcasttransaction.

  5. Transatron responds with:

    • PENDING status
    • Transaction hash

    The transaction will appear on-chain after the expiration time.

tip

You can:

What if the User Doesn’t Want an Instant Payment?​

Simply prepare, sign, and broadcast the transaction via Transatron without specifying a fee payment method.
In this case, Transatron bypasses fee coverage and forwards the transaction to TRON. The TRON blockchain will then charge fees normally (burning TRX or using staked resources).

Additional Information​

  1. Example flows: Transatron TronWeb Examples (GitHub)
  2. Detailed guide: Preparing and Broadcasting Transactions
  3. API reference: Extended RPC Calls — including Transatron JSON extensions in responses.