About Delayed Transactions

Delayed transactions are created by extending the expiration parameter beyond the standard 1-hour window. Instead of broadcasting immediately, Transatron stores these transactions in an internal buffer and processes them in batches closer to the expiration time. This batching reduces overall resource consumption and fees.

This approach is well suited for custody solutions that process large volumes of withdrawals or consolidation transactions where immediate confirmation is not critical. You can check the status of buffered transactions via GET Pending Transactions or trigger immediate processing with POST Flush Pending Transactions. For a full custody integration guide, see Sending Transactions for Custody Services.

Disabling delayed transactions per API key

Delayed buffering is controlled per API key. By default the setting is enabled — any transaction you broadcast with an extended expiration is buffered and processed in batches as described above.

If you want a key's transactions to always broadcast immediately — even when they carry a long expiration — turn the setting off. In the Transfer Edge Dashboard, open the API key, go to its Advanced Settings tab, and disable Delayed transactions.

When the setting is off for a key:

• Transactions broadcast to the TRON node immediately, regardless of their expiration.
• Nothing is held in the internal buffer, so there are no pending transactions to check via GET Pending Transactions and no Flush is needed via POST Flush Pending Transactions.

The setting only affects how transactions with a long expiration are handled; normal short-expiration transactions are unaffected either way.