TER Codes

These codes indicate that the transaction failed, but it could apply successfully in the future, usually if some other hypothetical transaction applies first. They have numerical values in the range of -99 to -1. The exact code for any given error is subject to change, so don't rely on it.

Caution: Transactions with ter codes are not applied to the current ledger and cannot cause any changes to the Xahau state. However, a transaction that provisionally failed may still succeed or fail with a different code after being automatically reapplied. For more information, see Finality of Results and Reliable Transaction Submission.





The account sending the transaction does not have enough XAH to pay the Fee specified in the transaction.


Used internally only. This code should never be returned.


The address sending the transaction is not funded in the ledger (yet).


The transaction would involve adding currency issued by an account with lsfRequireAuth enabled to a trust line that is not authorized. For example, you placed an offer to buy a currency you aren't authorized to hold.


Used internally only. This code should never be returned.


Used internally only. This code should never be returned.


The transaction requires that account sending it has a nonzero "owners count", so the transaction cannot succeed. For example, an account cannot enable the lsfRequireAuth flag if it has any trust lines or available offers.


The Sequence number of the current transaction is higher than the current sequence number of the account sending the transaction.


The transaction attempted to use a Ticket, but the specified TicketSequence number does not exist in the ledger. However, the Ticket could still be created by another transaction.


Unspecified retriable error.


The transaction met the load-scaled transaction cost but did not meet the open ledger requirement, so the transaction has been queued for a future ledger.


The transaction attempted to use a HookHash that doesn't exist on the ledger.

Last updated