Skip to main content

Transfer Edge FAQ

How does Transatron work when I submit a transaction?​

Transatron provides a standard Tron node with JSON RPC and GRPC support. When you send a transaction via the Transatron node using /broadcasttransaction, here's what happens:

  1. Transatron catches the transaction
  2. Calculates the required resources (energy/bandwidth)
  3. Charges your company account
  4. Assigns resources to your transaction
  5. Ensures resources are delivered
  6. Broadcasts the transaction to the Tron network

What happens if I submit the same transaction to both Transatron and another node?​

If you submit a transaction to Transatron and later submit the same transaction to another node, you will still get the energy/bandwidth assigned by Transatron. However, the process of including the transaction into the Tron blockchain is not under Transatron's control.

This means there can be cases where the transaction arrives in the blockchain earlier than Transatron assigns resources, which will result in TRX burning or an OutOfEnergy issue.

It's not recommended to send transactions to different RPCs in parallel. Transatron itself broadcasts transactions via a set of nodes to guarantee delivery, so there's no need to use multiple nodes simultaneously.

Do you guarantee resources will always be available?​

Yes, we guarantee that resources will always be available. When Transatron runs out of resources, it automatically sends TRX from its own wallet to cover the required resources. Resource availability is our responsibility, not yours.

We recommend that customers keep some TRX balance in their wallet (up to 100 TRX on a hot wallet, 1-3 TRX on a rarely used wallet) as a safety buffer, but this is normally not used.

For example, when Transatron runs out of bandwidth, it might send 0.345 TRX to a wallet before the user transaction is broadcast to cover the customer's bandwidth needs.

How does pricing work when you run out of resources?​

We charge based on energy and bandwidth consumption, not for the TRX we spend when running out of resources. Our pricing is market-based, and we tend to keep it flat and change it rarely.

There are cases when TRX is used directly (such as for calldata or activating a new address in Tron), and in those cases, we charge for TRX at a 1:1 ratio.

What happens when my account balance is insufficient?​

When your balance is lower than required for a transaction, Transatron will bypass the transaction without providing resources, and TRX will be burned from your wallet to cover the fees.

What is the "reclaim" operation I see in logs?​

After a user transaction is completed (added to the blockchain), Transatron recovers the resources from the user address. This recovery process is called "reclaim."

Does Transatron batch transactions?​

Yes, sometimes Transatron batches transactions when they are sent consecutively. For example, it might process 3-5-20-50 transactions at once. In this case, there will be one Delegate operation, followed by multiple user transactions, then a Reclaim operation.

Does Transatron support special use cases like providing TRX for a calldata?​

Yes, Transatron can handle special cases. For example, we have a customer who integrated their wallet with LayerZero-based OFT USDT in Tron. LayerZero charges a few TRX as a fee sent within calldata.

Since they wanted to go completely TRX-free on accounts, we implemented a feature that analyzes calldata. If it contains up to 30 TRX, Transatron charges the user for TRX and tops up their account so it has enough TRX to cover the LayerZero bridging fee.

How do I monitor my account balance?​

It's crucial to monitor your customer account balance on Transatron regularly. You can check your balance using the methods described in our Accounts and Balances documentation. Check our Examples Repository for working code samples.

What headers should I use for API requests?​

You can use either of these headers for your API key:

  • TRANSATRON-API-KEY
  • TRON-PRO-API-KEY

Both are accepted by Transatron for compatibility purposes.

What happens if my instant payment transaction fails due to price changes?​

If the transaction fee changes between /triggersmartcontract and /broadcasttransaction calls (due to network conditions), and the change exceeds the 7% tolerance corridor, Transatron will return an INSTANT_PAYMENT_UNDERPRICED error code and will NOT broadcast the main transaction.

In this case, you should:

  1. Call /triggersmartcontract again to get updated fee estimates
  2. Create new payment and user transactions with the updated amounts
  3. Retry the broadcast process

This prevents transactions from being processed without proper fee coverage.

Do instant payments work with all TRC-20 tokens?​

Yes, instant payments work with all TRC-20 tokens and smart contracts. The payment mechanism is universal and doesn't depend on the specific token being transferred.

However, note that only TRX and USDT are accepted as payment currencies for instant payments.

What's the priority order for transaction fee payment?​

Transatron processes transaction fees in the following order:

  1. Instant payments: If an instant payment transaction is received, it takes priority
  2. Internal account balance: If no instant payment is detected, fees are charged from your RTRX/RUSDT balance
  3. TRX burning: If neither of the above options work, TRX is burned from your wallet

This means that even if you have RTRX/RUSDT balance, sending an instant payment will use the instant payment method instead.

What happens with insufficient funds for USDT instant payments?​

When using USDT instant payments, Transatron processes both the payment transaction and the main transaction as a batch. If there are insufficient USDT funds for the payment transaction, the system will return a NOT_ENOUGH_FUNDS error and will not broadcast either transaction.

It's recommended to check the user's USDT balance before initiating the instant payment flow to provide better user experience.

Why might my transaction hash not appear in the blockchain explorer?​

If Transatron returns a transaction hash but it's not visible in the blockchain explorer, this typically means:

  1. Payment transaction failed: The instant payment transaction didn't have sufficient funds or failed validation
  2. Network issues: There may be temporary issues with the underlying Tron nodes
  3. Transaction was rejected: The transaction didn't meet validation requirements and wasn't broadcast

Check the transatron.code field in the response for specific error details like INSTANT_PAYMENT_UNDERPRICED or NOT_ENOUGH_FUNDS.

What should I do if I need help or have questions?​

For support or to request features, reach out to: